Some  logging calls use the wrong resource bundle
-------------------------------------------------

                 Key: UIMA-1055
                 URL: https://issues.apache.org/jira/browse/UIMA-1055
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
    Affects Versions: 2.2.2AS
            Reporter: Burn Lewis
            Priority: Minor
             Fix For: 2.2.2AS


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


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to