The app client and web server injection will be moving over to an mc based generic core. The ejb3 javaURLContextFactory can't be used by default since its package is not in the jbossas jndi.properties config. Need to ask Carlo why he created it.

Adrian Brock wrote:

On Wed, 2008-04-16 at 13:42 +0300, Dimitris Andreadis wrote:

And a few more:

Now the goal is to drill into each of those and try to resolve them so *volunteers are needed*

------------------------------------------------------------
ejb3/core
   ./org/jboss/ejb3/naming/client/java/javaURLContextFactory.java
depends on org.jboss.jbossas:jboss-as-server
   org.jboss.corba.ORBFactory

------------------------------------------------------------
ejb3/core
   ./org/jboss/ejb3/naming/client/java/javaURLContextFactory.java
depends on org.jboss.jbossas:jboss-as-server
   org.jboss.naming.client.java.HandleDelegateFactory;


The appclient should be independent of the ejb3 project.
The appclient naming context should just be a reference
to a remote jndi context and some injection of singletons.

With the exception of creating handle delegate singleton
this has nothing to do with the ejbs.

It does reuse some of the same injection processing, but then
so does servlets.

So it is EJB3 trying to own something that should be more
generic.