These are common JNDI utility stuff that does not depend on the JNDI implementation details so it should be in common, say in a org.jboss.util.jndi package.
The org.jboss.naming package in server exists because the jnp implementation of JNDI existed standalone prior to jboss. In 4.0 this will move to the naming module and the org.jnp package will be moved to org.jboss.naming. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: "jboss-dev" <[EMAIL PROTECTED]> Sent: Saturday, November 23, 2002 7:50 PM Subject: [JBoss-dev] Maybe NonserializableFactory could be in a better package... > I'd like to use org.jboss.naming.NonSerializableFactory in the transaction > module. However, it is currently in the server module, built after the tx > module. I'd like to move it. Where is the best place? > > common -- seems good, is it OK to have jndi utilities there since we can > run without jndi? > > naming -- also seems good, I don't really understand why there is a naming > dir in server. > > system -- seems unrelated to me. > > > Comments? > > I imagine moving at least the naming.Util class at the same time would be > advisable. > > thanks > david jencks ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
