Sorry, I've just realised that the resource properties document may do
what you want. I'm just not sure if you mean custom resource properties
to be those you want to access via GetResourcePropertyDocument.
Bruno.
Bruno Harbulot wrote:
Hi,
It's not really clear what you mean by "custom" resource properties.
Aren't they all "custom"?
I think that, according to the specs, properties may or may not exist
for a particular resource at a given point in time. This is probably why
they're not in the WSDL file (and why there is no extension for them).
One way to find out which properties are valid is to implement
QueryResourceProperties and to use it from the client (with "*").
I also think one of the aims of WSRF is not to depend on an
object-oriented approach. WSDL doesn't define 'methods' but 'operations'
(within port types or the soon-to-come "interfaces" in WSDL 2.0).
Listing the object fields might be too close to a Java class model
(including reflection), although I can see the use for knowing which
properties a resource has got (and in this case, QueryResourceProperties
seems to be fine).
Regards,
Bruno.
Asaf Lahav wrote:
What is the best way to generate custom resource properties?
Is there a way to define custom resource properties in the service
WSDL file like it's done with Methods?
---------------------------------------------------------------------
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]
