[jboss-dev-forums] [Design of EJB 3.0] - Re: jboss-ejb3-project

[ALRubinger]

Some more thoughts:

Naming

I like "org.jboss.ejb3:jboss-ejb3"

Remove the component artifacts from JBossAS

If we provide a unified assembly for all EJB3 projects, then we may provide "jboss-ejb3.jar" as one artifact into AS.  This provides the following benefits:

1) No more user confusion as to what version of the EJB3 project is in AS.  A check into the manifest will simply say "1.0.0".

2) Removes the half-upgraded problem.  Users won't be upgrading ejb3-core while neglecting to update ejb3-proxy or ejb3-common.

3) We can do away with the explicit dependencies upon the client classifier JARs:

    <version.org.jboss.ejb3>1.0.0</version.org.jboss.ejb3> < This one stays
  |     <version.org.jboss.ejb3.common.client>1.0.0</version.org.jboss.ejb3.common.client>
  |     <version.org.jboss.ejb3.core.client>1.0.0</version.org.jboss.ejb3.core.client>
  |     <version.org.jboss.ejb3.proxy.client>1.0.0</version.org.jboss.ejb3.proxy.client>
  |     <version.org.jboss.ejb3.proxy.clustered.client>1.0.0</version.org.jboss.ejb3.proxy.clustered.client>
  |     <version.org.jboss.ejb3.security.client>1.0.0</version.org.jboss.ejb3.security.client>

Refactoring Required

In order to implement this, each component must have a dedicated namespace, ie. "org.jboss.ejb3.core" that doesn't conflict anywhere else.  Otherwise there will be overwrites when we pack everything into one assembly.  Take for instance in ejb3-core:

http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/core/src/main/java/org/jboss/ejb3/proxy/

S,
ALR




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

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