Hi,
Yes - the reason for raising the 1.4 issue (and suggesting we should
support it) was a client request here.
I guess using the retrotranslator would be ok, assuming that it made the
upgrade path simple enough i.e. there aren't any interface changes as a
result ....
Regards,
Marnie
"Robert Greig" <[EMAIL PROTECTED]>
14/09/2006 17:11
Please respond to qpid-dev
To: [email protected]
cc:
Subject: Re: QPID Client JDK Support
> If this tool really works then it would be preferable not to backport
> everything to 1.4. If it almost-but-not-quite works it could be a big
> headache. How much experience do folks have with this?
On the MINA list this was discussed and IIRC at least one person on
that list had positive experiences with retrotranslator (although it
could have been retroweaver...) It is generally run at build time so
there should not be any run-time performance hit - although even if
there was presumably anyone using 1.4 isn't overly concerned with
performance?
Since 1.6 is going to be GA'd very soon, by supporting 1.5 and 1.6 we
would be supporting the two most recent GA'd JDK versions.
Originally we wanted to support 1.4 and 1.5 on the client since we
were following the "most recent two JDK versions" rule at that time
(which was something like 18 months ago).
The main advantage I see of making the client codebase depend on 1.5
would be that some more code could be pushed into common. Anyone
looking at the code will spot that there is quite a lot of similarity
and to a certain extent duplication between some classes in the client
and the broker, with the broker using generics.
Marnie, can you elaborate on the 1.4 requirement? Do we have any
(JPMC) people asking for 1.4?
RG
This communication is for informational purposes only. It is not intended as an
offer or solicitation for the purchase or sale of any financial instrument or
as an official confirmation of any transaction. All market prices, data and
other information are not warranted as to completeness or accuracy and are
subject to change without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and
affiliates.
This transmission may contain information that is privileged, confidential,
legally privileged, and/or exempt from disclosure under applicable law. If you
are not the intended recipient, you are hereby notified that any disclosure,
copying, distribution, or use of the information contained herein (including
any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and
any attachments are believed to be free of any virus or other defect that might
affect any computer system into which it is received and opened, it is the
responsibility of the recipient to ensure that it is virus free and no
responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and
affiliates, as applicable, for any loss or damage arising in any way from its
use. If you received this transmission in error, please immediately contact the
sender and destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
