You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-user@ws.apache.org by Pablo Javier Roca Mendez <pa...@linux.intel.com> on 2006/08/16 10:14:52 UTC
splitting wsdl file in wsdl+xsd
Hello everyone!
I am using Muse 1.0.0 Final and trying to write my own services.
I wanted to split the wsdl file in one xsd file for the schema definitions
(properties and request/responses) that I then include in the wsdl file
(messages and porttype) with xsd:import.
If I split, then "ant generate" fails (after wsdl2Java imports the wsdl files,
but not the xsd) with following message:
BUILD FAILED
$WORK_DIR/build.xml:54: org.apache.ws.resource.InvalidWsrfWsdlException: Unable to locate the ResourceProperties document element with QName {http://my.company.com/MyService}ResourceProperties
If I put the xsd into the wsdl again, then "ant generate" succeeds.
My question is: Is it possible to split the wsdl into two files (xsd+wsdl) or
is it unsupported by wsdl2Java?
In case it is possible, is there any documentation where I can learn how to do
it?
Thanks in advance. Best regards,
Pablo
--
Pablo Javier Roca Mendez
Intel GmbH/Bruehl, Hermuelheimer Str. 8a, 50321 Bruehl, Germany
Tel.: +49-2232-209024
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
Re: splitting wsdl file in wsdl+xsd
Posted by Pablo Javier Roca Mendez <pa...@linux.intel.com>.
Hi Asaf,
thanks for the advice. I looked at the enterprise example before and also
noticed that you can import the schema files (*.xsd), but that is only usefull
after running "ant generate" (which calls wsdl2Java, which expects one big
wsdl).
My approach right now is to write the wsdl+xsd files and just before running
"ant generate" I merge them into a big wsdl file. After the generation I split
them again. Not very nice, but at least it works.
Best regards,
Pablo
On Tue, Aug 22, 2006 at 07:42:30PM +0200, Asaf Lahav wrote:
> Hi Pablo,
>
>
>
> I found a sample on the MUSE project that might help you...
>
> Look at the attached WSDL file.
>
> Mind the following imported schema baring the following namespace:
> http://ws.apache.org/muse/example/application/properties
>
>
>
> Hope this helps,
>
> Asaf
>
>
>
>
>
> -----Original Message-----
> From: Pablo Javier Roca Mendez
> [mailto:pablo_javier_roca_mendez@linux.intel.com]
> Sent: Wednesday, August 16, 2006 4:13 PM
> To: Asaf Lahav
> Cc: muse-user@ws.apache.org
> Subject: Re: splitting wsdl file in wsdl+xsd
>
>
>
> Hi Asaf,
>
>
>
> > Apparently the Wsdl2Java coming with the MUSE 1.0v doesn't allow importing
>
> > external XSD's nor WSDL's which are not part of the standard specs set.
>
>
>
> I also tried copying the xsd to $TOMCAT/webapps/muse/spec, but this also
>
> fails.
>
>
>
> Does this also means that it won't even work to import another wsdl file
> that
>
> isn't one of the standard ones? This will be a big problem when you have
>
> several wsdl files and want one of them to use definitions of another.
> Having
>
> to copy&paste the contents every time is not optimal...
>
> Do you know if this is the way to go? Do we need to have one big wsdl file
>
> with everything in it that is not in the spec directory? Or do you know a
> way
>
> to import your own wsdl files?
>
>
>
> Regards,
>
> Pablo
>
>
>
>
>
> On Wed, Aug 16, 2006 at 04:53:36PM +0200, Asaf Lahav wrote:
>
> > Hi Pablo,
>
> > Apparently the Wsdl2Java coming with the MUSE 1.0v doesn't allow importing
>
> > external XSD's nor WSDL's which are not part of the standard specs set.
>
> >
>
> > AFAIK, the way to accomplish what you are trying to do is by embedding the
>
> > schema into the WSDL
>
> >
>
> > -----Original Message-----
>
> > From: Pablo Javier Roca Mendez
>
> > [mailto:pablo_javier_roca_mendez@linux.intel.com]
>
> > Sent: Wednesday, August 16, 2006 3:37 PM
>
> > To: muse-user@ws.apache.org
>
> > Subject: Re: splitting wsdl file in wsdl+xsd
>
> >
>
> > Hi Asaf!
>
> >
>
> > > Send the WSDL and XSD files...
>
> >
>
> > I attached both files that produce the error.
>
> > If I copy the contents of the xsd file (omitting the very first line) and
>
> > paste it between the <types> and </types> marks in the wsdl file then it
>
> > works, so I guess the
>
> > <xsd:import namespace="http://gpe.intel.com/mgmt/vm"
>
> > schemaLocation="Vm.xsd" />
>
> > isn't working for wsdl2Java.
>
> >
>
> > Regards,
>
> > Pablo
>
> >
>
> > On Wed, Aug 16, 2006 at 01:39:55PM +0200, Asaf Lahav wrote:
>
> > > Hi Pablo,
>
> > > Send the WSDL and XSD files...
>
> > >
>
> > >
>
> > >
>
> > > -----Original Message-----
>
> > > From: Pablo Javier Roca Mendez
>
> > > [mailto:pablo_javier_roca_mendez@linux.intel.com]
>
> > > Sent: Wednesday, August 16, 2006 10:15 AM
>
> > > To: muse-user
>
> > > Subject: splitting wsdl file in wsdl+xsd
>
> > >
>
> > > Hello everyone!
>
> > >
>
> > > I am using Muse 1.0.0 Final and trying to write my own services.
>
> > > I wanted to split the wsdl file in one xsd file for the schema
> definitions
>
> > > (properties and request/responses) that I then include in the wsdl file
>
> > > (messages and porttype) with xsd:import.
>
> > > If I split, then "ant generate" fails (after wsdl2Java imports the wsdl
>
> > > files,
>
> > > but not the xsd) with following message:
>
> > > BUILD FAILED
>
> > > $WORK_DIR/build.xml:54: org.apache.ws.resource.InvalidWsrfWsdlException:
>
> > > Unable to locate the ResourceProperties document element with QName
>
> > > {http://my.company.com/MyService}ResourceProperties
>
> > >
>
> > > If I put the xsd into the wsdl again, then "ant generate" succeeds.
>
> > >
>
> > > My question is: Is it possible to split the wsdl into two files
> (xsd+wsdl)
>
> > > or
>
> > > is it unsupported by wsdl2Java?
>
> > > In case it is possible, is there any documentation where I can learn how
>
> > to
>
> > > do
>
> > > it?
>
> > >
>
> > > Thanks in advance. Best regards,
>
> > > Pablo
>
> > >
>
> >
>
>
>
> <?xml version="1.0"?>
>
> <definitions name="Application"
> targetNamespace="http://ws.apache.org/muse/example/application"
> xmlns="http://schemas.xmlsoap.org/wsdl/"
> xmlns:tns="http://ws.apache.org/muse/example/application"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
> xmlns:wsrp="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"
> xmlns:wsrpw="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.wsdl"
> xmlns:wsrlw="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-01.wsdl"
> xmlns:wsntw="http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-01.wsdl"
> xmlns:muws-p2-wsdl="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part2.wsdl"
> xmlns:app-prop="http://ws.apache.org/muse/example/application/properties"
> xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex"
> xmlns:wsa04="http://schemas.xmlsoap.org/ws/2004/08/addressing">
>
> <!-- Created by Kinga Dziembowski -->
>
> <import namespace="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.wsdl"
> location="../spec/wsrf/WS-ResourceProperties-1_2-Draft_01.wsdl"/>
>
> <import namespace="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-01.wsdl"
> location="../spec/wsrf/WS-ResourceLifetime-1_2-Draft_01.wsdl"/>
>
> <import namespace="http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-01.wsdl"
> location="../spec/wsn/WS-BaseNotification-1_2-Draft_01.wsdl"/>
>
> <import namespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part2.wsdl"
> location="../spec/wsdm/MUWS-Part2-1_0.wsdl"/>
> <import namespace="http://schemas.xmlsoap.org/ws/2004/09/mex"
> location="../spec/wsx/WS-MetadataExchange-2004_09.wsdl" />
>
> <types>
> <schema elementFormDefault="qualified"
> targetNamespace="http://ws.apache.org/muse/example/application"
> xmlns:tns="http://ws.apache.org/muse/example/application"
> xmlns="http://www.w3.org/2001/XMLSchema"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:wsrl="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-01.xsd"
> xmlns:wsbf="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-BaseFaults-1.2-draft-01.xsd"
> xmlns:wsnt="http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-01.xsd"
> xmlns:muws-p1-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part1.xsd"
> xmlns:muws-p2-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part2.xsd"
> xmlns:ws-ext="http://ws.apache.org/namespaces/muse/muws-ext-1.xsd"
> xmlns:example-wsf="http://ws.apache.org/muse/example/shared"
> xmlns:app-prop="http://ws.apache.org/muse/example/application/properties" >
>
> <xsd:import namespace="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-BaseFaults-1.2-draft-01.xsd"
> schemaLocation="../spec/wsrf/WS-BaseFaults-1_2-Draft_01.xsd"/>
>
> <xsd:import namespace="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-01.xsd"
> schemaLocation="../spec/wsrf/WS-ResourceLifetime-1_2-Draft_01.xsd"/>
>
> <xsd:import namespace="http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-01.xsd"
> schemaLocation="../spec/wsn/WS-BaseNotification-1_2-Draft_01.xsd"/>
>
> <xsd:import namespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part1.xsd"
> schemaLocation="../spec/wsdm/MUWS-Part1-1_0.xsd"/>
>
> <xsd:import namespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part2.xsd"
> schemaLocation="../spec/wsdm/MUWS-Part2-1_0.xsd"/>
> <xsd:import namespace="http://ws.apache.org/namespaces/muse/muws-ext-1.xsd"
> schemaLocation="../wsdl/muws-ext-1.xsd"/>
> <xsd:import namespace="http://ws.apache.org/muse/example/shared"
> schemaLocation="../wsdl/shared.xsd"/>
> <xsd:import namespace="http://ws.apache.org/muse/example/application/properties"
> schemaLocation="../wsdl/application.xsd"/>
>
> <!-- *** Add an element definition here for each of your custom resource properties *** -->
> <!-- *** e.g.: <element name="MyProperty" type="xsd:string" /> *** -->
>
> <!-- Resource Properties Document Schema -->
> <element name="ApplicationProperties">
> <complexType>
> <sequence>
>
> <!-- *** If you wish to implement the wsrl:ScheduledResourceTermination portType,
> uncomment the below two lines *** -->
> <!--
> <element ref="wsrl:CurrentTime" />
> <element ref="wsrl:TerminationTime" />
> -->
>
> <!-- *** If you wish to implement the wsnt:NotificationProducer portType,
> uncomment the below three lines *** -->
>
> <element ref="wsnt:Topic" minOccurs="1" maxOccurs="1" />
> <element ref="wsnt:FixedTopicSet" />
> <element ref="wsnt:TopicExpressionDialects" minOccurs="1" maxOccurs="1" />
>
> <!-- *** The ResourceId property is _required_ by the MUWS spec *** -->
> <element ref="muws-p1-xs:ResourceId"/>
>
> <!-- *** If you wish to implement the MUWS ManageabilityCharacteristics capability,
> uncomment the below line *** -->
>
> <element ref="muws-p1-xs:ManageabilityCapability" minOccurs="0" maxOccurs="unbounded"/>
>
>
> <!-- *** If you wish to implement the MUWS CorrelatableProperties capability,
> uncomment the below line *** -->
> <!--
> <element ref="muws-p1-xs:CorrelatableProperties" minOccurs="0" maxOccurs="unbounded"/>
> -->
>
> <!-- *** If you wish to implement the MUWS Description capability,
> uncomment the below three lines *** -->
>
> <element ref="muws-p2-xs:Caption" minOccurs="1" maxOccurs="1"/>
> <element ref="muws-p2-xs:Description" minOccurs="0" maxOccurs="unbounded"/>
> <element ref="muws-p2-xs:Version" minOccurs="0"/>
>
>
> <!-- *** If you wish to implement the MUWS OperationalStatus capability,
> uncomment the below line *** -->
>
> <element ref="muws-p2-xs:OperationalStatus"/>
>
>
> <!-- *** If you wish to implement the MUWS Metrics capability,
> uncomment the below line *** -->
>
> <element ref="muws-p2-xs:CurrentTime"/>
>
>
> <!-- *** If you wish to implement the MUWS Relationships capability,
> uncomment the below line *** -->
>
> <element ref="muws-p2-xs:Relationship" minOccurs="0" maxOccurs="unbounded"/>
>
> <!-- SHARED PROPERTIES DEFINED muws-ext-1.xsd
> Resource exposing this properties should add to the list returned by GetProperty
> for muws-p1-xs:ManageabilityCapability property,
> the string "http://ws.apache.org/namespaces/muse/capabilities/muws-ext-1".
> This signals that the resource support extended management capability.
>
> -->
>
>
> <element ref="ws-ext:ResourceType" minOccurs="1" maxOccurs="1" />
> <element ref="ws-ext:ResourceHostname" minOccurs="1" maxOccurs="1" />
> <element ref="ws-ext:CreationTime" minOccurs="1" maxOccurs="1" />
> <element ref="ws-ext:Owner" minOccurs="1" maxOccurs="1" />
>
> <!-- SPECIFIC PROPERTIES DEFINED IN APPLICATION.XSD -->
>
> <element ref="app-prop:NumberOfOutstandingRequests" minOccurs="1" maxOccurs="1" />
> <element ref="app-prop:TotalNumberOfRequests" minOccurs="1" maxOccurs="1" />
> <element ref="example-wsf:CumulativeExecutionTime" minOccurs="1" maxOccurs="1" />
>
>
>
> <!-- *** Uncomment the below any element if you want to permit resource property elements
> with arbitrary names (not generally recommended) *** -->
> <!--
> <any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/>
> -->
>
> </sequence>
> </complexType>
> </element>
>
> <!-- *** Add element definitions for custom request/response/fault types here *** -->
>
> </schema>
> </types>
>
> <!-- *** Add message definitions for custom request/response/fault types here *** -->
>
>
> <message name="StartEventsRequest">
> <part name="StartEventsRequest" element="app-prop:StartEvents"/>
> </message>
> <message name="StartEventsResponse">
> <part name="StartEventsResponse" element="app-prop:StartEventsResponse"/>
> </message>
>
> <message name="StopEventsRequest">
> <part name="StopEventsRequest" element="app-prop:StopEvents"/>
> </message>
> <message name="StopEventsResponse">
> <part name="ResumeResponse" element="app-prop:StopEventsResponse"/>
> </message>
>
> <message name="EventsEmitFaultMessage">
> <part name="document" element="app-prop:EventsEmitFault"/>
> </message>
>
> <portType name="ApplicationPortType" wsrp:ResourceProperties="tns:ApplicationProperties">
>
> <operation name="GetResourceProperty">
> <input name="GetResourcePropertyRequest" message="wsrpw:GetResourcePropertyRequest"/>
> <output name="GetResourcePropertyResponse" message="wsrpw:GetResourcePropertyResponse"/>
> <fault name="ResourceUnknownFault" message="wsrpw:ResourceUnknownFault"/>
> <fault name="InvalidResourcePropertyQNameFault" message="wsrpw:InvalidResourcePropertyQNameFault"/>
> </operation>
>
> <!-- *** If you wish to implement the WSRP GetMultipleResourceProperties portType,
> uncomment the below operation block *** -->
>
> <operation name="GetMultipleResourceProperties">
> <input name="GetMultipleResourcePropertiesRequest" message="wsrpw:GetMultipleResourcePropertiesRequest"/>
> <output name="GetMultipleResourcePropertiesResponse" message="wsrpw:GetMultipleResourcePropertiesResponse"/>
> <fault name="ResourceUnknownFault" message="wsrpw:ResourceUnknownFault"/>
> <fault name="InvalidResourcePropertyQNameFault" message="wsrpw:InvalidResourcePropertyQNameFault"/>
> </operation>
>
>
> <!-- *** If you wish to implement the WSRP SetResourceProperties portType,
> uncomment the below operation block *** -->
> <!--
> <operation name="SetResourceProperties">
> <input name="SetResourcePropertiesRequest" message="wsrpw:SetResourcePropertiesRequest"/>
> <output name="SetResourcePropertiesResponse" message="wsrpw:SetResourcePropertiesResponse"/>
> <fault name="ResourceUnknownFault" message="wsrpw:ResourceUnknownFault"/>
> <fault name="InvalidResourcePropertyQNameFault" message="wsrpw:InvalidResourcePropertyQNameFault"/>
> <fault name="InvalidSetResourcePropertiesRequestContentFault" message="wsrpw:InvalidSetResourcePropertiesRequestContentFault"/>
> <fault name="UnableToModifyResourcePropertyFault" message="wsrpw:UnableToModifyResourcePropertyFault"/>
> <fault name="SetResourcePropertyRequestFailedFault" message="wsrpw:SetResourcePropertyRequestFailedFault"/>
> </operation>
> -->
>
> <!-- *** If you wish to implement the WSRP QueryResourceProperties portType,
> uncomment the below operation block *** -->
>
> <operation name="QueryResourceProperties">
> <input name="QueryResourcePropertiesRequest" message="wsrpw:QueryResourcePropertiesRequest"/>
> <output name="QueryResourcePropertiesResponse" message="wsrpw:QueryResourcePropertiesResponse"/>
> <fault name="ResourceUnknownFault" message="wsrpw:ResourceUnknownFault"/>
> <fault name="InvalidResourcePropertyQNameFault" message="wsrpw:InvalidResourcePropertyQNameFault"/>
> <fault name="UnknownQueryExpressionDialectFault" message="wsrpw:UnknownQueryExpressionDialectFault"/>
> <fault name="InvalidQueryExpressionFault" message="wsrpw:InvalidQueryExpressionFault"/>
> <fault name="QueryEvaluationErrorFault" message="wsrpw:QueryEvaluationErrorFault"/>
> </operation>
>
>
> <!-- *** If you wish to implement the WSRL ImmediateResourceTermination portType,
> uncomment the below operation block *** -->
> <!--
> <operation name="Destroy">
> <input message="wsrlw:DestroyRequest"/>
> <output message="wsrlw:DestroyResponse"/>
> <fault name="ResourceUnknownFault" message="wsrlw:ResourceUnknownFault"/>
> <fault name="ResourceNotDestroyedFault" message="wsrlw:ResourceNotDestroyedFault"/>
> </operation>
> -->
>
> <!-- *** If you wish to implement the WSRL ScheduledResourceTermination portType,
> uncomment the below operation block *** -->
> <!--
> <operation name="SetTerminationTime">
> <input message="wsrlw:SetTerminationTimeRequest"/>
> <output message="wsrlw:SetTerminationTimeResponse"/>
> <fault name="ResourceUnknownFault" message="wsrlw:ResourceUnknownFault"/>
> <fault name="UnableToSetTerminationTimeFault" message="wsrlw:UnableToSetTerminationTimeFault"/>
> <fault name="TerminationTimeChangeRejectedFault" message="wsrlw:TerminationTimeChangeRejectedFault"/>
> </operation>
> -->
>
> <!-- *** If you wish to implement the WSNT NotificationProducer portType,
> uncomment the below two operation blocks *** -->
>
> <operation name="Subscribe">
> <input message="wsntw:SubscribeRequest" />
> <output message="wsntw:SubscribeResponse" />
> <fault name="ResourceUnknownFault" message="wsntw:ResourceUnknownFault" />
> <fault name="SubscribeCreationFailedFault" message="wsntw:SubscribeCreationFailedFault" />
> <fault name="TopicPathDialectUnknownFault" message="wsntw:TopicPathDialectUnknownFault" />
> </operation>
>
> <operation name="GetCurrentMessage">
> <input message="wsntw:GetCurrentMessageRequest" />
> <output message="wsntw:GetCurrentMessageResponse" />
> <fault name="ResourceUnknownFault" message="wsntw:ResourceUnknownFault" />
> <fault name="InvalidTopicExpressionFault" message="wsntw:InvalidTopicExpressionFault" />
> <fault name="TopicNotSupportedFault" message="wsntw:TopicNotSupportedFault" />
> <fault name="NoCurrentMessageOnTopicFault" message="wsntw:NoCurrentMessageOnTopicFault" />
> </operation>
>
>
> <!-- *** If you wish to implement the MUWS QueryRelationshipsByType operation,
> uncomment the below operation block *** -->
>
> <operation name="QueryRelationshipsByType">
> <input message="muws-p2-wsdl:QueryRelationshipsByTypeRequest"/>
> <output message="muws-p2-wsdl:QueryRelationshipsByTypeResponse"/>
> </operation>
>
>
> <!-- *** Add an operation block here for each of your custom operations *** -->
>
>
> <operation name="StartEvents">
> <input message="tns:StartEventsRequest" />
> <output message="tns:StartEventsResponse" />
> <fault name="EventsEmitFault" message="tns:EventsEmitFaultMessage" />
> </operation>
>
> <operation name="StopEvents">
> <input message="tns:StopEventsRequest" />
> <output message="tns:StopEventsResponse" />
> <fault name="EventsEmitFault" message="tns:EventsEmitFaultMessage" />
> </operation>
>
> <!-- GetMetadata operation for retrieving WSDL -->
>
> <operation name="GetMetadata" >
> <input message="wsx:GetMetadataMsg"
> wsa04:Action="http://schemas.xmlsoap.org/ws/2004/09/mex/GetMetadata/Request" />
> <output message="wsx:GetMetadataResponseMsg"
> wsa04:Action="http://schemas.xmlsoap.org/ws/2004/09/mex/GetMetadata/Response" />
> </operation>
> <operation name="Get" >
> <input message="wsx:GetMsg"
> wsa04:Action="http://schemas.xmlsoap.org/ws/2004/09/mex/Get/Request" />
> <output message="wsx:GetResponseMsg"
> wsa04:Action="http://schemas.xmlsoap.org/ws/2004/09/mex/Get/Response" />
> </operation>
>
>
> </portType>
>
> <binding name="ApplicationSoapHttpBinding" type="tns:ApplicationPortType">
>
> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
>
> <operation name="GetResourceProperty">
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> <fault name="ResourceUnknownFault">
> <soap:fault name="ResourceUnknownFault" use="literal"/>
> </fault>
> <fault name="InvalidResourcePropertyQNameFault">
> <soap:fault name="InvalidResourcePropertyQNameFault" use="literal"/>
> </fault>
> </operation>
>
> <!-- *** If you wish to implement the WSRP GetMultipleResourceProperties portType,
> uncomment the below operation block *** -->
>
> <operation name="GetMultipleResourceProperties">
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> <fault name="ResourceUnknownFault">
> <soap:fault name="ResourceUnknownFault" use="literal"/>
> </fault>
> <fault name="InvalidResourcePropertyQNameFault">
> <soap:fault name="InvalidResourcePropertyQNameFault" use="literal"/>
> </fault>
> </operation>
>
>
> <!-- *** If you wish to implement the WSRP SetResourceProperties portType,
> uncomment the below operation block *** -->
> <!--
> <operation name="SetResourceProperties">
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> <fault name="ResourceUnknownFault">
> <soap:fault name="ResourceUnknownFault" use="literal"/>
> </fault>
> <fault name="InvalidResourcePropertyQNameFault">
> <soap:fault name="InvalidResourcePropertyQNameFault" use="literal"/>
> </fault>
> <fault name="UnableToModifyResourcePropertyFault">
> <soap:fault name="UnableToModifyResourcePropertyFault" use="literal"/>
> </fault>
> <fault name="InvalidSetResourcePropertiesRequestContentFault">
> <soap:fault name="InvalidSetResourcePropertiesRequestContentFault" use="literal"/>
> </fault>
> <fault name="SetResourcePropertyRequestFailedFault">
> <soap:fault name="SetResourcePropertyRequestFailedFault" use="literal"/>
> </fault>
> </operation>
> -->
>
> <!-- *** If you wish to implement the WSRP QueryResourceProperties portType,
> uncomment the below operation block *** -->
>
> <operation name="QueryResourceProperties">
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> <fault name="ResourceUnknownFault">
> <soap:fault name="ResourceUnknownFault" use="literal"/>
> </fault>
> <fault name="InvalidResourcePropertyQNameFault">
> <soap:fault name="InvalidResourcePropertyQNameFault" use="literal"/>
> </fault>
> <fault name="UnknownQueryExpressionDialectFault">
> <soap:fault name="UnknownQueryExpressionDialectFault" use="literal"/>
> </fault>
> <fault name="InvalidQueryExpressionFault">
> <soap:fault name="InvalidQueryExpressionFault" use="literal"/>
> </fault>
> <fault name="QueryEvaluationErrorFault">
> <soap:fault name="QueryEvaluationErrorFault" use="literal"/>
> </fault>
> </operation>
>
>
> <!-- *** If you wish to implement the WSRL ImmediateResourceTermination portType,
> uncomment the below operation block *** -->
> <!--
> <operation name="Destroy">
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> <fault name="ResourceUnknownFault">
> <soap:fault name="ResourceUnknownFault" use="literal"/>
> </fault>
> <fault name="ResourceNotDestroyedFault">
> <soap:fault name="ResourceNotDestroyedFault" use="literal"/>
> </fault>
> </operation>
> -->
>
> <!-- *** If you wish to implement the WSRL ScheduledResourceTermination portType,
> uncomment the below operation block *** -->
> <!--
> <operation name="SetTerminationTime">
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> <fault name="ResourceUnknownFault">
> <soap:fault name="ResourceUnknownFault" use="literal"/>
> </fault>
> <fault name="UnableToSetTerminationTimeFault">
> <soap:fault name="UnableToSetTerminationTimeFault" use="literal"/>
> </fault>
> <fault name="TerminationTimeChangeRejectedFault">
> <soap:fault name="TerminationTimeChangeRejectedFault" use="literal"/>
> </fault>
> </operation>
> -->
>
> <!-- *** If you wish to implement the WSNT NotificationProducer portType,
> uncomment the below two operation blocks *** -->
>
> <operation name="Subscribe">
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> <fault name="ResourceUnknownFault">
> <soap:fault name="ResourceUnknownFault" use="literal"/>
> </fault>
> <fault name="SubscribeCreationFailedFault">
> <soap:fault name="SubscribeCreationFailedFault" use="literal"/>
> </fault>
> <fault name="TopicPathDialectUnknownFault">
> <soap:fault name="TopicPathDialectUnknownFault" use="literal"/>
> </fault>
> </operation>
> <operation name="GetCurrentMessage">
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> <fault name="ResourceUnknownFault">
> <soap:fault name="ResourceUnknownFault" use="literal"/>
> </fault>
> <fault name="InvalidTopicExpressionFault">
> <soap:fault name="InvalidTopicExpressionFault" use="literal"/>
> </fault>
> <fault name="TopicNotSupportedFault">
> <soap:fault name="TopicNotSupportedFault" use="literal"/>
> </fault>
> <fault name="NoCurrentMessageOnTopicFault">
> <soap:fault name="NoCurrentMessageOnTopicFault" use="literal"/>
> </fault>
> </operation>
>
>
> <!-- *** If you wish to implement the MUWS QueryRelationshipsByType operation,
> uncomment the below operation block *** -->
>
> <operation name="QueryRelationshipsByType">
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> </operation>
>
>
> <!-- *** Add an operation block here for each of your custom operations *** -->
>
> <operation name="StartEvents">
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> <fault name="EventsEmitFault">
> <soap:fault name="EventsEmitFault" use="literal"/>
> </fault>
> </operation>
> <operation name="StopEvents">
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> <fault name="EventsEmitFault">
> <soap:fault name="EventsEmitFault" use="literal"/>
> </fault>
> </operation>
>
> <!-- GetMetadata operation for retrieving WSDL -->
>
> <operation name="GetMetadata" >
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> </operation>
> <operation name="Get" >
> <soap:operation style="document"/>
> <input>
> <soap:body use="literal"/>
> </input>
> <output>
> <soap:body use="literal"/>
> </output>
> </operation>
>
>
> </binding>
>
> <service name="ApplicationService">
> <!-- Note: the port name becomes the service name in the wsdd generated by Wsdl2Java -->
> <!-- *** Change the port name and the soap:address location below to reflect the desired endpoint URL *** -->
> <port name="application" binding="tns:ApplicationSoapHttpBinding">
> <soap:address location="http://localhost:8080/muse/services/application" />
> </port>
> </service>
>
> </definitions>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
--
Pablo Javier Roca Mendez
Intel GmbH/Bruehl, Hermuelheimer Str. 8a, 50321 Bruehl, Germany
Tel.: +49-2232-209024
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: splitting wsdl file in wsdl+xsd
Posted by Asaf Lahav <as...@primagrid.com>.
Hi Pablo,
I found a sample on the MUSE project that might help you...
Look at the attached WSDL file.
Mind the following imported schema baring the following namespace:
http://ws.apache.org/muse/example/application/properties
Hope this helps,
Asaf
-----Original Message-----
From: Pablo Javier Roca Mendez
[mailto:pablo_javier_roca_mendez@linux.intel.com]
Sent: Wednesday, August 16, 2006 4:13 PM
To: Asaf Lahav
Cc: muse-user@ws.apache.org
Subject: Re: splitting wsdl file in wsdl+xsd
Hi Asaf,
> Apparently the Wsdl2Java coming with the MUSE 1.0v doesn't allow importing
> external XSD's nor WSDL's which are not part of the standard specs set.
I also tried copying the xsd to $TOMCAT/webapps/muse/spec, but this also
fails.
Does this also means that it won't even work to import another wsdl file
that
isn't one of the standard ones? This will be a big problem when you have
several wsdl files and want one of them to use definitions of another.
Having
to copy&paste the contents every time is not optimal...
Do you know if this is the way to go? Do we need to have one big wsdl file
with everything in it that is not in the spec directory? Or do you know a
way
to import your own wsdl files?
Regards,
Pablo
On Wed, Aug 16, 2006 at 04:53:36PM +0200, Asaf Lahav wrote:
> Hi Pablo,
> Apparently the Wsdl2Java coming with the MUSE 1.0v doesn't allow importing
> external XSD's nor WSDL's which are not part of the standard specs set.
>
> AFAIK, the way to accomplish what you are trying to do is by embedding the
> schema into the WSDL
>
> -----Original Message-----
> From: Pablo Javier Roca Mendez
> [mailto:pablo_javier_roca_mendez@linux.intel.com]
> Sent: Wednesday, August 16, 2006 3:37 PM
> To: muse-user@ws.apache.org
> Subject: Re: splitting wsdl file in wsdl+xsd
>
> Hi Asaf!
>
> > Send the WSDL and XSD files...
>
> I attached both files that produce the error.
> If I copy the contents of the xsd file (omitting the very first line) and
> paste it between the <types> and </types> marks in the wsdl file then it
> works, so I guess the
> <xsd:import namespace="http://gpe.intel.com/mgmt/vm"
> schemaLocation="Vm.xsd" />
> isn't working for wsdl2Java.
>
> Regards,
> Pablo
>
> On Wed, Aug 16, 2006 at 01:39:55PM +0200, Asaf Lahav wrote:
> > Hi Pablo,
> > Send the WSDL and XSD files...
> >
> >
> >
> > -----Original Message-----
> > From: Pablo Javier Roca Mendez
> > [mailto:pablo_javier_roca_mendez@linux.intel.com]
> > Sent: Wednesday, August 16, 2006 10:15 AM
> > To: muse-user
> > Subject: splitting wsdl file in wsdl+xsd
> >
> > Hello everyone!
> >
> > I am using Muse 1.0.0 Final and trying to write my own services.
> > I wanted to split the wsdl file in one xsd file for the schema
definitions
> > (properties and request/responses) that I then include in the wsdl file
> > (messages and porttype) with xsd:import.
> > If I split, then "ant generate" fails (after wsdl2Java imports the wsdl
> > files,
> > but not the xsd) with following message:
> > BUILD FAILED
> > $WORK_DIR/build.xml:54: org.apache.ws.resource.InvalidWsrfWsdlException:
> > Unable to locate the ResourceProperties document element with QName
> > {http://my.company.com/MyService}ResourceProperties
> >
> > If I put the xsd into the wsdl again, then "ant generate" succeeds.
> >
> > My question is: Is it possible to split the wsdl into two files
(xsd+wsdl)
> > or
> > is it unsupported by wsdl2Java?
> > In case it is possible, is there any documentation where I can learn how
> to
> > do
> > it?
> >
> > Thanks in advance. Best regards,
> > Pablo
> >
>
--
Pablo Javier Roca Mendez
Intel GmbH/Bruehl, Hermuelheimer Str. 8a, 50321 Bruehl, Germany
Tel.: +49-2232-209024
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: splitting wsdl file in wsdl+xsd
Posted by Asaf Lahav <as...@primagrid.com>.
This is the only way in which I succeeded adding schema types to MUSE 1.0
services.
-----Original Message-----
From: Pablo Javier Roca Mendez
[mailto:pablo_javier_roca_mendez@linux.intel.com]
Sent: Wednesday, August 16, 2006 4:13 PM
To: Asaf Lahav
Cc: muse-user@ws.apache.org
Subject: Re: splitting wsdl file in wsdl+xsd
Hi Asaf,
> Apparently the Wsdl2Java coming with the MUSE 1.0v doesn't allow importing
> external XSD's nor WSDL's which are not part of the standard specs set.
I also tried copying the xsd to $TOMCAT/webapps/muse/spec, but this also
fails.
Does this also means that it won't even work to import another wsdl file
that
isn't one of the standard ones? This will be a big problem when you have
several wsdl files and want one of them to use definitions of another.
Having
to copy&paste the contents every time is not optimal...
Do you know if this is the way to go? Do we need to have one big wsdl file
with everything in it that is not in the spec directory? Or do you know a
way
to import your own wsdl files?
Regards,
Pablo
On Wed, Aug 16, 2006 at 04:53:36PM +0200, Asaf Lahav wrote:
> Hi Pablo,
> Apparently the Wsdl2Java coming with the MUSE 1.0v doesn't allow importing
> external XSD's nor WSDL's which are not part of the standard specs set.
>
> AFAIK, the way to accomplish what you are trying to do is by embedding the
> schema into the WSDL
>
> -----Original Message-----
> From: Pablo Javier Roca Mendez
> [mailto:pablo_javier_roca_mendez@linux.intel.com]
> Sent: Wednesday, August 16, 2006 3:37 PM
> To: muse-user@ws.apache.org
> Subject: Re: splitting wsdl file in wsdl+xsd
>
> Hi Asaf!
>
> > Send the WSDL and XSD files...
>
> I attached both files that produce the error.
> If I copy the contents of the xsd file (omitting the very first line) and
> paste it between the <types> and </types> marks in the wsdl file then it
> works, so I guess the
> <xsd:import namespace="http://gpe.intel.com/mgmt/vm"
> schemaLocation="Vm.xsd" />
> isn't working for wsdl2Java.
>
> Regards,
> Pablo
>
> On Wed, Aug 16, 2006 at 01:39:55PM +0200, Asaf Lahav wrote:
> > Hi Pablo,
> > Send the WSDL and XSD files...
> >
> >
> >
> > -----Original Message-----
> > From: Pablo Javier Roca Mendez
> > [mailto:pablo_javier_roca_mendez@linux.intel.com]
> > Sent: Wednesday, August 16, 2006 10:15 AM
> > To: muse-user
> > Subject: splitting wsdl file in wsdl+xsd
> >
> > Hello everyone!
> >
> > I am using Muse 1.0.0 Final and trying to write my own services.
> > I wanted to split the wsdl file in one xsd file for the schema
definitions
> > (properties and request/responses) that I then include in the wsdl file
> > (messages and porttype) with xsd:import.
> > If I split, then "ant generate" fails (after wsdl2Java imports the wsdl
> > files,
> > but not the xsd) with following message:
> > BUILD FAILED
> > $WORK_DIR/build.xml:54: org.apache.ws.resource.InvalidWsrfWsdlException:
> > Unable to locate the ResourceProperties document element with QName
> > {http://my.company.com/MyService}ResourceProperties
> >
> > If I put the xsd into the wsdl again, then "ant generate" succeeds.
> >
> > My question is: Is it possible to split the wsdl into two files
(xsd+wsdl)
> > or
> > is it unsupported by wsdl2Java?
> > In case it is possible, is there any documentation where I can learn how
> to
> > do
> > it?
> >
> > Thanks in advance. Best regards,
> > Pablo
> >
>
--
Pablo Javier Roca Mendez
Intel GmbH/Bruehl, Hermuelheimer Str. 8a, 50321 Bruehl, Germany
Tel.: +49-2232-209024
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
Re: splitting wsdl file in wsdl+xsd
Posted by Pablo Javier Roca Mendez <pa...@linux.intel.com>.
Hi Asaf,
> Apparently the Wsdl2Java coming with the MUSE 1.0v doesn't allow importing
> external XSD's nor WSDL's which are not part of the standard specs set.
I also tried copying the xsd to $TOMCAT/webapps/muse/spec, but this also
fails.
Does this also means that it won't even work to import another wsdl file that
isn't one of the standard ones? This will be a big problem when you have
several wsdl files and want one of them to use definitions of another. Having
to copy&paste the contents every time is not optimal...
Do you know if this is the way to go? Do we need to have one big wsdl file
with everything in it that is not in the spec directory? Or do you know a way
to import your own wsdl files?
Regards,
Pablo
On Wed, Aug 16, 2006 at 04:53:36PM +0200, Asaf Lahav wrote:
> Hi Pablo,
> Apparently the Wsdl2Java coming with the MUSE 1.0v doesn't allow importing
> external XSD's nor WSDL's which are not part of the standard specs set.
>
> AFAIK, the way to accomplish what you are trying to do is by embedding the
> schema into the WSDL
>
> -----Original Message-----
> From: Pablo Javier Roca Mendez
> [mailto:pablo_javier_roca_mendez@linux.intel.com]
> Sent: Wednesday, August 16, 2006 3:37 PM
> To: muse-user@ws.apache.org
> Subject: Re: splitting wsdl file in wsdl+xsd
>
> Hi Asaf!
>
> > Send the WSDL and XSD files...
>
> I attached both files that produce the error.
> If I copy the contents of the xsd file (omitting the very first line) and
> paste it between the <types> and </types> marks in the wsdl file then it
> works, so I guess the
> <xsd:import namespace="http://gpe.intel.com/mgmt/vm"
> schemaLocation="Vm.xsd" />
> isn't working for wsdl2Java.
>
> Regards,
> Pablo
>
> On Wed, Aug 16, 2006 at 01:39:55PM +0200, Asaf Lahav wrote:
> > Hi Pablo,
> > Send the WSDL and XSD files...
> >
> >
> >
> > -----Original Message-----
> > From: Pablo Javier Roca Mendez
> > [mailto:pablo_javier_roca_mendez@linux.intel.com]
> > Sent: Wednesday, August 16, 2006 10:15 AM
> > To: muse-user
> > Subject: splitting wsdl file in wsdl+xsd
> >
> > Hello everyone!
> >
> > I am using Muse 1.0.0 Final and trying to write my own services.
> > I wanted to split the wsdl file in one xsd file for the schema definitions
> > (properties and request/responses) that I then include in the wsdl file
> > (messages and porttype) with xsd:import.
> > If I split, then "ant generate" fails (after wsdl2Java imports the wsdl
> > files,
> > but not the xsd) with following message:
> > BUILD FAILED
> > $WORK_DIR/build.xml:54: org.apache.ws.resource.InvalidWsrfWsdlException:
> > Unable to locate the ResourceProperties document element with QName
> > {http://my.company.com/MyService}ResourceProperties
> >
> > If I put the xsd into the wsdl again, then "ant generate" succeeds.
> >
> > My question is: Is it possible to split the wsdl into two files (xsd+wsdl)
> > or
> > is it unsupported by wsdl2Java?
> > In case it is possible, is there any documentation where I can learn how
> to
> > do
> > it?
> >
> > Thanks in advance. Best regards,
> > Pablo
> >
>
--
Pablo Javier Roca Mendez
Intel GmbH/Bruehl, Hermuelheimer Str. 8a, 50321 Bruehl, Germany
Tel.: +49-2232-209024
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: splitting wsdl file in wsdl+xsd
Posted by Asaf Lahav <as...@primagrid.com>.
Hi Pablo,
Apparently the Wsdl2Java coming with the MUSE 1.0v doesn't allow importing
external XSD's nor WSDL's which are not part of the standard specs set.
AFAIK, the way to accomplish what you are trying to do is by embedding the
schema into the WSDL
-----Original Message-----
From: Pablo Javier Roca Mendez
[mailto:pablo_javier_roca_mendez@linux.intel.com]
Sent: Wednesday, August 16, 2006 3:37 PM
To: muse-user@ws.apache.org
Subject: Re: splitting wsdl file in wsdl+xsd
Hi Asaf!
> Send the WSDL and XSD files...
I attached both files that produce the error.
If I copy the contents of the xsd file (omitting the very first line) and
paste it between the <types> and </types> marks in the wsdl file then it
works, so I guess the
<xsd:import namespace="http://gpe.intel.com/mgmt/vm"
schemaLocation="Vm.xsd" />
isn't working for wsdl2Java.
Regards,
Pablo
On Wed, Aug 16, 2006 at 01:39:55PM +0200, Asaf Lahav wrote:
> Hi Pablo,
> Send the WSDL and XSD files...
>
>
>
> -----Original Message-----
> From: Pablo Javier Roca Mendez
> [mailto:pablo_javier_roca_mendez@linux.intel.com]
> Sent: Wednesday, August 16, 2006 10:15 AM
> To: muse-user
> Subject: splitting wsdl file in wsdl+xsd
>
> Hello everyone!
>
> I am using Muse 1.0.0 Final and trying to write my own services.
> I wanted to split the wsdl file in one xsd file for the schema definitions
> (properties and request/responses) that I then include in the wsdl file
> (messages and porttype) with xsd:import.
> If I split, then "ant generate" fails (after wsdl2Java imports the wsdl
> files,
> but not the xsd) with following message:
> BUILD FAILED
> $WORK_DIR/build.xml:54: org.apache.ws.resource.InvalidWsrfWsdlException:
> Unable to locate the ResourceProperties document element with QName
> {http://my.company.com/MyService}ResourceProperties
>
> If I put the xsd into the wsdl again, then "ant generate" succeeds.
>
> My question is: Is it possible to split the wsdl into two files (xsd+wsdl)
> or
> is it unsupported by wsdl2Java?
> In case it is possible, is there any documentation where I can learn how
to
> do
> it?
>
> Thanks in advance. Best regards,
> Pablo
>
--
Pablo Javier Roca Mendez
Intel GmbH/Bruehl, Hermuelheimer Str. 8a, 50321 Bruehl, Germany
Tel.: +49-2232-209024
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
Re: splitting wsdl file in wsdl+xsd
Posted by Pablo Javier Roca Mendez <pa...@linux.intel.com>.
Hi Asaf!
> Send the WSDL and XSD files...
I attached both files that produce the error.
If I copy the contents of the xsd file (omitting the very first line) and
paste it between the <types> and </types> marks in the wsdl file then it
works, so I guess the
<xsd:import namespace="http://gpe.intel.com/mgmt/vm"
schemaLocation="Vm.xsd" />
isn't working for wsdl2Java.
Regards,
Pablo
On Wed, Aug 16, 2006 at 01:39:55PM +0200, Asaf Lahav wrote:
> Hi Pablo,
> Send the WSDL and XSD files...
>
>
>
> -----Original Message-----
> From: Pablo Javier Roca Mendez
> [mailto:pablo_javier_roca_mendez@linux.intel.com]
> Sent: Wednesday, August 16, 2006 10:15 AM
> To: muse-user
> Subject: splitting wsdl file in wsdl+xsd
>
> Hello everyone!
>
> I am using Muse 1.0.0 Final and trying to write my own services.
> I wanted to split the wsdl file in one xsd file for the schema definitions
> (properties and request/responses) that I then include in the wsdl file
> (messages and porttype) with xsd:import.
> If I split, then "ant generate" fails (after wsdl2Java imports the wsdl
> files,
> but not the xsd) with following message:
> BUILD FAILED
> $WORK_DIR/build.xml:54: org.apache.ws.resource.InvalidWsrfWsdlException:
> Unable to locate the ResourceProperties document element with QName
> {http://my.company.com/MyService}ResourceProperties
>
> If I put the xsd into the wsdl again, then "ant generate" succeeds.
>
> My question is: Is it possible to split the wsdl into two files (xsd+wsdl)
> or
> is it unsupported by wsdl2Java?
> In case it is possible, is there any documentation where I can learn how to
> do
> it?
>
> Thanks in advance. Best regards,
> Pablo
>
--
Pablo Javier Roca Mendez
Intel GmbH/Bruehl, Hermuelheimer Str. 8a, 50321 Bruehl, Germany
Tel.: +49-2232-209024
RE: splitting wsdl file in wsdl+xsd
Posted by Asaf Lahav <as...@primagrid.com>.
Hi Pablo,
Send the WSDL and XSD files...
-----Original Message-----
From: Pablo Javier Roca Mendez
[mailto:pablo_javier_roca_mendez@linux.intel.com]
Sent: Wednesday, August 16, 2006 10:15 AM
To: muse-user
Subject: splitting wsdl file in wsdl+xsd
Hello everyone!
I am using Muse 1.0.0 Final and trying to write my own services.
I wanted to split the wsdl file in one xsd file for the schema definitions
(properties and request/responses) that I then include in the wsdl file
(messages and porttype) with xsd:import.
If I split, then "ant generate" fails (after wsdl2Java imports the wsdl
files,
but not the xsd) with following message:
BUILD FAILED
$WORK_DIR/build.xml:54: org.apache.ws.resource.InvalidWsrfWsdlException:
Unable to locate the ResourceProperties document element with QName
{http://my.company.com/MyService}ResourceProperties
If I put the xsd into the wsdl again, then "ant generate" succeeds.
My question is: Is it possible to split the wsdl into two files (xsd+wsdl)
or
is it unsupported by wsdl2Java?
In case it is possible, is there any documentation where I can learn how to
do
it?
Thanks in advance. Best regards,
Pablo
--
Pablo Javier Roca Mendez
Intel GmbH/Bruehl, Hermuelheimer Str. 8a, 50321 Bruehl, Germany
Tel.: +49-2232-209024
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org