Re: Oracle specific jdbc and J2EE application server
- From: "kimtiede@xxxxxxxxx" <kimtiede@xxxxxxxxx>
- Date: Fri, 13 May 2005 09:40:29 +0200
Hi Joe,
Thanks for your reply - great to have an answer in such detail :-)
Joe Weinstein wrote:
kimtiede@xxxxxxxxx wrote:
Hi. Oracle made the mistake of delivering their extra methods without providing
an Interface, so you have to cast to a concrete class to access the methods.
If they had defined OracleCallableStatement as an Interface, then wrappers could
also implement the Interface, and simply pass your calls back and forth to the
Oracle object.
Yeah - that's true... That would have been nice... Unfortunately our project is locked on IBM WS since the customer has experiences with this application server. As far as I can see the WS does not have the same workaround but I havent made a deep investigation. I think we will try to contact IBM and hear what they have to say.
Once again thanks for your answer!
Kim .
- Follow-Ups:
- Re: Oracle specific jdbc and J2EE application server
- From: Mark Matthews
- Re: Oracle specific jdbc and J2EE application server
- References:
- Oracle specific jdbc and J2EE application server
- From: kimtiede@xxxxxxxxx
- Re: Oracle specific jdbc and J2EE application server
- From: Joe Weinstein
- Oracle specific jdbc and J2EE application server
- Prev by Date: Re: Oracle specific jdbc and J2EE application server
- Next by Date: Re: Oracle specific jdbc and J2EE application server
- Previous by thread: Re: Oracle specific jdbc and J2EE application server
- Next by thread: Re: Oracle specific jdbc and J2EE application server
- Index(es):
Relevant Pages
|