Currently XFire doesn't support schemas without a targetNamespace. I totally understand the use case though. I believe there are just a couple areas that need to be patched to support this. Would you be interested in helping make the changes in XFire? Unfortunately I'm completely swamped this next week so I don't have much spare bandwidth. Thanks, - Dan
On 1/10/07, Chris Mathrusse <[EMAIL PROTECTED]> wrote:
I'm using XFire 1.2.4 Spring 2.0 XmlBeans 2.1.0 I'm exposing a service based upon a schema. I've generated my XmlBeans from the schema and defined my service interface. I've defined my service as follows: <beans xmlns="http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xf="http://xfire.codehaus.org/config/1.0"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://xfire.codehaus.org/config/1.0 services.xsd"> <bean id="OrderServiceTarget" class="com.sybase.it.cosmos.web.services.impl.OrderServiceImpl" autowire="byName"/> <xf:service> <xf:name>OrderService</xf:name> <xf:namespace>http://it.sybase.com/rosettanet/pip3A4/purchaseorder </xf:namespace> <xf:serviceClass>com.sybase.it.cosmos.web.services.OrderService </xf:serviceClass> <xf:serviceBean>#OrderServiceTarget</xf:serviceBean> <xf:style>document</xf:style> <xf:serviceFactory>org.codehaus.xfire.xmlbeans.XmlBeansServiceFactory </xf:serviceFactory> <xf:properties> <xf:property key="wsdlBuilder.removeAllImports">true</xf:property> </xf:properties> </xf:service> </beans> When I access my wsdl I get the following exception: javax.servlet.ServletException: The name "" is not legal for JDOM/XML namespaces: Namespace URIs must be non-null and non-empty Strings. The schema that my XmlBeans are based on does not define a namespace and looks as follows: <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"; elementFormDefault="unqualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.w3.org/XML/1998/namespace"; schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:element name="Pip3A4PurchaseOrderRequest" type="Pip3A4PurchaseOrderRequest"/> <xs:element name="Pip3A4PurchaseOrderConfirmation" type="Pip3A4PurchaseOrderConfirmation"/> .... </xs:schema> My WebService has a namespace so that should not be the issue. Is this an issue with the fact that my schema does not define a namespace? If so can XFire support this? It is a requirement for our service to support a document that contains no namespace as the RosettaNet document is based upon a DTD and not a schema. In addition, our trading partners will not be able to provide a namespace within the document as it would violate the message guidelines. Help please!! Thanks very much... --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
-- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
