-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IncomingJmsMessage assumes message type it won't be empty #2625
Comments
Possible solution: IncomingJmsMessage(Message message, Executor executor, JsonMapping jsonMapping) {
this.delegate = message;
this.jsonMapping = jsonMapping;
this.executor = executor;
String cn = null;
try {
cn = message.getStringProperty("_classname");
if (cn == null) {
cn = message.getJMSType();
}
} catch (JMSException e) {
// ignore it
}
try {
this.clazz = cn != null && !cn.isEmpty() ? load(cn) : null;
} catch (ClassNotFoundException e) {
throw ex.illegalStateUnableToLoadClass(e);
}
this.jmsMetadata = new IncomingJmsMessageMetadata(message);
this.metadata = Metadata.of(this.jmsMetadata);
} |
Looks good! Fancy a PR? |
Yes, can you made me contributor? thanks |
Hello,
You just need to fork the project in github and then open a pull request.
…On Mon 20 May 2024 at 18:06, neazevedo ***@***.***> wrote:
Yes, can you made me contributor? thanks
—
Reply to this email directly, view it on GitHub
<#2625 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADCG7MFHKC47R3BOBKDWEDZDINSBAVCNFSM6AAAAABH7X57Y2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQG42TKNBSGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
done! Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When used to connect with (legacy activemq server) activemq-client v6.1.1, sending a JMSMessage by default type is "" (empty).
After consuming a JMSMessage JMSType came empty and we try to load type "" from the classloader.
Can we add extra isNotEmpty() validation?
Thanks
The text was updated successfully, but these errors were encountered: