Hi! we wanted to know if there were some advance on this issue

Thanks!

On 1/29/07, Celeste Gunski <[EMAIL PROTECTED]> wrote:
Ok, we created a JIRA for this issue here:

http://jira.codehaus.org/browse/XFIRE-850

Thanks again

On 1/19/07, Dan Diephouse <[EMAIL PROTECTED]> wrote:
> Hmm, the two XML statements that you made are equivalent in XML, so that
> shouldn't change anything. It could be a JWSDP bug. Or it could be an XFire
> bug. Could file a JIRA issue for this so we can track it? Thanks,
>
> - Dan
>
>
> On 1/19/07, Celeste Gunski <[EMAIL PROTECTED]> wrote:
> >
> > Hi, we're having some problems to process the response of the service
> > with our client, we're using rpc/literal encoding for the messages,
> > XFire Eclipse plugin to develop the server side and JWSDP to develop
> > the client side, the problem is:
> >
> > We send a message like the following to the server and it works fine,
> > but the client can't process the response:
> >
> > ---- REQUEST ----
> > <?xml version="1.0"?>
> > <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> >    xmlns:xsd="http://www.w3.org/2001/XMLSchema ">
> >    <soapenv:Body>
> >        <ans:methodName xmlns:ans="http://my.namespace";>
> >            <parameter1>
> >                <item1>value1</item1>
> >                <item2>value2</item2>
> >            </parameter1>
> >        </ans:methodName>
> >    </soapenv:Body>
> > </soapenv:Envelope>
> >
> > ---- RESPONSE ----
> > <soap:Envelope xmlns:soap="
> http://schemas.xmlsoap.org/soap/envelope/";
> >    xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> >    xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance";>
> >    <soap:Body>
> >        <methodNameResponse xmlns="http://my.namespace ">
> >            <ns2:methodNameResult xmlns:ns2="http://my.namespace";>
> >                  <!-- Parameters with correct values -->
> >            </ns2:methodNameResult>
> >        </methodNameResponse>
> >    </soap:Body>
> > </soap:Envelope>
> >
> > So, searching on the ws-i, Basic Profile 1.1 we found this:
> >
> >    /"3.1.3 SOAP Body Namespace Qualification/
> >    /The use of unqualified element names may cause naming conflicts,
> >    therefore qualified names must be used for the children of soap:Body./
> >    /    R1014 The children of the soap:Body element in an ENVELOPE MUST
> >    be namespace qualified."/
> >
> > then we assume that the problem is in this line of the response
> >
> > "       <methodNameResponse xmlns="http://my.namespace";> "
> >
> > so, we made a server (hardcoded) that returns the same response
> > message but with the previous line like this :
> >
> > "       <ns1:methodNameResponse xmlns:ns1="http://my.namespace";> "
> >
> > and everything works just fine
> >
> > The question is: what can we do to make the server generates messages
> > like the hardcoded one? is there a way to tell the server how to build
> > the response?
> >
> > Thanks!
> >
> > Oh, and one more thing, this only happens with rpc/literal, with
> > document/literal there is no problem.
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> >     http://xircles.codehaus.org/manage_email
> >
> >
>
>
>
> --
> Dan Diephouse
> Envoi Solutions
> http://envoisolutions.com | http://netzooid.com/blog



--
Cele

---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to