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

Andreas Veithen commented on SYNAPSE-399:
-----------------------------------------

If I remember well, there was a discussion about this and the conclusion was 
that it would be difficult to release a version based on Axis2 1.4.1, because 
there is already some code in Synapse that relies on features/fixes/changes in 
Axis2 1.5. However, at that time the expected release date for 1.5 was in 
December...

> JMSUtil.java class does not set all JMS Connection properties specified in 
> axis2.xml
> ------------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-399
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-399
>             Project: Synapse
>          Issue Type: Bug
>         Environment: Windows XP, JDK1.5.0_15
>            Reporter: Tanmay saha
>            Assignee: Asankha C. Perera
>             Fix For: 1.3
>
>
> JMSUtil.java in the JMS transport module does set all JMS Connection 
> properties specified in axis2.xml. setConnectionFactoryParameters() method of 
> JMSUtil.java class sets only the standard JMS Connection properties like 
> Initial Context Factory, Provider URL, User Principal and Credentials. It 
> ignores or does not set any JMS vendor specific connection properties .
> Proposed Fix: 
> Add the following "else" condition at the end of 
> setConnectionFactoryParameters() in JMSUtil.java class
> else
>  {
>       jmsConFactory.addJNDIContextProperty( (String)p.getName(), (String) 
> p.getValue());
>  }
> This will add any other connection properties to JNDIConnectionFactory. I 
> have made this change in my source and tested . It is setting 
> <parameter name="com.sonicsw.jndi.mfcontext.domain">dev3Domain</parameter> 
> specified in axis2.xml and
> working fine with my Sonic MQ dev3Domain
> -Thanks
> tanmay

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