about wsrf-rpQueryExpressionDialect capability

[SARA1232007]

Hi,

I declare the QueryExpressionDialect property in wsdl as following:

        <xsd:schema elementFormDefault="qualified" targetNamespace="http://ws.apache.org/muse/test/simple">
            <xsd:element name="MyProperty" type="xsd:string"/>
            <xsd:element name="WsResourceProperties">
                <xsd:complexType>
                    <xsd:sequence>
                                                <!--
                        <xsd:element maxOccurs="unbounded" minOccurs="0" ref="wsrf-rp:QueryExpressionDialect"/>
                                                -->
                        <xsd:element maxOccurs="unbounded" minOccurs="0" ref="tns:MyProperty"/>
                    </xsd:sequence>
                </xsd:complexType>
            </xsd:element>
        </xsd:schema>

After I run client, I get the error msg of 'NoCapability
ForProperty' from server. The trace information from server as following:

16:58:58,562 ERROR [STDERR] java.lang.IllegalStateException: [ID = 'NoCapability
ForProperty'] There is no capability that defines the property {http://docs.oasi
s-open.org/wsrf/rp-2}QueryExpressionDialect. If you have a capability that is su
pposed to define this property, make sure the name is returned as part of WsReso
urceCapability.getPropertyNames().
16:58:58,562 ERROR [STDERR]     at org.apache.muse.ws.resource.properties.impl.S
impleResourcePropertyCollection.validateSchema(Unknown Source)
16:58:58,562 ERROR [STDERR]     at org.apache.muse.ws.resource.impl.SimpleWsReso
urce.initialize(SimpleWsResource.java:227)

Can anyone tell me what's wrong?

Thanks.

Sara

[Chris Twiner]

On Wed, Apr 22, 2009 at 5:08 AM, SARA1232007 <cyl_axis@...> wrote:
>
> Hi,
>
> I declare the QueryExpressionDialect property in wsdl as following:
>

hiya,

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.

cheers,
Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@...
For additional commands, e-mail: muse-dev-help@...

[SARA1232007]

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