Hi Jeremy,

I'm glad you asked me that (!)- I was simply using the
javax.xml.namespace.QName from the Woden xml-apis.jar. However, this jar is
from the M4 Milestone, so I switched to using the latest Woden source from
svn. Unfortunately, the same problem appears as before.

Kind Regards,

Graham.
_____________________________________________
Graham C Turrell CEng, MBCS
Chartered IT Practitioner

WebSphere ESB Foundation Technologies
DE3F16 / MP 211
IBM Labs
Hursley Park
Winchester, Hampshire
England.  SO21 2JN

Tel +44-(0)1962-815018
email: [EMAIL PROTECTED]

"No army can withstand the force of an idea whose time
has come.". -Victor Hugo


                                                                           
             "Jeremy Hughes"                                               
             <[EMAIL PROTECTED]                                             
             rg>                                                        To 
             Sent by:                  [email protected]             
             [EMAIL PROTECTED]                                          cc 
             om                                                            
                                                                   Subject 
                                       Re: QName prefix and localpart      
             31/05/2006 21:42          handling                            
                                                                           
                                                                           
             Please respond to                                             
             [EMAIL PROTECTED]                                             
                  he.org                                                   
                                                                           
                                                                           




Hi Graham, whose QName class are you using? Are you using the one from a
JSE 5 JRE? Or perhaps the one from Woden itself?

Cheers,
Jeremy

On 5/31/06, Graham Turrell <[EMAIL PROTECTED]> wrote:
  Hi,

  I've been running through a simple woden test I put together, and am
  seeing
  strange behaviour with QNames.

  Heres some (unexciting) sample code:

  WSDLFactory factory = WSDLFactory.newInstance();
  WSDLReader reader = factory.newWSDLReader();
  DescriptionElement descElem = reader.readWSDL(wsdlurl);
  ServiceElement[] services = descElem.getServiceElements();

  I'm reading the following wsdl2.0 document :

  <?xml version="1.0" encoding="UTF-8"?>
  <description targetNamespace="http://example.com/bank";
               xmlns=" http://www.w3.org/2006/01/wsdl";
               xmlns:tns="http://example.com/bank";
               xmlns:ns1="http://example.com/bank ">
    <interface name="ns1:Bank">
      ....
    </interface>

    <binding name="ns1:BankSOAPBinding">
    ....
    </binding>

    <service name="ns1:BankService"
             interface="tns:Bank">
      <endpoint binding="ns1:BankSOAPBinding"></endpoint>
    </service>
  </description>


  Now, calling :
  services[0].getName().getPrefix() returns emply string
  and
  services[0].getName().getLocalPart() returns "ns1:BankService"

  (same thing happens on the component model).

  This looks like a bug. Unless anyone thinks otherwise I'll open a JIRA .



  Kind Regards,

  Graham.
  _____________________________________________
  Graham C Turrell CEng, MBCS
  Chartered IT Practitioner

  WebSphere ESB Foundation Technologies
  DE3F16 / MP 211
  IBM Labs
  Hursley Park
  Winchester, Hampshire
  England.  SO21 2JN

  Tel +44-(0)1962-815018
  email: [EMAIL PROTECTED]

  "No army can withstand the force of an idea whose time
  has come.". -Victor Hugo


  ---------------------------------------------------------------------
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to