[
https://jira.jboss.org/browse/JBMESSAGING-1628?page=com.atlassian.jira.pl...
]
mittul mishra commented on JBMESSAGING-1628:
--------------------------------------------
Hi Alex ,
The post above is very useful. I have exactly the same problem when connecting from java
1.4 client to java1.5 queue .
Used retro-translator and am stuck with the error you mentioned above :
java.lang.ClassFormatError: org/jboss/jms/client/delegate/ClientConnectionFactoryDelegate
(Invalid start_pc/length in local var table)
So now trying jboss-retro to make jbossall-client.jar 1.4 compatible.Problem is I havent
been successfully able to use jboss-retro. Any help would be greatly appreciated.
Thanks in advance.
lack of support for java 1.4 clients
------------------------------------
Key: JBMESSAGING-1628
URL:
https://jira.jboss.org/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/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira