How to connect to external web service and convert XML to a table

Hi experts,
I need to connect to external/non-SAP web service and convert XML in that site to a SAP table?
Is there a function call(SE37) to do this? Is it a must for me to install AS JAVA or PI and configure enterprise service? Please provide a link for me to retrieve relevant infomation, thx.

No, you don't need PI or the Java stack for this. You can create an ABAP proxy using the WSDL file for the web service and call the web service using the proxy class in an ABAP program. You can transform the XML response to internal tables/structures/variables using a transformation template that you create.

Similar Messages

How to connect to External Web Service? Error: ICM_HTTP_CONNECTION_FAILED

Hi all,
I have created an External Web Service, and I am trying to call the web service from SAP. I watched some tutorial and did everything like them, but I am getting this error:
SOAP:1,023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")
Can someone tell me how to solve this problem ?
Thank you in advance

Your AS ABAP is unable to connect to the remote server, talk to your network admins.

How can I call external web service from BPEL

1. I have "EmpService" webservice (simple webservice to get emp salary, not in BPEL domain) running in Oracle AS host1. If I want to call this web service from BPEL in another host2. How can I do this?
2. Is it a must to deploy this EmpService to Oracle BPEL domain in order to call it? If so, how can I deploy it. As many BPEL example tutorial demonstrate the "obant" command to deploy the BPEL process, but not show how to deploy a external web service not in BPEL project. Please help. ...

Create a partner link in BPEL and point it to the WSDL deployed on external server.
this thread will also help
Axis generated WS to Bpel WS

How to call an external web service from OIM?

Hi,
I have a question on how to call an external web service from OIM within e.g. creating user process? How should it be done; through adapter and task in the process?
Any recomendations?
Thanks in advance!

it is not clear to me if you are having problems with calling java code from OIM or if the problem is the web service API.
Lets do some divide and conquer:
Can you create a simple java class that just writes a couple of lines to the log? Please attach this code to the OIM task and make sure it runs.
Once this works we can start looking at the web service call.
Best regards
/Martin

Bad XML from external web service and would like to change the content

I am getting a bad XML(not valid) from external web service and I would like to change the content of the body in OSB proxy service to make it valid.
For example
<g:Information xsi:schemaLocation="http:// bad schema" xmlns:g="http://abc.com/t.xsd">
<test>Test Data</test>
</g:Information>
should become
<g:Information xmlns:g="http://abc.com/t.xsd">
<test>Test Data</test>
</g:Information>
Do you how can I do this?

I don't think it would be the best solution but you may try -
1. Conver the incoming XML to string using fn-bea:serialize() function
2. Replace the not-required content with a blank
3. Covert the string back to XML using fn-bea:inlinedXML
If you find any other solution, please let us know.
Regards,
Anuj

How to connect an external hard drive and monitor a single port thuderbolt

how to connect an external hard drive and monitor a single port thuderbolt

Yu connect the HDD to your Mac and then the monitor to the HDD.
The HDD should have TWO T-Bird ports on the enclosure.
Its called daisy chaining and up to five devices can be connected in this fashion.

Consume external web service and experience connection timed out issue

Hi all,
I followed tutorial:http://docs.oracle.com/cd/E18941_01/tutorials/jdtut_11r2_14/jdtut_11r2_14.html to consume external web service.
At step 2,substep 4, I experience the following error:
"DCA-40002: The WSDL document is invalid due to the following reason: WSDLException: faultCode=PARSER_ERROR: Failed to read wsdl file at:"http://www.webservicex.net/WeatherForecast.asmx?WSDL". Caused by : java.net.ConnectException: java.net.ConnectException: Connection timed out: connect."
I have tried to set up proxy:Tools > Preferences->Web Browser and Proxy. But it still doesn't work. Any idea?
Thanks in advance.
Regards,
weiyang
Edited by: user13304960 on Mar 15, 2012 8:42 PM
Edited by: user13304960 on Mar 15, 2012 8:43 PM

Hi,
Thanks for your reply. I have tried these 2 tutorials before. Both worked well. Publish an web service by myself, then consume it with a client. It works. But for this external wsdl published by USA weather forecast, it doesn't work. Navigate to http://www.webservicex.net/WeatherForecast.asmx?WSDL through firefox, and right response is returned. I wonder why connection timed out occurred and how to deal with it.
Could you please share your experience with me? Thanks.
Thanks.

How to connect to a web service??

I am banging my head on how to produce the appropriate code
to connect to a
web service I created locally.
I have a local web service:
http://localhost:8500/cfc/getprojects.cfc?wsdl
I am trying to figure out how to write a correct
<mx:WebService> to connect
to it so I can go on and bang my head on how to then bind the
results to
Labels.
I am attempting to follow the manual on this topic but it
goes all over the
place and my newbie mind can't wrap my head around it.
I tried this:
<mx:WebService id="get_projects"
wsdl="
http://localhost:8500/cfc/getprojects.cfc?wsdl"
useProxy="false"/>
</mx:WebService>
But I keep getting: The prefix "mx" for element
"mx:WebService" is not
bound.
I tried to find out more about it and thought I had to add:
<mx
peration name="getProjects">
<mx:request>
<projecttitle>????</projecttitle>
</mx:request>
</mx
peration>
But I have no idea on what to put in the request section per
each title
(<projecttitle>
And anyone show me how to write a correct
<mx:WebService> statement to be
able to connect to my web service?!
And if anyone is really bored:
The query results in 5 fields of data (project_title,
p_height, p_width,
p_type, live)
How do I then bind the project_title results to a label?
Wally Kolcz
Developer / Support

Hi Wally,
> I tried this:
> <mx:WebService id="get_projects"
> wsdl="
http://localhost:8500/cfc/getprojects.cfc?wsdl"
useProxy="false"/>
> </mx:WebService>
>
> But I keep getting: The prefix "mx" for element
"mx:WebService" is not
> bound.
Do you have a namespace declaration for mx in the root tag of
the file
that contains the WebService tag? For example, if you're in
the main
application file, your root tag should look something like:
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
...>
nj
Flex Builder team

Using an external web service and local element declarations

I am attempting to use (call) an external web service from workshop
8.1. It seems that if the web service's schema contains local element
declarations with the same name then workshop will generate incorrect
JCX code because it doesn't scope the generated classes.
I think the following simple example will do a better job explaining
than that last paragraph ;). In the following WSDL, the element
"testLocalDec" is used inside two different element types. In XML
Schema this is not a problem because each one is "scoped" by the
element types its included in. However, the generated JCX (listed
second) simply contains the testLocalDec structure twice which causes
problems in Java.
Is there some workaround for this? Note that making this element
declaration in the WSDL will not work because they are different
structures (with different names).
Also see my next email around using XMLBeans with external services
(since that could be a workaround if I knew how to do it).
thanks,
dave
*** sample WSDL ***
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
     <s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
     <s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn" element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
*** generated JCX ***
package helloTest;
* @jc:location
http-url="http://localhost:18080/tutorial/HelloWorldService"
* @jc:wsdl file="#HelloWorldServiceWsdl"
* @editor-info:link source="HelloWorldService.wsdl" autogen="true"
public interface HelloWorldServiceControl extends
com.bea.control.ControlExtension, com.bea.control.ServiceControl
public static class testLocalDec
implements java.io.Serializable
public static class sayHelloResponse
implements java.io.Serializable
public java.lang.String sayHelloReturn;
public testLocalDec testLocalDec;
public static class testLocalDec
implements java.io.Serializable
public java.lang.String different;
* @jc:protocol form-post="false" form-get="false"
public sayHelloResponse sayHello (java.lang.String caller,
testLocalDec testLocalDec);
static final long serialVersionUID = 1L;
/** @common:define name="HelloWorldServiceWsdl" value::
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
     <s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
     <s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn"
element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Hi David,
The folks in the workshop newgroup may have a suggestion, if you could
try your post there:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.workshop
Thanks,
Bruce
David Rees wrote:
>
I am attempting to use (call) an external web service from workshop
8.1. It seems that if the web service's schema contains local element
declarations with the same name then workshop will generate incorrect
JCX code because it doesn't scope the generated classes.
I think the following simple example will do a better job explaining
than that last paragraph ;). In the following WSDL, the element
"testLocalDec" is used inside two different element types. In XML
Schema this is not a problem because each one is "scoped" by the
element types its included in. However, the generated JCX (listed
second) simply contains the testLocalDec structure twice which causes
problems in Java.
Is there some workaround for this? Note that making this element
declaration in the WSDL will not work because they are different
structures (with different names).
Also see my next email around using XMLBeans with external services
(since that could be a workaround if I knew how to do it).
thanks,
dave
*** sample WSDL ***
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
<s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn" element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
*** generated JCX ***
package helloTest;
* @jc:location
http-url="http://localhost:18080/tutorial/HelloWorldService"
* @jc:wsdl file="#HelloWorldServiceWsdl"
* @editor-info:link source="HelloWorldService.wsdl" autogen="true"
public interface HelloWorldServiceControl extends
com.bea.control.ControlExtension, com.bea.control.ServiceControl
public static class testLocalDec
implements java.io.Serializable
public static class sayHelloResponse
implements java.io.Serializable
public java.lang.String sayHelloReturn;
public testLocalDec testLocalDec;
public static class testLocalDec
implements java.io.Serializable
public java.lang.String different;
* @jc:protocol form-post="false" form-get="false"
public sayHelloResponse sayHello (java.lang.String caller,
testLocalDec testLocalDec);
static final long serialVersionUID = 1L;
/** @common:define name="HelloWorldServiceWsdl" value::
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
<s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn"
element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Using an external web service and XMLBeans

I have an external document/literal web service that I want to use
(call) from inside workshop. I have listed a small example at the end
of this email.
I am wondering if there is a way to call and receive from the web
service using XMLBeans. In the tutorial examples XMLBeans are only
used by marshaling and unmarshaling the xml structure into a string
which is what is actually passed according to the WSDL. However, in
this case (and I personally think in most cases) the schema is
explicitly described in the WSDL and passed as the message. I might
add the structures for my real service are much more complex and so
the value of XMLBeans is certainly applicable to them.
Clearly I can somehow save off the schema and generate XMLBeans from
it. The next step is much less clear, how do I tell my JCX to use the
beans instead of generating private classes to represent the
structures?
To be honest I am a little surprised that for 8.1 the WSDL->JCX stuff
doesn't just leverage XMLBeans by default instead of generating basic
classes. This would give the power of XMLBeans to all web service
calls.
thanks,
dave
*** Sample WSDL ***
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
<s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn" element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

FYI, there is a XMLBeans newsgroup; w/ good feedback from the
developers:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.xmlbeans
Bruce Stephens wrote:
>
Hi David,
We are on the road, headed in that direction; pedal to the metal, etc.
just not there...yet.
We appreciate and value your input.
Thanks,
Bruce
David Rees wrote:
I have an external document/literal web service that I want to use
(call) from inside workshop. I have listed a small example at the end
of this email.
I am wondering if there is a way to call and receive from the web
service using XMLBeans. In the tutorial examples XMLBeans are only
used by marshaling and unmarshaling the xml structure into a string
which is what is actually passed according to the WSDL. However, in
this case (and I personally think in most cases) the schema is
explicitly described in the WSDL and passed as the message. I might
add the structures for my real service are much more complex and so
the value of XMLBeans is certainly applicable to them.
Clearly I can somehow save off the schema and generate XMLBeans from
it. The next step is much less clear, how do I tell my JCX to use the
beans instead of generating private classes to represent the
structures?
To be honest I am a little surprised that for 8.1 the WSDL->JCX stuff
doesn't just leverage XMLBeans by default instead of generating basic
classes. This would give the power of XMLBeans to all web service
calls.
thanks,
dave
*** Sample WSDL ***
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
<s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn" element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Web services and crossdomain.xml HELP

Hello
I am using the web services connector to consume a service it
all works
fine in flash however in the browser it fails
I can see it trying to load crossdomain.xml at the domain of
the WS
provider this is despite my putting:
System.security.loadPolicyFile("
http://dev.chatham.site/crossdomain.xml");
frankly I am at a loss as to how to make this work I have
tried.
var allowpath = "
http://www.postcoderwebsoap.co.uk";
System.security.allowDomain(allowpath);
how the hell do you let the connector connect?
any insight would be greatly apreciated
Rich

tjacobs01 wrote:
Hi all,
This is a follow-up to the question I posted and answered myself yesterday.
I have created a web service that returns Hebrew words in a string format of an XML document. This all appears to be working fine at this point. The only problem is that when I'm debugging in NetBeans, certain hebrew characters/words (note: some characters / words work!) xerces gives me an invalid utf-8 string (byte 1 of 2) exception in the display of the SOAP response - not the response itself, but I think in whatever netbeans is doing to display it. Not sure i follow. Are you referring to the debugger screens where the IDE shows variables/stacks etc? If so, i would say not to worry too much. IDE's are not perfect.
I have tried testing the strings I am returning by themselves - xerces can parse when I save them into a file and load. So it seems like the problem is just with the >SOAP response / with netBeans.
I understand that returning XML within a SOAP container could then be screwing up the parsing. Any thoughts as to why certain words and not others? Is there any way to fix this, and perhaps more importantly - is it important to fix this?Did you test this in a production like environment? If so, i would say its just a minor annoyance.

Connect to SharePoint web service using the XML / Web Service connector

Hi experts,
I am currently trying to display my SharePoint list in Crystal Report. Therefore my plan is to use a SharePoint web service to get the data and paste them to the Crystal Report.
Is it possible to use the "XML and Web services" connector of the Crystal Reports database expert?
When I enter the web service URL, for instance:
https://[url]/_vti_bin/lists.asmx?wsdl
and click next... I have to enter the web service credentials.
On the next page I have to enter Service, Port and Method.
Do I have to enter the service URL again here?
What If, there is no port? Can I leave that field empty?
I know the methods, but where can I add the mandatory parameters?
Thanks for any helps and comments!
Sebastian

Hi Ananth,
thank you, but this document does not help at all.
We are using Crystal Reports 2008 SP2.
We want to use the Web Service Connector.
What I need is more informationen about the Web service connect. For example - the connection in Microsoft InfoPath is much easier - there I don't have to enter a port and can choose the methods from a list.
Is it possible to use the Crystal web service connector for MS SharePoint Webservices?
Or must I use the Crystal SDK to carry out a connection?
Best regards,
Sebastian

Call Web Service and display return values in table

Hi all,
I am calling a self-implemented web service with visual composer. The webservice returns the following data shown below.
Each item like carID, carBrand etc. should be displayed in an output table.
The problem is, that he doesn't display any data at all. Is there a problem with the webservice data which is returned or do I have to do some further settings in visual composer?
Thank you for your help! Kind regards, Patrick.
<?xml version="1.0" encoding="utf-8" ?>
- <ArrayOfCar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://IBM-W2003-EAI/GetCarList">
- <Car>
<CarID>A-471</CarID>
<CarBrand>Alfa</CarBrand>
<CarModel>156</CarModel>
<Kw>100</Kw>
<Ps>136</Ps>
<Km>79000</Km>
<Year>1998</Year>
<Price>7500,0000</Price>
<Url />
<Status>Available</Status>
</Car>
- <Car>
<CarID>A-736</CarID>
<CarBrand>Audi</CarBrand>
<CarModel>A4</CarModel>
<Kw>110</Kw>
<Ps>150</Ps>
<Km>87000</Km>
<Year>2000</Year>
<Price>15780,0000</Price>
<Url />
<Status>Reserved</Status>
</Car>
</ArrayOfCar>

Hi Shai,
the webservice is working well, trying to test it with webservice navigator.
He also returns the correct number of rows (because there appears slider beneath the table output and I also counted the rows), but there is no data displayed in visual composer.
I have got no further ideas, what the problem is...
THank you for your support.
Kind regards, PAtrick.

Connect to a web service?

Can someone please tell me how to connect to a web service
and receive the array and display it in AS 2.0? It's more then one
item in the array I will receive. I need to do it by code and can
not use Web Service connector.

I have now added one Web Service Connector and bind it to a
label, this works fine. But, how do I do when the answer from the
web service contains more then one object? I think it have to be
something like this?
for(i = 0; i < WebServerConnector.Items.Length; i++){
WebServerConector
As you can see so have I no clue of how to do this. Can you
pleas help me with this?

How to dynamically connect to a web service

hello
i wana know how can i connect to a webservices dynamically in java
i am using MYeclipse i know how to create a web service client but i dnt know how to connect to a web service dynamically ie i give the url of the service at run time and then connect to that service....................
regards
Shakeel Abbas

Shakeel.Abbas wrote:
how can i connect to a webservices dynamically in java?you can do this following ways:
*σ* Use [javax.xml.soap|http://java.sun.com/javaee/5/docs/api/javax/xml/soap/package-summary.html] package for invoking web services using Simple Object Access Protocol (SOAP). Using SOAPConnection you can connect and communicate to a webservice via SOAPMessage . [More about SOAP Connection|http://java.sun.com/javaee/5/docs/tutorial/doc/bnbhg.html#bnbhq].
*σ* Use [java.net|http://java.sun.com/javase/6/docs/api/java/net/package-summary.html] package for invoking web services using Hypertext Transfer Protocol (HTTP). Using HttpURLConnection you can connect and communicate to a webservice.
Hope this will help.
Thanks,
Tejas

How to connect to external web service and convert XML to a table

Similar Messages

Maybe you are looking for