11:54 a.m.
Additional items:
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
artifacts created.
4. We need the some insight into the metadata refactoring/repository
work Adrian is doing as this affects deployer refactoring as well as the
profile service.
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)
Ivelin
12:39 p.m.
New subject: Fwd: AS 5 Beta 2 Discussion
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.
I was thinking the main reason we didn't switch to using unified
invokers for 4.x was due to needing to update docs and training
materials (since config would be completely different). However, if
this is not an issue and would prefer to switch default to be unified
invoker for 4.2, the change to standardjboss.xml, jboss-service.xml, and
cluster-service.xml is simple (but still have the issue of where else
needs to be changed, such as client user tx, testsuite, jmx invoker, etc.).
1:11 p.m.
New subject: Fwd: AS 5 Beta 2 Discussion
Yes, its work to align the remoting uses. This has to be done for
jboss5, and ejb3 pulls this issue into 4.2. I don't see keeping the
legacy remoting layers as default as beneficial for 4.2.
Tom Elrod wrote:
> 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.
I was thinking the main reason we didn't switch to using unified
invokers for 4.x was due to needing to update docs and training
materials (since config would be completely different). However, if
this is not an issue and would prefer to switch default to be unified
invoker for 4.2, the change to standardjboss.xml, jboss-service.xml,
and cluster-service.xml is simple (but still have the issue of where
else needs to be changed, such as client user tx, testsuite, jmx
invoker, etc.).
4:04 p.m.
New subject: Fwd: AS 5 Beta 2 Discussion
I agree. In fact, we specifically created 4.2 for these types of
issues. With the inclusion of EJB 3 in 4.2 as fully supported
technology, we should make this as clean as possible.
Andy
On Tue, 2006-11-28 at 11:11 -0800, Scott M Stark wrote:
Yes, its work to align the remoting uses. This has to be done for
jboss5, and ejb3 pulls this issue into 4.2. I don't see keeping the
legacy remoting layers as default as beneficial for 4.2.
Tom Elrod wrote:
>> 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.
>
> I was thinking the main reason we didn't switch to using unified
> invokers for 4.x was due to needing to update docs and training
> materials (since config would be completely different). However, if
> this is not an issue and would prefer to switch default to be unified
> invoker for 4.2, the change to standardjboss.xml, jboss-service.xml,
> and cluster-service.xml is simple (but still have the issue of where
> else needs to be changed, such as client user tx, testsuite, jmx
> invoker, etc.).
Andrig (Andy) Miller
VP, Engineering
JBoss, a division of Red Hat
6372
days inactive
6373
days old
jboss-development@lists.jboss.org
3 comments
4 participants
participants (4)
-
Andrig T Miller -
Scott M Stark -
Scott M Stark -
Tom Elrod