[
https://issues.apache.org/jira/browse/TAVERNA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688104#comment-16688104
]
Ian Dunlop commented on TAVERNA-118:
------------------------------------
This might be the same issue I noticed when trying to use the server via the
taverna-player-portal. It seems to be the same stack trace. I also found it
when using the t2-server-gem or via curl directly to a T3 server instance. I
don't quite understand what is meant by " the problem is with clients just
sending the wrong requests". What type of request should the client be sending?
Is it the content type that is wrong? The clients were sending
"application/vnd.taverna.t2flow+xml". Is this wrong?
> JSON PUTs do not work to REST API
> ---------------------------------
>
> Key: TAVERNA-118
> URL: https://issues.apache.org/jira/browse/TAVERNA-118
> Project: Apache Taverna
> Issue Type: Bug
> Components: Taverna Server
> Reporter: Stian Soiland-Reyes
> Priority: Critical
>
> The PUTting of JSON to the REST API gives a misinterpretation of the
> namespaces
> {code}
> JAXBException occurred : unexpected element
> (uri:"http://ns.taverna.org.uk/2010/xml/server/soap/";, local:"runInput").
> Expected elements are
> <{http://ns.taverna.org.uk/2010/xml/server/rest/}runInput>. unexpected
> element (uri:"http://ns.taverna.org.uk/2010/xml/server/soap/";,
> local:"runInput"). Expected elements are
> <{http://ns.taverna.org.uk/2010/xml/server/rest/}runInput>.
> {code}
> The JSON support should be corrected but in the meantime, the documentation
> should be updated to indicate it does not work
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
