[
https://jira.jboss.org/jira/browse/JBMESSAGING-1628?page=com.atlassian.ji...
]
alexguev commented on JBMESSAGING-1628:
---------------------------------------
Actually using jboss-retro seems to work nicely :) I did find an issue that was a bit
hard to overcome. Basically the messaging client code uses java.util.UUID to generate the
message correlation id. My fix involved changing the actual messaging client code to use
other library (jug in this case) to generate the correlation id. I had to jump yet another
obstacle, which made me really unhappy about how much I can trust the jboss messaging
project. The problem has been experienced by other developers:
see
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230225
For the time being, I've overcome this issue by doing the fix recommended at the end
of the post, but I don't feel comfortable about solving this problem like this. I
think this should be something the messaging impl. code should take care of.
I was wondering ..are there any plans to support java 1.4 clients ?
lack of support for java 1.4 clients
------------------------------------
Key: JBMESSAGING-1628
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1628
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Remoting
Affects Versions: 1.4.3.GA
Environment: windows xp, j2sdk1.4.2_13 and jdk1.6.0_05
Reporter: alexguev
Assignee: Tim Fox
The messaging clients libraries are java 5 bytecode, which prevents the use of jboss
messaging from java 1.4 code. I made an attempt to retro-translate the messaging client
libraries using the retrotranslator project with limited success. Basically, things went
pretty well up to the point where the java vm complained with this error:
java.lang.ClassFormatError: org/jboss/jms/client/delegate/ClientConnectionFactoryDelegate
(Invalid start_pc/length in local var table)
I was wondering if there are any plans for jboss-messaging to support java 1.4 clients ?
also, should I try using the jboss-retro project instead ?
thanks in advance.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira