Wsdl issue

Hi All,
I have a SOAP-XI-RFC scenario. I created WSDL from the wizard and when i test it from .Net client
i am getting "unable to import binding from Namespace"
when i test the same wsdl with Soapsonar i am not getting any errors.
I am not getting why this error is occuring when testing from .Net client
Help would be greatly appreciated and rewarded with points
Thanks,
sneha

Sneha,
Try with XML Spy. if it works with XML spy then I guess there is no issue in your WSDL and there is some problem with your .Net client
Regards
Bhavesh

Similar Messages

WSDL issue in Apex 4.0

Hi All
I am just beginning to broach the area of web services with APEX and running into some issues..
Environment I am working in:
Apex 4.0
Oracle 11.2.0.1.0 database
OHS Server
Unix OS
I have the following wdsl from a web service developed in house here:
http://appclstr1.oft.state.nyenet/wilma/getsetdataws.asmx?op=getDataNoSerialization
partial code -
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://sdc.oft.state.nyenet/wilma" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://sdc.oft.state.nyenet/wilma" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:types>
<wsdl:operation name="getlargeDataNoSerialization">
<soap:operation soapAction="http://sdc.oft.state.nyenet/wilma/getlargeDataNoSerialization" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
Here is where the problem starts.
1) I wanted to use Apex-Shared Componments- Create Web Service Reference - provide wsdl
No luck I received the error below. (Also when I tried to create it manually within Apex I got the same error)
Error
ORA-20001: The webservice was unreachable because either the URL you supplied was invalid, your environment requires a valid proxy server address for HTTP requests, or a wallet needs to be configured for HTTPS requests.
Error sending request.
Also when choosing one from the dropdown like amazon I get the same error.
2) I've search forums etc.. on the problem. Many say it's a problem with the ACL?? See below
Is is true that a host can only have one acl?
select host, lower_port, upper_port, acl from dba_network_acls order by acl;
HOST LOWER_PORT UPPER_PORT ACL
* */sys/acls/power_users.xml*
smtp.nysemail.nyenet 2525 2525 /sys/acls/utlpkg.xml
smtp.nysemail.nyenet /sys/acls/utlpkg.xml
* 20 5000 /sys/acls/utlpkg.xml
select acl, principal, privilege, is_grant from dba_network_acl_privileges;
ACL PRINCIPAL PRIVILEGE IS_GRANT
/sys/acls/utlpkg.xml CONNECT connect true
/sys/acls/utlpkg.xml ML_TEST connect true
/sys/acls/utlpkg.xml QYDDBA connect true
/sys/acls/utlpkg.xml ACTR connect true
/sys/acls/utlpkg.xml GINODBA connect true
/sys/acls/utlpkg.xml CMSDBA connect true
/sys/acls/utlpkg.xml APEX_040000 connect true
/sys/acls/power_users.xml APEX_040000 connect true
3) Additonal Details - I can open the url (webservice) in my browser no problem, I can append the ?wsdl and get the soap info which I used in my attempt to create one manually. It is not https so i do not need to create a wallet.
I also tried to copy my proxy server info from my broswer into the apex application definition page and try to create the web reference - did not work.
Query on the db-
SELECT DBMS_XDB.getPrivileges('/xdbconfig.xml').getCLOBVal() FROM DUAL;
DBMS_XDB.GETPRIVILEGES('/XDBCONFIG.XML').GETCLOBVAL()
<privilege xmlns="http://xmlns.oracle.com/xdb/acl.xsd" xmlns:xsi="http://www.w3.
This is all new terriority for me so any help would be greatly appreciated.

Hi Again
I have more info on the issue...
I tried to reach the the webservice from OAS/HTTP with mod_plsql directly. At first I was not able to.
A firewall request was completed and now I am sure the http server can reach the webservice in question.
Unfortunatley creating a webservice either manually or through a wsdl is still not working! Please Help , what else can I check.
Also
I'm confused ..taken from APEX 4.0 online documenation
SOAP offers two primary advantages:
SOAP is based on XML, and therefore easy to use.
SOAP messages are not blocked by firewalls because this protocol uses simple transport protocols, such as HTTP.
I can't see why it would be a firewall issue based on the statement above.
Thanks Again
Moe
-- just added to my post. Issue still unresolved
I'vw been trying to troubleshoot it myself.
From my database server -
I'm not able to use utl_http - example
set serveroutput on
DECLARE
req utl_http.req;
resp utl_http.resp;
value VARCHAR2(32000);
BEGIN
req := utl_http.begin_request('http://www.psoug.org');
resp := utl_http.get_response(req);
value := utl_http.request('http://www.psoug.org/');
dbms_output.put_line(value);
utl_http.end_response(resp);
EXCEPTION
WHEN utl_http.end_of_body THEN
utl_http.end_response(resp);
END;
error received is
ERROR at line 1:
ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1130
ORA-12535: TNS:operation timed out
ORA-06512: at line 6
Using ping
ping www.psoug.orgPING 66.221.222.85: 64 byte packets
----66.221.222.85 PING Statistics----
16 packets transmitted, 0 packets received, 100% packet loss
However I'm confused if I'm using Oracle Application Server 10g Release 3 (10.1.3.1)/Apache
Should I need to modify the firewall on the database side to access a webservice? Does it need to be port 80?
Getting frustrated by my ignorance
Thanks
Moe
Edited by: user570478 on Jul 28, 2011 2:23 PM

SOAP adapter: WSDL issue

Hi Experts,
I am working on File-XI-->Mail scenrio using SOAP adapter. My file contains only one line fields say:
TATA 407
I have configered File adapter perfectly and CC of it is showing perferctly green (Data is coming in MONI). On the counter SOAP side, I would like to send this file to the Gmail. But I am not able to do this due to the fact that I am not understanding the WSDL ? I have read several doucments but not one is giving the perfect idea about it.
Please tell me how to accomplish it. Please avoid to send the links. Please help ASAP.
-=Soniya=-

Hi Soniya,
>>I do agree that Mail adapter can be used in place of SOAP
No, it's not that.
SOAP and Mail adapter are two different things. SOAP adapter is used to exchange SOAP messages (do not confuse "message" with "email message") between applications (XI/PI to third pary OR third-party application to XI/PI) using SOAP/HTTP protocol. Whereas Mail adapter is used to send email using IMAP/POP3 protocol.
>>Somebody is saying that Webservices are the one, where you send your messages either side people are saying.
Correct. You can configure SOAP adapter as sender in PI and receive SOAP messages in PI sent by some third-party application. OR you can configure SOAP adapter as receiver and post the message form PI to some third-party provided URL.
For exposing webservice from PI all you need to do is to go to Integration directory. Select the sender aggrement you want to puslish as web service. From TOOLS menu say display WSDL. Save this WSDL and provide it to client/third-party application. They will have to generate the client proxy class and post the message from there to PI.
For cosuming webservice in PI (posting message from PI), third-party application has to provide you with a URL which you will enter into SOAP receiver type adapter.
Regards.

Generated WSDL Issue - Glassfish App Server

Hi,
I am at a loss as to how to modify the generated WSDL and associated schema for a webservice I am deploying to Glassfish V2 Milestone 4 - Build 33. I'm using EJB 3.0 and the entity beans I developed have one to many and many to one references to each other:
An OverrideVersion contains a reference to the OverrideRequest it belongs to. There can be numerous OverrideVersions. I've tested the database code extensively and there is no problem performing saves and retrieves. The following is taken from the OverrideVersion class:
@ManyToOne
@JoinColumn(name="request", referencedColumnName="pricingRef")
private OverrideRequest request;and this is from the OverrideRequest class:
@OneToMany(mappedBy="request", cascade=CascadeType.ALL,
          fetch = FetchType.EAGER)
private Set<OverrideVersion> overrideVersionCollection;The problem is that if I leave the app server to generate the WSDL these references are generated, which I don't want - I only want the Verson to reference :
<xs:complexType name="overrideVersion">
<xs:sequence>
    <xs:element name="request" type="tns:overrideRequest" minOccurs="0"/>
</xs:sequence>
</xs:complexType>and<xs:complexType name="overrideRequest">
<xs:sequence>
    <xs:element name="overrideVersionCollection" type="tns:overrideVersion" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>I need to be able to change the WSDL as I am getting the following error on retrieves:
com.sun.istack.SAXException2: A cycle is detected in the object graph. This will cause infinitely deep XML:I followed the advice in http://forum.java.sun.com/thread.jspa?threadID=725485&messageID=4184020
"For now, the way is to do this manually : stop the app server, edit the as_install_dir/domains/domain1/generated/xml/j2ee-{apps|modules}/{your-app}/{META|WEB}-INF/wsdl/XXXXX.wsdl, and restart the app server"
but no matter what I do the changes I make to the generated WSDL and schema files aren't refelected in the actual WSDL at the ?WSDL address.
So I decided to take the generated WSDL file, modify it (remove the cyclic references), and drop it in my applications META-INF/wsdl directory (along with the previously generated schema) and specify the @WebService wsdlLocation attribute in my stateless session bean:
@WebService(serviceName="PricingService",
          portName="PricingServicePort",
          wsdlLocation="META-INF/wsdl/PricingService.wsdl")But after deployment I try to access the WSDL (at the same address as the previous generated WSDL http://localhost:8080/PricingService/PricingService?wsdl) and get a plain white HTML page with: Invalid wsdl request http://localhost:8080/PricingService/PricingServiceI haven't been able to come up with a solution to this problem either.
This is doing my head in so any help would be greatly appreciated.
Thanks.

Hi Arvind,
First thing u shud do is..for invoking a webservice through XI do not import all the WSDLs ....Import only the WSDL under the porttypes....
Port types defines the interface in XI...Once u import them....Then check the msg type.....As per u info u shud see them as
getAuthorizationIn_doc---request
getAuthorizationOut_doc---Response..
If u want something more plz ask
Regards,
AshwinM
Note:- Reward If helpful

BPEL wsdl & issue with WS-I Profile check...

Hi all,
The .WSDL file corresponding to a BPEL always has an additional <partnerlinkType> element at the end.
This causes some tools that do a WS-I Profile check to report it as a failure to conform to standards (Of course, since it is an "extra" element NOT supposed to be there in a 'standard, portable' WSDL file..)
(How Can i ?!? and...)Can i manually remove this element..?!?
Or should i ignore this error/failure...?!?
What do you people suggest/follow..?!?
(Personally, i feel it should be there...)
Many Thanks..!

Thanks for some pointers...
But, i feel the Amazon/Google WSDL's do NOT have partnerlinkType elements in them simply (perhaps) because they represent "plain vanilla Web-services" & not BPEL processes.
The problem fer me is that when i develop & deploy a BPEL process, the associated WSDL for that process automatically/always has 1 or more partnerlinkType elements in it.
Kindly let me know your views on this, dear friends..
Thanks again...!!

Help to Configure Connection Pool For Jdeveloper

Hi ,
I am using Jdeveloper 10.1.2 and Oravle AS 10.1.2.
Language Used : J2EE,Struts and EJB
I am portletizing struts application.
I need help to configure Connection pool. By default it is taking a datasource.xml not the one i had defined. Pls help me out. Affecting the performance due to so many hit to db.
regards,
Jayashree Jegan

Hi John,
Go through this thread of mine. You will get the required information to setup the connection pool.
SOAP adapter: WSDL issue
Also just check in Visual Studio Help .NET Connector for Connection Config class settings. You will see all the relevent parameters related with connection pool.
Regards.

Get a single OBR composite being used outside of SOA.

Hi every one.
I have a SOA composite application composed of a web service upstream of a business rule only (no Mediator neither BPEL process). I am able to test it in soa-infra in EM without any issue.
I have a main question/problem.
It's about the possibility to transform my composite in a web service that would be consumed in a html page. I have been struggling for days on how to invoke using soap binding without any result. Is it possible? Any clue on how to do it?
thank you for your help.
RD

I actually checked those pages. I always ask my friend Google first.
I is not working as the WSDL generated by Jdev has a architecture different than a WSDL issued from a java class. Therefore I cannot find any example specific on how to do it from SOA composites.
I don't even know if someone tried it or if it is possible.
Regards,
RD

Issue with provided message for WSDL of SAP PI sender interface

Hi,
as I am not familar with SOAP interfaces and use of WSDL by partners with WSDL generated in SAP PI there are some issues that I have with a scenario:
1. Import of external xsd for message is done
2. Enterprise Repository and Integration Directory objects are completely created and activated
3. WSDL was generated from ID Sender agreement (This is PI 7.1)
4. Partner got the WSDL
The partner provided now some test messages by mail that I would like to test in the mapping as the message is really complex.
But the result is strange...
1. The header of the partner message is this:
<XJustiz_Daten xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Grunddaten xmlns="http://www.xjustiz.de">
(Some german words are in that example. But this doesn t matter!)
This is different to the xml that PI generates in mapping:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:XJustiz_Daten xmlns:ns0="http://www.xjustiz.de">
   <ns0:Grunddaten>
      <ns0:Grunddaten XJustizVersion="">
Partner defines xsi:   instead of ns0   and PI fails using this message!
So I had to change the message header and add ns0: to all element tags and node tags of the message.
(See for example with first node "Grunddaten").
2. There are some mandatory nodes and elements.
An example:
- Rechtsform is mandatory node (1..1) with element content (mandatory 1..1)
So it will appear in the payload like this:
                    <ns0:Rechtsform>
                            <ns0:content xmlns=""/>
                     </ns0:Rechtsform>
But the partner provides this:
<Rechtsform xsi:nil="true" />
which is the next issue as PI doesn t understand as xsi is not mapped to a namespace. !
It would be easy to use an "exist" function to solve the issue with the not provided element but this will not help
when the node is provided with additinal information xsi:....
Can you give any help/answer why PI is not able to handle such things.
Thank you!
Best regards
Dirk

Hello Meinhard,
If you are the Service Owner, the sender system must use your wsdl message (WebService Definition).
If there're other problems or the sender system can't use your message structure, in agreement with them you need to develope a different mapping.

Issues with WSDL file loading in BPEL process Composite

hi',
I am facing lot of issues in 11G
I am using:-->"Jdeveloper Studio Edition Version 11.1.1.2.0"
When I am trying to open a already working composite from a different machine in my machine, it start giving error
it is unable to build "Unable to load WSDL file", I have all the webservices in different machine OSB and my machine
is targeting that machine OSB with IP address, In my BPEL process I am using localhost, I am able to see all the methods
in composite and dosent shows any error, but when I try to compile it it gives unable to load WSDL file.
please advice,
thanks
Yatan

I suppose, any unhandled exception in the one-way BPEL process could have caused rollback of the instance and hence the instance might not be seen. Add fault handlers-catch/catch-all blocks in the one-way BPEL process if not done already, and test.

WSDL, custom datatypes, fault element name issues

Hello all,
I am having a LOT of problems with BEAs webservices. I am posting
this here in the hope that someone can help me and tell me what I am
doing incorrectly. I am running
WebLogic Server 7.0 SP1 Mon Sep 9 22:46:58 PDT 2002 206753
WebLogic XMLX Module 7.0 SP1 Mon Sep 9 22:54:41 PDT 2002 206753
Background:
My goal is to make my company's product web services aware. I take an
EJB, try to run it through the standard ant tasks and generate a web
services accessible EJB. Sounds pretty easy, but complex types seem
to make this quite difficult.
I have been able to create a web service accessible EJB (only since
7.0.1), but I am quite unhappy with the quality of what I am able to
produce.
I have a datatype which acts as a key, but it does not follow the
javabeans idiom - i.e. it does not have a default constructor or
accessor methods and I am not in the position to change it. I have
created a codec for this class which works and an xml schema (both by
hand). Its name is AgentKey. I have also had to use the autotyper to
create codecs and typemapping entries for java.util.Properties,
I can connect using the WebLogic classes and I am now trying to
interact using MS Excel and Apache's Axis as my test clients.
Issues:
My first question deals with generating a client. There seem to be
two ways to generate a client. Firstly via the <client> subtask of
<servicegen><service>, the second way via <clientgen> task. Since I
am using a custom data type (AgentKey) I have to manually insert the
AgentKey schema into the web-services.xml file generated by
servicegen. When I try to generate a client via the
servicegen/service/client task there is no opportunity for me to
insert this datatype schema information and I therefore get the
following messages (lots of them, but I'm only including one):
[servicegen] WARNINIG: Unable to find a javaType for the xmlType:['java:net.agentis.apml.runtime']:AgentKey.
Make sure that you have registered this xml type in the type mapping
[servicegen] Using SOAPElement instead
BTW: I am also receiving the same problem with java.util.Properties.
BTW: WARNING is misspelt
If I attempt to generate a client class via the <clientgen> task, I
need to supply either a wsdl or ear file as a parameter. I cannot
supply a wsdl file because I haven't deployed the EAR yet (and I don't
want to until the EAR has the client classes in it), and I can't
supply the EAR because I want the ear to include the client classes.
It is a bit of a catch 22 situation. Is there a solution I can't see?
NOTE: it would be very, very nice if you added a schemaMapping
attribute to the <servicegen/service> task so the web-services.xml
file didn't have to be manually hacked. Something similar to the
typemapping attribute already in the servicegen/service task would do
it.
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?
Another problem with the WSDL (once you have cleansed the multiple
exception messages) is that the fault elements of the
binding/operation elements require names and they don't have any. For
example, this is straight from the deployed EJB WSDL file:
<binding name="ExampleAgentPortSoapBinding" type="tns:ExampleAgentPort">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="serviceWithPrimitiveDatatypes">
<soap:operation soapAction="" style="rpc"/>
<input>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
<fault>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</fault>
</operation>
<operation ...
The schema definition at http://schemas.xmlsoap.org/wsdl/ says the
fault element require a name attribute:
<complexType name =" tBindingOperationFault">
<complexContent>
<extension base="wsdl:tExtensibleDocumented">
<attribute name="name" type="NCName" use="required"/>
</extension>
</complexContent>
</complexType>
The name of the fault should be the same name as the fault in the
portType definition. In my example the name is "AgentisException" as
evidenced by this snippet:
<portType name="ExampleAgentPort">
<operation name="serviceWithPrimitiveDatatypes">
<input message="tns:serviceWithPrimitiveDatatypes"/>
<output message="tns:serviceWithPrimitiveDatatypesResponse"/>
<fault name="AgentisException" message="tns:AgentisException"/>
</operation>
Once these changes have been made then the WSDL will validate. Are
there plans to fix these bugs?
On a different note, when I try to interact with a method that uses a
custom data type, such as AgentKey, via the "WebLogic Webservice
standard testing home page" the custom data type without a default
constructor cannot be rendered correctly. For instance, the AgentKey
value is:

<agentKey/>
Since I can't deploy a valid WSDL, I can't get either Axis or Excel to
connect to my web services.
When I attempt to invoke Axis' (beta 1.1) wsdl2java I recieve the
following message.
java.io.IOException: ERROR: Fault is missing a name= attribute in operation
"serviceWithPrimitiveDatatypes", in binding {http://sillyurl.com/reallysilly}ExampleAgentPortSoapBinding.
This seems understandable considering the issues I mentioned earlier.
Unfortunately Excel doesn't really give me anything to go with. If I
type in the WSDL URI then it will give me a list of methods I can
invoke, but if I try to add the service I get the very unhelpful "The
Web Service References Tool could not generate the requested code.
Any changes that were made to your project have been rolled back."
Any help with those two issues would be greatly appreciated also.
One final issue is that I cannot seem to fix is taskdef'ing
<servicegen> properly from Ant. I can do the actual taskdef but then
it cannot find classes from within the weblogic.jar. If I run the
setExamplesEnv.cmd first the I don't need to do the taskdef and
everything works fine. Has anyone else had this issue? (we can't run
that command on our clients desktops before we build our build scripts
- anyway, I've put it down to one of those weird Ant classpath
issues.)
In summary:
Problems I can see and would like some help on are:
- multiple exception messages
- fault operations with no name
- the ability to generate client code with complex data types before
the EAR is deployed.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
I know this has been quite a long email, but it has been months in the
making. Anyone's time would be greatly appreciated.
Mark Mansour
Agentis Software
[email protected]

Hi Mark,
From your base post:
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDL seems to be the root of most of
your issues.
Concerning the upcoming release, I believe it is scheduled for late this quarter; contact Michael
([email protected]) for more information.
Also, at the bottom of this post:
I would just like to see an automated way to do this (I've had to write my own
utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a look at this?
http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
Thanks,
Bruce
Mark Mansour wrote:
Hiya Bruce,
I will try and get some time to follow this up with the support people too.
In response:
Problems I can see and would like some help on are:
- multiple exception messages
In your client code, you can set the following property to avoid the exceptionmessages so that the typemapping
registry can be setup.
//dont parse wsdl till we set the typemapping
System.setProperty( "weblogic.webservice.servicenamechecking","false" );
This is not a client issue. The WSDL is generating incorrect WSDL. Here is a
little snippet :
<message name="AgentisException" >
<part name="AgentisException" xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
<message name="setTraceLevel" >
<part name="agentKey" xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
/>
<part name="intVal" xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
/>
</message>
<message name="AgentisException" >
<part name="AgentisException" xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
As you can see the AgentisException is defined twice (in my real WSDL it is redefined
every time a method has the AgentisException in its interface (which in my case
is 5 times))
- fault operations with no nameI believe the fault issues that you have raised have been addressed in the upcomingrelease that will be
available for beta testing shortly. Contact [email protected] if you
want to participate in the beta.
great. Is there any ETA on the final release date?
- the ability to generate client code with complex data types before
the EAR is deployed.
There is an example to show how to do this: http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
Unfortunately this doesn't solve my problem. I still don't have an EAR or WSDL
file from which I can generate a client to be included in the final EAR file that
gets deployed to the server. My original post explains this a bit better.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
Take a look at http://dev2dev.bea.com/direct/webservice/wswa.html#qz50 and others
in this area.
This was more in reference to the building of the web services in the first place
rather than registering custom datatypes at runtime. The manual procedure is
documented at http://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
I would just like to see an automated way to do this (I've had to write my own
utility to do this for me :(
Hope this helps,
Bruce
Thanks Bruce.
Mark

Bpelc issues with WSDL schema definition

Hi,
I have been attempting to deploy a relative simple BPEL example, developed using the BPEL Designer Eclipse plugin and deployed on BPEL Process Manager.
The BPEL consists of receiving a SOAP message, copying variables using assign from the input message to a message defined in an external WSDL, invoking that WSDL's service and copying the results of that service into the output message.
To design the external service, I developed a simple Java class in Apache Axis and used the Java2WSDL tool to create all the interfaces. I then copied that WSDL to the BPEL designer and started to design the BPEL.
The problem is to do with the definition of messages within the WSDL, the following snippet is from the WSDL generated in Apache Axis:
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
     targetNamespace="http://mdsuk.com/wsdl/example/PSP1">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<complexType name="OutputCT">
<sequence>
<element name="message" nillable="true" type="xsd:string"/>
<element name="paymentReference" nillable="true" type="xsd:string"/>
<element name="success" nillable="true" type="xsd:boolean"/>
</sequence>
</complexType>
</schema>
</wsdl:types>
I then tried to create the <assign> statement for the External Service Message -> BPEL Output Message using BPEL Designer using the visual editor, it generated the following code:
<assign name="assign-2">
<copy>
     <from variable="pspOutput" part="outputCT" query="/message"></from>
     <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:result"/>
</copy>
<copy>
     <from variable="pspOutput" part="outputCT" query="/success"></from>
     <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:success"/>
</copy>
</assign>
Trying to compile this generated code resulted in:
[bpelc] [Error ORABPEL-10057]: invalid query
[bpelc] [Description]: in line 94 of "D:\EclipseWorkspace\OrderTest\OrderTest.bpel", query "/message" is invalid, because step 'message' is not valid..
[bpelc] [Potential fix]: Check the XML schema and make sure your query string is valid.
[bpelc]
[bpelc] [Error ORABPEL-10057]: invalid query
[bpelc] [Description]: in line 98 of "D:\EclipseWorkspace\OrderTest\OrderTest.bpel", query "/success" is invalid, because step 'success' is not valid..
[bpelc] [Potential fix]: Check the XML schema and make sure your query string is valid.
So, the generated code from BPEL Designer was failing to compile. This resulted in a long check of the code, finally I realised that it expected the inputCT variable to be present in the XPath, so I manually changed the code to
<assign name="assign-2">
<copy>
     <from variable="pspOutput" part="outputCT" query="/outputCT/message"></from>
     <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:result"/>
</copy>
<copy>
     <from variable="pspOutput" part="outputCT" query="/outputCT/success"></from>
     <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:success"/>
</copy>
</assign>
This allowed to code to compile, so I deployed the BPEL to the Process Manager, and invoked a query using the Web Interface.
The BPEL started up fine, it invoked my external Axis Web Service, Axis produced the output (visible via debugging) however Process Manager tried to process the output, it crashed with the following exception:
06/01/19 16:29:11 com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.xmlsoap.org/ws/2003/03/business-process/}selectionFailure}
messageType: {null}
parts: {{summary=<summary>empty variable/expression result.
xpath variable/expression expression "/outputCT/message" is empty at line 94, when attempting reading/copying it.
Please make sure the variable/expression result "/outputCT/message" is not empty.
</summary>}}
So, the compiled BPEL code, which had the WSDL schema to compare against was failing during execution, I inspected the output from the Axis Web Service, which was:
<?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>
<processPaymentResponse xmlns="http://mdsuk.com/wsdl/example/PSP1">
<outputCT xmlns="">
<ns1:message xmlns:ns1="http://mdsuk.com/wsdl/example/PSP1">Payment Succesful</ns1:message>
<ns2:paymentReference xmlns:ns2="http://mdsuk.com/wsdl/example/PSP1">1137688175137</ns2:paymentReference>
<ns3:success xmlns:ns3="http://mdsuk.com/wsdl/example/PSP1">true</ns3:success>
</outputCT>
</processPaymentResponse>
</soapenv:Body>
</soapenv:Envelope>
The key difference was that the message / paymentReference and success attributes were prefixed with the namespace "http://mdsuk.com/wsdl/example/PSP1" , this makes sense as the schema has the attribute targetNamespace="http://mdsuk.com/wsdl/example/PSP1".
However, when I tried to modify the BPEL to read:
<assign name="assign-2">
<copy>
     <from variable="pspOutput" part="outputCT" query="/outputCT/nsxml1:message"></from>
     <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:result"/>
</copy>
<copy>
     <from variable="pspOutput" part="outputCT" query="/outputCT/nsxml1:success"></from>
     <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:success"/>
</copy>
</assign>
It complained:
[bpelc] [Error ORABPEL-10057]: invalid query
[bpelc] [Description]: in line 94 of "D:\EclipseWorkspace\OrderTest\OrderTest.bpel", query "/outputCT/nsxml1:message" is invalid, because step 'nsxml1:message' is not valid..
[bpelc] [Potential fix]: Check the XML schema and make sure your query string is valid.
[bpelc]
[bpelc] [Error ORABPEL-10057]: invalid query
[bpelc] [Description]: in line 98 of "D:\EclipseWorkspace\OrderTest\OrderTest.bpel", query "/outputCT/nsxml1:sucess" is invalid, because step 'nsxml1:sucess' is not valid..
[bpelc] [Potential fix]: Check the XML schema and make sure your query string is valid.
[bpelc] .
So, the BPEL would not validate against the WSDL schema that was being produced, I read up on the W3 Schema specification, and found that the schema can take the attribute elementFormDefault - this attribute takes the values 'qualified' or 'unqualified'. If qualified, then it explicitly states that all children elements should be beloning to the namespace of this element.
So, I changed the schema to read:
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
     targetNamespace="http://mdsuk.com/wsdl/example/PSP1"
     elementFormDefault="qualified">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<complexType name="OutputCT">
<sequence>
<element name="message" nillable="true" type="xsd:string"/>
<element name="paymentReference" nillable="true" type="xsd:string"/>
<element name="success" nillable="true" type="xsd:boolean"/>
</sequence>
</complexType>
</schema>
</wsdl:types>
The BPEL compiled and ran succesfully.
However, the problem/issue here is, Oracle bpelc assumed that if the elementFormDefault attribute was missing from the schema definition, it defaulted to unqualified, even with the targetNamespace attribute present.
Axis and <oXygen/> XML Editors, in which I tested the WSDL code, assumed that if the elementFormDefault attribute was missing, it defaulted to qualified.
I cannot find anything in the Schema Specification to say which is correct - can anyone shed any light on this? I also want to make Oracle BPEL users aware of this issue.
Regards,
Peter Dolukhanov

I resolved this issue by adding the following to the 2nd schema in the wsdl
xmlns:xsdLocal1="urn:/crmondemand/xml/integrationevent"
inside the 2nd schema
<xsd:schema
elementFormDefault="qualified"
attributeFormDefault="unqualified"
xmlns:xsdLocal1="urn:/crmondemand/xml/integrationevent"
targetNamespace="urn:crmondemand/ws/integrationevent/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
and this line immediately below it
<xsd:import namespace="urn:/crmondemand/xml/integrationevent" />
I could then create a proxy class using wsdl.exe

Issue with WSDL created for sender agreement

Hi,
Can you please help me why I am getting the erroe with WSDL that has been created from directory Sener agreement in PI 7.1 EHP1?
My interface is a SOAP to file ASYNC scenario and we have been given 5 XSDs that are referencing one each other ,5 XSDs are imported successfully and referenced properly,no errors/issues found.
Created all ESr and directory objects and I tried creating WSDL from sender agreement for my Source/outbound inteface that is created with XSDs in ESR.
When I try to import WSDL into SOPA UI to validate ,the import process stuck for ever while trying to import "http://www.w3.org/2001/xml.xsd" and finally throws me error.
After that I tried importing WSDL created in Directory into AltovaXML spy to created the webservice request,I am getting the following error""invalid XML Schema:"xml:lang" is already declared in the schema dcument C:|..my WSDL.
Even our partner who wants to make Webservice calls using this WSDL,they are not able to develop their Webservices they are getting errors something related to schema not found /not defined etc.
Please let me know,what might be the issue?I verified several times with my XSD imports and referencing properly and configuration objects.
Thank you for your help in advance.
Regards,
Prem

Hi Mark,
I am not getting issue while displaying/Exporting as WSDL in ESR.I am getting issue while trying import WSDL that is generated out of Service Interface into SOAP UI or Altova XML Spy.
I don't think PI created the WSDl out of W3 standards.
This is the error I am getting in XML Spy:
File C:\Documents and Settings\Prem\Desktop\SI_XYZ_O.wsdl is not valid
Invalid XML schema: ''xml:lang' is already declared.
Error location: schema / attribute++
and in SOAP UI:It is trying to import the WSDL and it stuck for ever while trying to import http://www.w3.org/2001/xml.xsd and never imprts the WSDL into SOAP UI project.
Please let me know,if you have any ideas.
Thank you,
Prem.

Issue with external WSDL in own Outbound interface using SOAP UI

Hello,
this is the issue:
a) Imported an external WSDL to PI as external definition
b) Added external definition to a sync. Service interface
c) Completed configuration and created a WSDL from the sender agreement in Directory (this is PI 7.1)
d) imported the WSDL from c) to soap UI which we are using for testing interfaces
    (already successful with other sync interface where the WSDL from c) contains a message type created in PI
e) testing this interface results in an error:
Error message in MONI:
SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_TestTrigger_Testm~</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:props. Value</SAP:P3>
<SAP:P4>s missing in queue context. Target XSD requires a~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_Test_Testm; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:props. Values missing in queue context. Target XSD requires a</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
This is the message as it looks like in soapUI:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:com="http://jusit.hp.com/sys/common/">
   <soapenv:Header/>
   <soapenv:Body>
      <props>
         <com:Property>
            <com:PropertyName>A</com:PropertyName>
            <com:PropertyValue>1</com:PropertyValue>
         </com:Property>
      </props>
   </soapenv:Body>
</soapenv:Envelope>
This is the payload in MONI as it comes from SOAP UI (using http connection):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<props xmlns:com='http://jusit.hp.com/sys/common/' xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/'>
         <com:Property>
            <com:PropertyName>A</com:PropertyName>
            <com:PropertyValue>1</com:PropertyValue>
         </com:Property>
      </props>
This is the payload as it looks like in Mapping Test in Enterprise Repos. from implemented ext.def.:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:props xmlns:ns0="http://jusit.hp.com/sys/common/">
   <ns0:Property>
      <ns0:PropertyName>A</ns0:PropertyName>
      <ns0:PropertyValue>1</ns0:PropertyValue>
   </ns0:Property>
</ns0:props>
Is there any restriction with external definitions to be used in PI which could be the reason for this strange behaviour?
The implementation contained a message type created in PI earlier which was running successful!
The problem came up with the external definition!
Thank you for your help!
Best regards
Dirk

Hi,
the problem is not the mapping as it is 1:1 with the same message on both sides.
But when I replace the "com"s with "ns0" and "props" with "ns0:props" in the request in soap UI
the payload will be accepted and mapping is successful!
So the issue is about the modification soap UI is doing on the imported WSDL.
a) Generated request in soap UI from imported WSDL: FAILS in PI!!!!
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:com="http://test.ap.com/sys/common/">
   <soapenv:Header/>
   <soapenv:Body>
      <props>
         <com:Property>
            <!You may enter the following 2 items in any order>
            <com:PropertyName>?</com:PropertyName>
            <com:PropertyValue>?</com:PropertyValue>
         </com:Property>
      </props>
   </soapenv:Body>
</soapenv:Envelope>
b) Modified request in soap UI from imported WSDL: WILL BE PROCESSED IN PI
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="http://test.ap.com/sys/common/">
   <soapenv:Header/>
   <soapenv:Body>
      <ns0:props>
         <ns0:Property>
            <!You may enter the following 2 items in any order>
            <ns0:PropertyName>B</ns0:PropertyName>
            <ns0:PropertyValue>5</ns0:PropertyValue>
         </ns0:Property>
      </ns0:props>
   </soapenv:Body>
</soapenv:Envelope>
But is there any possibility to avoid this effect in soap UI?
Regards
Dirk

Is there an issue with using a local copy of the WSDL versus a direct connect to Configure Web Service

I would like to build a WS connector to RemedyForce (~ Salesforce). I am attemptling to use the configuration tool to buid the MSCONFIG file. Salesforce does not let you connect directly to a wsdl file. you have to download a static copy.
This would seem fine using a "file://" path as the url - but as soon as I attempt to configure any import/synch the utility crashes. My assumption is it is attemping to reach a true webservice and using file location is not cutting
it.

I don't see any issue in downloading the static copy. Even if you were allowed to connect to the wsdl directly or add it as a service reference in Visual Studio then you would have to manually update that reference. In closing, you aren't losing
any functionality by downloading the static copy.
Thanks,
Follow my FIM blog at: http://forefrontidm.wordpress.com/

Q: Issues using WSDL wizard in Flex Builder

I'm having trouble generating AS Proxy files from a WSDL.
Incident (with the WSDL/schema files) is here
http://bugs.adobe.com/jira/browse/FB-10541
I'd appreciate it if you could try generating the AS proxy
stubs - if you have any luck, please forward them to me!
Thanks in advance.
Adam

Hi Adam,
Please read the following
bug report for
more details about this issue and how to fix it.
Thanks,
-Catalin

Wsdl issue

Similar Messages

Maybe you are looking for