"ALRubinger" wrote :
| However, we still have the standing question creeping up post GA - how will the Plugin
releases work? It'd be great to have only one Plugin version per EJB3 release, and
let it intelligently patch any AS after a certain cutoff (say, CR1).
|
| This way I can also tie the EJB3 Plugin into one of my Maven Plugins for AS
Installation and make upgrades to the user completely transparent.
| ALR
We've been through this discussion many times before. See for example
my recent discussion with Thomas Diesler in the webservices forum.
The short answer to your question (on the errors above),
is that you shouldn't be writing the deployers
in the ejb3 plugin project(s).
Instead the deployers should be in JBossAS and they should delegate to
a stable spi within EJB3
In fact, that spi (the ejb3 integration api) should be in the jboss-integration project
where you can't change it on a whim. :-)
The deployers themselves should be doing little more than
manipulating metadata which then gets registered as a "service" in the
Microcontainer.
Those services should then talk to an "EJB3 Service" from the deploy directory.
Again see recent discussion in Tomcat forum about how the Tomcat
deployers were wrong.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134994#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...