From: Dariusz Wojtas [mailto:[EMAIL PROTECTED]
> I tried it last week with Websphere 6.0 (jdk 1.4.2) using
> retrotranslator - with success.
Ditto on 8.1 with 1.4.2.
I don't recall that I had to do anything else in particular to get it to
work, the '-advanced' flag was the ticket.
Unfortunately
I tried it last week with Websphere 6.0 (jdk 1.4.2) using
retrotranslator - with success.
The app was a portlet.
There were problems with JARs found in the nightly builds (compiled
with retro 1.10), but it started to work when I processed the JARs
(xwork + struts) with retro 1.20 and option '-adva
On 1/22/07, Dave Newton <[EMAIL PROTECTED]> wrote:
As was pointed out you may need to run retro with the -advanced (?)
option so it will properly skirt the ThreadLocal.remove method.
Any other tips, Dave?
Has anyone tried Retotranslater as an alternative?
* http://retrotranslator.sourceforge.
On 1/22/07, bobmccune <[EMAIL PROTECTED]> wrote:
Will there will be a
full 1.4 distribution available when the 2.x release reaches GA status? By
this I mean one that is targeted at 1.4 and has the retroweaved jars rolled
into the root lib directory and the sample wars.
I'm not planning to do t
From: bobmccune [mailto:[EMAIL PROTECTED]
> [...] after replacing the default jars with the j4 versions and
> rebuilding the sample app source, I'm still getting unsupported
> major.minor problems with some of the plugins (spring and tiles
> in particular). Is there a solution to this?
IIRC I
--
View this message in context:
http://www.nabble.com/Struts-2-and-JDK-1.4-tf3059602.html#a8507542
Sent from the Struts - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
6 matches
Mail list logo
