August 2007 - jbossws-dev - Jboss List Archives

by Thomas Diesler

If stuff is ready can be seen in the roadmap. http://jira.jboss.org/jira/browse/JBWS?report=com.atlassian.jira.plugin.s... To answer your question more precisely: 2.1.0.GA has been postponed because we don't have a CXF release that passes our minimal set of required jaxws tests. We might do a CR1 in the near future. cheers -thomas On Mon, 2007-08-06 at 13:21 +0530, S.Satyamoorthy wrote: > Thomas, > Is the JBoss WS 2.1.0 GA ready? (as you had mentioned Aug 1st as > expected date). > Also, I need some help to position and present JBoss WS to a big TELCO > in APAC. The call is at 4:30 PM Wednesday Singapore time. Can one of the > WS core developers please volunteer to be on a conf call and help answer > customer queries? Please? > Thanks, > Satya -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 5 months

1
0
0 / 0

AS4x branch to install jbossws

by Thomas Diesler

Hi Dimitris, what is the correct AS4 branch to install jbossws-2.0.1? Is Branch_4_4 still the one? cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - EJB3 SPI for WS

by thomas.diesler＠jboss.com

Hi Carlo, please pull in | https://svn.jboss.org/repos/jbossws/container | there you find the integration layers for AS40, AS42, AS50 This code will eventually end up in the AS code base or the respective projects. For example the EJB3 invokers should be part of the EJB project and only have a dependency on the JBossWS SPI. It should be transparent to the invoker what stack there is deplyed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071148#4071148 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071148

17 years, 5 months

1
0
0 / 0

Re: EJB 3 SPI for WS

by Thomas Diesler

Hi Carlo, http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4071148#4071148 please pull in https://svn.jboss.org/repos/jbossws/container there you find the integration layers for AS40, AS42, AS50 This code will eventually end up in the AS code base or the respective projects. For example the EJB3 invokers should be part of the EJB project and only have a dependency on the JBossWS SPI. It should be transparent to the invoker what stack there is deplyed. On Thu, 2007-08-02 at 10:43 +0200, Carlo de Wolf wrote: > Thomas, > > What does WS need of EJB 3 in terms of SPI? > I know you use SessionContainer directly. Can we define an interface for > that? Anything else? > > Carlo > -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - JBossWS without EJB3 support

by thomas.diesler＠jboss.com

in jbossws.sar/META-INF/jboss-services.xml you comment out |  | in jbossws.sar/jbossws.beans/META-INF/jboss-services.xml you comment out | <bean name="WSApplicationMetaDataAdapterEJB3" ... --> | <bean name="WSSecurityHandlerEJB3" ... --> | <bean name="WSDeployerHook_JAXWS_EJB3" ... --> | basically everything ending with 'EJB3' I tried it out on jbossws-4.2.1.GA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071091#4071091 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071091

17 years, 5 months

1
0
0 / 0

JBossWS with no EJB3 support

by Thomas Diesler

Hi Mark, http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4071091#4071091 in jbossws.sar/META-INF/jboss-services.xml you comment out  in jbossws.sar/jbossws.beans/META-INF/jboss-services.xml you comment out <bean name="WSApplicationMetaDataAdapterEJB3" ... --> <bean name="WSSecurityHandlerEJB3" ... --> <bean name="WSDeployerHook_JAXWS_EJB3" ... --> basically everything ending with 'EJB3' I tried it out on jbossws-4.2.1.GA cheers -thomas On Fri, 2007-08-03 at 09:49 +0100, Mark Little wrote: > Thomas, a while back we discussed the apparent need to drag in EJB3 > when installing JBossWS. You said it wasn't strictly necessary. Is > that still the case? Can you remind me how to install JBossWS without > needing EJB3? > > > Thanks, > > > Mark. > > ---- > > > Mark Little > mlittle(a)redhat.com > > > JBoss, a Division of Red Hat > Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod > Street, Windsor, Berkshire, > SI4 1TE, United Kingdom. > Registered in UK and Wales under Company Registration No. 3798903 > Directors: Michael Cunningham (USA), Charlie Peters (USA) and David > Owens (Ireland) > > > > > > > > -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS project structure has changed

by thomas.diesler＠jboss.com

I recommend you checkout the top level directory non-recursive | foo> svn co -N https://svn.jboss.org/repos/jbossws | foo> cd jbossws | jbossws> svn up stack | This will allow you to run 'svn status' at the top level, showing the change set in all subprojects View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070716#4070716 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070716

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS project structure has changed

by thomas.diesler＠jboss.com

Legacy branches and tags have been moved to | https://svn.jboss.org/repos/jbossws/legacy | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070711#4070711 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070711

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS project structure has changed

by thomas.diesler＠jboss.com

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - JBossWS project structure has changed

by thomas.diesler＠jboss.com

The JBossWS project structure has changed | jbossws | + spi | + common | + framework | + container | + jboss40 | + jboss42 | + jboss50 | + stack | + native | + metro | + cxf | Each project defines binary dependencies only, source dependencies have been removed. Most of the time you will want to checkout a single stack and do your work there. You will not have to checkout the dependent projects unless you need to fix integration issues. cheers -thomas View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070640#4070640 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070640

17 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev August 2007