[
https://issues.apache.org/jira/browse/SYNAPSE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645562#action_12645562
]
Andreas Veithen commented on SYNAPSE-424:
-----------------------------------------
@Asankha: If you use a MC property instead of an EPR parameter, this means that
the information from the WSDL alone is no longer sufficient to send a message
to the endpoint. Personally I think that this is a more important aspect than
the additional clutter. Note that we could easily support both approaches. In
that case, the EPR generated by JMSListener#getEPRsForService would have the
additional parameter, so that the WSDL produced by Axis2 is complete. On the
other hand, in a Synapse mediation, users could use the MC property if they
prefer.
@Irantha: I don't understand your point about the fixed number of attachments.
Also I don't see where HTTP headers would have to be mapped. Since the JMS
transport now relies on message builders, it should support any content type,
including SwA and MTOM. The particularity with SwA (not sure about MTOM) is
that the content type contains information about the MIME boundary and SOAP
part ID. For the JMS transport this means that messages of this type can only
be processed if the sender adds a JMS property with the content type.
> JMS transport uses JMS properties in a way that violates the JMS
> specifications
> -------------------------------------------------------------------------------
>
> Key: SYNAPSE-424
> URL: https://issues.apache.org/jira/browse/SYNAPSE-424
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.2
> Environment: N/A
> Reporter: Andreas Veithen
> Attachments: commons_jms.patch
>
>
> According to section 3.5.1 of the JMS specification (version 1.1), "Property
> names must obey the rules for a message selector identifier." According to
> section 3.8.1.1 on selectors, "An identifier is an unlimited-length character
> sequence that must begin with a Java identifier start character; all
> following characters must be Java identifier part characters." The JMS
> transport's use of a property named "Content-Type" is in violation of this
> specification.
> Note that some JMS providers (such as qpid) accept illegal identifiers while
> others (such as WebSphere's SIBus client) don't.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
