-
15. Re: What Versions of AS5 Will EJB3 Plugin Support?
Anil, if you're concerned about location of code and separation of concerns, please start another thread and I'm sure someone with more architectural influence will weigh in.
Adrian, when did I infer that EJB3 will define AS security? Or that I'd be moving the deployers? All I want to know is what is expected of the Plugin looking forward so that I can account for it now.
S,
ALR -
16. Re: What Versions of AS5 Will EJB3 Plugin Support?
The "magical plugin" is a stopgap until we are thirdparty jars like everything else.
-
17. Re: What Versions of AS5 Will EJB3 Plugin Support?
"bdecoste" wrote:
The "magical plugin" is a stopgap until we are thirdparty jars like everything else.
Nobody is stopping you from making the ejb3 core code coming into AS as thirdparty.
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.
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. -
18. Re: What Versions of AS5 Will EJB3 Plugin Support?
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@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@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@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 -
19. Re: What Versions of AS5 Will EJB3 Plugin Support?
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135094
This is the thread I created with my suggestions. If I am making thoughtless comments, do correct me, please. -
20. Re: What Versions of AS5 Will EJB3 Plugin Support?
We are only going to support AS GA versions (starting with AS 5.0).
Beta4 support is nice because it allows us to release right now, but that is not a priority. It also visualized regression which was not due to EJB 3 changes. Anyway we're past that station.
The fact that we're coding against a moving target was already by Dimitris: there is no AS - EJB 3 SPI. (We're now in the same position as EJB 3 - WS SPI.)
I beg to differ with Adrian, that this is not an exercise of moving some interfaces + annotations to integration. This should be a component contract with which the AS EJB 3 deployers can boot up EJB 3 containers.
I don't think we'll be addressing this before RC1, and yes, it'll bite back some time down the line.
The one thing we do lose is our ability to code against a stable AS.