I'm trying to use wscompile with a WSDL file and XSDs and it keeps failing with the following error. The error is "[exec] error: modeler error: model error: invalid entity name: "EntityIdType" (in namespace: "http://ns.hr-xml.org/2004-08-02")" The type EntityIdType is defined in one of the included XSDs. The XSDs that I'm trying to use is for the HR-XML spec, so I don't really have any control over the XSDs themselves, but I tend to assume that the XSDs should be valid. I've got the WSDL file and XSDs available at http://quasistatic.com/webservices if anyone would be able to check them out for me. As a side note, I am able to use WSDL2Java from Axis on these files and it works fine. The command that I'm executing is "wscompile.bat -gen:server -f:documentliteral -mapping ${basedir}/generated/jaxrpc-mapping.xml -d ${basedir}/generated -s ${basedir}/generated/src -verbose -keep ${basedir}/wscompile-config.xml" and the wscompile-config.xml file contains:
<?xml version="1.0" encoding="UTF-8"?>
<configuration
xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">

<wsdl location="etc/AssessmentResult.wsdl" packageName="com.lominger.survey.assessment"/>
</configuration>

Thanks for any help you can provide!

 

 

Whats the wscompile version? you can check it by calling wscompile -version. Also send the wsdl file and I will have a look.

-vivek.

 

 

Vivek,

Thanks for responding to my post. I am using wscompile version:

C:\jwsdp-1.5\jaxrpc\bin>wscompile.bat -version
JAX-RPC Standard Implementation (1.1.2_01, build R40)

My WSDL and other files are up at http://quasistatic.com/webservices as well, but here's just the WSDL:

<?xml version="1.0" encoding="UTF-8"?>

<wsdl:definitions targetNamespace="http://assessment.survey.lominger.com/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://assessment.survey.lominger.com/"
xmlns:intf="http://assessment.survey.lominger.com/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:hrxml="http://ns.hr-xml.org/2004-08-02"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<wsdl:types>
<schema elementFormDefault="qualified"
targetNamespace="http://assessment.survey.lominger.com/"
xmlns="http://www.w3.org/2001/XMLSchema">

<xsd:import namespace="http://ns.hr-xml.org/2004-08-02"
schemaLocation="hrxml/Assessment/AssessmentResult.xsd" />

<xsd:element name="AssessmentResultResponse" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Root element for AssessmentResultResponse, which is designed to hold data necessary to convey information on the results of the assessment addition</xsd:documentation>
</xsd:annotation>
</xsd:element>

</schema>
</wsdl:types>

<wsdl:message name="AddAssessmentResultRequest">
<wsdl:part element="hrxml:AssessmentResult" name="parameters" />
</wsdl:message>

<wsdl:message name="AddAssessmentResultResponse">
<wsdl:part element="impl:AssessmentResultResponse" name="response" />
</wsdl:message>

<wsdl:portType name="Assessment">
<wsdl:operation name="addAssessmentResult">
<wsdl:input message="impl:AddAssessmentResultRequest" name="AddAssessmentResultRequest" />
<wsdl:output message="impl:AddAssessmentResultResponse" name="AddAssessmentResultResponse" />
</wsdl:operation>
</wsdl:portType>

<wsdl:binding name="AssessmentSoapBinding" type="impl:Assessment">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="addAssessmentResult">
<wsdlsoap:operation soapAction="" />
<wsdl:input name="AddAssessmentResultRequest">
<wsdlsoap:body use="literal" />
</wsdl:input>
<wsdl:output name="AddAssessmentResultResponse">
<wsdlsoap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>

<wsdl:service name="AssessmentService">
<wsdl:port binding="impl:AssessmentSoapBinding" name="AssessmentPort">
<wsdlsoap:address location="http://localhost:8180/axis/services/AssessmentResult" />
</wsdl:port>
</wsdl:service>

</wsdl:definitions>

Any help you can provide me is MUCH appreciated.

-Jesse

 

 

I downloaded the wsdl and hrxml.zip and able to reproduce the exception. But I see some problem in the hrxml/ResultAssesment/AssesmentResult.xsd.

There is no prefix declaration for EntityIdType. The way its declared is:

<xsd:element name="ClientId" type="EntityIdType">.

May be I can tell more if I could see EntityIdType.xsd, its not available thru the link you provided.

-vivek.

 

 

Vivek,

All the XSDs are actually out there, but the directory structure is confusing. If you go to http://www.quasistatic.com/webservices/hrxml/CPO/EntityIdType.xsd you will see the XSD you were interested in. If you look at the main XSD (i.e. AssessmentResult.xsd), you'll see that it does the following to include the EntityIdType.xsd:

<xsd:include schemaLocation="../CPO/EntityIdType.xsd"/>

I thought the absense of a prefix was wierd too, but I thought it was ok because the namespace declarations specify the xmlns and targetNamespace as the same as the ones in the EntityIdType.xsd file.

<xsd:schema 
targetNamespace="http://ns.hr-xml.org/2004-08-02" 
elementFormDefault="qualified" 
version="2004-08-02" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://ns.hr-xml.org/2004-08-02">

Thanks again for taking a look at this.

Jesse

 

 

Ok. I see that all the schema's are there as part of hrxml.zip. I think its bug in jaxrpc.

Please submit a bug at https://jax-rpc.dev.java.net/servlets/ProjectIssues. When we have a fix will post the jaxrpc build on this site.

This is where active discussion about jaxrpc takes place. Please join dev@jax-rpc.dev.java.net mailing list and post any problem issues related with it.

-vivek.

 

 

Hello.

Has there been any further activity on this issue?

Is there a workaround for this problem, please?

Kind Regards

 

 

Vivek,

I would be more than happy to post a bug regarding this issue, but I'm afraid I don't fully understand what the bug is. Do you think it's the way that wscompile handles included XSDs and their respective namespaces? If you could give me a little bit of an idea what to post the bug as, I'll go ahead and post it.

Thanks,
Jesse

 

 

Hi Vivek,

I am getting the exact same error that Jesse was getting. I was wondering if this is really a bug in JAX-RPC and if yes then has it been fixed in JWSDP 1.6?

Kindly reply ...

Thanks
Sharad

 

 

I am using JWSDP 1.6 and am getting the exact same error. I am fairly certain my WSDL and imported schemas are valid (everything validates in XMLSpy 2005). Would someone from Sun please post an update on this issue and let me know if there is a workaround?

Thanks!
Ian

 

 

I think this may have to do with a problem with reading the referenced schema from a relative path location.

You might want to try having the schemas accessible from a URL and using that value as the schemaLocation.