[ 
https://issues.apache.org/jira/browse/AMQ-8322?focusedWorklogId=731738&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-731738
 ]

ASF GitHub Bot logged work on AMQ-8322:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Feb/22 17:29
            Start Date: 23/Feb/22 17:29
    Worklog Time Spent: 10m 
      Work Description: mattrpav commented on pull request #729:
URL: https://github.com/apache/activemq/pull/729#issuecomment-1049029799


   @gemmellr yep. in my update to the test, I explicitly set the trusted 
packages list to a new list and get rid of using the system property (which may 
have been causing the irregularity). The 
ActiveMQConnectionFactory.getTrustedPackges() list is wired into the connection 
each time, so updates there should carry over regardless of the static block in 
CLAOIS
   
   ```
   ActiveMQConnectionFactory#configureConnection(ActiveMQConnection)
            connection.setTrustedPackages(getTrustedPackages());
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 731738)
    Time Spent: 9.5h  (was: 9h 20m)

> Implement JMS 2.0 Connection createContext methods
> --------------------------------------------------
>
>                 Key: AMQ-8322
>                 URL: https://issues.apache.org/jira/browse/AMQ-8322
>             Project: ActiveMQ
>          Issue Type: New Feature
>            Reporter: Matt Pavlovich
>            Assignee: Matt Pavlovich
>            Priority: Major
>              Labels: #jms2
>             Fix For: 5.18.0
>
>          Time Spent: 9.5h
>  Remaining Estimate: 0h
>
> Add support for JMSContext, JMSProducer and JMSConsumer for working with 
> queues



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to