[JBoss-dev] RE: JBAS-3272

[Heiko Braun]

Neither 1.0.2 nor 1.0.3 are setup for remoting 2.0.0.CR1.
This does require code changes that we scheduled for 1.0.4.
With these changes remoting 2.0 actually works, but for 1.0.3 we cannot
simply switch because jbossws 1.0.3 needs to be a drop-in replacement
for the latest AS GA release. That's still 4.0.4.GA. 

We planned to switch to remoting 2.0 with 1.0.4.DEV that's starting when
1.0.3 is released. 

I think we agreed that 4.0.5.CR1 will ship with 1.0.3.
But this would require JBAS-3272 to be scheduled for a subsequent
release.

Does this work for you guys?

/Heiko

-----Original Message-----
From: Tom Elrod 
Sent: Friday, August 25, 2006 4:38 PM
To: Dimitris Andreadis
Cc: Tom Elrod; Heiko Braun; Thomas Diesler; JBoss.org development list
Subject: Re: JBAS-3272

I don't think jbossws 1.0.2 will work with remoting 2.0.0.  So if 
jbossws 1.0.3 will not be in jbossas 4.0.5.CR1, then might as well as 
reassign JBAS-3272 to a later release.

The servlet-invoker.war is web deployment for the servlet invoker.  This

includes a servlet that gets deployed in web container to let it handle 
receiving http invocations and passing on to remoting server invoker 
(very similar to the invoker.war contained within http-invoker.sar).

Dimitris Andreadis wrote:
> Heiko, are we going to ship jboss 4.0.5.CR1 with jbossws 1.0.2? If so,
> we can't upgrade remoting to 2.0.0.CR1.
> http://jira.jboss.com/jira/browse/JBAS-3272
> 
> Or does jbossws 1.0.2 work with remoting 2.0.0.CR1?
> 
> Branch_4_0 builds currently against:
> 
>       <componentref name="jboss/jbossws" version="snapshot"/>
>       <componentref name="jboss/jbossws14" version="snapshot"/>
> 
> The other alternative is to wait for jbossws 1.0.3, but we are already
> late with the jboss 4.0.5.CR1 release.
> 
> PS
> Tom, what's this unpacked servlet-invoker.war directory in
> repository.jboss.com\jboss\remoting\2.0.0.CR1\lib ?
>