>From what I've seen / heard, it's impossible with Aegis & code-first approach.
You could try the Jaxb binding, or using a WSDL-first approach. Kind regards, Dylan Honorez R & D Consultant 4C Technologies / kZen +32 (0)485 / 69.28.12 [EMAIL PROTECTED] From: Gary Moh [mailto:[EMAIL PROTECTED] Sent: dinsdag 20 maart 2007 20:49 To: [email protected] Subject: RE: [xfire-user] attributeFormDefault = qualified hi. i'm facing the same issue. did you get any reply? gary ________________________________ From: Honorez Dylan [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 08:03 To: [email protected] Subject: [xfire-user] attributeFormDefault = qualified Is there a way with code-first approach to override this? The problem is, JAXB overrides it correctly for its types using package-info.java, but my main service is not using that. So my wsdl has two schema's: <xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://www.cronos.be/... "> TYPES RELATED TO SERVICE GO HERE [javax.jws annotations] </xsd:schema> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"; attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.cronos.be/fedict/search/ws"; version="1.0"> JAXB GENERATED TYPES GO HERE [javax.xml.bind annotations] </xsd:schema> In AbstractWSDL I found this, what looks like being the issue: public Element createSchemaType(String namespace) { Element e = (Element) typeMap.get(namespace); if (e == null) { e = new Element("schema", XSD_NS); e.setAttribute(new Attribute("targetNamespace", namespace)); e.setAttribute(new Attribute("elementFormDefault", "qualified")); e.setAttribute(new Attribute("attributeFormDefault", "qualified")); setSchema(namespace, e); } return e; } How do I avoid my wsdl using two schema's with the same namespace but different attributeFormDefault? Dylan Honorez R & D Consultant 4C Technologies / kZen +32 (0)485 / 69.28.12 [EMAIL PROTECTED]
