[UIMA-1055] Some logging calls use the wrong resource bundle

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.2.2AS
• Fix Version/s: 2.2.2AS
• Component/s: Async Scaleout
• Assignee: Marshall Schor
• Reporter: Burn L. Lewis
• Created: 30/May/08 15:27
• Updated: 05/Jun/08 04:29
• Resolved: 05/Jun/08 04:29

Description

Should use JmsConstants for UIMAJMS messages & UIMAEE_Constants for UIMAEE messages in these 4 cases:

uimaj-as-activemq/src/main/java/org/apache/uima/adapter/jms/activemq/JmsOutputChannel.java:
UIMAEE_Constants.JMS_LOG_RESOURCE_BUNDLE, "UIMAJMS_release_cas_req__FINE",

uimaj-as-jms/src/main/java/org/apache/uima/adapter/jms/client/BaseUIMAAsynchronousEngineCommon_impl.java:
UIMAEE_Constants.JMS_LOG_RESOURCE_BUNDLE, "UIMAJMS_meta_timeout_INFO",

uimaj-as-activemq/src/main/java/org/apache/uima/adapter/jms/activemq/JmsOutputChannel.java:
JmsConstants.JMS_LOG_RESOURCE_BUNDLE, "UIMAEE_exception__WARNING",

uimaj-as-activemq/src/main/java/org/apache/uima/adapter/jms/activemq/UimaDefaultMessageListenerContainer.java
JmsConstants.JMS_LOG_RESOURCE_BUNDLE, "UIMAEE_disabled_delegate_bad_broker__INFO",