Implementing an XI WSDL

Hi everybody!
I am just trying to import a WSDL file created out of XI in a webdynpro project. Somehow when I try to create a new Model nothing is happening even I don't get any error messages. What am I doing wrong? Is there any documetation?
Bye Markus

Hi Marcus.
I think you´d like to create a WS Model from a Message Interface definition (exported as WSDL)? In this WSDL-document you haven´t any receiver information for an executable webservice.
If you´d like to call a (xi)-webservice from webdynpro, you can create it from a service definition at configuration time. Please refer to the xi documentation (configuration time).
Regards,
Daniel

Similar Messages

How to create a WebService that implements a given WSDL

Hi
I am implementing a webservice that will be a subscriber for
another external webservice. The provider of the external
webservice will give me the WSDL for the subscribers he
expects. So, I'll have to setup a webservice that implements
the WSDL provided to me.
Would this be possible to do with WL7 ? Typically, one implements
a webservice using EJBs and such within WL, and the servicegen
script then creates the WSDL. However, this case is sort of in
reverse where the WSDL is already available and I need to
create a service that complies with this ...
thanx
-john

That still holds true.
Mike wrote:
Any updated info on when that will ship?
Last I heard it was 20-SEP?
Mike
"manoj cheenath" <[email protected]> wrote in message
news:[email protected]..
you need to wait for 7.0 sp1 which got a wsdl2service
ant task.
regards,
-manoj
"john" <[email protected]> wrote in message news:[email protected]..
Hi
I am implementing a webservice that will be a subscriber for
another external webservice. The provider of the external
webservice will give me the WSDL for the subscribers he
expects. So, I'll have to setup a webservice that implements
the WSDL provided to me.
Would this be possible to do with WL7 ? Typically, one implements
a webservice using EJBs and such within WL, and the servicegen
script then creates the WSDL. However, this case is sort of in
reverse where the WSDL is already available and I need to
create a service that complies with this ...
thanx
-john
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

APIs for parsing WSDL

Hi
Does 'Java technologies for Web services" have APIs for parsing WSDL files? Are there any open source implementations for parsing WSDL files.
Thanks
Pradeep

At present there is a JSR in the middle of being reviewed which is an API to handle WSDL files. JSR 110 gives all the important details. It will hopefully be release soon. What you could do is because WSDL is a xml-compliant you can produce your own xml parser specific to WSDL using JAXP.
HTH

External SOAP client Accessing Webservice using built in Java Data type

We have built a webservice and deployed it on WLS. We accessed this from a swing
client it works fine.The webservice methods uses non-built in JAVA data types
as parameters.These are Value Objects and the JAVA Serializer and Deserializer
classes are generated using Ant task itself.The client coding uses Value objects
given by the Client_jar (generated using <Clientgen> ant task) to pass to the
webservice. We dont want to go by this way.Is there anyway were in we can pass
parameters to the method which expects non-built in java datatypes?
Why i am asking this is, i want to know how an external client (.Net client )
will be able to exceute my webservice (i.e., passing the required Object which
the method is expecting)?

Hi Anish,
Well first off, your web service doesn't send or receive "objects". It only sends
and recieves XML, which is in turn converted to/from Java objects at invocation
time. Second, a .NET (or Perl, or Python, or C++) client will be able to call
your web service, because the wsdl.exe tool (for .NET) will generate "programming
language specific" objects from the <types><schema> elements, in the WSDL of your
web service :-) The wsdl.exe tool will create C# objects from the WSDL, that will
convert XML to/from C# when your web service is called. That's the beauty of XML
schema - it's a "universal typing system", so it's not tied to a particular programming
language. The only issue is whether or not the web services platform vendor's
XML Schema/WSDL processor, can successfully process the WSDL. Some vendors have
more complete implementations of the WSDL and XML Schema specs than others, so
expect varying success here. The one in WLS 7.0 is pretty good, so you shouldn't
have too many problems consuming WSDL generated by .NET tools (or any other tool
for that matter).
Regards,
Mike Wooten
"Anish" <[email protected]> wrote:
>
We have built a webservice and deployed it on WLS. We accessed this from
a swing
client it works fine.The webservice methods uses non-built in JAVA data
types
as parameters.These are Value Objects and the JAVA Serializer and Deserializer
classes are generated using Ant task itself.The client coding uses Value
objects
given by the Client_jar (generated using <Clientgen> ant task) to pass
to the
webservice. We dont want to go by this way.Is there anyway were in we
can pass
parameters to the method which expects non-built in java datatypes?
Why i am asking this is, i want to know how an external client (.Net
client )
will be able to exceute my webservice (i.e., passing the required Object
which
the method is expecting)?

How to install Soap on the (Apache) Oracle HTTP Server

Hi,
Does anyone know how to install SOAP on the Oracle HTTP Server? I downloaded a soap version (it seems that the standard version comes without SOAP) from the xml.apache.org site and followed the installation instructions as far as I could (only Tomcat is described). However, no 'soaping'!!! Maybe I'm overlooking something because I cannot imagine that it should be difficult.
Thanks in advance!
Hans

Hans, the SOAP implementation is part of OC4J. You get it out of the box. Check out how to use the out-of-the-box implementation in the tutorials on Web services with Oracle9i JDeveloper at:
http://otn.oracle.com/tech/webservices/htdocs/series/content.html
These tutorials/samples use the implementation of SOAP/WSDL that Oracle calls J2EE Web Services and this is the long term direction of Oracle's Web services implementation. This implementation is what Oracle will be evolving to Sun's Java Web Services Developer Pack as it finalizes into J2EE 1.4.
If you want to use Oracle/Apache SOAP, this too is included in OC4J but its support is being deprecated in future releases of Oracle9iAS in favour of the J2EE Web Services implementation. To find it, check out the OC4J/soap/webapps/ directory for the soap.ear file (it is in a slightly different spot if you are using the full Oracle9iAS R2 but still within the soap directory structure. Simply add <application name="soap" path="../../../soap/webapps/soap.ear" auto-start="true"/> to your OC4J server.xml and <web-app application="soap" name="soap" root="/soap" /> to your OC4J http-web-site.xml, re-start and away you go.
Finally, just to be sure, SOAP support in Oracle9iAS did not appear until 1.0.2.2.x and higher. If using 1.0.2.1 or less, you are correct, there is no SOAP support.
Mike.
Most folks that try out the J2EE Web Services find it is pretty easy to use so

高手指教:weblogic7.0上开发webservice的问题,多谢!

我在用weblogic7.0开发webservice应用时，遇到了几个问题，具体情况是：
1)我在webservice的方法中返回值为ArrayList，且ArrayList中若包含一些自定义类型，如javabean时，部署完成后，从确省的访问页执行此方法，出现下列错误信息：
javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException: mapping lookup failure. type=['http://www.w3.org/2001/XMLSchema']:anyType schema context=TypedSchemaContext{javaType=javax.xml.soap.SOAPElement}
注：但是若单独返回这个javabean没有问题
2）另外，如果返回的数据对象中包含中文数据的话，也会出现错误，具体信息如下：javax.xml.rpc.soap.SOAPFaultException: Error reading the response from: http://192.0.2.211:7001/basic_javaclass/HelloWorld. Please ensure that this is a valid SOAP response. The message was: l?q èq:œÔ

Hi Supine:
I had the same problem with blue_sky. I followed your instructions and that error msg disappeared. But I got another error message:
SERVICE FAULT:
Code:com.bea.xml.marshal.XmlEncodingException
String:Encountered an xml tag without a recognized type: the type must be declared with an xsi:type attribute.
Here is the service implementation and the wsdl file:
* @common:operation
* @jws:return-xml include-java-types="PersonName"
public ArrayList getNameList()
ArrayList names = new ArrayList();
PersonName name1 = new PersonName("Tom", "Bell");
names.add(name1);
PersonName name2 = new PersonName("John", "Smith");
names.add(name2);
return names;
<?xml version="1.0" encoding="utf-8"?>

<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/" xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.openuri.org/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://www.openuri.org/">
<types>
<s:schema elementFormDefault="qualified" targetNamespace="http://www.openuri.org/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:ope="http://www.openuri.org/">
<s:element name="getPersonName">
<s:complexType>
<s:sequence/>
</s:complexType>
</s:element>
<s:element name="getPersonNameResponse">
<s:complexType>
<s:sequence>
<s:element name="getPersonNameResult" type="ope:PersonName" minOccurs="0"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="PersonName" nillable="true" type="ope:PersonName"/>
<s:element name="getStringList">
<s:complexType>
<s:sequence/>
</s:complexType>
</s:element>
<s:element name="getStringListResponse">
<s:complexType>
<s:sequence>
<s:element name="getStringListResult" type="ope:List" minOccurs="0"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="List" nillable="true" type="ope:List"/>
<s:element name="getNameList">
<s:complexType>
<s:sequence/>
</s:complexType>
</s:element>
<s:element name="getNameListResponse">
<s:complexType>
<s:sequence>
<s:element name="getNameListResult" type="ope:List" minOccurs="0"/>
</s:sequence>
</s:complexType>
</s:element>
<s:complexType name="PersonName">
<s:sequence>
<s:element name="firstName" type="s:string" minOccurs="0"/>
<s:element name="lastName" type="s:string" minOccurs="0"/>
</s:sequence>
</s:complexType>
<s:complexType name="List">
<s:sequence>
<s:element name="item" type="s:anyType" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
</s:sequence>
</s:complexType>
</s:schema>
</types>
<message name="getPersonNameSoapIn">
<part name="parameters" element="s0:getPersonName"/>
</message>
<message name="getPersonNameSoapOut">
<part name="parameters" element="s0:getPersonNameResponse"/>
</message>
<message name="getStringListSoapIn">
<part name="parameters" element="s0:getStringList"/>
</message>
<message name="getStringListSoapOut">
<part name="parameters" element="s0:getStringListResponse"/>
</message>
<message name="getNameListSoapIn">
<part name="parameters" element="s0:getNameList"/>
</message>
<message name="getNameListSoapOut">
<part name="parameters" element="s0:getNameListResponse"/>
</message>
<message name="getPersonNameHttpGetIn"/>
<message name="getPersonNameHttpGetOut">
<part name="Body" element="s0:PersonName"/>
</message>
<message name="getStringListHttpGetIn"/>
<message name="getStringListHttpGetOut">
<part name="Body" element="s0:List"/>
</message>
<message name="getNameListHttpGetIn"/>
<message name="getNameListHttpGetOut">
<part name="Body" element="s0:List"/>
</message>
<message name="getPersonNameHttpPostIn"/>
<message name="getPersonNameHttpPostOut">
<part name="Body" element="s0:PersonName"/>
</message>
<message name="getStringListHttpPostIn"/>
<message name="getStringListHttpPostOut">
<part name="Body" element="s0:List"/>
</message>
<message name="getNameListHttpPostIn"/>
<message name="getNameListHttpPostOut">
<part name="Body" element="s0:List"/>
</message>
<portType name="helloServiceSoap">
<operation name="getPersonName">
<input message="s0:getPersonNameSoapIn"/>
<output message="s0:getPersonNameSoapOut"/>
</operation>
<operation name="getStringList">
<input message="s0:getStringListSoapIn"/>
<output message="s0:getStringListSoapOut"/>
</operation>
<operation name="getNameList">
<input message="s0:getNameListSoapIn"/>
<output message="s0:getNameListSoapOut"/>
</operation>
</portType>
<portType name="helloServiceHttpGet">
<operation name="getPersonName">
<input message="s0:getPersonNameHttpGetIn"/>
<output message="s0:getPersonNameHttpGetOut"/>
</operation>
<operation name="getStringList">
<input message="s0:getStringListHttpGetIn"/>
<output message="s0:getStringListHttpGetOut"/>
</operation>
<operation name="getNameList">
<input message="s0:getNameListHttpGetIn"/>
<output message="s0:getNameListHttpGetOut"/>
</operation>
</portType>
<portType name="helloServiceHttpPost">
<operation name="getPersonName">
<input message="s0:getPersonNameHttpPostIn"/>
<output message="s0:getPersonNameHttpPostOut"/>
</operation>
<operation name="getStringList">
<input message="s0:getStringListHttpPostIn"/>
<output message="s0:getStringListHttpPostOut"/>
</operation>
<operation name="getNameList">
<input message="s0:getNameListHttpPostIn"/>
<output message="s0:getNameListHttpPostOut"/>
</operation>
</portType>
<binding name="helloServiceSoap" type="s0:helloServiceSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="getPersonName">
<soap:operation soapAction="http://www.openuri.org/getPersonName" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="getStringList">
<soap:operation soapAction="http://www.openuri.org/getStringList" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="getNameList">
<soap:operation soapAction="http://www.openuri.org/getNameList" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<binding name="helloServiceHttpGet" type="s0:helloServiceHttpGet">
<http:binding verb="GET"/>
<operation name="getPersonName">
<http:operation location="/getPersonName"/>
<input>
<http:urlEncoded/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
<operation name="getStringList">
<http:operation location="/getStringList"/>
<input>
<http:urlEncoded/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
<operation name="getNameList">
<http:operation location="/getNameList"/>
<input>
<http:urlEncoded/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
</binding>
<binding name="helloServiceHttpPost" type="s0:helloServiceHttpPost">
<http:binding verb="POST"/>
<operation name="getPersonName">
<http:operation location="/getPersonName"/>
<input>
<mime:content type="application/x-www-form-urlencoded"/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
<operation name="getStringList">
<http:operation location="/getStringList"/>
<input>
<mime:content type="application/x-www-form-urlencoded"/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
<operation name="getNameList">
<http:operation location="/getNameList"/>
<input>
<mime:content type="application/x-www-form-urlencoded"/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
</binding>
<service name="helloService">
<port name="helloServiceSoap" binding="s0:helloServiceSoap">
<soap:address location="http://localhost:7001/RiskProfileEngineWeb/helloService.jws"/>
</port>
<port name="helloServiceHttpGet" binding="s0:helloServiceHttpGet">
<http:address location="http://localhost:7001/RiskProfileEngineWeb/helloService.jws"/>
</port>
<port name="helloServiceHttpPost" binding="s0:helloServiceHttpPost">
<http:address location="http://localhost:7001/RiskProfileEngineWeb/helloService.jws"/>
</port>
</service>
</definitions>
I can return a single object of PersonName and I can also return a list of Strings. I am stuck here. Any help is greatly appreciated.
solidrock

Immediate Response required for Fire-and-forget OSB pattern.

Hi,
I have a BPEL process (fire-and-forget pattern) which runs for few minutes, but want to send an immediate response back to the caller. The important condition is to have a Proxy implemented as a WSDL-based service type.
For this, I am calling BS (of BPEL process) in request pipeline and sending a changed $body in response pipeline; but the OSB response document us null, though in response pipeline, I do see $body getting replaced.
Any pointers will be really helpful.
Thnx,
Nikhil

like AbhishekJ said
if you defined your operation in the wsdl for the proxy service oneway and in the testconsole you do see the body is getting replaced after the routing is executed it's mostly like because of the oneway operation on your proxyservice itself, make it synchronous and do a test again?
or put a replace with some static xml in the response pipeline, remove the route and see if if still returns null
then you're pretty sure it's the oneway operation in the proxy wsdl itself

Can weblogic run serializer classes created by wscompile tool

Hi,
I am trying to deploy a webservice on weblogic.
This webservice implements a given wsdl.
I have created type mapping classes from 'wscompile' tool and not by 'autotype'
provided by weblogic as i want my code to follow JAX-RPC standards and it should
not depend upon weblogic classes.
when i package the webservice and deploy it on weblogic, i get the following error:
weblogic.webservice.server.ConfigException: failed to add type mapping to registry:
- with nested exception:
[java.lang.InstantiationException: com.egain.adapter.StartMonitoringResponse_LiteralSerializer]
at weblogic.webservice.server.WebServiceFactory.initTypeMaps(WebServiceFactory.java:228)
How can we deploy a webservice created with JAX-RPC standard (with either Apache
Axis or JWSDP) on weblogic?
I am using WLS 7.0 SP1.
Thanx for any help in advance.
Davinder

JAX-RPC serializer classes are not portable. So you can not use the
serializer classes
generated by Sun's RI in weblogic JAX-RPC runtime.
provided by weblogic as i want my code to follow JAX-RPC standards and itshould
not depend upon weblogic classes.You dont have to refer any weblogic specific classes to use WLS JAX-RPC
impl. You
only need to use the weblogic provied tools. The application code you write
is portable.
Check out the edoc for more details:
http://edocs.bea.com
-regards,
manoj
"davinder" <[email protected]> wrote in message
news:3e66e03a$[email protected]..
>
Hi,
I am trying to deploy a webservice on weblogic.
This webservice implements a given wsdl.
I have created type mapping classes from 'wscompile' tool and not by'autotype'
provided by weblogic as i want my code to follow JAX-RPC standards and itshould
not depend upon weblogic classes.
when i package the webservice and deploy it on weblogic, i get thefollowing error:
>
weblogic.webservice.server.ConfigException: failed to add type mapping toregistry:
- with nested exception:
[java.lang.InstantiationException:com.egain.adapter.StartMonitoringResponse_LiteralSerializer]
atweblogic.webservice.server.WebServiceFactory.initTypeMaps(WebServiceFactory.
java:228)
>
How can we deploy a webservice created with JAX-RPC standard (with eitherApache
Axis or JWSDP) on weblogic?
I am using WLS 7.0 SP1.
Thanx for any help in advance.
Davinder

RPC and XML based ?

Hi
We are in mid of confusion :-) between confusion between JAX RPC and XML based
web services. Now as i understand there are 2 ways of doing web service
1) JAX RPC
2) JAXM
My questiuon when do we use each of them and which would be deciding factor ?
Also say i make a service using java and servicegen. Deploy on weblogic 7.0. I
have my WSDL in place. Now can any client ( C or .NET) access my webservice as
far as they are able to grab my WSDL ?
DO we have tools like WSDL2JAVA for other languages. WSDL2C or WSDL2NET etc.
I am be too offf but am confused and need something to go ahead with weblogic
and java based sewrvice.
Thanks

To keep it simple, JAX-RPC provides an API for building web services and web service
clients that use RPC and XML. While JAXM is an API for XML-based messaging, where
using a messaging provider you can send/receive SOAP messages.
JAXM is used when you are doing a messaging (a la JMS or JavaMail) with SOAP messages.
I would suggest to refer to the following links for good starter course on web
services :
http://java.sun.com/webservices/docs/1.1/tutorial/doc/
http://dev2dev.bea.com/technologies/webservices/tutorials.jsp
In BEA WebLogic we provide "wsdl2service", which is an Ant task that takes as
input an existing WSDL file, and generates the following WebLogic Web service
components:
- the web-services.xml deployment descriptor file
- a Java source file that partially implements the Web service.
Now we probably we could have utilities provided by other vendors to generate
service components in a certain implementation from a WSDL.
Regards
Shridhar
"pranav" <[email protected]> wrote:
>
Hi
We are in mid of confusion :-) between confusion between JAX RPC and
XML based
web services. Now as i understand there are 2 ways of doing web service
1) JAX RPC
2) JAXM
My questiuon when do we use each of them and which would be deciding
factor ?
Also say i make a service using java and servicegen. Deploy on weblogic
7.0. I
have my WSDL in place. Now can any client ( C or .NET) access my webservice
as
far as they are able to grab my WSDL ?
DO we have tools like WSDL2JAVA for other languages. WSDL2C or WSDL2NET
etc.
I am be too offf but am confused and need something to go ahead with
weblogic
and java based sewrvice.
Thanks

HTTP params of the connection

Hi,
Is there any way how to get HTTP connection parameters/attributes when using WS?
I have WS on AS and client connect into it using SOAP over HTTP and I need to get HTTP attrs/params for the connection. The param(s) I'm interested in is SESSIONID/JSESSIONID.
Thanks to all.
Pat

Hello,
So, I found the solution to keep http cookies. (next questions are at the bottom of the message).
steps are these:
~~~
server:
~~~
1) use RPC style (when I try this with document style I received only errors when trying to create method Call).
2) create server implementation from the WSDL (or from scratch)
3) the server implementation has to implement javax.xml.rpc.server.ServiceLifecycle interface and provide necessary implementations
client:
~~~
1) generate implementation from the WSDL
2) follow the steps from the J2EE 1.4 tutorial section "Dynamic Invocation Interface Client"
3) when the login operation s successful, then over Call object do this:
Object cookieJar = call.getProperty("com.sun.xml.rpc.client.http.CookieJar");
the cookieJar contains (I hope) all cookie from the HTTP response
4) when creating next call after the login, simply setup the cookieJar as property, like this:
call.setProperty("com.sun.xml.rpc.client.http.CookieJar", cookieJar);
And that's it :-)
Questions:
~~~
1) Is it possible to create Call objects in the document WS style and how?
2) I think, better solution will be using SOAPMessage, etc. classes, but how to use them at all. Can someone point me to the sample which explains this way?
3) If there's another way how to do this, please let me know.
Thanks to all.
Pat

Possible Bug? autotype + wsdl2service generates implementation that does not conform to the WSDL

Hey folks,
I've got some hand crafted, valid, WS-I compliant WSDL + imported XSD that I've
been using for awhile now to generate an Apache Axis 1.2 beta Document Literal
Web Service implementation. I'm now trying to use the same WSDL to generate a
BEA WL 8.1 SP2 Document Literal Web Service implementation and I'm running into
problems.
I've attached the WSDL, XSD, and build script that I'm using to generate the implementation.
It deploys fine, but notice that the autogenerated WSDL that is returned from
the deployed BEA Web Service contains two <xs:schema> sections: one for the imported
WSDL (as expected) and one for several new elements that seem to get substituted
for the elements used in the orignal WSDL message parts.
The results of this are two fold:
1) the autogenerated WSDL appears to be invalid when loaded into both XMLSpy and
SOAPscope
2) the SOAP requests to invoke the operations on the service do not conform to
the hand crafted original WSDL. I've attached examples of both a BEA generated
SOAP request and an EXPECTED SOAP request.
I've poured over both the types.xml and the web-services.xml, and I'll be damned
if I can see the problem. I'm wondering if the way I import schemas and reference
elements declared therein is somehow not supported by BEA's ant tasks?
Any advice or pointers at all would be appreciated.
Regards,
-Jonathan Anderson
Booz Allen Hamilton
[BankService2.zip]

I don't know if you already now this but if you are using <autotype> to generate
the types.xml from the XML Schema then you should first
1) autotype the imported schema first.
2) Then for the actual achema (that uses the imported xsd) <autotype> but with
the
typeMappingFile="importedSchemas/types.xml"
option set to the types.xml output from 1)
The types.xml will then contain all types from both Schemas. You can then pass
this final types.xml from 2) to <source2wsdd> via
typesInfo="types.xml"
Any help ?
Pete
"Jonathan Anderson" <[email protected]> wrote:
>
Definitely seems as if BEA monitors these newsgroups. Lot's of developers
talking
to themselves, it seems.
<sigh>
"Jonathan Anderson" <[email protected]> wrote:
Hey folks,
I've got some hand crafted, valid, WS-I compliant WSDL + imported XSD
that I've
been using for awhile now to generate an Apache Axis 1.2 beta Document
Literal
Web Service implementation. I'm now trying to use the same WSDL togenerate
a
BEA WL 8.1 SP2 Document Literal Web Service implementation and I'm running
into
problems.
I've attached the WSDL, XSD, and build script that I'm using to generate
the implementation.
It deploys fine, but notice that the autogenerated WSDL that is returned
from
the deployed BEA Web Service contains two <xs:schema> sections: onefor
the imported
WSDL (as expected) and one for several new elements that seem to get
substituted
for the elements used in the orignal WSDL message parts.
The results of this are two fold:
1) the autogenerated WSDL appears to be invalid when loaded into both
XMLSpy and
SOAPscope
2) the SOAP requests to invoke the operations on the service do notconform
to
the hand crafted original WSDL. I've attached examples of both a BEA
generated
SOAP request and an EXPECTED SOAP request.
I've poured over both the types.xml and the web-services.xml, and I'll
be damned
if I can see the problem. I'm wondering if the way I import schemas
and reference
elements declared therein is somehow not supported by BEA's ant tasks?
Any advice or pointers at all would be appreciated.
Regards,
-Jonathan Anderson
Booz Allen Hamilton

Java implementation from WSDL file

Hello All
I am working on my thesis and have to deal with web services. I have a WSDL file where I have to create the Java implementation for and deploy it to TomCat which is comming with JWSDP1.3.
The steps I do are as follow:
1. Get the WSDL file
2. Create the config.xml file
3. run wscompile with "-import" option
4. implement service implementation (provider interface)
5. run wsdeploy tool
All tools are running successfully without exception. When I try to access the webservice I receive the following message from tomcat:
"No JAX-RPC context information available."
and I cannot access the webservice from my client program. The "hello" example works with my setup.
Below, please find my WSDL file and my config file as well as my provider interface implementation.
Thanks for your help.
===========
calculatesqrt1.wsdl:
<definitions xmlns:tns="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calcultesqrt1.wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calcultesqrt1.wsdl" name="Calculatesqrt1">
     <types/>
     <message name="CalculatesqrtProvider1_sqrt">
          <part name="double_1" type="xsd:double"/>
     </message>
     <message name="CalculatesqrtProvider1_sqrtResponse">
          <part name="result" type="xsd:double"/>
     </message>
     <portType name="CalculatesqrtProvider1">
          <operation name="sqrt" parameterOrder="double_1">
               <input message="tns:CalculatesqrtProvider1_sqrt"/>
               <output message="tns:CalculatesqrtProvider1_sqrtResponse"/>
          </operation>
     </portType>
     <binding name="CalculatesqrtProvider1Binding" type="tns:CalculatesqrtProvider1">
          <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="sqrt">
               <input>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calculatesqrt1.wsdl"/>
               </input>
               <output>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calculatesqrt1.wsdl"/>
               </output>
               <soap:operation/>
          </operation>
     </binding>
     <service name="Calculatesqrt1">
          <port name="CalculatesqrtProvider1Port" binding="tns:CalculatesqrtProvider1Binding">
               <soap:address location="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calcultesqrt1"/>
          </port>
     </service>
</definitions>
===========
config.xml:
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
     <wsdl location="Calculatesqrt1.wsdl" packageName="calcusqrt1">
     </wsdl>
</configuration>
============
CalculatesqrtServiceImpl1.java:
package calcusqrt1;
public class CalculatesqrtServiceImpl1 implements calcusqrt1.CalculatesqrtProvider1 {
public double sqrt(double double0) {
    return Math.sqrt(double0);

Please post future JAXRPC related questions to [email protected]
Sounds like it did not get deployed properly on the web server. You should be able to hit the URL for the
web service in a web browser to get an information.
The client will use the address stored in the WSDL to access the webservice, please make sure that it is correct. If you download the WSDL from the deployed service the address should be fixed up for you.

How many process in order to implement a multi-operations WSDL?

Hello everyone,
I have designed a WSDL describing two operations, that I want to implement with BPEL.
I was wondering whether I needed to implement two BPEL files independently, one for each operation, or I was compelled to put the orchestration of both operations in a single BPEL file, with the help of a pick activity to separate the flows.
I tried both ways and only succeeded with the latter, but I am not convinced with the approach. The first option falls short when building the CASA. I get a "WARNING: 1 port with 2 providers", and effectively only one operation is exposed.
According to you, what is the way to go?
Thanks

Hi, Ricardo,
Why do you need to do this? What is the business requirement that demands this? It seems like a waste of time and effort, and you'll have to re-do it every time a row is INSERTed or DELETEd, or when any of the columns involved is UPDATEd.
Given that you really want to do it, here's one way:
MERGE INTO     table_x          dst
USING (
           WITH    got_nums     AS
               SELECT key1, key2, filename
            ,       ROW_NUMBER () OVER ( ORDER BY key1 )
                                                   AS key_1_num
            ,       ROW_NUMBER () OVER ( ORDER BY SUBSTR (filename, -8)
                                               ,         key2
                              )     AS filename_num
            FROM    table_x
        SELECT k.key1
        ,        f.key2
        ,        f.filename
        FROM        got_nums     f
        JOIN        got_nums     k ON f.filename_num = k.key_1_num
       )               src
ON     (src.filename     = dst.filename)          -- or any unique column(s), not including key1
WHEN MATCHED
THEN UPDATE SET dst.key1 = src.key1
;If you'd care to post CREATE TABLE and INSERT statements for the sample data, then I could test it.
As posted above, this assumes that filename is unique. If not, you'll have to change the join condition between src and dst to guarantee a unique match.
This does NOT assume that filename is always 19 characters; only that it is at least 8 characters, and that the last 8 characters determine the order.

Outside-in service implementation from WSDL file for CAF and WS consumption

Hi All,
I'm having one of those weeks and struggling to get my head around a problem I have...
I'm working on a CE 7.2 system (with no ESR as it's only a demo at the moment) with an SOA architect to deliver some demo capability for a customer. The architect is defining contracts for services we plan to implement on the CE system and supplying them to me as a bundle of .wsdl and .xsd files.
I am trying to import these service contracts into my NWDS with the intention of implementing the logic behind them and then deploying the services to the CE system. I can then consume those services in Composite Apps, whilst other areas of the business can consume them direct as web services. Unfortunately, I've hit a brick wall and can't figure out how to achieve this.
Ordinarily I would create a CAF modelled app service based on an RFC or WSDL and then generate and deploy that but in this case, we want to define the WSDL first and then implement the logic behind it, ensuring the resultant service deployed to the CE runtime complies to the pre-defined service contract.
So, can anyone suggest how I go about this? I feel like I'm missing something really obvious but just can't seem to get going with this.
Thanks in advance,
Gareth.

Ok, been doing some more reading, thinking and testing.
Am I correct in thinking the only way to use this outside-in approach is to have the ESR activated on CE. My SOA architect can then define the service interface/contract in the ESR, and I can then import this into NWDS and build the implementation?
I'm trying to get to a point where a CAF implemented application complies with a pre-defined WSDL definition but I really don't think this is possible actually.
Gareth.

How to create the WSDL using the search function is to implement it ?

Hi
I have a question to everyone.
I have developed LivecycleDesigner now.
PDF Once the search process was conducted in the screen press the search button, the ability to display search results and we want to create PDF on the screen.
I want to implement a WSDL to connect, not handled properly.
MicrosoftInfoPath has been successfully processed, the WSDL no problem I think.
Would you be able to advise?
I would like a sample if possible.
Thanks and best regards,

Mingfei is correct, you probably have no Streaming Reserved Unit configured in your account.
Dynamic packaging from MP4 to Smooth, HLS, and DASH only works if you have a Streaming RU turned on. Otherwise, you can only progressive download the MP4 files or use the Smooth Streaming encoding presets only (which will not support dynamic packaging to
HLS and DASH).
Have you tried to use the Azure Media Explorer tool to test this out again? I think you will find that it works just fine through the AME tool.
The tool will show you the existing streaming Locators on your asset and it will give you access to multiple Players that can play the video back.
You can find the installation package on http://aka.ms/amse
Once you install it, encode and publish your asset, and then use the Publish->Playback menu to test out the stream.

Implementing an XI WSDL

Similar Messages

Maybe you are looking for