None of this is related to the topic.
"bdecoste" wrote : The "magical plugin" is a stopgap until we are
thirdparty jars like everything else.
...and we are now. :) But the Plugin may also be used for EJB3 upgrades.
"anil.saldhana(a)jboss.com" wrote : Nobody is stopping you from making the ejb3
core code coming into AS as thirdparty.
As was the subject of about a month of AS Status calls, there were a series of barriers
preventing this. Bottom line is you do not have to run the Plugin now, just build AS per
usual.
"anil.saldhana(a)jboss.com" wrote : What I do not understand is why should the
interceptors (which as AS integration code) sit in the externalized project? Like Adrian
said, interceptors etc are integration code and should be in AS, tomcat or any other
container workspace.
Please stop hijacking my Thread.
"anil.saldhana(a)jboss.com" wrote : Additionally, the ejb3 tests that require AS,
should be in the AS workspace. The external project that houses the core ejb3 code should
just test ejb3 code with junit/JBossTest.
Please stop hijacking my Thread.
Dude, at some point we have to stop refactoring and actually release a compliant
implementation. I'm not disagreeing with your points, big picture, big picture. We
can always move tests around later.
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135044#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...