September 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: javaee5 signature compliance vs. backport portability

by heiko.braun＠jboss.com

Well, there is a few things to be considered: * The jax-ws 2.1 additions are not removed, the stack will still be able to consume it * They moved to a separate jar (JDK 6 endorsed requires it). That means client that rely on 2.1 API need update their class-path * It breaks compatibility for those client that rely on JAX-WS artifacts that exist in two versions, i.e. Service. * However this deals with WebServiceFeature and EndpointReference. I don't believe many people used it, since WebServiceFeature was non-functional. But yes, you are right. It breaks backwards compatibility in a few places. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089203#4089203 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089203

19 years

1
0
0 / 0

TBoD in Neuchatel

by Thomas Diesler

Folks, for the rest of this week I'll be in Neuchatel for TBoD. Email response will probably be slow because of this. cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

19 years

2
1
0 / 0

[Design of JBoss Web Services] - Re: Exception propagation for one way messaqges

by adinn

By way of comparison I'll add the following: glassfish swallows any SOAPFaultException thrown by the implementation of an @Oneway method and does not generate a client side exception CXF notifies the error by returning a 500 code error to the http client. This results in the JaxWS proxy throwing an exception View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089187#4089187 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089187

19 years

1
0
0 / 0

[Design of JBoss Web Services] - javaee5 signature compliance vs. backport portability

by thomas.diesler＠jboss.com

Heiko, we recently removed jaxws-2.1 related API and make that functionality proprietary. How does this play with backward compatibility? To my understanding, going back to jaxws-2.0 API may break clients generated with previous jbossws releases. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089185#4089185 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089185

19 years

1
0
0 / 0

[Design of JBoss Web Services] - Development IRC channel

by heiko.braun＠jboss.com

I've started a development IRC channel in order to give people a chance get in touch, remove barriers and evtl. contribute. orwell.freenode.net#jbossws Here is quick intro on IRC for those who havn't used it since the late 80's: http://www.irchelp.org/irchelp/irctutorial.html View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088695#4088695 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088695

19 years

1
0
0 / 0

Development IRC channel

by Heiko Braun

I've started a development IRC channel in order to give people a chance get in touch, remove barriers and evtl. contribute. orwell.freenode.net#jbossws Here is quick intro on IRC for those who havn't used it since the late 80's: http://www.irchelp.org/irchelp/irctutorial.html Right on, Heiko

19 years

1
0
0 / 0

increase font size for wiki code snipets

by Thomas Diesler

Heiko, could you please have a look at this? -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

19 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: Endpoint redeployment

by richard_opalka

To be more concrete problem is related to JAXWS endpoints only. In the case of JAX-RPC endpoints there's no problem, because webservices archive detections is based on webservices.xml file existence in classloader. Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088477#4088477 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088477

19 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: Endpoint redeployment

by richard_opalka

"thomas.diesler(a)jboss.com" wrote : Richard, you are probably aware that JBWS124TestCase already works for all jbossas versions, aren't you? In this case it works because JAXRPC war deployer hook checks whether there's the webservices.xml file. If yes it is recognized as webservices archive. In the case of JAX-RPC based webservices that provide webservices.xml there's no problem. In such case webservices.xml is inspected to look for webservices, and not web.xml (as in the case of JAXWS services) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088471#4088471 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088471

19 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: Endpoint redeployment

by thomas.diesler＠jboss.com

Yes anonymous wrote : | An endpoint deployment must survive a server crash. When the server comes up again, endpoints must be recognized as such. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088468#4088468 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088468

19 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev September 2007