I have used retroweaver... and it does not work. (when you use a new
method by mistake).
People that are on IBM or BEA old version can keep using old version of
Struts/WW2.
When they upgrade to JEE5 then they can have more options.
.V
Jason Carreira wrote:
+1 from me
Currently both tools (Retroweaver and Retrotranslator) have verifier that is
able
to trap most of such errors.
Taras
When you say: when you use a new method by mistake,
are you refering
to using API available only on 1.5? If so, this is a
known problem,
and indeed it is difficult to trap
+0
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=27314messageID=54494#54494
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Ditto... +1 along with Bob, Don, and James
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=27314messageID=53785#53785
-
To
+1
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=27314messageID=53821#53821
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
On 4/24/06, Don Brown [EMAIL PROTECTED] wrote:
[x] +0 I am fine with this move, but I'll still mainly interested in 1.4
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all!
I wrote Retrotranslator - a tool like Retroweaver,
but it supports generics and annotations at runtime,
so it is even possible to run JAXB 2 on JRE 1.4:
http://retrotranslator.sourceforge.net/
http://www.javalobby.org/java/forums/t66348.html
Taras
+1
Leon
On 4/24/06, Don Brown [EMAIL PROTECTED] wrote:
There has been a lot of discussion on Java 5 support for Struts Action 2, and
from my reading of the comments, we have
settled on a path, but I want to formalize it in a vote to ensure we are all
on the same page.
I vote we develop
+1 - as this is the next version of struts I think it makes sense to
make this move now. There is always webwork 2.2.2 for users that
require a JDK 1.4, which will allow for the majority of the framework
features and an easy stepping stone over to struts2.
/Ian
Don Brown wrote:
There has
Hi,
+0 .
I like the java 5 features, but I can't use it right now, since the companies I
work for, don't have application servers with java 5.
So I am very interested to have jdk 1.4 support. I particularly don't care if
all the features will not be available for jdk1.4 users :-)
thanks
--
[ ] +1 Make Java 5 the target
'
+1
- Erik
Hey there,
I would like to see Struts Action 2 support Java 5 as the default
platform, so +1 from me.
If Retroweaver and/or Retrotranslater provide full support for Java
5 language extensions
we should definately use it/them to have a Java 1.4 compliant version
as well.
Haven't looked at
There has been a lot of discussion on Java 5 support for Struts Action 2, and from my reading of the comments, we have
settled on a path, but I want to formalize it in a vote to ensure we are all on the same page.
I vote we develop Struts Action 2 with Java 5, taking advantage of it where ever
So... is that a +1? :)
As for annotations, I'd imagine we'd keep the XML as override so most anything you can do with annotations, you could
also do in XML. This would give Java 1.4 users mostly the same capabilities.
Don
Alexandru Popescu wrote:
This looks quite nice. I cannot figure out
On 4/24/06, Don Brown [EMAIL PROTECTED] wrote:
So... is that a +1? :)
As for annotations, I'd imagine we'd keep the XML as override so most
anything you can do with annotations, you could
also do in XML. This would give Java 1.4 users mostly the same
capabilities.
I think he was
Craig, you are almost right :-). You can store annotations in the
bytecode (check the class, field, method attributes), and we've done
this in AspectWerkz and AspectJ for quite a while ;-). The problem is
consuming them.
./alex
--
.w( the_mindstorm )p.
On 4/25/06, Craig McClanahan [EMAIL
Craig McClanahan wrote:
I think a better strategy would be to have the core framework depend solely
on 1.4, but provide an optional layer on top which leverages 1.5 things for
those who actually do have a 1.5 runtime environment. That's the approach
taken by the Tiger Extensions to Shale[1].
+1 to that.
Bob
On 4/24/06, Don Brown [EMAIL PROTECTED] wrote:
Craig McClanahan wrote:
I think a better strategy would be to have the core framework depend solely
on 1.4, but provide an optional layer on top which leverages 1.5 things for
those who actually do have a 1.5 runtime
+1 -- Git 'r dun!!
--
James Mitchell
On Apr 24, 2006, at 4:24 PM, Don Brown wrote:
There has been a lot of discussion on Java 5 support for Struts
Action 2, and from my reading of the comments, we have settled on a
path, but I want to formalize it in a vote to ensure we are all on
PROTECTED]
To: Struts Developers List dev@struts.apache.org
Sent: Monday, April 24, 2006 6:49:14 PM
Subject: Re: [action2] [VOTE] Target Java 5, support 1.4 through Retroweaver
So... is that a +1? :)
As for annotations, I'd imagine we'd keep the XML as override so most anything
you can do
20 matches
Mail list logo
