2 Replies Latest reply on Jul 16, 2007 9:49 PM by jktinoco

    implicit namespace support?


      Hi, im attempting to upgrade from jboss-net/axis to JBossWS. I want to do this transparently to existing clients. When I issue an existing request :

      <?xml version="1.0" encoding="UTF-8"?>
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

      i get an error saying my endpoint "does not contain operation metadata for: getAccount"

      if i qualify that node w/ a namespace it works , but is there any way to support it without modifying the request? Why wouldn't it default to the namespace specified in the service?

      Thanks in advance.


        • 1. Re: implicit namespace support?

          The question is: does the client send a request that conforms to the abstract contract defined in wsdl.

          You might find that the message is invalid because it incorrectly does not namespace qualify the RPC element.

          To further support such "invalid" messages, you would need to have a pre-processing stage (i.e. a servlet filter)

          • 2. Re: implicit namespace support?

            I was using JBoss 4.0.5 and the next SOAP request works perfectly, now with JBoss 4.2 this request doesn't works.

            <?xml version="1.0"?>
            <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            <find xmlns="http://ejb.evoti.com/">

            This same request with explicit namespace works perfectly in Jboss 4.2

            <?xml version="1.0"?>
            <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            xmlns:ejb="http://ejb.evoti.com/" >
            <ejb:find >

            Why doesn't work in JBoss 4.2 my first request?

            Thanks in advance!!

            Jair Karim