[jboss-dev] RE: Plan for next JBossAS 4.x releases

[Carlo de Wolf]

Easier said than done. Currently the ejb3 project is tightly coupled to
the AS. I would like to see an ejb3 module which is binary compatible
across multiple AS versions (4.2, 5.0, 5.2 and maybe 4.0.5). For names
sake call this one ejb3-core. For the different AS versions we would
have to build abstraction layers (Bill already has a lot in). The
components ejb3-core would depend on must be downwards compatible across
all AS versions (no more let's upgrade component x and shift
compatibility problems to ejb3).

I propose we move ejb3x to a separate project asap and make it a binary
dependency in all the branches. This one is simple and binary compatible
across all AS versions. It only depends on j2ee project. (Note: JavaEE 5
API changes are in j2ee.)

Next in trunk create ejb3-core and move as much as possible to there
while keeping dependencies limited and managed. Then create
ejb3-abstraction-layer-5.0. By then we should tackled the problem and we
move the stuff to projects.

Okay, Brock me.

Carlo

On Thu, 2006-11-02 at 09:51 -0600, Galder Zamarreno wrote:
> +1 on independent EJB3 module.
> 
> Galder Zamarreño
> Sr. Software Maintenance Engineer
> JBoss, a division of Red Hat
> 
> 
> -----Original Message-----
> From: Fernando Nasser [mailto:fnasser at redhat.com] 
> Sent: 02 November 2006 15:47
> To: Ivelin Ivanov
> Cc: Dimitris Andreadis; jboss-development at lists.jboss.org; jboss-as at redhat.com; Andy Miller; Scott M Stark; Sacha Labourey; Patrick McDonald; QA; Shaun Connolly; Ram Venkataraman; Support Team (not including Core Developers); Remy Maucherat; Mladen Turk
> Subject: Re: Plan for next JBossAS 4.x releases
> 
> Ivelin Ivanov wrote:
> > Thank you, Dimitris. The plan looks great.
> > 
> > Since 4.2 will be aligned with the release of the first JBoss
> > Enterprise Platform App Edition, which includes SEAM and EJB3, I would
> > suggest adding these major features to the roadmap early and begin
> > immediate discussion on scoping the amount of work required.
> > 
> 
> Also, due to the way updates are handled in RHEL systems, this will also 
> be the release where JBoss Portal wil run on.
> 
> One thing we need to do as soon as possible, like next week, is to make 
> sure the AS, SEAM and PORTAL teams agree on the versions of all 
> thirdpart dependencies, which we will be locked into for quite some time.
> 
> > Respectively, JBEP Web Edition will be a subset of App Edition, which
> > will also include SEAM, EJB3 and newer version of jgroups. A parallel
> > discussion would need to occur as soon as possible regarding the
> > organization of the source code structure and JIRA for these
> > dependencies.
> > 
> 
> We really need to have EJB3 as an external module as Dimitris suggests. 
>   With its own SVN source tree, etc.
> 
> 
> Regards to all,
> Fernando
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development