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?

Thanks,
Ray

-- Ceki G�lc�

For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to