Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 363655
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T13:21:48+00:00 2026-05-12T13:21:48+00:00

I am trying to consume a third party WSDL using the Weblogic 10.3 clientgen

  • 0

I am trying to consume a third party WSDL using the Weblogic 10.3 clientgen ant task (which wraps wsimport). When doing this I get the following error:

[clientgen] [ERROR] in message “JobSubmissionErrorFault”, part “exception” must specify a “element” attribute

Below is a subset of the WSDL I am trying to consume (names have been changed to protect the innocent)

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
              xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
              xmlns:xsd="http://www.w3.org/2001/XMLSchema"                
              xmlns:asjx="urn:XXXXX:XML:AAA:2006/01:Types"
              xmlns:tns="urn:XXXXX:Central:2006/01:AAAService"
              targetNamespace="urn:XXXXX:Central:2006/01:AAAService">
<wsdl:types>
<xsd:schema elementFormDefault="qualified"
            targetNamespace="urn:XXXXX:XML:AAA:2006/01:Types">

  <xsd:element name="SubmitRequest">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element name="Type" type="xsd:string" form="unqualified"/>
        <xsd:element name="Definition" type="xsd:string" form="unqualified"/>
      </xsd:sequence>
    </xsd:complexType>
  </xsd:element>
  <xsd:element name="SubmitResponse">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element name="JobResult" type="asjx:JobResultType" form="unqualified"/>
      </xsd:sequence>
    </xsd:complexType>
  </xsd:element>

  <xsd:complexType name="JobSubmissionErrorFaultType">
    <xsd:sequence>
      <xsd:element name="Detail" type="xsd:string" />
    </xsd:sequence>
  </xsd:complexType>

</xsd:schema>

Is this WSDL valid? Can wsdl:part ‘type’ be used when the element in question is a wsdl:fault? I have looked at the specifications and am a little confused.

Looking at this link it appears using type is not valid

The following link does not clarify if it is valid or not

And finally the following metro bug link (Weblogic 10.3 used metro under the covers) does not confirm if this is an issue or not (it is still being debated).

If anyone is able to confirm once and for all if using ‘type’ is valied for a wsdl:fault it would be much appreciated.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T13:21:48+00:00Added an answer on May 12, 2026 at 1:21 pm

    Depends on who you ask. It’s OK according to W3, but the WS-I people beg to differ.

    WS-I: (BP2113) The soapbind:header, soapbind:headerfault or soapbind:fault elements refer to wsd:part element(s) that are not defined using only the “element” attribute.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am trying to consume a third party service like this: var context =
I'm trying to consume a .net webservice using ksoap2. this is the envelope of
I am trying to consume a WSDL from WCF using PHPs SoapClient. When using
I'm trying to use WCF to consume a web service provided by a third-party's
I'm trying to consume and use a third party REST Json based API. I
I am trying to consume a rest service which returns XMI data like this:
I'm trying to consume a third party web service with OracleAS web services. The
I'm trying to consume a webservice from camel using the cxf component, like this:
I'm trying to consume a rest service(wcf) using restsharp This is my service [ServiceContract]
I'm trying to consume twitter's REST api mentioned at this link using WCF REST

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.