<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Agree, but the refactoring cannot be done until after the first jboss5
beta. The ejb3x move is a trivial one that could be done.<br>
<br>
Carlo de Wolf wrote:
<blockquote cite="mid1162552391.8271.126.camel@carlo-desktop"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="MS Exchange Server version 6.5.7638.1">
<title>Re: [jboss-dev] RE: Plan for next JBossAS 4.x releases</title>
<!-- Converted from text/plain format -->
<p><font size="2">Easier said than done. Currently the ejb3 project
is tightly coupled to<br>
the AS. I would like to see an ejb3 module which is binary compatible<br>
across multiple AS versions (4.2, 5.0, 5.2 and maybe 4.0.5). For names<br>
sake call this one ejb3-core. For the different AS versions we would<br>
have to build abstraction layers (Bill already has a lot in). The<br>
components ejb3-core would depend on must be downwards compatible across<br>
all AS versions (no more let's upgrade component x and shift<br>
compatibility problems to ejb3).<br>
<br>
I propose we move ejb3x to a separate project asap and make it a binary<br>
dependency in all the branches. This one is simple and binary compatible<br>
across all AS versions. It only depends on j2ee project. (Note: JavaEE 5<br>
API changes are in j2ee.)<br>
<br>
Next in trunk create ejb3-core and move as much as possible to there<br>
while keeping dependencies limited and managed. Then create<br>
ejb3-abstraction-layer-5.0. By then we should tackled the problem and we<br>
move the stuff to projects.<br>
<br>
Okay, Brock me.<br>
<br>
Carlo<br>
<br>
</font></p>
</blockquote>
<br>
</body>
</html>