[JBoss JIRA] (JBESB-3958) Please make DefaultJmsReplyToEpr more compatible with industry conventions for Messaging.
by Tom Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBESB-3958?page=com.atlassian.jira.plugin... ]
Tom Cunningham resolved JBESB-3958.
-----------------------------------
Resolution: Done
> Please make DefaultJmsReplyToEpr more compatible with industry conventions for Messaging.
> -----------------------------------------------------------------------------------------
>
> Key: JBESB-3958
> URL: https://issues.jboss.org/browse/JBESB-3958
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transports
> Affects Versions: 4.12
> Environment: All JBossESB.
> Reporter: Rick Wagner
> Assignee: Tom Cunningham
> Priority: Minor
> Fix For: 4.13
>
>
> org.jboss.internal.soa.esb.addressing.eprs.DefaultJmsReplyToEpr does not allow the user to choose a queue name that includes uppercase letters.
> The most widespread messaging system in the field is most often used with uppercase queue names. This forces administrators to break conventions for JBossESB.
> 1) The constructor needs to pass along JMS credentials to it's parent.
> 2) An option should be added so WSMQ users can comply with IBM queue naming standards (upper case names).
> These can be implemented with the following code snippets:
> >>> In the class declarations <<<
> private static final String ackMode = AcknowledgeMode.AUTO_ACKNOWLEDGE.toString();
> >>> Replace the 'short' constructor with this longer one <<<
> super(epr.getVersion(), epr.getDestinationType(), replyDestinationName(epr), epr.getConnectionFactory(), epr.getJndiEnvironment(), replySelector(epr), epr.getPersistent(), ackMode, epr.getJMSSecurityPrincipal(), epr.getJMSSecurityCredential());
> >>> Implement 'replyDestinationName' with conditional <<<
> private static String replyDestinationName(JMSEpr toEpr)
> throws URISyntaxException
> {
> if ("UPPERCASE" == System.getProperty("REPLY_TO_SUFFIX_CASE")){
> return new StringBuilder().append(toEpr.getDestinationName()).append("_REPLY").toString();
> }else{
> return new StringBuilder().append(toEpr.getDestinationName()).append("_reply").toString();
> }
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
- 1
- 0
[JBoss JIRA] (JBESB-3958) Please make DefaultJmsReplyToEpr more compatible with industry conventions for Messaging.
by Tom Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBESB-3958?page=com.atlassian.jira.plugin... ]
Tom Cunningham updated JBESB-3958:
----------------------------------
Fix Version/s: 4.13
(was: 4.11 CP3)
> Please make DefaultJmsReplyToEpr more compatible with industry conventions for Messaging.
> -----------------------------------------------------------------------------------------
>
> Key: JBESB-3958
> URL: https://issues.jboss.org/browse/JBESB-3958
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transports
> Affects Versions: 4.12
> Environment: All JBossESB.
> Reporter: Rick Wagner
> Assignee: Tom Cunningham
> Priority: Minor
> Fix For: 4.13
>
>
> org.jboss.internal.soa.esb.addressing.eprs.DefaultJmsReplyToEpr does not allow the user to choose a queue name that includes uppercase letters.
> The most widespread messaging system in the field is most often used with uppercase queue names. This forces administrators to break conventions for JBossESB.
> 1) The constructor needs to pass along JMS credentials to it's parent.
> 2) An option should be added so WSMQ users can comply with IBM queue naming standards (upper case names).
> These can be implemented with the following code snippets:
> >>> In the class declarations <<<
> private static final String ackMode = AcknowledgeMode.AUTO_ACKNOWLEDGE.toString();
> >>> Replace the 'short' constructor with this longer one <<<
> super(epr.getVersion(), epr.getDestinationType(), replyDestinationName(epr), epr.getConnectionFactory(), epr.getJndiEnvironment(), replySelector(epr), epr.getPersistent(), ackMode, epr.getJMSSecurityPrincipal(), epr.getJMSSecurityCredential());
> >>> Implement 'replyDestinationName' with conditional <<<
> private static String replyDestinationName(JMSEpr toEpr)
> throws URISyntaxException
> {
> if ("UPPERCASE" == System.getProperty("REPLY_TO_SUFFIX_CASE")){
> return new StringBuilder().append(toEpr.getDestinationName()).append("_REPLY").toString();
> }else{
> return new StringBuilder().append(toEpr.getDestinationName()).append("_reply").toString();
> }
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
- 1
- 0
[JBoss JIRA] (JBESB-3958) Please make DefaultJmsReplyToEpr more compatible with industry conventions for Messaging.
by Tom Cunningham (JIRA)
Tom Cunningham created JBESB-3958:
-------------------------------------
Summary: Please make DefaultJmsReplyToEpr more compatible with industry conventions for Messaging.
Key: JBESB-3958
URL: https://issues.jboss.org/browse/JBESB-3958
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.12
Environment: All JBossESB.
Reporter: Rick Wagner
Assignee: Tom Cunningham
Priority: Minor
Fix For: 4.11 CP3
org.jboss.internal.soa.esb.addressing.eprs.DefaultJmsReplyToEpr does not allow the user to choose a queue name that includes uppercase letters.
The most widespread messaging system in the field is most often used with uppercase queue names. This forces administrators to break conventions for JBossESB.
1) The constructor needs to pass along JMS credentials to it's parent.
2) An option should be added so WSMQ users can comply with IBM queue naming standards (upper case names).
These can be implemented with the following code snippets:
>>> In the class declarations <<<
private static final String ackMode = AcknowledgeMode.AUTO_ACKNOWLEDGE.toString();
>>> Replace the 'short' constructor with this longer one <<<
super(epr.getVersion(), epr.getDestinationType(), replyDestinationName(epr), epr.getConnectionFactory(), epr.getJndiEnvironment(), replySelector(epr), epr.getPersistent(), ackMode, epr.getJMSSecurityPrincipal(), epr.getJMSSecurityCredential());
>>> Implement 'replyDestinationName' with conditional <<<
private static String replyDestinationName(JMSEpr toEpr)
throws URISyntaxException
{
if ("UPPERCASE" == System.getProperty("REPLY_TO_SUFFIX_CASE")){
return new StringBuilder().append(toEpr.getDestinationName()).append("_REPLY").toString();
}else{
return new StringBuilder().append(toEpr.getDestinationName()).append("_reply").toString();
}
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
- 1
- 0