"There Ain't No Such Thing As A Free Lunch"....Try Axis 1.2 alpha, If you find the problem persists, write up a small test case and post it as a bug in bugzilla.
thanks, dims --- Tony Opatha <[EMAIL PROTECTED]> wrote: > Do you know why AXIS 1.1 would include as part of each element it serializes (in > Doc/Lit SOAP) > the fully qualified namespace rather than just the namespace prefix? > > If we declare elementFormDefault as "qualified" in the XSD, > AXIS should not need to include explicitly the fully-qualified > namespace of the element that is defined as part of the > specific namespace that is declared in the XSD schema, right? > The namespace specific element schema is actually imported. > > Any ideas if there is a better way to workaround this problem in AXIS 1.1? > > Do you know if this problem does not exist in AXIS 1.2 > > Do you think this is a valid behaviour for web service run-time, e.g., in other > products? > > > Thanks. > > > List: axis-user > Subject: Re: xmlns=" " in the doc\literal SOAP message > From: "Dimuthu Leelarathne" <muthulee () vijayaba ! cse ! mrt ! ac ! lk> > Date: 2003-09-08 4:13:13 > [Download message RAW] > > It looks like a lot of discussion has been going on while I am away. > > It is news to me that this bug has been around for rpc\lit case. So I checked out \ > with wrap\lit case and it is not there, i.e. wrap\literal does not send any > xmlns="". \ > I thought of just mentioning it to the list. > > Dimuthu. > > > Tony Opatha <[EMAIL PROTECTED]> wrote: > >Since elementFormDefault is "qualified" -- then one could safely assume that \ > since >Axis generated this wsdl, it should also be serializing local elements in the > \ > appropriate >namespace...NOT adding xmlns="". > > Is there any workaround for this currently? > > That is exactly the problem I was identifying in AXIS previously (see below). If > \ > the elementFormDetail is qualified then we should not see explictly xmlns attributes > \ > in each element rather the namespace prefix should qualify the element that is part \ > of the document instance in the SOAP Body. > > This is especially problematic when we import additional schema from other \ > namespaces and declare them in the document schema that will serialized as part of \ > the SOAP Body by AXIS. I have observed that if you use directly AXIS SOAP APIs to \ > serialize the payload using the XSD schema this beahviour does not happen (if you > set \ > the QNames properly..), but it is jot the case using the AXIS messaging pipeline > (the \ > conventional way of processing SOAP payloads using WSDL). > > >>Is there a way in AXIS to support only inclusion of namespace prefix for \ > elements that >>are defined in a namespace that is not the default namespace rather > \ > than explcitly >>including the complete i.e., fully qualified namespace for each \ > sub-element of the >>document instance that is included in the SOAP Body? > >> > >>I would presume that either based on the XSD schema spec of the document and/or > >>the WSDL interface spec AXIS would be able to use the namespace prefix to \ > identify >>that a particular element is associated in a particular namespace. > > > Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > Cory, > > You're correct. Please file a bug report. > > Anne > > At 10:05 AM 9/5/2003 -0500, you wrote: > >I think I now know what the source of Dimuthu's problem was/is -- I've > >generated a doc/lit service in Axis and the schema that Axis generates for > >a given service indicates that the elementFormDefault is qualified, ie: > > > > > > > targetNamespace="http://test.xml.travelnow.com"; \ > elementFormDefault="qualified"> > > > > > > > > > > > > --------------------------------- > Do you Yahoo!? > Yahoo! Finance: Get your refund fast by filing online ===== Davanum Srinivas - http://webservices.apache.org/~dims/
