Discussions

XML & Web services: invalid qname prefix

  1. invalid qname prefix (4 messages)

    Does anybody know what could cause that exception? org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exce ption is org.codehaus.xfire.fault.XFireFault: invalid QName prefix org.codehaus.xfire.fault.XFireFault: invalid QName prefix at org.codehaus.xfire.fault.XFireFault.createFault(XF ireFault.java:89) at org.codehaus.xfire.client.Client.onReceive(Client. java:386) at org.codehaus.xfire.transport.http.HttpChannel.send ViaClient(HttpChann el.java:120) at org.codehaus.xfire.transport.http.HttpChannel.send (HttpChannel.java:4 4) at org.codehaus.xfire.handler.OutMessageSender.invoke (OutMessageSender.j ava:26) at org.codehaus.xfire.handler.HandlerPipeline.invoke( HandlerPipeline.jav a:110) at org.codehaus.xfire.client.Invocation.invoke(Invoca tion.java:75) at org.codehaus.xfire.client.Client.invoke(Client.jav a:335) at org.codehaus.xfire.client.XFireProxy.handleRequest (XFireProxy.java:77 ) at org.codehaus.xfire.client.XFireProxy.invoke(XFireP roxy.java:57) at $Proxy0.echo(Unknown Source) at TestRunner.main(TestRunner.java:12) Caused by: java.lang.IllegalArgumentException: invalid QName prefix at javax.xml.namespace.QName.(QName.java:81) at com.bea.xml.stream.MXParser.getName(MXParser.java: 1439) at org.codehaus.xfire.soap.handler.ReadHeadersHandler .checkForFault(Read HeadersHandler.java:107) at org.codehaus.xfire.soap.handler.ReadHeadersHandler .invoke(ReadHeaders Handler.java:67) at org.codehaus.xfire.handler.HandlerPipeline.invoke( HandlerPipeline.jav a:110) at org.codehaus.xfire.client.Client.onReceive(Client. java:382) ... 10 more

    Threaded Messages (4)

  2. What are your namespace prefixes?[ Go to top ]

    Well, "invalid QName prefix" suggests that there could be an issue with the characters in a namespace prefix that you are using. Can you list the namespace prefixes that your instances and Schemas are using? Cheers, Tony.
  3. wsdl[ Go to top ]

    the wsdl it generates there all all the prefixes <!--?xml version="1.0" encoding="UTF-8" ?--> - - - - - - - - - - - - - - - - - - -
  4. What about the instances?[ Go to top ]

    I don't see any obvious prefix issues in the WSDL, but the exception occurs during an invocation, which I guess means it happens as a message arrives. That means the prefixes in the arriving instance could also be the problem. Are you able to see the instance/message that triggered this exception when it occurs? Do you log it anywhere, for example?
  5. axis client[ Go to top ]

    this time i used axis client instead of xfire client and everything worked fine