[
https://issues.apache.org/jira/browse/TUSCANY-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997505#comment-12997505
]
TC Fenstermaker commented on TUSCANY-3654:
------------------------------------------
I am getting this exact problem--a schema validation failure on the use of the
wireFormat tag inside the binding.jms element. Yet this bug has been closed
without comment. Is there a work-around, a config change, a patch, or...what?
> wireformat within the jms binding response element don't work
> -------------------------------------------------------------
>
> Key: TUSCANY-3654
> URL: https://issues.apache.org/jira/browse/TUSCANY-3654
> Project: Tuscany
> Issue Type: Bug
> Components: OASIS Compliance - OASIS
> Reporter: ant elder
>
> wireformat within the jms binding response element don't work with the latest
> oasis schema. Fail is:
> SEVERE: XMLSchema validation error occured in:
> jmstextxmlinjmsobjectout/helloworld.composite ,line = 46, column = 21,
> Message = cvc-complex-type.2.4.a: Invalid content was found starting with
> element 'tuscany:wireFormat.jmsObject'. One of
> '{"http://docs.oasis-open.org/ns/opencsa/sca/200912":wireFormat,
> "http://docs.oasis-open.org/ns/opencsa/sca/200912":destination,
> "http://docs.oasis-open.org/ns/opencsa/sca/200912":connectionFactory,
> "http://docs.oasis-open.org/ns/opencsa/sca/200912":activationSpec}' is
> expected.
> so it knows a wireformat is valid, it just doesn't like the concrete
> instances of the type. This breaks the itest
> FormatJMSTextXMLInJMSObjectOutTestCase
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
