You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Joel Hawkins (JIRA)" <ji...@apache.org> on 2006/08/16 16:00:14 UTC

[jira] Created: (MUSE-58) Problems with QueryRelationshipsByType

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
         Attachments: muse-wsdm-relationships-fix-query-uri.patch, muse-wsdm-relationships-serialization.patch, 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org


[jira] Commented: (MUSE-58) Problems with QueryRelationshipsByType

Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/MUSE-58?page=comments#action_12429058 ] 
            
Dan Jemiolo commented on MUSE-58:
---------------------------------

ok - I will try to make the change in the MUWS 2 XSD so that the WSRP attribute can reference an element w/ sequence.


> 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, 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org


[jira] Commented: (MUSE-58) Problems with QueryRelationshipsByType

Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/MUSE-58?page=comments#action_12429053 ] 
            
Dan Jemiolo commented on MUSE-58:
---------------------------------

Joel - I have applied these patches, except for the WSDL - it's the simple WSRF WS-resource WSDL, and I'm not sure what to do with it. I think you just attached the wrong file by mistake.

http://svn.apache.org/viewvc?rev=432629&view=rev

> 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, 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org


[jira] Commented: (MUSE-58) Problems with QueryRelationshipsByType

Posted by "Joel Hawkins (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/MUSE-58?page=comments#action_12429056 ] 
            
Joel Hawkins commented on MUSE-58:
----------------------------------

Ack, I think you're right! 

Here's the problem:

in the current version, the ResourceProperties comes directly from the muws2 XSD, 

	<portType name="RelationshipPortType"
		wsrf-rp:ResourceProperties="muws2:RelationshipType">

which points to 

	<xs:complexType name="RelationshipType">
		<xs:sequence>
			<xs:element ref="muws2:Name" minOccurs="0" />
			<xs:element ref="muws2:Type" />
			<xs:element ref="muws2:Participant" minOccurs="2"
				maxOccurs="unbounded" />
			<xs:element name="AccessEndpointReference"
				type="wsa:EndpointReferenceType" minOccurs="0" />
			<xs:any minOccurs="0" maxOccurs="unbounded"
				namespace="##other" processContents="lax" />
		</xs:sequence>
		<xs:anyAttribute namespace="##other" />
	</xs:complexType>

Sadly, muse wants an element, not a type.  I tried feeding it 

	<xs:element name="Relationship" type="muws2:RelationshipType" />

but it wants a sequence.

My work-around was to make the following change to the WS-Resource-1_2.wsdl:

	<types>
		<xs:schema elementFormDefault="qualified"
			targetNamespace="http://docs.oasis-open.org/wsdm/muws2-2.wsdl">

			<xs:import
				namespace="http://docs.oasis-open.org/wsdm/muws2-2.xsd"
				schemaLocation="WSDM-MUWS-Part2-1_1.xsd" />

			<xs:import
				namespace="http://docs.oasis-open.org/wsdm/muws1-2.xsd"
				schemaLocation="WSDM-MUWS-Part1-1_1.xsd" />
				
			<xs:element name="WsdmResourceProperties">
				<xs:complexType>
					<xs:sequence>
			<xs:element ref="muws2:Name" minOccurs="0" />
			<xs:element ref="muws2:Type" />
			<xs:element ref="muws2:Participant" minOccurs="2"
				maxOccurs="unbounded" />
						
					</xs:sequence>
				</xs:complexType>
			</xs:element>
				
				
		</xs:schema>


	<portType name="RelationshipPortType"
		wsrf-rp:ResourceProperties="tns:WsdmResourceProperties">


I think the right change is actually in the XSD - but all those angle brackets scare me. :-)



> 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, 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org


[jira] Commented: (MUSE-58) Problems with QueryRelationshipsByType

Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/MUSE-58?page=comments#action_12429274 ] 
            
Dan Jemiolo commented on MUSE-58:
---------------------------------

Okay, I think the last part (XSD/WSDL) was just the result of referencing a number of different versions of the files. Your XSD had Relationship as the type name, mine had RelationshipType. For the sake of simplicity, I changed the XSD/WSDL to use muws2:Relationship everywhere, as you had it. Let me know if the new files work.


> 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org


[jira] Commented: (MUSE-58) Problems with QueryRelationshipsByType

Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/MUSE-58?page=comments#action_12429066 ] 
            
Dan Jemiolo commented on MUSE-58:
---------------------------------

I modified the MUWS part 2 XSD such that you should be able to use RelationshipType as the WSRP doc element for Relationship resources. You should also be able to reference it in the WSRP doc of any resource that participates in relationships. Please confirm this fix before it's closed.

http://svn.apache.org/viewvc?view=rev&revision=432656

> 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, 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org


[jira] Closed: (MUSE-58) Problems with QueryRelationshipsByType

Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/MUSE-58?page=all ]

Dan Jemiolo closed MUSE-58.
---------------------------

    Resolution: Fixed

> 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org


[jira] Commented: (MUSE-58) Problems with QueryRelationshipsByType

Posted by "Joel Hawkins (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/MUSE-58?page=comments#action_12430041 ] 
            
Joel Hawkins commented on MUSE-58:
----------------------------------

Works fine. You can mark it closed. Thanks.

> 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org


[jira] Updated: (MUSE-58) Problems with QueryRelationshipsByType

Posted by "Joel Hawkins (JIRA)" <ji...@apache.org>.
     [ 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org


[jira] Updated: (MUSE-58) Problems with QueryRelationshipsByType

Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/MUSE-58?page=all ]

Dan Jemiolo updated MUSE-58:
----------------------------

    Fix Version/s: 2.0.0
         Due Date: 31/Aug/06

Accepted for 2.0.0 final release

> 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, 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org