"wolfc" wrote : The only point I worry about is that it must not have a
dependency on AS trunk itself.
Def not. :)
I've committed a project skeleton, jboss-ejb3-as-int. For now it simply declares
dependencies on jboss-ejb3-core and jboss-ejb3-deployers so that AS doesn't bring in
deployers via core.
Looking forward the migration path is:
* Our deployers in AS to jboss-ejb3-deployers
* AS-specific configurations (ie *-jboss-beans.xml) and code to jboss-ejb3-as-int
* Stuff in the "ejb3" module in AS shouldn't depend on other AS code
* "ejb3" module of AS gets smaller and smaller, and we get to reuse the stuff
that's there elsewhere
* AS defines dependency on jboss-ejb3-as-int alone. I'm not sure how we can move out
the dependencies AS has on the "client" artifacts yet, or how those can get
brought in transitively as well?
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186298#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...