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 8397367
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T20:46:12+00:00 2026-06-09T20:46:12+00:00

I have a WSDL and some schema files that I used to generate a

  • 0

I have a WSDL and some schema files that I used to generate a JAX-WS web service client. When I try to get an instance of the client, I get this stack trace:

Caused by: java.lang.IllegalArgumentException: The specified prefix was null.
    at com.ibm.xml.xlxp.api.stax.msg.StAXMessageProvider.throwIllegalArgumentException(StAXMessageProvider.java:42)
    at com.ibm.xml.xlxp.api.stax.XMLStreamReaderImpl.getNamespaceURI(XMLStreamReaderImpl.java:721)
    at com.ibm.xml.xlxp.api.stax.XMLInputFactoryImpl$XMLStreamReaderProxy.getNamespaceURI(XMLInputFactoryImpl.java:212)
    at com.sun.xml.internal.ws.util.xml.XMLStreamReaderFilter.getNamespaceURI(XMLStreamReaderFilter.java:242)
    at com.sun.xml.internal.ws.wsdl.parser.ParserUtil.getQName(ParserUtil.java:78)
    at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parsePortTypeOperationInput(RuntimeWSDLParser.java:721)
    at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parsePortTypeOperation(RuntimeWSDLParser.java:694)
    at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parsePortType(RuntimeWSDLParser.java:668)
    at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parseWSDL(RuntimeWSDLParser.java:305)
    at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:136)
    at com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:227)
    at com.sun.xml.internal.ws.client.WSServiceDelegate.(WSServiceDelegate.java:190)
    at com.sun.xml.internal.ws.client.WSServiceDelegate.(WSServiceDelegate.java:160)
    at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:92)
    at javax.xml.ws.Service.(Service.java:67)
...

It looks a lot to me like the Service class is trying to parse the WSDL as a part of its initialization, and then fails because some prefix is null. The line at com.sun.xml.internal.ws.wsdl.parser.ParserUtil.getQName(ParserUtil.java:78) suggests it’s having trouble parsing the QName. When the service is created, the QName is set like this:

new QName("http://www.mycompany.ca/some/schema/MyService", "MyService")

The error message is not too clear though. Is a prefix needed before "MyService" or are changes to the WSDL necessary (I am not the WSDL owner so changes are difficult to push to other teams).

(environment is RAD 7.5 for WAS 7.0)

  • 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-06-09T20:46:14+00:00Added an answer on June 9, 2026 at 8:46 pm

    If you examine the details of the stack trace, you’ll notice that the problem is with the name of a port type operation input in the WSDL:

    <wsdl:definitions .... > 
      <wsdl:portType .... >
        <wsdl:operation>
           <wsdl:input message="qname"/>    <--- your problem is here
        </wsdl:operation>
      </wsdl:portType >
    </wsdl:definitions>
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a client which connects to a Web service to get some information.
I have some WSDL from which I need to generate a web service implementation.
I have an WSDL / Web Service and I need to generate an set
I have some simple SOAP client to get data from WSDL and display it.
I have a WSDL file defining a service that I have to implement in
I have a WSDL 1.1 file which describes my Web Service. Now I need
I have created two wsdl files with shared types imported from xsd schema file.
I have some web services that I need to reference in a Windows 8
I have some web services and I am creating a web client using ws-import.
I can generate a client from http://localhost:8080/service?wsdl just fine, but now I want to

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.