[
https://issues.apache.org/jira/browse/AMQ-8322?focusedWorklogId=766777&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-766777
]
ASF GitHub Bot logged work on AMQ-8322:
---------------------------------------
Author: ASF GitHub Bot
Created on: 05/May/22 16:51
Start Date: 05/May/22 16:51
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #729:
URL: https://github.com/apache/activemq/pull/729#issuecomment-1118822433
I'll admit I gave up before the end as many of the comments seem to apply to
a lot of the tests and I got bored seeing/saying the same things, but I cant
say I saw an actual _unit_ test despite the various comments about them. Just
lots of system/integration tests running up full brokers and clients, often to
check things that dont even hit the wire at all. Given a lot of this stuff just
wraps existing impl it is easy to unit test those wrapping bits in isolation,
system testing all of it in that way seems largely just a waste, but even more
so when also repeating tests for every type of destination or message type or
ack mode etc....and doing so without _any_ unit tests that could achivee the
same more quickly and give better errors on failure etc.
Issue Time Tracking
-------------------
Worklog Id: (was: 766777)
Time Spent: 12h 50m (was: 12h 40m)
> 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: 12h 50m
> Remaining Estimate: 0h
>
> Add support for JMSContext, JMSProducer and JMSConsumer for working with
> queues
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
