-
1. Re: AS Components Bound to AS Release Cycle
adrian.brock Mar 20, 2008 3:31 PM (in response to alrubinger)If you depend upon a jbossas sub-project then you are doing it wrong.
Circular dependency anyone? :-)
Your dependency should be on the integration-spi (which should not change)
not implementation details.
But then again, the aspects project is an abortion anyway
I've been complaining about it for years :-(
The transaction aspect should be in the transaction project,
the security aspect in the security project, etc.....
Classic example of re-inventing the wheel or NIH. -
2. Re: AS Components Bound to AS Release Cycle
alrubinger Mar 20, 2008 3:40 PM (in response to alrubinger)"adrian@jboss.org" wrote:
If you depend upon a jbossas sub-project then you are doing it wrong. Circular dependency anyone? :-)
This is the pattern we'd laid out. We avoid circular dependency by:
( -> == "Depends on")
* EJB3 -> AS Components
* AS -> AS Components, EJB3
...where AS itself is just an Assembly of modules. No AS Components may depend on any AS Component Consumer (ie. EJB3)."adrian@jboss.org" wrote:
Your dependency should be on the integration-spi (which should not change) not implementation details.
Yes, I'd like to see more use of the integration project for well-defined SPIs between modules/projects, but for now it's one step at a time. Else we'll never release anything.
The goal is to keep untangling interdependent modules; I'd like to see the day when we have enough separation that the monolithic structure of AS can disintegrate."adrian@jboss.org" wrote:
But then again, the aspects project is an abortion anyway I've been complaining about it for years :-(
Was just an example, but you get the point. :)
S,
ALR -
3. Re: AS Components Bound to AS Release Cycle
alrubinger Mar 20, 2008 3:43 PM (in response to alrubinger)"ALRubinger" wrote:
I'd like to see the day when we have enough separation that the monolithic structure of AS can disintegrate.
I'll revise that. Either the monolithic structure can disintegrate, *OR* AS Components all have SPIs upon which consumers can depend, making it OK for AS Components to be tied to AS Release Cycle.
At the moment, we've got a hybrid that isn't going to work. What can be done?
S,
ALR -
4. Re: AS Components Bound to AS Release Cycle
starksm64 Mar 20, 2008 4:55 PM (in response to alrubinger)There should not be AS projects in the parent pom. Only spis and thirdparty dependencies. If it has to be in jboss-as-dependency-matrix due to ejb3, webservices, or other project integration dependencies, then the project either needs an spi added to integration, or broken out like naming was.
-
5. Re: AS Components Bound to AS Release Cycle
alrubinger Mar 20, 2008 11:40 PM (in response to alrubinger)Allright.
I'm going to move the AS Components back to jboss-as-parent (out of jboss-as-component-matrix), and that'll have to suffice for now while I switch back to EJB3.
A heads up that proper releases won't be possible until we tackle this.
S,
ALR -
6. Re: AS Components Bound to AS Release Cycle
kabirkhan Mar 25, 2008 7:55 AM (in response to alrubinger)"adrian@jboss.org" wrote:
I
But then again, the aspects project is an abortion anyway
I've been complaining about it for years :-(
The transaction aspect should be in the transaction project,
the security aspect in the security project, etc.....
+100