No such plans exist, as for now.
Messaging has the concept of "facade" that wraps around a JMS-agnostic messaging core. This is s starting point, put I haven't actually thought about how C++ support could be implemented.
A JNI wrapper (a C++ client calling a Java client) would be possible.
But just that by itself would be a whole new project.
The JNI wrapper would seem to be the easiest route. Do you think people would get some use out of this? Do you get enough request's for a c++ client to make such an endeavor worthwhile? I might consider doing it (at least the jni wrapper) if so.
Also, there may be such requests for JBossMQ, but Adrian or genman are more qualified to answer this one, since I don't monitor that user list.
Although one of the purposes for having the AOP stack in the new jms
is so you can move most of the processing to the server and have
a very thin client.
e.g. a webservices or iiop client
This would be at the expense of more network chattiness but wouldn't require the client to run a JVM as would the JNI solution.
I suspect it would be simpler to implement than the JNI solution too.