Mike, thanks for the Q. After the JBoss4.0 release this month, there will be no point in backporting JBossWS into 3.2 branch. 4.0 will be a J2EE1.4 compliant App Server. All your 3.2 apps should run without modifications on the 4.0 server.
JBossWS is a J2EE1.4 compliant web services subsystem.
Thanks for the answer. Was hoping to get WS in 3.2, because we have a dozen or so apps in prod on a 3.2.2 cluster, incl. WebServices (currently on jboss-net). Don't have time for the logistics of a 4.0 upgrade right now, so I was looking for a way to to WS4EE before then.
Anil is right, there will be no backporting of the JBossWS subsystem to the jboss-3.2 brach. Main reason is that ws4ee relies on j2ee-1.4 features which are and will not be supported in jboss-3.2.x.
> All your 3.2 apps should run without modifications on the 4.0 server.
Maybe they should, but they absolutely do not.
Do you have WS related porting issues to JBoss.NET in jboss-4.0? Going from JBoss.NET to JBossWS is probably the last step in your migration efford.