At 11:46 PM 5/21/2004, Raymond DeCampo wrote:
Ceki G�lc� wrote:
Other errors included the usage of the javax.rmi.PortableRemoteObject class which is not part of JDK 1.2. This problem affects only the o.a.l.db.JNDIConnectionSource class.
Ceki,
The PortableRemoteObject class should be available in J2EE distributions or RMI/JNDI distributions. We can include one of these for compilation purposes. It should not be necessary to include it in the binary distribution, as anyone using the JNDIConnectionSource class would get this class from their JNDI provider libraries.
Please let me know if you need any assistance on this issue.
Thank you very much for responding to this. I was hoping you would comment.
Do you have any example of where the current JNDI lookup for the datasource would not succeed without a call to PortableRemoteObject.narrow? Note that the JMSAppender also uses JNDI lookup without ever calling PortableRemoteObject.narrow ant this was never reported as a problem by our users.
I am missing something?
Ceki,
Using PortableRemoteObject.narrow() is considered the best practice to ensure interoperability with CORBA and RMI over IIOP.
Most of the references I've found so far focus on the need to use it in EJB clients.
At this point I'm not certain if it is necessary in this case (where EJBs are not involved). The most likely usage scenario for this class will be a J2EE component that is in the same JVM as the JNDI provider. It should not be needed in that case. It may be needed when the client is external to the JNDI provider although I suspect that it is probably not needed when everybody is in a Java environment.
Perhaps the simplest solution will be to remove the use of PortableRemoteObject.narrow() and make a note in the documentation that the class does not use PortableRemoteObject.narrow() when casting the object from JNDI. Then we can deal with issues if they come up.
Ray
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
