[
https://issues.apache.org/jira/browse/AMQ-9478?focusedWorklogId=947106&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-947106
]
ASF GitHub Bot logged work on AMQ-9478:
---------------------------------------
Author: ASF GitHub Bot
Created on: 06/Dec/24 20:33
Start Date: 06/Dec/24 20:33
Worklog Time Spent: 10m
Work Description: pa-deasy commented on PR #1360:
URL: https://github.com/apache/activemq/pull/1360#issuecomment-2524125127
> Yeah, I wasn't sure if it would be possible to easily verify for that
reason. You could try and use reflection to get access to the private/protected
socket and make it accessible. I can also take a look next week as well...if
it's not really possible that's ok but it would certainly be nice if we could
do it.
I managed to gain access to the `Socket` by iterating through the transports
and a little reflection magic as you suggested.
It's a little verbose but it provides the ability to verify changes to the
`Socket`.
Issue Time Tracking
-------------------
Worklog Id: (was: 947106)
Time Spent: 1h 10m (was: 1h)
> Add unit test for modernized IntrospectionSupport
> -------------------------------------------------
>
> Key: AMQ-9478
> URL: https://issues.apache.org/jira/browse/AMQ-9478
> Project: ActiveMQ Classic
> Issue Type: Task
> Reporter: Matt Pavlovich
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 6.2.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Update unit test to verify transport connector and network connector uri
> handling for
> IntrospectionSupport to deal with TcpSocket properties
> IntrospectionSupport to deal with SSLSocket properties
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
