> What is the reason of this "empty namespace" > generation? Is it correlated with the option namespace="##other" used in > the payload type definition?
It definitely should be qualified. The "Switches" element should be in the "http://iec.ch/TC57/2008/CIM-schema-cim12#" namespace. Do you have the code you are using to generate this? Dan On Monday, June 13, 2011 4:55:49 AM daniele1984 wrote: > Hello, i'm new to CXF and i'm trying to implement the simple web service > described here: > > http://my.epri.com/portal/server.pt?Abstract_id=000000000001018795 > > in appendix A and B. > The message specification also includes a payload, and i'm trying to use the > example payload defined on page 68 of the above document (which is the > description of three simple switches). I'm using the java classes > automatically generated from that WSDL file, however i have a problem with > the namespaces generated: the message i get is the following: > > [...] > <Payload> > <Switches xmlns:ns5="http://www.iec.ch/TC57/2008/schema/message" > xmlns="" xmlns:m="http://www.iec.ch/TC57/2008/CIM-schema-cim12#" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > schemaLocation="http://www.iec.ch/TC57/2008/CIM-schema-cim12#Switches.xsd"> > <Switch> > <mRID>35378383838</mRID> > <name>SW1</name> > <normalOpen>true</normalOpen> > </Switch> > <Switch> > <mRID>363482488448</mRID> > <name>SW2</name> > <normalOpen>true</normalOpen> > </Switch> > <Switch> > <mRID>894094949444</mRID> > <name>SW3</name> > <normalOpen>false</normalOpen> > </Switch> > </Switches> > </Payload> > [...] > > As you cas see, the 'm' namespace isn't used at all, and the empty namespace > xmlns="" is generated instead. What is the reason of this "empty namespace" > generation? Is it correlated with the option namespace="##other" used in > the payload type definition? > Thanks a lot! > Daniele Pala > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/cxf-namespace-handling-tp4484079p4484079.ht > ml Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
