RE: [Php-java-bridge-users] Problems with InitialNamingFactory

[<php...@li...>]

Hi,

I was able to reproduce this problem with our
classloader.

I will switch it off when the backend runs in a
servlet engine or a j2ee application server.

The whole concept of the dynamic classloader doesn't
work when the j2ee server uses two seperate
classloaders for the webapp and for the j2ee classes. 

The org.jnp.interfaces.NamingContextFactory is in the
jboss j2ee classpath, it is not visible to the webapp
classloader. Since the dynamic classloader only
delegates to its parent and doesn't have access to the
jboss j2ee classloader the code:

new Java("org.jnp.interfaces.NamingContextFactory")

always fails when the dynamic classloader is set as
the bridge thread context classloader.

The situation is different when the dynamic
classloader runs within our standalone container, so I
will not remove it entirely. But j2ee or servlet
environments have their own way to handle jar and
class files.

As a workaround please add a policy file which
disables the dynamic classloader, or use a commercial
AS which ships with a reasonable policy file. The Sun
J2EE AS 8.1 for example ships with a default policy
file which denies us to dynamically load classes, so
the dynamic classloader is switched off automatically.


Regards,
Jost Boekemeier





	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de