[Design of EJB 3.0] - Remaining EJB3 > AS Dependencies
by ALRubinger
As of this posting, we have:
$> mvn dependency:tree -Dincludes=org.jboss.jbossas
|
| [INFO] [dependency:tree]
| [INFO] org.jboss.ejb3:jboss-ejb3-core:jar:0.1.0-SNAPSHOT
| [INFO] +- org.jboss.jbossas:jboss-as-mbeans:jar:5.0.0-SNAPSHOT:compile
| [INFO] | \- org.jboss.jbossas:jboss-as-j2se:jar:5.0.0-SNAPSHOT:compile
| [INFO] +- org.jboss.jbossas:jboss-server-manager:jar:0.1.0.GA:test
| [INFO] +- org.jboss.jbossas:jboss-as-server:jar:5.0.0-SNAPSHOT:compile
| [INFO] \- org.jboss.jbossas:jboss-as-system-jmx:jar:5.0.0-SNAPSHOT:compile
| [INFO] +- org.jboss.jbossas:jboss-as-main:jar:5.0.0-SNAPSHOT:compile
| [INFO] +- org.jboss.jbossas:jboss-as-system:jar:5.0.0-SNAPSHOT:compile
| [INFO] | \- org.jboss.jbossas:jboss-as-bootstrap:jar:5.0.0-SNAPSHOT:compile
| [INFO] \- org.jboss.jbossas:jboss-as-jmx:jar:5.0.0-SNAPSHOT:compile
| [INFO] \- org.jboss.jbossas:jboss-as-j2se:test-jar:tests:5.0.0-SNAPSHOT:compile
We have some dependencies (ie, Timer Service invocations) going through the legacy JMX bus (and AS code); Carlo has identified this as a "will not fix" issue for CR1. How, then, are we working around this so we can remove the dependency?
I've started tonight to remove the dependency on "jboss-as-server", where most of the violations are in cases where we're relying on members defined by the EJB2 Container. In those cases, I might simply move the code into EJB3, since AS is allowed to depend on EJB3, but not the other way around.
S,
ALR
PS - "server-manager" may be ignored; it does not exist within the AS tree.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147431#4147431
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147431
16 years, 7 months
[Design of EJB 3.0] - EJB3 Artifact Assemblies
by ALRubinger
Under jbossas/trunk/ejb3/src/assembly are a series of Maven2 Assembly Configurations:
jboss-ejb3.xml
jboss-ejb3-client.xml
hibernate-client.xml
Looks like "jboss-ejb3-client" is duplicated from the config of same name located in EJB3 Core. EJB3 Core has no notion of "hibernate-client", and I imagine jboss-ejb3 is there to contain most org.jboss.ejb3 classes.
How do we want to handle unifying these with projects/trunk/ejb3? At the very least, jboss-ejb3-client is a duplicate; perhaps the other two are AS-specific?
First thought that comes to mind is a new artifact under EJB3, "assembly" to contain these. Then the dependency plugin can bring these in, unpack under "target", and let them be used by the assembly plugin to create custom artifacts.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147417#4147417
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147417
16 years, 7 months