Web service alternative to request.getRemoteAddress

I am new to web services i want to know how to access the remote address like we do in http with request.getRemoteAddress

you actually use something like this...
call.setTargetEndpointAddress(END_POINT);
END_POINT is something like
http://localhost:8080/mywebservice
If you have the WSDL, there is also another way to connect to it.

Similar Messages

Web Service Stateless Session request using JDeveloepr 11g (JAX-RPC)

I have been trying to consume web Service by sending Stateless Session request to the system.
I generated the Java Proxy using JDeveloepr 11g, using JAX-RPC.
As it is Stateless I need to add following SOAP Header for authentication
<soap:Header>
<wsse:Security soap:mustUnderstand="1">
<wsse:UsernameToken>
<wsse:Username>[email protected]</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wssusername-
token-profile-1.0#PasswordText">adminOnDemand</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
To do this I tried clientuntcredentialprovider as suggested by most of the post online, but found of little help as the server complained of not be able to find the User Name and Password.
To add to the mess problem I hit was I was not able to View the SOAP Request or Response sent by JDeveloper hence not helping me in debugging the same
I have tried it on XML SPY by manually adding SOAP Header to the SOAP request and was able to find the response, but I have not been able to do the same using the JDeveloper 11g IDE.
I have tried HTTP Analyzer assuming it might help, but unfortunately due to the huge size of WSDL, tool hanged my PC each time I loaded it.
I know it should be fairly straight forward but just feel like missing something.
Has anybody has got this thing working ?
Regards,
Deepak

What exactly you mean that since your request is stateless you must send a Username token?
Also, can you put here the code you used to populate the UNT.
Finally, if possible, can you zip and email your wsdl, the http analyzer should be able to handle wsdls, even if they are huge.
Thanks,
Vishal

Synchronous RFC-XI-Web Service with no request method

Hello guys,
I'm trying to set up an RFC-XI-Web Service scneario. But with the particularitity that the WSDL does not have a request method. It only has a very simple response method.
How can I make this? How can XI call the Web Service, if I dont have any request method?
Thanks for your help.
Felipe

Matias, after some test I think that VJ is correct.
It is failing at the moment of delivering the message to the WS, I'm getting the followin error messages:
com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/PLAIN; HTTP 302 Moved Temporarily
I tested the WS with XMLspy and works correctly.
I'm starting to believe that the best solution is to simply create a dummy request in the WS.
It would be great if someone else test in their own and see if we get the same result. Thanks,
Felipe

Azure ML Published Web Services - Cross Origin Requests

It appears Azure ML published web services do not support cross-origin requests. Simply trying to call a published Azure ML service using jQuery in Chrome, Firefox, Safari, or IE is blocked because because of the missing access control headers in the
response. Is there any way to publish an Azure ML web service so it can be called from a domain other than *.azureml.net?

Hi ejasoncline,
Yes, CORS is currently not supported for the web services, but we will make a note of this request and consider adding support.
You can use the sample code to call the published webservice using a standalone client. The webservice help page (<score url>/help) should have sample code for C#, Python & R.
Richie

Web service sends multiple requests after flash upgrade

I have a Xcelsius engage 2008 SP3 FP2 and i just found out that my dashboard send multiple reqests to web service and this will render my dashboard useless. This is a major bug, is there any solution? Service methods will get around 2-20 request and the dashboard will not be usable any more. Triggers are correct and will not trigger web service unless button is clicked.

Dear Expert,
Tcode RZ10
set the parameter rdisp/gui_auto_logout = 30M in all Instance profiles / orwhat ever time limit u want to specify.
See that this parameter is set on each server.
And you can make it a default.
Regards,
Shankar K B
Edited by: Shankar.kb on Feb 19, 2012 2:25 AM

Data Federator - Building Web Services Data Source - Request Guidance

Hello -
I am trying to build a web services data source in Data Federator.
I have:
1. In ECC, I have created a web service, proxy, port, endpoint, etc. and am testing it with WS Navigator
2. I have created a Project in Data Federator of the type web service
    a. Here I have assigned the WSDL URL (generated in ECC) as the URL
    b. I have setup web service authentication using the same userid, pwd in the web services definition (note: I have set the
        web services authentication to 'NONE' to avoing authorization issues)\
    c. I am now trying to "Generate Operations"
I keep getting the error :
The File Access Parameters are not valid (directory path = <HERE IS THE PATH TO THE WSDL WITH THE HOST/PORT stripped OUT>; file pattern = document
I believe that it is finding the WSDL, becuase when I change the WSDL from 'Document' to 'RPC', the error changes with the file pattern = rpc.
What needs to be done to the file access parameter piece.
PLEASE provide guidance. Thanks.
- abhi

Ananya,
We are using XI to load data to BI from source system. XI basically uses the same concept as Web Services - Real time data concept via RFC embeded in Proxies.
I was using web services to test data load - eventually we will use XI.
KJs blog is pretty good. I was able to get data loaded - after several iterations and several OSS notes. It is still not perfect - there are several manual steps . I am going to pick KJs brain on that.
We are on SP10 and looks like there are several bugs in RSRDA. Some of these are addressed in SP11 an SP12.
Some notes to consider are
0001003963, 0001008276,0001009260 and 001003265.
Let me know if you have any questions.

SharePoint 2013 web service: Error while sending claim based authentication request (The corresponding SID in the domain is not part of the intended account type)

We are using .asmx services for SharePoint features such as comments, and rating.
Service
Feature used
http://<<hostname>>/_vti_bin/socialdataservice.asmx
Commenting, Rating
http://<<hostname>>/_vti_bin/UserProfileService.asmx
For out of box workflows
In SharePoint 2013,
SharePoint – 80 web application is on claims based mode and user is logging in with windows authentication. With logged-in client context used to call SharePoint's default web service, we are getting below error message from
web service (Social data and user profile services).
Server was unable to process request. ---> The corresponding SID in the domain is not part of the intended account type.
When the service is accessed using console application with Visual Studio credentials (logged in user), we are able to access the service. Below is the code snippet
using (SocialDataService
service = new
SocialDataService())
service.Credentials =
CredentialCache.DefaultCredentials;
SocialCommentDetail detail = service.AddComment("<<url>>",
"Test Comment",
null,
null);
Are SharePoint 2013 web services not supporting request coming with claim based authentication web application?
Thanks, Pratik Agrawal (MAQ Software)

While this applies to 2010, I believe the same is true with 2013:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/925e5f46-317f-46d3-bc55-c67f07eb2372/call-sharepoint-web-services-using-claimbased-authentication?forum=sharepointgeneralprevious
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Web Service - Request never turns to GREEN

Friends,
I have created Web Service Source System followed by Data Source and did the required setting in Web Service Admn screen (WSADMIN) and could able to generate/publish WSDL and able to see that PSA getting the records with trigger of web service.
My concern is, after creating the Web Service Data Source, I did create the "Scheduler: InfoPackage for Real-Time Data Acquisition (Push)" and set the "Automatic Closure of the Request" (in Processing Tab) to "1 Hour". I am able to see that system is creating new Request for all the transaction triggered in that particular Hour but it is NOT setting the previous Requests to GREEN (So that the PSA data couble us triggered to ODS)..
That means, all the Requests (which are getting generated every hour) are in Yellow status.. how to turn them Green (Automatic)..? Is that anything I am missing here..
Please let me know if you have any thoughts..
Thanks
Mavip

Heres the correct answer-
<b>Rationale -</b>
When you transfer data using a Web service or real-time data acquisition (using a SAPI and a Web service), the InfoPackage requests (also called PSA requests) remain open across several load processes.
<b>The requests are closed when the threshold values set in the InfoPackage are reached.</b> The system opens new requests and data transfer is continued using the new requests. With process type <b>Close Real-Time InfoPackage Request</b>, you can close an open PSA request before the threshold value is reached.
This means that you can use a Web service to send data to the PSA in BI and then use the standard scheduling process to update it further.
You can close requests in this way to perform regular analyses at set times on an InfoProvider that is down stream of a DataStore object that you are using for real-time data acquisition.
<b>Procedure -</b>
1. In the process chain, choose process type Close Real-Time InfoPackage Request.
2. On the next screen, enter a technical name for the process variant and choose Create.
3.On the next screen, enter a description for the process variant and choose Continue.
The maintenance screen for the process variant appears.
4.In the table, select the InfoPackage for which you want to close a request.
5.Choose Save and go back.
<b>PS -</b>
Do not schedule this process to take place more frequently than once an hour. Otherwise performance is affected. If you schedule the process to take place more frequently, it is possible that the system will generate so many requests that performance is affected.
<b>Result</b>
When the process chain is run, the system closes the PSA request, as well as the DTP and change log request, if they exist.

Retrieving Request XML Element in Web Service Code

to create a web service: I write java code and using JDeveloper, I 'create J2EE web service' from the java code.
I need to get and handle a parameter, passed to the web service in the request xml and process it in my java code. For example I want to access a header element received in the request.
How can I retrieve those elements in my code?
Regards
Farbod

Hi V.S,
[Here|http://img144.imageshack.us/my.php?image=datetimekb1.jpg] by the screenshot of the working example.
The expression that I have used is :
=DSTR(@DATE1,"XML_DATE")&TSTR(@TIME1,"XML_TIME")
Where,
XML_DATE YYYY-MM-DD 2001-01-31
XML_TIME THH:NN:SS 02:39:40
This should work now. Let me know.
Best regards,
Dharmi
Edited by: Dharmi Tanna on Sep 8, 2008 2:29 PM

Possible Bug - Web Service Request Not Correct

Hi,
I am running ApEx 2.2 and think I may have come across a bug when referencing a web service that has been created using JDeveloper.
I have created my WSDL in JDev that looks like the following:
<definitions
name="MyHelloWorldService"
targetNamespace="http://helloworldserver/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://helloworldserver/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://helloworldserver/"
elementFormDefault="qualified" xmlns:tns="http://helloworldserver/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/">
<element name="getCountElement">
<complexType>
<sequence/>
</complexType>
</element>
<element name="getCountResponseElement">
<complexType>
<sequence>
<element name="result" type="int"/>
</sequence>
</complexType>
</element>
<element name="sayHelloElement">
<complexType>
<sequence>
<element name="name" type="string" nillable="true"/>
</sequence>
</complexType>
</element>
<element name="sayHelloResponseElement">
<complexType>
<sequence>
<element name="result" type="string" nillable="true"/>
</sequence>
</complexType>
</element>
</schema>
</types>
<message name="IHelloWorld_getCount">
<part name="parameters" element="tns:getCountElement"/>
</message>
<message name="IHelloWorld_getCountResponse">
<part name="parameters" element="tns:getCountResponseElement"/>
</message>
<message name="IHelloWorld_sayHello">
<part name="parameters" element="tns:sayHelloElement"/>
</message>
<message name="IHelloWorld_sayHelloResponse">
<part name="parameters" element="tns:sayHelloResponseElement"/>
</message>
<portType name="MyHelloWorldService">
<operation name="getCount">
<input message="tns:IHelloWorld_getCount"/>
<output message="tns:IHelloWorld_getCountResponse"/>
</operation>
<operation name="sayHello">
<input message="tns:IHelloWorld_sayHello"/>
<output message="tns:IHelloWorld_sayHelloResponse"/>
</operation>
</portType>
<binding name="MyHelloWorldServiceSoapHttp" type="tns:MyHelloWorldService">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getCount">
<soap:operation soapAction="http://helloworldserver//getCount"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="sayHello">
<soap:operation soapAction="http://helloworldserver//sayHello"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="MyHelloWorldService">
<port name="MyHelloWorldServiceSoapHttpPort" binding="tns:MyHelloWorldServiceSoapHttp">
<soap:address location="http://cjbrown-lap:8888/HelloWorld-HelloWorldServer-context-root/MyHelloWorldServiceSoapHttpPort"/>
</port>
</service>
</definitions>
When referencing this in ApEx it can see the methods getCount and sayHello, and it can also see all the input and output parameters. The problem comes when I test the web service.
The request generated by ApEx is the following for the sayHello method:
<?xml version='1.0' encoding='UTF-8'?><SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body><namesp1:sayHello xmlns:namesp1="http://helloworldserver/"><namesp1:name xsi:type="xsd:string"></namesp1:name></namesp1:sayHello></SOAP-ENV:Body></SOAP-ENV:Envelope>
This returns the following message from the webservice:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://helloworldserver/"><env:Body><env:Fault><faultcode>env:Client</faultcode><faultstring>Caught exception while handling request: unexpected element name: expected={http://helloworldserver/}sayHelloElement, actual={http://helloworldserver/}sayHello</faultstring></env:Fault></env:Body></env:Envelope>
The correct request should in fact be:
<?xml version='1.0' encoding='UTF-8'?><SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body><namesp1:sayHelloElement xmlns:namesp1="http://helloworldserver/"><namesp1:name xsi:type="xsd:string">Chris</namesp1:name></namesp1:sayHelloElement></SOAP-ENV:Body></SOAP-ENV:Envelope>
This will return the expected message:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://helloworldserver/"><env:Body><ns0:sayHelloResponseElement><ns0:result>Hello Chris</ns0:result></ns0:sayHelloResponseElement></env:Body></env:Envelope>
What ApEx seems to be doing is using the name of the method, rather than what is being detailed in the WSDL as the expected input envelope. It is also not showing the input parameters as an input box in the test instead is shows "Report returned no rows".
I have managed to get around this issue in a less than ideal way be modifying the NAME column in the WWV_FLOW_WS_OPERATIONS table to sayHelloElement instead of sayHello, and the TYPE_IS_XSD column in the WWV_FLOW_WS_PARAMETERS table to Y instead of N, in the FLOWS_020200 schema.
It now works fine, but why what could have caused it to not be correct in the first place? The answer to this is very important to me as I am working on a way to call XML Publisher seemlessly, without using a URL link, from ApEx, and then emailing the output document to the user. I don't want to have to modify the underlying tables each time I add a new web service reference in ApEx.
Any comments, views, assistance is welcome here.
Many Thank in Advance
Cj

Tony:
Thanks for reporting the issue. There was a change in the session pop-up page to include reporting on the new xmltype column in collections. Unfortunately the wrong function is being called on the xmltype column to display its contents. This will be fixed in an upcoming release.
Application Express 4.0 Web service support makes use of this new xmltype column in a collection. Therefore if you call a web service that returns a large XML document, and you click the session toolbar, you will receive the error.
Regards,
Jason

How does a web service process requests?

WebLogic Server Version: 10.3.3.0, JDeveloper Studio Edition Version 11.1.1.5.0
We noticed that when the same web service has multiple requests the 2nd request waits until the first request completes.
Is this standard behavior?
chuck

hello jbrener, websites can also approximate your location by the ip address your ISP is assigning to you - there's no way around that (without using a vpn service or a proxy which disguises your ip address).
http://www.yougetsignal.com/tools/network-location/

Problem updating a SOAP Web Service with ArrayCollection

Hello,
I am having issues POST'ing an ArrayCollection to a C# Web
Method. Here's how I have my application set up:
I have a DataGrid in my application and set the dataProvider
to be the result object of a Web Service operation. I set the
DataGrid's editable property to "true" and would like to be able to
edit the data and send off the DataGrid's dataProvider as the
parameter for the Web Method. If I edit the first row of the
DataGrid and trigger the operation, it gets saved just fine. If I
try to edit any other row this way, it keeps sending the same
packet (as verified by a packet sniffer) not allowing me to update
any other row. It seems the Web Service is sending the first 255
characters of the serialized ArrayCollection.
My questions are: why is this happening?
and
How can I fix this?
Here is the request of my Web Service operation:
<mx:request xmlns="">
<GlossaryTerms>
{GlossaryArrayCollection}
</GlossaryTerms>
</mx:request>
This is the definition of GlossaryArrayCollection:
[Bindable]
public var GlossaryArrayCollection:ArrayCollection = new
ArrayCollection();
Here is the SOAP packet that the C# Web Method is expecting:
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
xmlns:soap12="
http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<GlossaryUpdate xmlns="">
<GlossaryTerms>
<Glossary cID="int" cDeleted="boolean" cTerm="string"
cDefinition="string" cURL="string" cPublic="boolean"
cRowVersion="string"/>
<Glossary cID="int" cDeleted="boolean" cTerm="string"
cDefinition="string" cURL="string" cPublic="boolean"
cRowVersion="string" />
</GlossaryTerms>
</GlossaryUpdate>
</soap12:Body>
</soap12:Envelope>
Thanks to anyone for their help.
Brian Cary

Where exactly you are seeing this error? possible for you share the screenshot?
Execution failed: These policy alternatives can not be satisfied:
{http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}SupportingTokens

Accessing BPEL processes via a proxy web service performance issues

Hello,
I have more BPEL processes implemented, each such a process implementing business functionality in a certain domain (generally, a domain has more business processes).
The request was to provide a single web service for each domain. It means that all the business methods (processes) in the same domain should be accessed through the same web service. This request doesn't make possible to expose the BPEL processes themselves as web services that could be directly consumed by different clients of the application.
The alternative will be to implement the "domain" web services through a Java class, for instance. With this approach, the Java based domain web services will expose the needed business methods to the clients. And the Java class will get the request input parameters and will call the corresponding BPEL process via SOAP. This scenario would be fine, but... this approach would imply a supplementary marshalling/unmarshalling process at the domain web service level. The data returned by the BPEL processes could be very large and in such a situation the Java based domain web service will introduce an important performance drawback.
Is there any other solution to this case that will allow the using of a "proxy" domain web services that will not introduce any important drawback via marshalling/unmarshalling?
Many thanks in advance!
Regards,
Marinel

Hello,
First, thank you Sandor for your answer.
I understand that it is possible to create a BPEL process that exposes multiple operations/messages. This would be exactly what I need: a single process (web service) that will expose many operations. Could anyone, please, point me to such an example?
So far I thought that there is possible to have only one operation exposed with a BPEL process, what is delimited between the receive/reply blocks (in the synchronous case).
Regards,
Marinel

Problems sending xml data as string to a web service

Hello!
I need to develop a client in order to invoke a web service. I have the WSDL of the web service, so I generate a web service proxy, from that WSDL, using JDeveloper 10.1.3.0.
Among other things, that web service receive RPC request (binding style is RPC) and the request has only one parameter, which consists of a string. That string must be an XML document (that is, the web service receives one parameter which is a XML document as a String). I generate that parameter, and it looks like the following:
<?xml version = '1.0' encoding = 'UTF-8'?>
<inputMessage xmlns="http://ws/validacion" xmlns:xsi="http://www.w3.o
rg/2001/XMLSchema-instance" xsi:SchemaLocation="http://localhost/ws/xsd/mservic/ws.xsd">
<request>ServiceRequest</request>
<versionMsg>1.0</versionMsg>
<data>AAAAAAAAAAAAAA</data>
</inputMessage>
However, when I send the request and capture it through HTTPAnalyzer, I get the following:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><MyWebService xmlns="http://soapinterop.org/"><myWebServiceRequest xsi:type="xsd:string" xmlns=""><?xml version = '1.0' encoding = 'UTF-8'?>
<inputMessage xmlns="http://ws/validacion" xmlns:xsi="http://www.w3.o
rg/2001/XMLSchema-instance" xsi:SchemaLocation="http://localhost/ws/xsd/mservic/ws.xsd">
<request>ServiceRequest</request>
<versionMsg>1.0</versionMsg>
<data>AAAAAAAAAAAAAA</data>
</inputMessage></myWebServiceRequest></MyWebService></soapenv:Body></soapenv:Envelope>
As you can see, the symbol '<' y replaced with '<'.
Why does it happen? Is there a way of avoiding that?
Could anybody be so kind to help me, please?
Thank you very much in advance.

Hello!
I need to develop a client in order to invoke a web
service. I have the WSDL of the web service, so I
generate a web service proxy, from that WSDL, using
JDeveloper 10.1.3.0.
Among other things, that web service receive RPC
request (binding style is RPC) and the request has
only one parameter, which consists of a string. That
string must be an XML document (that is, the web
service receives one parameter which is a XML
document as a String). I generate that parameter, and
it looks like the following:
<?xml version = '1.0' encoding = 'UTF-8'?>
<inputMessage xmlns="http://ws/validacion"
xmlns:xsi="http://www.w3.o
rg/2001/XMLSchema-instance"
xsi:SchemaLocation="http://localhost/ws/xsd/mservic/ws
.xsd">
<request>ServiceRequest</request>
<versionMsg>1.0</versionMsg>
<data>AAAAAAAAAAAAAA</data>
nputMessage>
However, when I send the request and capture it
through HTTPAnalyzer, I get the following:
<?xml version="1.0"
encoding="UTF-8"?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelop
e/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body><MyWebService
xmlns="http://soapinterop.org/"><myWebServiceRequest
xsi:type="xsd:string" xmlns=""><?xml version =
'1.0' encoding = 'UTF-8'?>
<inputMessage xmlns="http://ws/validacion"
xmlns:xsi="http://www.w3.o
rg/2001/XMLSchema-instance"
xsi:SchemaLocation="http://localhost/ws/xsd/mservic/ws
.xsd">
<request>ServiceRequest</request>
<versionMsg>1.0</versionMsg>
<data>AAAAAAAAAAAAAA</data>
;/inputMessage></myWebServiceRequest></MyWebService></
soapenv:Body></soapenv:Envelope>
As you can see, the symbol '<' y replaced with
'<'. (I hope you can see it now)
The symbol '<' is replace with '& l t ;' (with no whitespaces)
>
Why does it happen? Is there a way of avoiding that?
Could anybody be so kind to help me, please?
Thank you very much in advance.

How to get the cookie from a web service using Axis

I used the AXIS wizard to consume a WSDL and create a bunch of boiler plate code. It works great in that I can talk to the web service and submit requests.
The problem is that I need to retrieve the cookie from the login request and use it when making subsequent requests. I have been unable to find the cookie and would appreciate a point in the right direction.
Currently I'm trying something like this
String cookie = (String)((Stub)service)._getCall().getMessageContext().getProperty(HTTPConstants.HEADER_COOKIE);
Thanks in advance.

Answered on my own:
Just have to use
x_result = http_client->response->get_data( ).
instead of
x_result = http_client->response->to_xstring( ).
Just don't knwo why the filesize is wrong also - but I can work with this image!

Web service alternative to request.getRemoteAddress

Similar Messages

Maybe you are looking for