Since the custom capability didn't add any properties/operations to the
resource's interface (WSDL), we didn't need to add the namespace to the
WSDL. It is possible to have capabilities that perform function or add
semantics but do not alter the resource interface - examples would be WSDM
Configuration and WSDM Advertisement (and our test consumer
capability :) ). In these cases, the capability URI in muse.xml can be
whatever you want, since it doesn't have to match up with definitions in
the WSDL/XSD.
Dan
dchou <[EMAIL PROTECTED]> wrote on 05/09/2007 01:56:28 PM:
>
> I've been working with the sample code for the Muse 2.2.0 consumer. I
know
> that each capability must have its own Capability URI and the convention
in
> Muse is the that Capability URI == Namespace URI. Where is the Namespace
URI
> defined in the sample wsn-consumer? The muse.xml file defines the
> <capability-uri>
> http://ws.apache.org/muse/test/wsn/consumer</capability-uri> However, I
can
> not find where this namespace is defined. I found the Namespace
definition
> in the Producer sample but no definition for the consumer. Sorry if this
is
> a stupid question, but I am a total noob to Muse.
>
> Thanks,
> Dave
> --
> View this message in context: http://www.nabble.com/How-is-the-%
> 3Ccapability-uri%3E-determined-in-the-consumer--tf3717353.html#a10399578
> Sent from the Muse User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
