Hi Dan,
Thanks for the quick response. I don¹t believe that I have multiple schemas
with the same namespace. I¹ve included representative samples of my WSDL
and XSD below (perhaps that will help?)... I was just doing some more
looking would setting the jaxb.search.packages property help? I have not
set it to anything. The error looks like it¹s happening in reading the WSDL
though, so I suspect the jaxb.search.packages property isn¹t even relevant
at this point.
Thanks,
Chris
===== BEGIN myservice.wsdl =====
<wsdl:definitions
name="MyService"
targetNamespace="http://mycompany.com/myservice"
xmlns:tns=" http://mycompany.com/myservice"
xmlns:types=" http://mycompany.com/myservice/types"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<xsd:schema>
<xsd:import namespace=" http://mycompany.com/myservice/types"
schemaLocation="mytypes.xsd"/>
</xsd:schema>
</wsdl:types>
...
</wsdl:definitions>
===== END myservice.wsdl =====
===== BEGIN mytypes.xsd =====
<?xml version="1.0" ?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace=" http://mycompany.com/myservice/types"
xmlns:tns=" http://mycompany.com/myservice/types"
version="1.0">
<xs:element name="someType">
<xs:complexType>
<xs:sequence>
<xs:element name="string1" type="xs:string"/>
<xs:element name="string2" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
...
</xs:schema>
===== END mytypes.xsd =====
On 1/2/07 1:56 PM, "Dan Diephouse" <[EMAIL PROTECTED]> wrote:
> Hi Christopher,
>
> Do you per chance have a WSDL with multiple <schema>s with the same
> targetNamespace? Someone filed that bug as XFIRE-720 and I just fixed it in
> SVN. I'll be publishing snapshots later today, but just wanted to see if it
> was the same issue.
>
> - Dan
>
> On 1/2/07, Christopher Moesel <[EMAIL PROTECTED]> wrote:
>> Hello All,
>>
>> I am attempting to use Xfire for a contract-first web service. I've written
>> the WSDL which imports a .XSD XML Schema file containing the types. I've
>> been able to successfully use the WsGen ANT task to generate all the
>> server-side files.
>>
>> My problem is in declaring the wsdlURL in the service definition. I am
>> using the spring configuration and have set the wsdlURL property to point to
>> the WSDL in several ways:
>> A) On the classpath
>> B) Via HTTP URL
>> C) On the file system
>>
>> In all cases it's able to find the WSDL, but seems to have trouble finding
>> the types. I get the following error when the service is instantiated on
>> the server:
>>
>> org.codehaus.xfire.XFireRuntimeException: Couldn't find schema for part:
>> {http://mycompany.com/myservice/types}someType
>>
>> [Note that I've changed the name of the NS and type for IP reasons]
>>
>> I am using Xfire 1.2.3 and XmlSchema 1.1. I've looked through the archives
>> and haven't seen any helpful info yet. Anyone have any ideas?
>>
>> Thanks,
>> Chris
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>
>