You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by "Hohlen, John" <JH...@erac.com> on 2003/03/01 02:54:45 UTC
RE: Struts-el NOT working with Struts 1.1 RC1 Release
David Karr said he fixed this problem in last night's Struts-EL build. This
means in order to pick up the fix, you have to migrate from the RC1 version
of Struts to a nightly build version (due to other changes made to the
regular Struts tags since the RC1 release -- otherwise you'll have
incompatability issues -- I think). Many projects are reluctant to use
nightly builds (for obvious reasons). Therefore, this hurts the overall
likelihood of other projects incorporating Struts-EL. I would think that
the Struts-EL team would want to provide a version of their project that's
compatible with RC1. This will allow for wider user base which would be
good for the overall project. Doesn't this make sense or am I missing
something?
Thanks,
JOHN
P.S. I had these same problems with the beta 3 release. My development team
is getting frustrated to the point that they're almost ready to punt with
Struts-EL. No offense to the developers of Struts-EL. We really appreciate
all the hard work you've put into this "valuable" subproject. We're just
starting to get behind schedule and need some stability.
P.S.S. How come others aren't complaining about this? Are we the only one's
trying to Struts-EL with RC1??
-----Original Message-----
From: Hohlen, John
Sent: Thu 2/27/2003 7:50 AM
To: Struts-User (E-mail)
Cc: 'dmkarr@earthlink.net'
Subject: Struts-el NOT working with Struts 1.1 RC1 Release
Is anyone able to use the Struts-EL subproject with the Struts 1.1 RC1
release? I'm encountering the following error using the "struts-el.jar"
from the "contrib" folder in the RC1 release:
/jsp/login/loginTile.jsp(12): Error in using tag library
uri='/WEB-INF/struts-html-el.tld' prefix='html-el': The Tag class
'org.apache.strutsel.taglib.html.ELImgTag' has no setter method
corresponding to TLD declared attribute 'onkeypress', (JSP 1.1 spec, 5.4.1)
I'm currently using WebLogic 6.1 SP 2. I encountered problems similar to
this when the beta 3 release first came out. It wasn't until about a week
later that the Struts-EL project would work with the beta 3 release (for me
at least).
Thanks,
JOHN
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: Struts-el NOT working with Struts 1.1 RC1 Release
Posted by Rick Reumann <ma...@reumann.net>.
On Fri, Feb 28,'03 (07:59 PM GMT-0800), Craig wrote:
> I get somewhat depressed about the "for obvious reasons" reason that
> people give for not at least *trying* your app against the nightly
> builds. After all, the day that Struts 1.1 final is released, guess
> what -- it will have exactly the same classes as that night's nightly
> build :-). There is nothing magical about the label "final release"
> that makes it any better (or worse) other than marginally more
> testing.
Thanks for the reminder Craig. I'm going to start making sure to use the
latest nightly builds in all of my development. I think I'll also send
out a reminder on the list occasionally about this since it is important
these nightly builds get tested since the entire Struts community as a
whole suffers when there are bugs in final releases.
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
RE: Struts-el NOT working with Struts 1.1 RC1 Release
Posted by Ray Madigan <ra...@madigans.org>.
Craig,
I guess I made other assumptions about the process. I thought that
there were people on the list that volunteered to test just like you
volunteer to write code. I would have been more apt to run my project
on the nightly builds had I knew you were counting on us. I appreciate
you clearing that up for me. I am relatively new to struts - have
been here about three weeks.
Thanks and I do appreciate all you do and am willing to contribute
where I can.
Ray Madigan
-----Original Message-----
From: Craig R. McClanahan [mailto:craigmcc@apache.org]
Sent: Friday, February 28, 2003 7:59 PM
To: Struts Users Mailing List
Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release
On Fri, 28 Feb 2003, Hohlen, John wrote:
> Date: Fri, 28 Feb 2003 19:54:45 -0600
> From: "Hohlen, John" <JH...@erac.com>
> Reply-To: Struts Users Mailing List <st...@jakarta.apache.org>
> To: Struts Users Mailing List <st...@jakarta.apache.org>
> Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release
>
> David Karr said he fixed this problem in last night's Struts-EL build.
This
> means in order to pick up the fix, you have to migrate from the RC1
version
> of Struts to a nightly build version (due to other changes made to the
> regular Struts tags since the RC1 release -- otherwise you'll have
> incompatability issues -- I think). Many projects are reluctant to use
> nightly builds (for obvious reasons). Therefore, this hurts the overall
> likelihood of other projects incorporating Struts-EL. I would think that
> the Struts-EL team would want to provide a version of their project that's
> compatible with RC1. This will allow for wider user base which would be
> good for the overall project. Doesn't this make sense or am I missing
> something?
>
The other side of that coin is also important -- if nobody tests the
nightly builds, then we developers never find out about the bugs until
after a release build is published, which harms the reputation for quality
that we would all prefer.
I get somewhat depressed about the "for obvious reasons" reason that
people give for not at least *trying* your app against the nightly builds.
After all, the day that Struts 1.1 final is released, guess what -- it
will have exactly the same classes as that night's nightly build :-).
There is nothing magical about the label "final release" that makes it any
better (or worse) other than marginally more testing.
Going into production is a different story -- but the harsh reality is the
only reason RC1 was called RC1 instead of beta 4 was to get at least a
*few* more people to test it. Fortunately for the quality of the final
release, that goal was achieved. Unfortunately, many of the bugs could
have been found and fixed quite a while ago, with more testing.
> Thanks,
>
> JOHN
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
RE: Struts-el NOT working with Struts 1.1 RC1 Release
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Fri, 28 Feb 2003, Hohlen, John wrote:
> Date: Fri, 28 Feb 2003 19:54:45 -0600
> From: "Hohlen, John" <JH...@erac.com>
> Reply-To: Struts Users Mailing List <st...@jakarta.apache.org>
> To: Struts Users Mailing List <st...@jakarta.apache.org>
> Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release
>
> David Karr said he fixed this problem in last night's Struts-EL build. This
> means in order to pick up the fix, you have to migrate from the RC1 version
> of Struts to a nightly build version (due to other changes made to the
> regular Struts tags since the RC1 release -- otherwise you'll have
> incompatability issues -- I think). Many projects are reluctant to use
> nightly builds (for obvious reasons). Therefore, this hurts the overall
> likelihood of other projects incorporating Struts-EL. I would think that
> the Struts-EL team would want to provide a version of their project that's
> compatible with RC1. This will allow for wider user base which would be
> good for the overall project. Doesn't this make sense or am I missing
> something?
>
The other side of that coin is also important -- if nobody tests the
nightly builds, then we developers never find out about the bugs until
after a release build is published, which harms the reputation for quality
that we would all prefer.
I get somewhat depressed about the "for obvious reasons" reason that
people give for not at least *trying* your app against the nightly builds.
After all, the day that Struts 1.1 final is released, guess what -- it
will have exactly the same classes as that night's nightly build :-).
There is nothing magical about the label "final release" that makes it any
better (or worse) other than marginally more testing.
Going into production is a different story -- but the harsh reality is the
only reason RC1 was called RC1 instead of beta 4 was to get at least a
*few* more people to test it. Fortunately for the quality of the final
release, that goal was achieved. Unfortunately, many of the bugs could
have been found and fixed quite a while ago, with more testing.
> Thanks,
>
> JOHN
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org