Details
-
Type:
Sub-task
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.2.6
-
Fix Version/s: None
-
Component/s: Core
-
Labels:None
-
Environment:Windows XP, java 1.5.0_11, xfire-1.2.6
-
Number of attachments :
Description
I'm trying to invoke the following method on generated (from wsdl) client:
LoaderSoap.java
public LoginResponse login( @WebParam(name = "Login", targetNamespace = "http://tourml.ru/serviceSecurity/2006-03-14/") ru.tourml.servicesecurity._2006_03_14.Login Login, @WebParam(name = "UserSessionId", targetNamespace = "http://tourml.ru/serviceSecurity/2006-03-14/", header = true, mode = WebParam.Mode.OUT) Holder<ru.tourml.servicesecurity._2006_03_14.UserSessionId> UserSessionId);
My client code:
UserSessionId.java
@XmlAccessorType(XmlAccessType.FIELD) @XmlType(name = "UserSessionId", propOrder = { "currentGuid" }) public class UserSessionId { @XmlElement(required = true) protected String currentGuid; public String getCurrentGuid() { return currentGuid; } public void setCurrentGuid(String value) { this.currentGuid = value; } }
Client.java
LoaderClient service = new LoaderClient(); javax.xml.ws.Holder<UserSessionId> holder = new javax.xml.ws.Holder<UserSessionId>(new UserSessionId()); Login login = new Login(); login.setLogin("xxx"); login.setPassword("xxx"); LoginResponse lr = service.getLoaderSoap().login(login, holder); log.debug("value: " + holder.value.getCurrentGuid());
The
holder.value.getCurrentGuid()
is always null - the
currentGuid
value not set, but it is present in the answer from service.
The folloing is track of real xml sent-received, which was logged while invoking the
service.getLoaderSoap().login(login, holder);
method:
POST http://touralliance.bronni.ru/Loader.asmx HTTP/1.1 SOAPAction: "http://tourml.ru/serviceSecurity/2006-03-14/Login" Content-Type: text/xml; charset=UTF-8 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; XFire Client +http://xfire.codehaus.org) Host: touralliance.bronni.ru Proxy-Connection: Keep-Alive Expect: 100-continue Content-Length: 356 <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 xmlns:ns1="http://tourml.ru/serviceSecurity/2006-03-14/"> <ns1:Login> <ns1:login>xxx</ns1:login> <ns1:password>xxx</ns1:password> </ns1:Login> </soap:Body></soap:Envelope>
HTTP/1.1 100 Continue HTTP/1.1 200 OK Date: Mon, 14 May 2007 08:07:49 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 1.1.4322 Cache-Control: private, max-age=0 Content-Type: text/xml; charset=utf-8 Content-Length: 492 <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <soap:Header> <UserSessionId xmlns="http://tourml.ru/serviceSecurity/2006-03-14/"> <currentGuid>2f107e25-287e-48d2-9ba8-b1805853757f</currentGuid> </UserSessionId> </soap:Header> <soap:Body> <LoginResponse xmlns="http://tourml.ru/serviceSecurity/2006-03-14/" /> </soap:Body> </soap:Envelope>
So, the problem remains???