1. Synchronization between jbossas5, jbossas4.2. Primarily this is a
function of ejb3 support and what refactoring we need to do to support
ejb3 effectively on both platforms.
2. A related issue is alignment on jboss-remoting transports. There was
a jira issue to make the pooled invoker the default. The real question
is why don't we move to the unified invoker based on remoting to align
the transports between 4.2/5/ejb3.
3. Dependencies on jbossas artifacts. As project are split out from the
jbossas codebase, there are dependencies on jbossas integration points
that have not been well defined. These need to be defined and proper
4. We need the some insight into the metadata refactoring/repository
work Adrian is doing as this affects deployer refactoring as well as the
Ivelin Ivanov wrote:
> Andy put together an Initial list of requirements for AS 5 Beta 5.
> Please add on to it.
> Dimitris is tracking the list in JIRA. We will review it on Friday
> after the cts call.
> Here is what is needed for the Beta 2 Discussion:
> - Beta Releases of JBoss Messaging 1.2,
> - JBoss Cache 2.0.0, and JGroups 2.5 (Ovidiu, Manik, Bela)
> - ProfileService implementation with agreed upon management API for
> JON (Scott and Charles)
> - Refactoring of deployers based on what was learned from Beta 1
> - Final release of MC 2.0.0 (or beta, but I'm not sure)