[jboss-dev] How can a project run in both AS 4.2.0 and AS 5.0?

[Thomas Diesler]

On Thu, 2007-07-19 at 18:53 -0400, Jason T. Greene wrote:
> +100 All integration code should live in AS. Otherwise it becomes nearly 
> impossible to make large changes to AS, since such integration modules 
> rely on internal implementation details. Not to mention it would be a 
> royal pain to track down and fix each component, since they would be in 
> separate repositories.

Yes, this is certainly the right approach. We must however not forget
about the plugability aspect of the integration code. i.e. it must be
possible to fix a bug in AS integration without replacing jboss.jar

Project X should define a stable SPI. Implementations of that SPI should
live in the projects that X has a dependency on.

> 
> Adrian wrote:
> > On Thu, 2007-07-19 at 17:48 +0300, Dimitris Andreadis wrote:
> >> The real issue is to have as much as possible a single codebase. JBossWS uses a common 
> >> "core" and different integration layers depending on the runtime (as40, as42, as50).
> > 
> > That is the wrong approach. It's not JBossWS's job to define how
> > webservices integrate into JBossAS.
> > 
> > JBossAS should define a stable integration point, test it and JBossWS
> > should implement it.
> > 
> > I'm currently going through the process of fixing AOP
> > (which takes the same wrong approach)
> > to use the new jboss-classloading-spi instead of
> > "deep diving" into the UnifiedClassLoader.
> > 
> > For legacy reasons, it's difficult to fix the problem in 4.x
> > (we can't change the api now it is released)
> > but we can in JBoss5 and we can come up with something
> > that is;
> > 1) supportable for a long time.
> > 2) makes it easier to understand what work
> > needs to be done to integrate a project with
> > other "platforms" - e.g. running JBoss Messaging inside Tomcat,
> > Eclipse or a unit test, etc.
> > 
> > Oh no Tim! More platforms/versions to test. :-)
> 
> 
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx