[billflood]

I developed a JAX-WS from the bottom up in ME 7.

When invoking this service from an axis client an explicit name space on a method is used by default and fails. Note the explicit name space on GetMessageHeaders

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Header/>
   <soapenv:Body>
      <GetMessageHeaders xmlns="http://mail.uc.uep.company.com/"]
...

However, the following invocation style does work but either of these methods should be perfectly legal. Note that the name space for “mail” on GetMessageHeaders is forward declared.

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"  xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:mail= "http://mail.uc.uep.company.com/">
    <SOAP-ENV:Body>
        <mail:GetMessageHeaders>
...

You can try this with any Web service from a soap tester.
This looks like a bug in JAX-WS or am I missing something?

[Loyal Water]

billflood,
The dev team is looking into this issue. They will get back to you with a reply asap.

[Brian Fernandes]

billflood,

Are you sure the GetMessageHeaders operation is in the “http://mail.uc.uep.company.com/” namespace? Can you confirm this in the WSDL generated?

If so, I agree it should be working and this seems like an odd bug. Unfortunately, I cannot help with JAX-WS framework issues and would suggest you post directly to the JAX-WS forum here: http://forums.java.net/jive/forum.jspa?forumID=46&start=0

Hope his helps.

[Author]

Posts