January 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: JBWS-1260 - Sequence containing 2 elements

by jason.greene＠jboss.com

Right, a simple type is not a valid wrapper type, so if it is used only the bare parameter style can be used. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999045#3999045 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999045

17 years, 4 months

1
0
0 / 0

jbossws-1.2.0 release

by Thomas Diesler

Folks, next Thursday (18-Feb-2007) is jbossws-1.2.0 code freeze. Please complete the open issues that are assigned to you by that time. If for some reason you cannot meet the target, please speak up so we can take appropriate action. Attached is a snapshot of open issues. cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 4 months

2
2
0 / 0

Re: EJBTHREE-757: getMessageContext not yet implemented

by Thomas Diesler

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Support JAXWS on EJB2.1

by jason.greene＠jboss.com

I don't think anyone is using it, or at least I have never seen a question relating to it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999022#3999022 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999022

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Using jbossws/trunk for jboss-5.0, jboss-4.2, jboss-4.0.

by darran.lofthouse＠jboss.com

Yes that fixes it, thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998990#3998990 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998990

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Using jbossws/trunk for jboss-5.0, jboss-4.2, jboss-4.0.

by thomas.diesler＠jboss.com

Yes, jbossall-client.jar is the culprit. Please try this |  | <path id="test.client.classpath"> | <path refid="jbossws.client.classpath"/> | <pathelement location="${jboss.client}/jbossall-client.jar"/> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998982#3998982 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998982

17 years, 4 months

1
0
0 / 0

Re: EJBTHREE-757: getMessageContext not yet implemented

by Thomas Diesler

Thanks, I'll take care of it. http://jira.jboss.org/jira/browse/JBWS-1443 cheers -thomas Carlo de Wolf wrote: > Hi Thomas, > > We still have some unimplemented stuff in EJB3: > http://jira.jboss.org/jira/browse/EJBTHREE-757 > > Basically it's the getMessageContext that's not implemented for session > beans. > > Who can take a look at it? > > Would it be enough to create a SOAPMessageContextJAXRPC and setMessage > on it? > > Carlo > > -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Using jbossws/trunk for jboss-5.0, jboss-4.2, jboss-4.0.

by darran.lofthouse＠jboss.com

I can get JBossWS to deploy to JBoss 5 and JBoss 4.2 and run the testsuite with a high test success rate but for JBoss 4.0 I am getting a lot of failures. I am using the JBoss 4.0.5 release and I am getting this error logged for a lot of the tests: - anonymous wrote : 2007-01-08 12:13:21,026 ERROR [org.jboss.ws.core.soap.SOAPMessageUnMarshaller:80] Cannot unmarshall SOAPMessage | javax.xml.soap.SOAPException: Cannot find SOAPFactory implementation | at javax.xml.soap.SOAPFactory.newInstance(SOAPFactory.java:96) | at org.jboss.ws.core.soap.SOAPFactoryImpl.createElement(SOAPFactoryImpl.java:113) | at org.jboss.ws.core.soap.SAAJPayloadBuilderDOM.build(SAAJPayloadBuilderDOM.java:86) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessageInternal(MessageFactoryImpl.java:254) | at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:75) | at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:175) | at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:81) | at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) | at org.jboss.remoting.Client.invoke(Client.java:525) | at org.jboss.remoting.Client.invoke(Client.java:488) It looks like an old version of 'javax.xml.soap.SOAPFactory' is being used from the JBoss jars instead of the latest version from JBossWS. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998960#3998960 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998960

17 years, 4 months

1
0
0 / 0

JBossWS cruise control

by Thomas Diesler

Hi Prabhat, the jbossws build has changed and we are now using a single codebase across jbossas versions. For details please see http://www.jboss.org/index.html?module=bb&op=viewtopic&t=98635 Could you please change the jbossws cruise control projects according to this matrix jbossws jbossas jdk ---------------------------------- trunk trunk jdk1.5 trunk Branch_4_2 jdk1.5 trunk Branch_4_0 jdk1.5 trunk Branch_4_0 jdk1.4 http://jira.jboss.org/jira/browse/JBWS-1442 cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 4 months

1
0
0 / 0

Re: Help needed

by Thomas Diesler

17 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev January 2007