[ http://issues.apache.org/jira/browse/MUSE-58?page=all ]
Joel Hawkins updated MUSE-58:
-----------------------------
Attachment: RelationshipResourceChanges.zip
Well, you pull one thread....
I had to make a few more changes - the properties schema loader REALLY wanted
the element name="RelationshipType" to be name="Relationship".
Also, the machinary really wants all the elements inside the sequence to be
references, not declarations. OK fine.
Of course, this means the wsdl has to reference "muws2:Relationship" for
properties, not "muws2:RelationshipType". Easy enough.
Ack! - the AccessEnpointReference has to be added to the property list in
RelationshipResource, plus a getter (don't really want a setter!). OK fine. And
that means the SimpleRelationshipResource needs the new getter method added.
Finally, the QName for AccessEndpointReference (which was already in
MuwsConstants ?!?) had a muws1 namespace reference, not muws2.
After all that, my test started working again - so here's the attachments. Hope
I got them all. :-)
> Problems with QueryRelationshipsByType
> --------------------------------------
>
> Key: MUSE-58
> URL: http://issues.apache.org/jira/browse/MUSE-58
> Project: Muse
> Issue Type: Bug
> Components: WSDM MUWS Relationships
> Affects Versions: 2.0.0 M2
> Environment: All
> Reporter: Joel Hawkins
> Assigned To: Dan Jemiolo
> Fix For: 2.0.0
>
> Attachments: muse-wsdm-relationships-fix-query-uri.patch,
> muse-wsdm-relationships-serialization.patch, RelationshipResourceChanges.zip,
> WS-Resource-1_2.wsdl
>
>
> According to the spec, the QueryByRelationships capability URI should be
> http://docs.oasis-open.org/wsdm/muws/capabilities/Relationships.
> Additionally, the creation of relationships programatically was failing due
> to a NPE. This had to do with the fact that the dependent relationship
> resource was being initialized before the containing resource.
> Then, the serialization of the query response was failing due to a
> class-cast exception (an array of WSResources was being supplied to a method
> that expected an array of RelationshipResources).
> Finally, the RelationshipClient was throwing an exception because the
> response did not include the EPR of the relationship containing the
> participants, etc.
> Additionally, I had trouble getting the WSDL to be accepted, as the WSDLUtils
> refused to accept the the wsrf-rp:ResourceProperties directly from the
> specified XSD file (it was expecting an xsd:sequence) . I've attached the
> WSDL that works for me - see what you want to do with it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
