November 2008 - jbossws-users - Jboss List Archives

by aalissa

thanks alot richard i don't have poreferred stack so i will try metro thanks again View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190384#4190384 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190384

16 years, 3 months

1
0
0 / 0

[JBossWS] - Help us learn how Feature Requests R gathered

by plaurentphd

My name is Paula Laurent. I am a Computer Science PhD student at DePaul University conducting research on soliciting and prioritizing requirements. The goal of this research is to find out about the current requirements processes used in Open Source projects. Weâre requesting 20 minutes of your time to complete an online survey which can be accessed at http://www.surveymonkey.com/s.aspx?sm=973NJ9LtxAuHs224fvrbBg_3d_3d Thank you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190344#4190344 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190344

16 years, 3 months

1
0
0 / 0

[JBossWS] - Re: Logging SOAP Messages

by brintoul

"brintoul" wrote : | I've tried setting the category org.jboss.ws.core.MessageTrace to a priority of "TRACE" in jboss-log4j.xml but I'm still not seeing the outgoing/incoming SOAP messages. | | I'm communicating with a web service using SSL - does this change anything? I'm using jbossws-native-3.0.2.GA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190283#4190283 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190283

16 years, 3 months

1
0
0 / 0

[JBossWS] - Logging SOAP Messages

by brintoul

I've tried setting the category org.jboss.ws.core.MessageTrace to a priority of "TRACE" in jboss-log4j.xml but I'm still not seeing the outgoing/incoming SOAP messages. I'm communicating with a web service using SSL - does this change anything? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190282#4190282 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190282

16 years, 3 months

1
0
0 / 0

[JBossWS] - Re: replacement of REPLACE_WITH_ACTUAL_URL when using annota

by will.tatam

nobody from the JBossWS team going to comment ? @bschmoll1 - manage to fix your port -1 issue ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190231#4190231 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190231

16 years, 3 months

1
0
0 / 0

[JBossWS] - Re: Problem consuming .net webservice with jbossws-3.0.1-nat

by jeckles933

its this your working message has Content-Length: bla broken one: Transfer-Encoding: chunked looks like not everybody supports chunked, now - how do we turn of chunking?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190218#4190218 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190218

16 years, 3 months

1
0
0 / 0

[JBossWS] - Problem in interpreting SOAP message on JBoss EAP 4.3.0

by eontech

Hi All, We are using XFire to invoke webservices. We were using Jboss AS 4.0.5 earlier to deploy our webservices. This combination was working fine. Now we have upgraded to JBossEAP 4.3.0. When we generate webservice clients via XFire to test webservices deployed on EAP, the parameters passed are null. If we generate clients from wsconsume (Jboss utility), it works fine. It works well with .NET clients as well. I am wondering what has changed in EAP which is not interpreting XFire request correctly. Following are the SOAP messages from various clients, all work well in JBoss AS 4.0.4 but on EAP with XFire, parameters become null. <=====================Jboss Client====================> | | <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'> | <env:Header/> | <env:Body> | <ns1:callwebsvcService xmlns:ns1='http://ws.websvc.services.abhishek.com/standard/head/websvctest'> | <token>myvalue</token> | <holdingId>101</holdingId> | </ns1:callwebsvcService> | </env:Body> | </env:Envelope> | <=====================.NET Client====================> | | <soap:Envelope xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'> | <soap:Body> | <callwebsvcService xmlns='http://ws.websvc.services.abhishek.com/standard/head/websvctest'> | <token xmlns=''>test</token> | <holdingId xmlns=''>1</holdingId> | </callwebsvcService> | </soap:Body> | </soap:Envelope> | <=====================XFIRE Client===================> | | <soap:Envelope xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'> | <soap:Body> | <ns1:callwebsvcService xmlns:ns1='http://ws.websvc.services.abhishek.com/standard/head/websvctest'> | <ns1:token>XFire</ns1:token> | <ns1:holdingId>123</ns1:holdingId> | </ns1:callwebsvcService> | </soap:Body> | </soap:Envelope> | <====================================================> Following is the wsdl contents | <?xml version="1.0" encoding="UTF-8"?> | <definitions name="websvcCallService" targetNamespace="http://ws.websvc.services.abhishek.com/standard/head/websvctest" | xmlns:tns="http://ws.websvc.services.abhishek.com/standard/head/websvctest" xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/"> | <types> | <xs:schema targetNamespace="http://ws.websvc.services.abhishek.com/standard/head/websvctest" version="1.0" | xmlns:tns="http://ws.websvc.services.abhishek.com/standard/head/websvctest" xmlns:xs="http://www.w3.org/2001/XMLSchema"> | <xs:element name="callwebsvcService" type="tns:callwebsvcService"/> | <xs:element name="callwebsvcServiceResponse" type="tns:callwebsvcServiceResponse"/> | <xs:complexType name="callwebsvcService"> | <xs:sequence> | <xs:element minOccurs="0" name="token" type="xs:string"/> | <xs:element name="holdingId" type="xs:int"/> | </xs:sequence> | </xs:complexType> | <xs:complexType name="callwebsvcServiceResponse"> | <xs:sequence> | <xs:element minOccurs="0" name="callwebsvcServiceResponse" type="xs:string"/> | </xs:sequence> | </xs:complexType> | </xs:schema> | </types> | <message name="websvcCallService_callwebsvcService"> | <part name="callwebsvcService" element="tns:callwebsvcService"> | </part> | </message> | <message name="websvcCallService_callwebsvcServiceResponse"> | <part name="callwebsvcServiceResponse" element="tns:callwebsvcServiceResponse"> | </part> | </message> | <portType name="websvcCallService"> | <operation name="callwebsvcService" parameterOrder="callwebsvcService"> | <input message="tns:websvcCallService_callwebsvcService"> | </input> | <output message="tns:websvcCallService_callwebsvcServiceResponse"> | </output> | </operation> | </portType> | <binding name="websvcCallServiceBinding" type="tns:websvcCallService"> | <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> | <operation name="callwebsvcService"> | <soap:operation soapAction=""/> | <input> | <soap:body use="literal"/> | </input> | <output> | <soap:body use="literal"/> | </output> | </operation> | </binding> | <service name="websvcCallService"> | <port name="websvcCallServicePort" binding="tns:websvcCallServiceBinding"> | <soap:address location="http://127.0.0.1:8080/ws/websvcCallService"/> | </port> | </service> | </definitions> | <====================================================> XFire uses namespace with the attribute which is correct, why does EAP fails to parse these values. Any Help on this matter is highly appreciated. Regards, Abhishek View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190027#4190027 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190027

16 years, 3 months

1
0
0 / 0

[JBossWS] - Re: WS Addressing

by richard.opalka＠jboss.com

This is metro approach that doesn't work in native. See our WS-Addressing documentation/tutorials/tests to see how to enable WS-Addressing in native if native is your preferred SOAP stack. If you don't have preferred stack, use metro integration instead. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190003#4190003 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190003

16 years, 3 months

1
0
0 / 0

[JBossWS] - Re: jax-ws soap protocol handler and white space.

by mignaak

After days spent debugging I found a solution. It seems the remote server does not support chunked requests. The remote server is websphere 5.1. The solution is to put chunksize=0 in client config "Standard Client" in file "standard-jaxws-client-config.xml" in jbossws. Hope this solution ca be useful to others. Bye. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189993#4189993 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189993

16 years, 3 months

1
0
0 / 0

[JBossWS] - Re: How can I do mutual SSL when using JBoss as Web service

by jeckles933

I have a similiar problem. I can call a ws via https using stand alone project just fine. Run same code in jboss container, get error Can not connect http client invoker. Invalid HTTP server response [403] - Service Error. Response: Service Error/403 Side note: to get around the multiple keystores, you can use this approach HttpsURLConnection.setDefaultSSLSocketFactory(sslSocketFactory); you'll find a bunch of posts on it. i can provide more detail if needed. if you find solution to 403 problem, please post it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189942#4189942 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189942

16 years, 3 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-users November 2008