Wscompile error with PayPalSvc.wsdl

Hi,
I am trying to use wscompile to generate the client artifacts for the PaypalSvc.wsdl file.
The error is: error: modeler error: duplicate "complexType" entity: "AmountType"
The link to the wsdl file is: http://www.sandbox.paypal.com/wsdl/PayPalSvc.wsdl
My version of wscompile is: JAX-RPC Standard Implementation (1.1.2_04, build R45)
Thanks,
Jim

We are having the same problem with the case changes in WSDL generation, preventing us from upgrading, too. Haven't heard a peep from Adobe on it.
- http://forums.adobe.com/message/1053957
Wish I could help more.
Fred

Similar Messages

Why do I get parsing errors with my WSDL URL for Web Services usage

Hi,
I am puzzled with the errors I get when I want to create a Web Service datastore.
Scenario: I have created a SAP Web Service from CRM using SOAMANAGER. The WSDL URL produced by SOAMANAGER is accessibile when pasting the URL directly in Internet Explorer. WSDL URL [http://UXCIQ0M.WDF.SAP.CORP:50076/sap/bc/srt/wsdl/srvc_CBDCB34C89C29304E10000000A4282C0/wsdl11/allinone/ws_policy/document?sap-client=504]
When using the WSDL URL in the Web Service datastore URL field, I get the error An error occurred while importing metadata: WSDLException; faultcode=PARSER_ERROR: Problem parsing: The element type "br" must be terminated by matching tag "/br". (BODI-1111469) (BODI-1112446)
When I save the WSDL defintion in a local file and use a local file path, I get the errors An error occurred while importing metadata: WSDLException (at /wsdl:definitions/wsdl:portype/wsp:Policy): faultcode=INVALID_WSDL: Encountered unexpected element 'Policy. (BODI-1111469) (BODI-1112446)
My questions:
- Why do I get different parsing errors despite the fact that the XML is the same?
- The WSDL is generated by SOAMANAGER. Shouldn't it work directly when integrating with Web Services generated from an SAP environment?
- Is this related to confiurgation issue? I have set the Job Manager to Support adapter, message broker and SNMP communication
- What is the difference between the datastore of type Adapter and the datastore Web Service? In the white paper [http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/20bd5e60-11f9-2b10-2bbb-b5109cceff08?quicklink=index&overridelayout=true] it is mentioned to use the Adapter type to consume a Web Service. It is not clear to me why we have those 2 types.
Thanks & Best Regards
Isabelle

Some updates on this issue, which might help others in the community.
- Data Service doesn't support ws_policy.
- SAP NetWeaver 7.0 SOAMANAGER generate WDSL with ws_policy. In future releases, it is possible to specify not to use ws_policy
- In most cases, replacing ws_policy with standard in the URL directly, works. It doesn't work with Data Services :(.
- Replacing ALL ws_policy in the XML directly is currently the only way to have the WSDL definition being parsed properly by Data Services.

Error with TaskQueryService wsdl

Hello ...
I.m having problems loading TaskQueryService WSDL into Eclipse WebServices Explorer:
IWAB0380E Errors were encountered while validating XML schemas.
XSD: The location 'http://fmw.inspyrusdev.com:9700/integration/services/TaskQueryService/TaskQueryService?XSD=UserMetadata.xsd' has not been resolved because the import is unused
XSD: The location 'http://fmw.inspyrusdev.com:9700/integration/services/TaskQueryService/TaskQueryService?XSD=WorkflowCommon.xsd' has not been resolved because the import is unused
XSD: The location 'http://fmw.inspyrusdev.com:9700/integration/services/TaskQueryService/TaskQueryService?XSD=TaskQuery.xsd' has not been resolved because the import is unused
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/common#principleRefType' is unresolved
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/common#principleRefType' is unresolved
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/taskQuery#taskOptionalInfoType' is unresolved
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/taskQuery#taskPredicateType' is unresolved
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/taskQuery#taskOrderingType' is unresolved
XSD: The base type 'http://www.w3.org/2001/XMLSchema#string' must be complex to support complex content
XSD: The base type must be the content type
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/common#principleRefType' is unresolved
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/common#principleRefType' is unresolved
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/common#principleRefType' is unresolved
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/common#principleRefType' is unresolved
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/common#principleRefType' is unresolved
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/common#principleRefType' is unresolved
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/common#principleRefType' is unresolved
XSD: The base type 'http://www.w3.org/2001/XMLSchema#string' must be complex to support complex content
XSD: The base type must be the content type
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/task#identityType' is unresolved
XSD: Type reference 'http://xmlns.oracle.com/bpel/workflow/task#identityType' is unresolved
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
XSD: The enumeration facet is not permitted in a type based on 'http://www.w3.org/2001/XMLSchema#string'
Anybody knows what is the problem?
Regards.

Hi
Not answering your question, but was inquisitive, why you would like to make use of it.
I use TaskQueryService too, but by not calling the webservice directly.
http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10224/bp_worklistcust.htm#BHAHBHID , chapter 28, talks about using the jars that have TaskQueryService and APIs for other service. We can also configure the project to use webservice or remoteEJBs. And it is specified that it is just a configuration file change and nothing else. So, once we have these jars, we will never be required to create webservice clients ourseleves.
Thanks
Satinder

BPEL Compilation Error: Load of wsdl "with Message part element undefined..

Hi Friends,
I am getting following error while compiling my BPEL process:
Error: Load of wsdl "FTPWrite.wsdl with Message part element undefined in wsdl [file:/D:/MyData/_MyProjects/052_Amazon_MetadataInterface/001_SVN/002_Intl/trunc/MetadataInterfaceIntl_2013Apr15_WorkingCode/MetadataInterface_Intl/MetadataInterface_Intl.wsdl] part name = reply type = {http://com.fox.metadata/MetadataInterfaceIntl/MetadataInterface_Intl/types}processResponse" failed
However the reply message is already defined in the MetadataInterface_Intl.wsdlas shown below:
Code for MetadataInterface_Intl.wsdl::::
"<?xml version= '1.0' encoding= 'UTF-8' ?>
<wsdl:definitions
name="MetadataInterface_Intl"
targetNamespace="http://xmlns.oracle.com/MetadataInterfaceIntl/MetadataInterface_Intl/MetadataInterface_Intl"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:inp1="http://com.fox.metadata/MetadataInterfaceIntl/MetadataInterface_Intl/types"
xmlns:tns="http://xmlns.oracle.com/MetadataInterfaceIntl/MetadataInterface_Intl/MetadataInterface_Intl"
>
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://com.fox.metadata/MetadataInterfaceIntl/MetadataInterface_Intl/types" schemaLocation="xsd/Metadata_Interface.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="requestMessage">
<wsdl:part name="request" element="inp1:process"/>
</wsdl:message>
*<wsdl:message name="replyMessage">*
*<wsdl:part name="reply" element="inp1:processResponse"/>*
*</wsdl:message>*
<wsdl:portType name="execute_ptt">
<wsdl:operation name="execute">
<wsdl:input message="tns:requestMessage"/>
<wsdl:output message="tns:replyMessage"/>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>"
Surprisingly, this same code was compiling file last week and now I have no clue why I am getting this error. Can someone please shade some light on this issue?
Thanks,
Sachin.

Hello
I have had the same problem in Oracle BPM and solved it using the following steps:
1- In your application navigator window, expand the project that contains the business rule.
2- In the SOA Content, double click on your wsdl file.
3- When the file opens, select the schema view from the bottom of the page.
4- In the schema view, expand all the schema nodes and check if you see any values in red. If you see one, that value has probably caused the error and you should correct it using the property inspector window.
In my case, the schema location value was set to a wrong path, so I changed it and the error resolved.
Also, some error that appear as warning in the rule editor will show as compile error later, such as input types not being used and such, so those must be resolved before compiling.
Hope that was helpful
good luck

JWSDP1.5: wscompile error: "(should not happen): tie.generator.002

Hi all,
I'm working with a doc/lit webservice; I have a WSDL and I'm attempting to generate Java artefacts with wscompile. I'm using JWSDP1.5. I've had a range of errors (I'm updating an old WSDL for the Tentative Hold Protocol, see http://www.w3.org/TR/tenthold-2/). The latest, though, is problematic. The final error message is:
error: generator error: internal error (should not happen): tie.generator.002I have included the full output from wscompile at the end of this posting; I'll post the full WSDL in a reply. Any advice would be much appreciated!
Cheers,
--Tim West
Full output (from wscompile Ant task) - added linebreaks for readability
Buildfile: C:\common\eclipse-projects\thp\build.xml
wscompile-init:
ANEW-generate-server-binding:
[wscompile] command line: wscompile -d C:\common\eclipse-projects\thp\zant-build \
-features:documentliteral,wsi -g -gen:server -keep -verbose \
C:\common\eclipse-projects\thp\server-wscompile-config.xml -classpath (path omitted for readability)
[wscompile] [CustomClassGenerator: generating JavaClass for: userDefinedBody]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdHeader]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestAckHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyRequestHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyResponseChoiceHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyGrantHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdGrantHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyDenialHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdDenialHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationRequestHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationResponseHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusQueryHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseBody]
[wscompile] [CustomClassGenerator: generating JavaClass for: statusStructure]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: userDefinedBody]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdHeader]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdRequestHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdRequestAckHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdModifyRequestHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdGrantHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdModifyGrantHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdDenialHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdModifyDenialHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdModifyResponseChoiceHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdCancellationRequestHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdCancellationResponseHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdStatusQueryHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: statusStructure]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdStatusResponseBody]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdStatusResponseHdr]
[wscompile] error: generator error: internal error (should not happen): tie.generator.002
BUILD FAILED: C:\common\eclipse-projects\thp\build.xml:342: wscompile failed
Total time: 2 seconds

Hi again,
The offending WSDL is below. I should add that I Googled this and couldn't find anything useful. Axis is happy with the WSDL, as is the validator at http://www.soapclient.com/SoapTools.html (though I'm not sure of its quality). I'm now downloading IBM Websphere 6 to see how that goes.
Thanks again,
-Tim West
<?xml version="1.0" encoding="UTF-8"?>
<definitions
    name="TentativeHold"
    targetNamespace="http://www.w3.org/2001/08/thp/definitions"
    xmlns:tns="http://www.w3.org/2001/08/thp/definitions"
    xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema"
        xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
        targetNamespace="http://www.w3.org/2001/08/thp/schemas">
      
      
      
      
      
      
      
      
      <complexType name="holdHeader">
        <sequence>
          <element name="holdID" type="int"/>
          <element name="customerID" type="string"/>
          <element name="replyTo" type="string"/>
          <element name="comment" type="string"/>
        </sequence>
      </complexType>
      
      
      
      
      
        
      <complexType name="userDefinedBody">
        <sequence>
          <element name="someRequestField" type="string"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdRequestHdr">
        <sequence>
          <element name="baseHeader" type="holdSchema:holdHeader"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdRequestAckHdr">
        <sequence>
          <element name="baseHeader" type="holdSchema:holdHeader"/>
          <element name="timeUntilResponse" type="duration"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdGrantHdr">
        <sequence>
          <element name="baseHeader" type="holdSchema:holdHeader"/>
          <element name="holdDuration" type="duration"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdDenialHdr">
        <sequence>
          <element name="baseHeader" type="holdSchema:holdHeader"/>
          <element name="reason" type="string"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdModifyRequestHdr">
        <sequence>
          <element name="modifiedHoldRequest" type="holdSchema:holdHeader"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdModifyGrantHdr">
        <sequence>
          <element name="modifiedHoldRequest" type="holdSchema:holdGrantHdr"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdModifyDenialHdr">
        <sequence>
          <element name="modifiedHoldRequest" type="holdSchema:holdDenialHdr"/>
        </sequence>
      </complexType>
      
      
      
      
      
      
      <complexType name="holdModifyResponseChoiceHdr">
        <sequence>
          <element name="grant" type="holdSchema:holdModifyGrantHdr"/>
          <element name="deny" type="holdSchema:holdModifyDenialHdr"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdCancellationRequestHdr">
        <sequence>
          <element name="customerHold" type="holdSchema:holdHeader"/>
          <element name="customerReason" type="string"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdCancellationResponseHdr">
        <sequence>
          <element name="customerHold" type="holdSchema:holdHeader"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdCancellationNotificationHdr">
        <sequence>
          <element name="customerHold" type="holdSchema:holdHeader"/>
          <element name="cancellationReason" type="string"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdStatusQueryHdr">
        <sequence>
          <element name="customerHold" type="holdSchema:holdHeader"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="holdStatusResponseHdr">
        <sequence>
          <element name="baseHeader" type="holdSchema:holdHeader"/>
        </sequence>
      </complexType>
      
      
      
      
      
      <complexType name="statusStructure">
        <sequence>
          <element name="itemHeader" type="holdSchema:holdHeader"/>
          <element name="holdState" type="string"/>
        </sequence>
      </complexType>
      
      
      
      
      
      
      <complexType name="holdStatusResponseBody">
        <sequence>
          <element name="holdItemsCount" type="int"/>
          <element name="itemList" type="holdSchema:statusStructure" minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </complexType>
      
      
      
      
      
      
      <complexType name="holdError">
        <sequence>
          <element name="baseHeader" type="holdSchema:holdHeader"/>
          <element name="holdErrorType" type="int"/>
          <element name="holdErrorDesc" type="string"/>
        </sequence>
      </complexType>
      
      <element name="userDefinedBody" type="holdSchema:userDefinedBody"/>
      <element name="holdRequestHdr" type="holdSchema:holdRequestHdr"/>
      <element name="holdRequestAckHdr" type="holdSchema:holdRequestAckHdr"/>
      <element name="holdGrantHdr" type="holdSchema:holdGrantHdr"/>
      <element name="holdDenialHdr" type="holdSchema:holdDenialHdr"/>
      <element name="holdModifyRequestHdr" type="holdSchema:holdModifyRequestHdr"/>
      <element name="holdModifyGrantHdr" type="holdSchema:holdModifyGrantHdr"/>
      <element name="holdModifyDenialHdr" type="holdSchema:holdModifyDenialHdr"/>
      <element name="holdModifyResponseChoiceHdr" type="holdSchema:holdModifyResponseChoiceHdr"/>
      <element name="holdCancellationRequestHdr" type="holdSchema:holdCancellationRequestHdr"/>
      <element name="holdCancellationResponseHdr" type="holdSchema:holdCancellationResponseHdr"/>
      <element name="holdCancellationNotificationHdr" type="holdSchema:holdCancellationNotificationHdr"/>
      <element name="holdStatusQueryHdr" type="holdSchema:holdStatusQueryHdr"/>
      <element name="holdStatusResponseHdr" type="holdSchema:holdStatusResponseHdr"/>
      <element name="holdStatusResponseBody" type="holdSchema:holdStatusResponseBody"/>
      <element name="holdError" type="holdSchema:holdError"/>
    </schema>
</types>
<message name="HoldRequest">
    <part name="headerHoldRequest" element="holdSchema:holdRequestHdr"/>
    <part name="bodyHoldRequest" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldRequestAck">
    <part name="headerHoldRequestAck" element="holdSchema:holdRequestAckHdr"/>
    <part name="bodyHoldRequestAck" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldGrantResponse">
    <part name="headerHoldGrantResponse" element="holdSchema:holdGrantHdr"/>
    <part name="bodyHoldGrantResponse" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldDenialResponse">
    <part name="headerHoldDenialResponse" element="holdSchema:holdDenialHdr"/>
    <part name="bodyHoldDenialResponse" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldModifyRequest">
    <part name="headerHoldModifyRequest" element="holdSchema:holdModifyRequestHdr"/>
    <part name="bodyHoldModifyRequest" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldModifyResponse">
    <part name="headerHoldModifyResponse" element="holdSchema:holdModifyResponseChoiceHdr"/>
    <part name="bodyHoldModifyResponse" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldCancellationRequest">
    <part name="headerHoldCancellationRequest" element="holdSchema:holdCancellationRequestHdr"/>
    <part name="bodyHoldCancellationRequest" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldCancellationResponse">
    <part name="headerHoldCancellationResponse" element="holdSchema:holdCancellationResponseHdr"/>
    <part name="bodyHoldCancellationResponse" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldCancellationNotification">
    <part name="header" element="holdSchema:holdCancellationNotificationHdr"/>
    <part name="body" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldStatusQueryRequest">
    <part name="headerHoldStatusQueryRequest" element="holdSchema:holdStatusQueryHdr"/>
    <part name="bodyHoldStatusQueryRequest" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldStatusResponse">
    <part name="headerHoldStatusResponse" element="holdSchema:holdStatusResponseHdr"/>
    <part name="bodyHoldStatusResponse" element="holdSchema:holdStatusResponseBody"/>
</message>
<message name="HoldErrorResponse">
    
    <part name="bodyHoldErrorResponse" element="holdSchema:holdError"/>
</message>
<portType name="TentativeHoldServicePortType">
    <operation name="InitiateHold">
      <input message="tns:HoldRequest"/>
      <output message="tns:HoldRequestAck"/>
      
    </operation>
    <operation name="InitiateHoldModify">
      <input message="tns:HoldModifyRequest"/>
      <output message="tns:HoldModifyResponse"/>
      
    </operation>
    <operation name="InitiateHoldCancellation">
      <input message="tns:HoldCancellationRequest"/>
      <output message="tns:HoldCancellationResponse"/>
      
    </operation>
    <operation name="InitiateStatusQuery">
      <input message="tns:HoldStatusQueryRequest"/>
      <output message="tns:HoldStatusResponse"/>
      
    </operation>
</portType>
<portType name="TentativeHoldNotificationServicePortType">
    <operation name="NotifyHoldGranted">
      <output message="tns:HoldGrantResponse"/>
    </operation>
    <operation name="NotifyHoldDenied">
      <output message="tns:HoldDenialResponse"/>
    </operation>
    <operation name="NotifyServerHoldCancellation">
      <output message="tns:HoldCancellationNotification"/>
    </operation>
</portType>
<binding name="TentativeHoldSoapBinding" type="tns:TentativeHoldServicePortType">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
      <operation name="InitiateHold">
        <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHold"/>
        <input>
          <soap:body use="literal"/>
        </input>
        <output>
          <soap:body use="literal"/>
        </output>
        
      </operation>
      <operation name="InitiateHoldModify">
        <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldModify"/>
        <input>
          <soap:body use="literal"/>
        </input>
        <output>
          <soap:body use="literal"/>
        </output>
        
      </operation>
      <operation name="InitiateHoldCancellation">
        <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldCancellation"/>
        <input>
          <soap:body use="literal"/>
        </input>
        <output>
          <soap:body use="literal"/>
        </output>
        
      </operation>
      <operation name="InitiateStatusQuery">
        <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateStatusQuery"/>
        <input>
          <soap:body use="literal"/>
        </input>
        <output>
          <soap:body use="literal"/>
        </output>
        
      </operation>
</binding>
<service name="TentativeHoldService">
    <documentation> Mythical Tentative Hold Web service</documentation>
    <port name="TentativeHoldPort" binding="tns:TentativeHoldSoapBinding">
      <soap:address location="http://xyz.com/tentativeHold/"/>
    </port>
</service>
<service name="TentativeHoldNotificationService">
    <port name="NotificationPort" binding="tns:TentativeHoldSoapBinding">
      <soap:address location="http://xyz.com/tentativeHoldNotification"/>
    </port>
</service>
</definitions>

Wscompile error : exclusive attributes: "type", "substitutionGroup"

Hi All,
I'm trying to use wscompile with a WSDL file and a set of XSDs. It keeps failing with the following error
error: modeler error: model error: exclusive attributes: "type", "substitutionGroup"
all the XSDs are standard files available in "http://www.starstandards.org/STAR"
wscompile version is "JAX-RPC Standard Implementation (1.1.3, build R1)" and I am able to deploy services/access them using our own XSDs and the same approach.
Appreciate if anyone could help me figure out a solution for this.
Thanks,
Nilantha

I'm getting the exact same problem when I compile my wsdl - hopefully someone will come up with a solution or at least a lead!!
Russ

Http post issue in soa suite 11g with 10g wsdl

I have 10g process that has http post wsdl as below. When I'm trying to create a project in 11g 11.1.1.4 with same wsdl, getting the following error at building the project. "Error(12,61): Parse of component type files failed, check the adf-config.xml file : "Error at line 34 char 64: Malformed WS Binding port. Missing # between namespace URI and service/port names."
I'm sure that http post mechanism is changed in 11g, but can you please help what exactly is wrong ?
<?xml version="1.0"?>
<definitions name="HTTPPostService"
targetNamespace="http://services.otn.com"
xmlns:tns="http://services.otn.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
          xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
          xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
>

<types>
<schema attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://services.otn.com"
xmlns="http://www.w3.org/2001/XMLSchema">
<element name="Postreq">
<complexType>
<sequence>
<element name="Order_Update_Request">
<complexType>
<sequence>
<element name="ORD_ID" type="string"/>
<element name="E_MAIL" type="string"/>
</sequence>
</complexType>
</element>
</sequence>
</complexType>
</element>
<element name="Postresp">
<complexType>
<sequence>
<element name="Order_Update_Response">
<complexType>
<sequence>
<element name="RETURN_STATUS" type="string"/>
<element name="MESSAGE_TEXT" type="string"/>
</sequence>
</complexType>
</element>
</sequence>
</complexType>
</element>
</schema>
</types>

<message name="HTTPPostServiceRequestMessage">
<part name="payload" element="tns:Postreq"/>
</message>
<message name="HTTPPostServiceResponseMessage">
<part name="payload" element="tns:Postresp"/>
</message>


<portType name="HTTPPostService">
<operation name="IScript_Update_Order">
<input message="tns:HTTPPostServiceRequestMessage" />
<output message="tns:HTTPPostServiceResponseMessage"/>
</operation>
</portType>
<binding name="HTTPPost" type="tns:HTTPPostService">
<http:binding verb="POST"/>
<operation name="IScript_Update_Order">
<http:operation location="/PSIG/HttpConnector?From=PSFT_XINBOUND&MessageName=ABC_ORD_UPDORDER&MessageType=sync&MessageVersion=v1"/>
<input>
<mime:mimeXml part="payload"/>
<mime:content type="text/xml"/>
</input>
<output>
<mime:mimeXml part="payload"/>
          <mime:content type="text/xml"/>
</output>
</operation>
</binding>
<service name="HTTPPostService">
<port name="HTTPPost" binding="tns:HTTPPost">
<http:address location="http://myserver.mycompany.com"/>
</port>
</service>

<plnk:partnerLinkType name="HTTPPostService">
<plnk:role name="HTTPPostServiceProvider">
<plnk:portType name="tns:HTTPPostService"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>

Can you make sure your helloworld is using adf bindings as mentioned in thread Re: Urgent :: 11g Invoking Composite from Java/From Webservice Proxy

Error while reading wsdl file

I created and deployed a BPEL process with a JMS adapter and DB adapter.
I have tested this and it works fine.
After a few days, I try to open the project and the BPEL process, and click on the DB
adapter and it throws an exception on the designer :
"Error while reading wsdl file ... (wsdl file name) NULL Exception"
This is hard to debug as the exception does not provide any info, NULL.
This has happened several times for my project. The next time the JMS adapter hit the
same exception while opening on designer. This one I notice happened after I imported
a new schema file (xsd) into the BPEL process.
Only way around that I have for this currently is to delete and recreate the adapters, which as time
consuming as I have to re-create and re-assign a lot of the activities.
Has anyone encountered this and is there a way to fix this without deleting/recreating the adapters ?
Thanks.

I experienced the same issue and found the cause and a workaround;
"Error while reading wsdl file …. Exception: null"
http://www.petervannes.nl/files/b7c08911ce3cde3677e2182bbc5f032a-47.php
Edited by: 944333 on Jul 3, 2012 10:24 PM

"Error in loading WSDL file" --- Adaptive Webservice Model

Hi All,
I have been using Deprecated web service model. But now my application is moving to Test. So in order not to change the URL of the webservice model in the Test, i tried with the Adaptive webservice model. But when i try to import the model its saying " Error in loading WSDL file. Check the error log for more details." Please help me out in this.
Thanks in advance,
Pranesh.

Hi Pranesh,
Please refer to this thread for similar issue and check the log file for NWDS for more details
Error in loading the WSDL file. Check the error log for more details
Hope it helps
Regards
Arun

Error while importing WSDL file created in JDeveloper inside BS

Hi All,
I am facing error while importing WSDL of the DBAdapter service created using JDeveloper inside my business service in OSB.
The error in OSB is 'The Resource Mapped Does not exist'

Which version of OSB are you using? You need to upload schema (.xsd) files as well. WSDL has references to that schema(s) but they are not uploaded hence this error. On sbconsole, if you click on a WSDL name to see it, a button comes with name "Edit References". Click that to point to the xsd's you uploaded.
Regards,
Anuj

What's wrong with the wsdl

We are trying to create a proxy from the following wsdl file and getting an error message: illegal syntax: API:Parameter BINDING has initial value
The webservice that we are trying to consume is from TIBCO .
Can someone please help me to find out what's wrong with the wsdl.
<?xml version = "1.0" encoding = "UTF-8"?>

<wsdl:definitions name = "Untitled" targetNamespace = "http://xmlns.example.com/1268018884234/OperationImpl" xmlns:soap = "http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns = "http://xmlns.example.com/1268018884234/OperationImpl" xmlns:wsdl = "http://schemas.xmlsoap.org/wsdl/" xmlns:xs = "http://www.w3.org/2001/XMLSchema">
     <wsdl:types/>
     <wsdl:service name = "TIBCO__ABAP">
          <wsdl:port binding = "tns:SOAPEventSourceBinding" name = "SOAPEventSource">
               <soap:address location = "http://192.168.9.58:10001/TIBCO_ABAP"/>
          </wsdl:port>
     </wsdl:service>
     <wsdl:portType name = "PortType">
          <wsdl:operation name = "Operation">
               <wsdl:input message = "tns:Input"/>
               <wsdl:output message = "tns:Output"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name = "SOAPEventSourceBinding" type = "tns:PortType">
          <soap:binding style = "document" transport = "http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name = "Operation">
               <soap:operation soapAction = "http://192.168.9.58:10001/TIBCO_ABAP" style = "document"/>
               <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
               <wsdl:output>
        <soap:body use="literal" />
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:message name = "Input">
          <wsdl:part name = "Param1" type = "xs:int"/>
          <wsdl:part name = "Param2" type = "xs:int"/>
     </wsdl:message>
     <wsdl:message name = "Output">
          <wsdl:part name = "Result" type = "xs:int"/>
     </wsdl:message>
</wsdl:definitions>

Léon Hoeneveld's response works for me. You will need to download a tool that allows you to edit the WSDL and reorder the values.
I've used a freeware tool like notepad++ collapsed all the levels and opened up the <wsdl:definitions xmlns:wsdl... segment and reordered the subgroups beneath it accordingly.
1. types
2. message
3. portType
4. binding
5. service
Thanks again Léon!

Getting Invalid WSDL error for every WSDL file

hi
I recently started to work on jdeveloper 10.1 3 and i am trying to develope client for google web api.
but when i trying to create webservice using java web service form WSDL option.but when i am giving wsdl file it is giving me error like Invalid WSDL and when i click why not ? button it is saying that URL is malformed.
here is URL
jdev.uddi.bindingtemplate:http://uddi.xmethods.com/inquire/0B06E7E7-0F4D-BC86-4FFD-E2C8C0F43C2A
this is generated by UDDI registrey browser by jdeveloper it self.
this is happening with evety WSDL file. I think there is some problem with my Jdeveloper.
Please help me.

hi
Could you help me on following error.
I am trying to deploy webservice on Oracle Applicaiton server.
But i am getting following message on Deployment message window of Jdeveloper
---- Deployment started. ---- Apr 27, 2006 5:40:38 PM
Target platform is Oracle Application Server 10g 10.1.3 (KunalAppServer).
Wrote WAR file to D:\users\kunal\sdk\oracel_ide\jdevstudio1013_JDK\jdev\mywork\WebService\heloservice\deploy\WebServices.war
Wrote EAR file to D:\users\kunal\sdk\oracel_ide\jdevstudio1013_JDK\jdev\mywork\WebService\heloservice\deploy\WebService-heloservice-WS.ear
Uploading file WebService-heloservice-WS.ear ...
Application Deployer for WebService-heloservice-WS STARTS.
Copy the archive to D:\product\10.1.3\OracleAS_1\j2ee\home\applications\WebService-heloservice-WS.ear
Initialize D:\product\10.1.3\OracleAS_1\j2ee\home\applications\WebService-heloservice-WS.ear begins...
Unpacking WebService-heloservice-WS.ear
Done unpacking WebService-heloservice-WS.ear
Unpacking WebServices.war
Done unpacking WebServices.war
Initialize D:\product\10.1.3\OracleAS_1\j2ee\home\applications\WebService-heloservice-WS.ear ends...
Starting application : WebService-heloservice-WS
Initializing ClassLoader(s)
Initializing EJB container
Loading connector(s)
Starting up resource adapters
Initializing EJB sessions
Committing ClassLoader(s)
Initialize WebServices begins...
Initialize WebServices ends...
Started application : WebService-heloservice-WS
Binding web application(s) to site default-web-site begins...
Binding WebServices web-module for application WebService-heloservice-WS to site default-web-site under context root WebService-heloservice-context-root
Operation failed with error:
org.apache.xerces.dom.DeferredElementNSImpl
Deployment failed
Elapsed time for deployment: 1 minute, 8 seconds
#### Deployment incomplete. #### Apr 27, 2006 5:41:47 PM

Namespace error with JAXB

Hello everyone! This is my problem:
I am using jaxb to unmarshall a xml file. When I unmarshall, the program doesn�t work at this point:
JAXBContext jc = JAXBContext.newInstance("com.claynet.core.clom");
Unmarshaller u = jc.createUnmarshaller();
u.setValidating(true);
Clom clom =
(Clom)u.unmarshal(
new FileInputStream( ".." + File.separatorChar +
"webapps"+ File.separatorChar + "claybrary" + File.separatorChar
+ "objetosCLOM" + File.separatorChar + file_name.trim()) );
The error I get is the following one:
javax.xml.bind.UnmarshalException: Probably namespace URI of tag "clom" is wrong (correct one is "http://www.clayformacion.com/xsd/clomv1.0")
- with linked exception:
[com.sun.msv.verifier.ValidityViolation: Probably namespace URI of tag "clom" is wrong (correct one is "http://www.clayformacion.com/xsd/clomv1.0")]
The problem seems to be a conflict with the namespace, but the schema has the namespace correctly set:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:clom="http://www.clayformacion.com/xsd/clomv1.0" xmlns="http://www.clayformacion.com/xsd/clomv1.0" targetNamespace="http://www.clayformacion.com/xsd/clomv1.0" elementFormDefault="qualified">
The validation inside the unmarshalling crash.
Is there any errors with the code? Can Anyone help me?
Thanks

Looks like error is clear namespace mismatch...try changing the following url in wsdl and regen the code
http://example.ws found http://example.ws/xsd

Proxy Generation Problem with Separate WSDL

Hi,
I'm trying to create Proxy with seperate WSDL, then i'm getting error. It is a simple Hello world BPEL and OSB.
Here is my WSDL
<?xml version="1.0" encoding="UTF-8" ?>
<definitions targetNamespace="http://www.uk.gov.hmrc.chiefste.org/hello"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://www.uk.gov.hmrc.chiefste.org/hello"
xmlns:imp1="http://xmlns.oracle.com/HelloWorld"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/">
<types>
<xsd:schema targetNamespace="http://www.uk.gov.hmrc.chiefste.org/hello/types"
elementFormDefault="qualified">
<xsd:import schemaLocation="Hello.xsd"
namespace="http://xmlns.oracle.com/HelloWorld" id="hello.xsd"/>
</xsd:schema>
</types>
<message name="helloRequest">
<part name="inputParam" element="imp1:process"/>
</message>
<message name="helloResponse">
<part name="outputParam" element="imp1:processResponse"/>
</message>
<portType name="HelloService">
<operation name="sayHello">
<input message="tns:helloRequest"/>
<output message="tns:helloResponse"/>
</operation>
</portType>
<binding name="HelloServicePortBinding"
type="tns:HelloService">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="sayHello">
<soap:operation style="document"
soapAction="http://www.uk.gov.hmrc.chiefste.org/common/sayHello"/>
<input>
<soap:body use="literal" parts="inputParam"/>
</input>
<output>
<soap:body use="literal" parts="outputParam"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloServicePort"
binding="tns:HelloServicePortBinding">
<soap12:address location="temp"/>
</port>
</service>
</definitions>
And here is my xsd
<?xml version="1.0" encoding="UTF-8"?>
<schema attributeFormDefault="unqualified"
          elementFormDefault="qualified"
          targetNamespace="http://xmlns.oracle.com/HelloWorld"
          xmlns="http://www.w3.org/2001/XMLSchema">
     <element name="process">
          <complexType>
               <sequence>
                    <element name="input" type="string"/>
               </sequence>
          </complexType>
     </element>
     <element name="processResponse">
          <complexType>
               <sequence>
                    <element name="result" type="string"/>
               </sequence>
          </complexType>
     </element>
</schema>
This is the WSDL i used to create a proxy service.
And this is the WSDL i used to generate Business Service (Which i got from my BPEL)
<?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions name="HelloWorld" targetNamespace="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:documentation>
<abstractWSDL>http://chfbpm1.acentres.capgemini.co.uk:8001/soa-infra/services/default/TestProjectForOSB!1.0/HelloWorld.wsdl</abstractWSDL>
</wsdl:documentation>
- <plnk:partnerLinkType name="HelloWorld">
- <plnk:role name="HelloWorldProvider">
<plnk:portType name="client:HelloWorld" />
</plnk:role>
</plnk:partnerLinkType>
- <wsdl:types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" schemaLocation="http://chfbpm1.acentres.capgemini.co.uk:8001/soa-infra/services/default/TestProjectForOSB/helloworld_client_ep?XSD=xsd/HelloWorld.xsd" />
</schema>
</wsdl:types>
- <wsdl:message name="HelloWorldRequestMessage">
<wsdl:part name="payload" element="client:process" />
</wsdl:message>
- <wsdl:message name="HelloWorldResponseMessage">
<wsdl:part name="payload" element="client:processResponse" />
</wsdl:message>
- <wsdl:portType name="HelloWorld">
- <wsdl:operation name="process">
<wsdl:input message="client:HelloWorldRequestMessage" />
<wsdl:output message="client:HelloWorldResponseMessage" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="HelloWorldBinding" type="client:HelloWorld">
<soap:binding xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="process">
<soap:operation xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" soapAction="process" />
- <wsdl:input>
<soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal" namespace="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" />
</wsdl:input>
- <wsdl:output>
<soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal" namespace="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="helloworld_client_ep">
- <wsdl:port name="HelloWorld_pt" binding="client:HelloWorldBinding">
<soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="http://chfbpm1.acentres.capgemini.co.uk:8001/soa-infra/services/default/TestProjectForOSB/helloworld_client_ep" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thx,
Rahul

Yes, U r rite. It takes input like that in SoapUI.
And in OSB Console it takes like below:
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<hel:process xmlns:hel="*http://xmlns.oracle.com/HelloWorld*">
<hel:input>?</hel:input>
</hel:process>
And this is my Input for Business Service in OSB Console:
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<hel:process xmlns:hel="*http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld*">
<hel:input>?</hel:input>
</hel:process>
Note: And if i use the Bolded namespace of Business Service in Proxy,, it is working.
This is my Request XQuery:
(:: pragma bea:global-element-parameter parameter="$process1" element="ns1:process" location="../Proxy/wsdl/Hello.xsd" ::)
(:: pragma bea:global-element-return element="ns0:process" location="../Business/wsdl/XMLSchema_1137514867.xsd" ::)
declare namespace ns1 = "http://xmlns.oracle.com/HelloWorld";
declare namespace ns0 = "http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld";
declare namespace xf = "http://tempuri.org/Hello/xquery/dsha/";
declare function xf:dsha($process1 as element(ns1:process))
as element(ns0:process) {
<ns0:process>
<ns0:input>{ data($process1/ns1:input) }</ns0:input>
</ns0:process>
declare variable $process1 as element(ns1:process) external;
xf:dsha($process1)
Response XQuery:
(:: pragma bea:global-element-parameter parameter="$processResponse1" element="ns0:processResponse" location="../Business/wsdl/XMLSchema_1137514867.xsd" ::)
(:: pragma bea:global-element-return element="ns1:processResponse" location="../Proxy/wsdl/Hello.xsd" ::)
declare namespace ns1 = "http://xmlns.oracle.com/HelloWorld";
declare namespace ns0 = "http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld";
declare namespace xf = "http://tempuri.org/Hello/xquery/resp/";
declare function xf:resp($processResponse1 as element(ns0:processResponse))
as element(ns1:processResponse) {
<ns1:processResponse>
<ns1:result>{ data($processResponse1/ns0:result) }</ns1:result>
</ns1:processResponse>
declare variable $processResponse1 as element(ns0:processResponse) external;
xf:resp($processResponse1)
Thx,
Rahul

Error with web service SRT: Unexpected failure in SOAP processing occurred:

Hello,
I get the following error with a web service
"SRT: Unexpected failure in SOAP processing occurred: ("No configuration for this HTTP server instance")"
Any ideas on how to solve this ?
Thanks.
Regards, Michel

Hi,
I think the WSDL file shared with you and the soap message you are getting are a mismatch.
Try to check the soap message xml format and see if matches the ouputs tags structure in WSDL file.
Thanks & Rgds,
Aditya

Wscompile error with PayPalSvc.wsdl

Similar Messages

Maybe you are looking for