December 2007 - jbossws-users - Jboss List Archives

[JBossWS] - Problem in Serialization of java objects

by zeeshan.javeed

I got an issue with Jbossws. I am using 2.0.2 version. I have two interface, TShippingFeePriceIFV1 and TShippingFeePriceIFV1_1 both are implemented by third interface TShippingFeePriceIF. interface TShippingFeePriceIFV1 has two methods, getPrice, setPrice, getSum, setSum and interface TShippingFeePriceIFV1_1 has three methods, getPrice, setPrice, getSum, setSum and additionaly getQuantity, setQuantity. Now I am supporting two different versions of wsdl file. One is having version one of the shipping fee and new version is supportint the version wiht quantity. Now even casting the obect to TShippingFeePriceIFV1 (which has two only methods) the quantity is still serailized and passed to the end clietns... Any comments why it is happening. From my understanding it should not serilaze the extra values in object and pass the values only which the current object support... ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109917#4109917 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109917

17 years

1
0
0 / 0

[JBossWS] - Re: MTOM interop issue with WSE 3.0

by jmaenen

Issue above was related to the fact that the proxy class on the C# side was not generated properly .. Should be derived from : Microsoft.Web.Services3.WebServicesClientProtocol Unfortunatly the there is still an issue related to the content type of the respons sent from the server. With the request the content type is Content-Type: multipart/related; type="application/xop+xml" But on the repons of this request the content type is set to : Content-Type: text/xml;charset=UTF-8 WSE cannot support this feature ! http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1099016&SiteID=1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109865#4109865 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109865

17 years

1
0
0 / 0

[JBossWS] - Re: Does JBossWS 2.0.2.GA support POJO based service?

by richard.opalka＠jboss.com

Hi, no, you can use JAX-RPC based webservices as well. But our code base is based on JDK 1.5 sources. Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109809#4109809 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109809

17 years

1
0
0 / 0

[JBossWS] - Re: Does JBossWS 2.0.2.GA support POJO based service?

by thejavafreak

So all of it is based on JAX-WS? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109773#4109773 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109773

17 years

1
0
0 / 0

[JBossWS] - Re: Big problem with WebXMLRewriterImpl.java rename

by heiko.braun＠jboss.com

Sorry, wrong buffer. This is the correct link: http://jira.jboss.org/jira/browse/JBWS-1925 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109752#4109752 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109752

17 years

1
0
0 / 0

[JBossWS] - Re: Big problem with WebXMLRewriterImpl.java rename

by heiko.braun＠jboss.com

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=124906 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109750#4109750 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109750

17 years

1
0
0 / 0

[JBossWS] - Re: Does JBossWS 2.0.2.GA support POJO based service?

by richard.opalka＠jboss.com

Hi, JBoss WS 2.x and above requires JDK 1.5 Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109745#4109745 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109745

17 years

1
0
0 / 0

[JBossWS] - Re: Big problem with WebXMLRewriterImpl.java rename

by heiko.braun＠jboss.com

Yes, i can see it now. I'll provide you with a new container integration. Stay tuned... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109743#4109743 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109743

17 years

1
0
0 / 0

[JBossWS] - Re: how to set headers in JAX-WS

by alessio.soldano＠jboss.com

I think your issue is due to the way the wsdl:message is defined; I would have expected you to have a binding/operation/input block specifying the two part names, instead you have two different messages for the soap header and the soap body. Take a look at the PingService.wsdl of the webparam samples in the binary distribution for an example. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109715#4109715 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109715

17 years

1
0
0 / 0

[JBossWS] - Re: how to set headers in JAX-WS

by tpawankumar

Hi Alessio, This is the wsdl <?xml version="1.0" encoding="utf-8" ?> | <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://McAfeeAsap.com" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://McAfeeAsap.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> | <wsdl:types> | <s:schema elementFormDefault="qualified" targetNamespace="http://McAfeeAsap.com"> | <s:element name="ProcessOrder"> | <s:complexType> | <s:sequence> | <s:element minOccurs="0" maxOccurs="1" name="sOrderXML" type="s:string" /> | </s:sequence> | </s:complexType> | </s:element> | <s:element name="ProcessOrderResponse"> | <s:complexType> | <s:sequence> | <s:element minOccurs="0" maxOccurs="1" name="ProcessOrderResult" type="s:string" /> | </s:sequence> | </s:complexType> | </s:element> | <s:element name="AuthHeader" type="tns:AuthHeader" /> | <s:complexType name="AuthHeader"> | <s:sequence> | <s:element minOccurs="0" maxOccurs="1" name="sToken" type="s:string" /> | </s:sequence> | <s:anyAttribute /> | </s:complexType> | </s:schema> | </wsdl:types> | <wsdl:message name="ProcessOrderSoapIn"> | <wsdl:part name="parameters" element="tns:ProcessOrder" /> | </wsdl:message> | <wsdl:message name="ProcessOrderSoapOut"> | <wsdl:part name="parameters" element="tns:ProcessOrderResponse" /> | </wsdl:message> | <wsdl:message name="ProcessOrderAuthHeader"> | <wsdl:part name="AuthHeader" element="tns:AuthHeader" /> | </wsdl:message> | <wsdl:portType name="McAfee_x0020_Order_x0020_ProcessingSoap"> | <wsdl:operation name="ProcessOrder"> | <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">McAfee Order Processing</wsdl:documentation> | <wsdl:input message="tns:ProcessOrderSoapIn" /> | <wsdl:output message="tns:ProcessOrderSoapOut" /> | </wsdl:operation> | </wsdl:portType> | <wsdl:binding name="McAfee_x0020_Order_x0020_ProcessingSoap" type="tns:McAfee_x0020_Order_x0020_ProcessingSoap"> | <soap:binding transport="http://schemas.xmlsoap.org/soap/http" /> | <wsdl:operation name="ProcessOrder"> | <soap:operation soapAction="http://McAfeeAsap.com/ProcessOrder" style="document" /> | <wsdl:input> | <soap:body use="literal" /> | <soap:header message="tns:ProcessOrderAuthHeader" part="AuthHeader" use="literal" /> | </wsdl:input> | <wsdl:output> | <soap:body use="literal" /> | </wsdl:output> | </wsdl:operation> | </wsdl:binding> | <wsdl:binding name="McAfee_x0020_Order_x0020_ProcessingSoap12" type="tns:McAfee_x0020_Order_x0020_ProcessingSoap"> | <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" /> | <wsdl:operation name="ProcessOrder"> | <soap12:operation soapAction="http://McAfeeAsap.com/ProcessOrder" style="document" /> | <wsdl:input> | <soap12:body use="literal" /> | <soap12:header message="tns:ProcessOrderAuthHeader" part="AuthHeader" use="literal" /> | </wsdl:input> | <wsdl:output> | <soap12:body use="literal" /> | </wsdl:output> | </wsdl:operation> | </wsdl:binding> | <wsdl:service name="McAfee_x0020_Order_x0020_Processing"> | <wsdl:port name="McAfee_x0020_Order_x0020_ProcessingSoap" binding="tns:McAfee_x0020_Order_x0020_ProcessingSoap"> | <soap:address location="http://testdrive.mcafeeasap.com/ws/mop/mop.asmx" /> | </wsdl:port> | <wsdl:port name="McAfee_x0020_Order_x0020_ProcessingSoap12" binding="tns:McAfee_x0020_Order_x0020_ProcessingSoap12"> | <soap12:address location="http://testdrive.mcafeeasap.com/ws/mop/mop.asmx" /> | </wsdl:port> | </wsdl:service> | </wsdl:definitions> and on the server side i don't have the implementation,it is third party service we are using. But i knew there is a method processOrder which takes two parameters one is xmlstring and the other is authheader object. The Jboss server i am using is Jboss 4.2.1 GA and jbossws is 1.2.1GA. Please let me know if you have any suggestions? Thanks, Pavan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109706#4109706 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109706

17 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users December 2007