[jboss-dev-forums] [JBoss AS Development] - Re: Naming over Remoting 3

ALRubinger do-not-reply at jboss.com
Tue Nov 24 15:45:59 EST 2009


"ron.sigal" wrote : Are you ok with "ejb3" -> "invokable"? Do you still want it in repos/common?

Sure, I hadn't given it much thought.  I'd say let's keep it in the same repo for now so that we can "svn mv" without losing version history.

The groupId might change eventually too, who knows?  I'd say let's just keep the naming until we know the intent of the project IMO.

"ron.sigal" wrote : I'm curious why  org.jboss.ejb3.container.core.MapBasedInvocationContext is a non-public class (which requires the related tests to go in org.jboss.ejb3.container.core instead of org.jboss.test.ejb3.container.core), but the other classes in org.jboss.ejb3.container.core are public.

Because it didn't *need* to be public, so I scoped it down as small as possible. :)  By convention lately I've been doing this so that I can have tests in the same packages and get at package-private members.

S,
ALR

PS - Hehe, "package-private members".

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267399#4267399

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4267399



More information about the jboss-dev-forums mailing list