why do you want to do that? It may be a completely legitimate thing to do but I don't really understand it.
Normally the expressiondialects are only used when making a query such as a filter for subscriptions, not exposed as resource properties. The error message tells you that no capability configured for that resource provides that property, if you really do want it as a property then you must declare (and possibly implement) a capability that provides it. Hi Chris, This program is developed according to the Muse wsrf example. Wsrf example declare a wsrf-rpQueryExpressionDialect without configure a capability for it. The reason I want wsrf-rpQueryExpressionDialect is I might need to query the managed resource using query expression. Your further help is very much appreciated. Thanks. Sara -- View this message in context: http://www.nabble.com/about-wsrf-rpQueryExpressionDialect-capability-tp23168896p23186067.html Sent from the Muse - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
