Eclipse tooling is described here:
http://marc.theaimsgroup.com/?l=muse-user&m=116845081504368&w=2
It calls wsdl2java under the covers.
I'm curious - are you using WSDL 2.0? WSDL 1.1 doesn't support any notion
of inheritance (which is why we don't support it ;) ). If you're
referring to XSD type inheritance, that should be part of 2.1 - please
submit a bug if a case isn't working right. Be sure to specify if
wsdl2java is getting it wrong, or the runtime, or both.
thanks,
Dan
"Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 01/26/2007
02:53:49 PM:
> Hi Baseer,
> Where can I find this Eclipse muse tooling thing? I am more concerned
> with maintaining the muse.xml, especially when wsdls change over time.
> I originally planned to use wsdl2java and compare the generated
> artifacts each time a set of wsdls change. But, I think wsdl2java is
> not quite reliable because it doesn't completely generate the muse.xml
> properly, especially when it comes to wsdls that support inheritence.
> Sometimes I have to do a test run, find the errors, and then manually
> add missing capabilities to muse.xml which wsdl2java didn't do.
> -Vinh
>
>
> -----Original Message-----
> From: Baseer Khan (bakhan)
> Sent: Friday, January 26, 2007 7:54 AM
> To: [email protected]
> Subject: RE: unused messege elements
>
> Eclipse muse tooling is your answer to this.
>
> --Baseer
>
> -----Original Message-----
> From: Vinh Nguyen (vinguye2)
> Sent: Friday, January 26, 2007 12:22 AM
> To: [email protected]
> Subject: RE: unused messege elements
>
> Thanks Baseer!
> You were right, it had nothing to do with the unused message elements.
> Thanks to your tip, I discovered that my muse.xml defined the following:
> <capability>
>
> <capability-uri>http://docs.oasis-open.org/wsrf/rpw-2/Query</capability-
> uri>
>
> <java-capability-class>org.apache.muse.ws.resource.properties.query.impl
> .SimpleQueryCapability</java-capability-class>
> </capability>
>
> This capability required the QueryExpressionDialect property. Turns out
> that the operation was removed from the wsdl recently, so I had to
> remove it from the muse.xml. So I have to be more careful now what I
> put in muse.xml, especially when the wsdl files are not maintained by
> me.
>
> It's a little cumbersome to manually run wsdl2java and compare the
> generated muse.xml everytime a wsdl changes, just to see if my muse.xml
> is accurate. Would be nice if Muse had a warning if capabilities are
> defined that have no corresponding operation is the wsdl. It already
> gives an error for the opposite case.
> -Vinh
>
>
> -----Original Message-----
> From: Baseer Khan (bakhan)
> Sent: Friday, January 26, 2007 12:01 AM
> To: [email protected]
> Subject: RE: unused messege elements
>
> Problem that you are seeing might not be related to unused message
> elements in wsdl.
>
> If you have added any capabilitiy classes implemented by muse as part of
> a WS-resource in muse.xml there are certain minimum set of properties
> required to be part of that WS-Resource's ResourceProperty document.
>
>
>
> If you add QueryExpressionDialect property as part of the resource
> property document of your WS-Resource this error might go away.
>
> --Baseer
>
>
>
> -----Original Message-----
> From: Vinh Nguyen (vinguye2)
> Sent: Thursday, January 25, 2007 11:39 PM
> To: [email protected]
> Subject: unused messege elements
>
> Hi all,
> I have a wsdl which defines the following message element:
> <wsdl:message name="UnknownQueryExpressionDialectFault">
> <wsdl:part name="UnknownQueryExpressionDialectFault"
> element="wsrf-rp:UnknownQueryExpressionDialectFault"/>
> </wsdl:message>
>
> I don't have an operations which use this message. But, Muse2.1.0 is
> giving me the following error:
>
> java.lang.RuntimeException: [ID = 'PropertyNotFound'] The schema has no
> property with the name
> '{http://docs.oasis-open.org/wsrf/rp-2}QueryExpressionDialect'. Use the
> hasProperty method to determine if a property exists.
> at
> org.apache.muse.ws.resource.properties.schema.impl.SimpleResourcePropert
> iesSchema.getProperty(SimpleResourcePropertiesSchema.java:233)
> at
> org.apache.muse.ws.resource.properties.schema.impl.SimpleResourcePropert
> iesSchema.setCapability(SimpleResourcePropertiesSchema.java:271)
> at
> org.apache.muse.ws.resource.properties.impl.SimpleResourcePropertyCollec
> tion.addCapability(SimpleResourcePropertyCollection.java:123)
> at
> org.apache.muse.ws.resource.impl.AbstractWsResourceCapability.initialize
> (AbstractWsResourceCapability.java:299)
> at
> org.apache.muse.ws.resource.properties.query.impl.SimpleQueryCapability.
> initialize(SimpleQueryCapability.java:107)
> at
> org.apache.muse.core.SimpleResource.initializeCapabilities(SimpleResourc
> e.java:296)
> ...
>
> I can make the error message go away in two ways:
> 1) Remove the unused message element, or
> 2) Add the wsrf-rp:QueryExpressionDialect property to the resource
> properties.
>
> Out of curiousity, why does Muse require that all message properties be
> explicitly defined, even if the message elements aren't used in any
> operation? It's as if Muse does wsdl validation forwards (i.e. message
> to operations) instead of backwards (ie. operations to messages).
> -Vinh
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
