[
https://issues.apache.org/jira/browse/OPENWIRE-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon updated OPENWIRE-74:
-------------------------------------------
Description:
Right now the prototcol sends the fully qualified Exception class name for
errors between the broker and client. This has led to multiple problems
including security bugs such as https://issues.apache.org/jira/browse/AMQ-9370
(fixed in this project in https://issues.apache.org/jira/browse/OPENWIRE-67)
and problems marshalling/unmarshalling if the package changes such as the
jakarta update: https://issues.apache.org/jira/browse/AMQ-9418
The updated ActiveMQ java client works around handling the translation issues
between javax and jakarta but that only applies to java.
Going forward we should decouple java exception types entirely and just return
an error code and reason and let clients/brokers translate how they want into
whatever exception/error types.
was:
Right now the prototcol sends the fully qualified Exception class name for
errors between the broker and client. This has led to multiple problems
including security bugs such as https://issues.apache.org/jira/browse/AMQ-9370
and problems marshalling/unmarshalling if the package changes such as the
jakarta update: https://issues.apache.org/jira/browse/AMQ-9418
The updated ActiveMQ java client works around handling the translation issues
between javax and jakarta but that only applies to java.
Going forward we should decouple java exception types entirely and just return
an error code and reason and let clients/brokers translate how they want into
whatever exception/error types.
> Add marshal support for error code on JMSExceptions
> ---------------------------------------------------
>
> Key: OPENWIRE-74
> URL: https://issues.apache.org/jira/browse/OPENWIRE-74
> Project: ActiveMQ OpenWire
> Issue Type: New Feature
> Reporter: Matt Pavlovich
> Priority: Major
> Labels: #v13
> Fix For: 1.0.0
>
>
> Right now the prototcol sends the fully qualified Exception class name for
> errors between the broker and client. This has led to multiple problems
> including security bugs such as
> https://issues.apache.org/jira/browse/AMQ-9370 (fixed in this project in
> https://issues.apache.org/jira/browse/OPENWIRE-67) and problems
> marshalling/unmarshalling if the package changes such as the jakarta update:
> https://issues.apache.org/jira/browse/AMQ-9418
> The updated ActiveMQ java client works around handling the translation issues
> between javax and jakarta but that only applies to java.
> Going forward we should decouple java exception types entirely and just
> return an error code and reason and let clients/brokers translate how they
> want into whatever exception/error types.
--
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
