[
https://issues.apache.org/jira/browse/TAVERNA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688123#comment-16688123
]
Donal Fellows commented on TAVERNA-118:
---------------------------------------
That's not wrong, but doesn't help.
The problem is that the annotations that guide the deserialization on the
server side are based on those for XML with multiple namespaces, and the
Jettison library does _not_ handle that at all well. For serialization, this
isn't a problem: all the namespaces are mapped to have an empty prefix string.
But for deserialization, something else is needed. Apparently that something
else is the badgerfish stuff I linked, but do not claim to understand that.
My workaround for this was always to work with XML. Future versions of the code
could instead switch to using a single namespace for everything, which would
make the JSON mapping simpler, but would (probably?) require some
reorganisation of the code.
> 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)
