[ 
https://issues.apache.org/jira/browse/SYNAPSE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645387#action_12645387
 ] 

Asankha C. Perera commented on SYNAPSE-424:
-------------------------------------------

Andreas

The suggestion is very good.. However, for the last paragraph of your comment, 
I think we should rely on MC properties.. I also wanted to update the Endpoint 
and Send mediator to be able to specify these at that level. e.g:

<send>
    <property name="transport-specific-property" value="yy"/>
    ....
    (endpointref | endpoint)+
</send>

and 

<endpoint [name="string"] [key="string"]>
  <property name="transport-specific-property" value="yy"/>
  ..
  address-endpoint | default-endpoint | wsdl-endpoint | load-balanced-endpoint 
| fail-over-endpoint
</endpoint> 

i think this will allow one to set endpoint specific transport properties in 
one place and reuse-it, and prevent the clutter of EPR's as well, and reduce 
the code needed to write a mediation, without using many instances of the 
property mediator..

asankha

> 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]

Reply via email to