Hi all,

I was working on TomEE 9 and I came into an issue with our
RemoteInitialContextFactory
See issue https://issues.apache.org/jira/browse/TOMEE-3857

In essence, the test is running in a different order causing the test to
fail. The reason is that there is some kind of state in our Remote factory.

Java NamingManager keeps the instance in a cache per classloader which
means every time there is a new InitialContext, it's created with the same
configuration, even though the Hashtable with the configuration is
different.

For the moment, I flagged the test as @Ignore but wanted to gather some
thoughts before I start looking at how to fix it.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

Reply via email to