0 Replies Latest reply on Apr 29, 2008 3:15 AM by Andrew Rubinger

    Remaining EJB3 > AS Dependencies

    Andrew Rubinger Master

      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.


      PS - "server-manager" may be ignored; it does not exist within the AS tree.