Re: Struts-el NOT working with Struts 1.1 RC1 Release
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts-el NOT working with Struts 1.1 RC1 Release
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:[EMAIL PROTECTED] 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" <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: Struts Users Mailing List <[EMAIL PROTECTED]> > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts-el NOT working with Struts 1.1 RC1 Release
AFAIK, the commons components strive for backwards compatibility so theoretically you should be able to use the versions that come with Struts. You make a great point about using beta OSS in production. I hope your mgmt. listens :-). David From: "Hohlen, John" <[EMAIL PROTECTED]> Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> To: Struts Users Mailing List <[EMAIL PROTECTED]> Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release Date: Fri, 28 Feb 2003 22:40:41 -0600 Craig, I hear what you're saying. At times, I feel like we're dealing with a two-edge sword. I wish our teams could do more work with nightly builds. One of the battles I constantly face with our management is their reluctancy to even allow us to work with "beta" releases (or lesser) in our development environment. Their fear is, not knowing when an official release will occur, that beta open-source software will end up in production. But my argument is, hey if we've successfully completed all levels of testing (unit, integration, q/a, etc.), have the corresponding source code, know what the open bugs/issues/limitations are, what's the worse that can happen? We discover a bug that we have to fix (and possibly relay back to the open-source development team). How is this any different that with the code we develop in-house? I guarantee you we have in-house software running in production that should be labeled "beta" (or less), but isn't because of a schedule that had to be met. It's too bad the label "beta" has to be used, it has such a negative connotation. I did read on the mailing lists a while back that Lands End was using a beta 1 version of Struts 1.1 in production. I think that says something in it's own right. I'm sure there are others doing the same. There is an "open-source" mindset that I'm trying to slowly change in our company. I've tried to convince our management that beta "open-source" is different than beta "commercial". Open-source projects don't have schedule deadlines that will affect the quarterly financial results. Hence, they move a slower and strive for 100% perfection. If we do a thorough job of testing, with a high-level of confidence, it might be possible to use "beta" software in production (in some instances). One issue we do have with Struts, however, is the many other Jakarta Commons libraries that it depends upon. Since we're using other libraries that also uses the Jakarta-Commons libraries, we do have compatability concerns. For the beta releases of Struts, many of the Jakarta-Comons libraries used were simply nighty build versions. Hence, it's a little trickier trying to use a "unofficially" released version of Struts vs. some project that has very little, or no dependency on other libraries. Additional thoughts on this are greatly appreciated, Thanks, JOHN -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 9:59 PM To: Struts Users Mailing List Cc: 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" <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: Struts Users Mailing List <[EMAIL PROTECTED]> > 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
RE: Struts-el NOT working with Struts 1.1 RC1 Release
Craig, I hear what you're saying. At times, I feel like we're dealing with a two-edge sword. I wish our teams could do more work with nightly builds. One of the battles I constantly face with our management is their reluctancy to even allow us to work with "beta" releases (or lesser) in our development environment. Their fear is, not knowing when an official release will occur, that beta open-source software will end up in production. But my argument is, hey if we've successfully completed all levels of testing (unit, integration, q/a, etc.), have the corresponding source code, know what the open bugs/issues/limitations are, what's the worse that can happen? We discover a bug that we have to fix (and possibly relay back to the open-source development team). How is this any different that with the code we develop in-house? I guarantee you we have in-house software running in production that should be labeled "beta" (or less), but isn't because of a schedule that had to be met. It's too bad the label "beta" has to be used, it has such a negative connotation. I did read on the mailing lists a while back that Lands End was using a beta 1 version of Struts 1.1 in production. I think that says something in it's own right. I'm sure there are others doing the same. There is an "open-source" mindset that I'm trying to slowly change in our company. I've tried to convince our management that beta "open-source" is different than beta "commercial". Open-source projects don't have schedule deadlines that will affect the quarterly financial results. Hence, they move a slower and strive for 100% perfection. If we do a thorough job of testing, with a high-level of confidence, it might be possible to use "beta" software in production (in some instances). One issue we do have with Struts, however, is the many other Jakarta Commons libraries that it depends upon. Since we're using other libraries that also uses the Jakarta-Commons libraries, we do have compatability concerns. For the beta releases of Struts, many of the Jakarta-Comons libraries used were simply nighty build versions. Hence, it's a little trickier trying to use a "unofficially" released version of Struts vs. some project that has very little, or no dependency on other libraries. Additional thoughts on this are greatly appreciated, Thanks, JOHN -Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 9:59 PM To: Struts Users Mailing List Cc: 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" <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: Struts Users Mailing List <[EMAIL PROTECTED]> > 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.
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" <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: Struts Users Mailing List <[EMAIL PROTECTED]> > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts-el NOT working with Struts 1.1 RC1 Release
Geez...I'm losing it. I've been staring at the computer screen for too many hours this week. Time to pop open a Budweiser and get away from all this *exciting* stuff for a while. Thanks again, JOHN -Original Message- From: David Graham [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 8:51 PM To: [EMAIL PROTECTED] Cc: Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release I haven't contributed to Struts-EL, that's David Karr. I was pointing out that you should download a recent nightly to get the fixes you need. There's nothing terribly special about RC1 vs. the nightly that came the day after RC1 was released. David *Graham* :-) >From: "Hohlen, John" <[EMAIL PROTECTED]> >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >To: Struts Users Mailing List <[EMAIL PROTECTED]> >Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release >Date: Fri, 28 Feb 2003 20:47:00 -0600 > >David, > > First, sorry for the miscommunication. I put the word valuable in >quotes to emphasize it's usefulness, not sarcasm. If I doubted it's >usefulness, I would have done something like this: valuable? > I guess I should use asterisks next time. > Personally, I'm under the impression that a "RC" release is more than >just a regular nightly build. From the Jakarta News page: > > "The Struts Team believes that this release is ready for prime time, >hence its designation as a release candidate." > > From the "Binaries" page: > > "Nightly Builds are those that are very unstable (a.k.a. dynamite!). >We >have no confidence in them. They are for developers who are helping to >develop the technology and want "the latest bits." Use at your own risk!" > > Obviously, every product is the result of a nightly build (final or >not). I don't really want to get into a debate over "release" semantics. >I realize "Struts-EL" has only been released under the category of >"nightly". Since it's so tightly coupled with Struts, I just thought it >would be nice if there was a compatible version for RC1. I'm not saying it >has to be bug-free, but at least JSP code generation error free (i.e. the >JSP doesn't blow up during the code generation process -- as these are easy >to detect, almost impossible to workaround.). I'm just trying to help >out. >Not trying to start any type of personal war. > >Thanks again for all your contributions to Struts-EL, > >JOHN > >-Original Message- >From: David Graham [mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] >Sent: Fri 2/28/2003 8:05 PM >To: [EMAIL PROTECTED] >Cc: >Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release > > > >I don't understand. You say that David fixed the problem but you're still >unhappy? RC1 != 1.1 final. There will be bugs until the final version. >You say that using nightlies is risky but you're using RC1 (which is a >nightly)! Furthermore, Struts-EL is still in the contrib folder which >gives > >it a different status than the standard code base. > >FYI, putting a word in quotes normally implies sarcasm. > >David > > > > >From: "Hohlen, John" <[EMAIL PROTECTED]> > >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > >To: Struts Users Mailing List <[EMAIL PROTECTED]> > >Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release > >Date: Fri, 28 Feb 2003 19:54:45 -0600 > > > >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 gettin
RE: Struts-el NOT working with Struts 1.1 RC1 Release
I haven't contributed to Struts-EL, that's David Karr. I was pointing out that you should download a recent nightly to get the fixes you need. There's nothing terribly special about RC1 vs. the nightly that came the day after RC1 was released. David *Graham* :-) From: "Hohlen, John" <[EMAIL PROTECTED]> Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> To: Struts Users Mailing List <[EMAIL PROTECTED]> Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release Date: Fri, 28 Feb 2003 20:47:00 -0600 David, First, sorry for the miscommunication. I put the word valuable in quotes to emphasize it's usefulness, not sarcasm. If I doubted it's usefulness, I would have done something like this: valuable? I guess I should use asterisks next time. Personally, I'm under the impression that a "RC" release is more than just a regular nightly build. From the Jakarta News page: "The Struts Team believes that this release is ready for prime time, hence its designation as a release candidate." From the "Binaries" page: "Nightly Builds are those that are very unstable (a.k.a. dynamite!). We have no confidence in them. They are for developers who are helping to develop the technology and want "the latest bits." Use at your own risk!" Obviously, every product is the result of a nightly build (final or not). I don't really want to get into a debate over "release" semantics. I realize "Struts-EL" has only been released under the category of "nightly". Since it's so tightly coupled with Struts, I just thought it would be nice if there was a compatible version for RC1. I'm not saying it has to be bug-free, but at least JSP code generation error free (i.e. the JSP doesn't blow up during the code generation process -- as these are easy to detect, almost impossible to workaround.). I'm just trying to help out. Not trying to start any type of personal war. Thanks again for all your contributions to Struts-EL, JOHN -----Original Message- From: David Graham [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 8:05 PM To: [EMAIL PROTECTED] Cc: Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release I don't understand. You say that David fixed the problem but you're still unhappy? RC1 != 1.1 final. There will be bugs until the final version. You say that using nightlies is risky but you're using RC1 (which is a nightly)! Furthermore, Struts-EL is still in the contrib folder which gives it a different status than the standard code base. FYI, putting a word in quotes normally implies sarcasm. David >From: "Hohlen, John" <[EMAIL PROTECTED]> >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >To: Struts Users Mailing List <[EMAIL PROTECTED]> >Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release >Date: Fri, 28 Feb 2003 19:54:45 -0600 > >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: '[EMAIL PROTECTED]' >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 i
RE: Struts-el NOT working with Struts 1.1 RC1 Release
David, First, sorry for the miscommunication. I put the word valuable in quotes to emphasize it's usefulness, not sarcasm. If I doubted it's usefulness, I would have done something like this: valuable? I guess I should use asterisks next time. Personally, I'm under the impression that a "RC" release is more than just a regular nightly build. From the Jakarta News page: "The Struts Team believes that this release is ready for prime time, hence its designation as a release candidate." From the "Binaries" page: "Nightly Builds are those that are very unstable (a.k.a. dynamite!). We have no confidence in them. They are for developers who are helping to develop the technology and want "the latest bits." Use at your own risk!" Obviously, every product is the result of a nightly build (final or not). I don't really want to get into a debate over "release" semantics. I realize "Struts-EL" has only been released under the category of "nightly". Since it's so tightly coupled with Struts, I just thought it would be nice if there was a compatible version for RC1. I'm not saying it has to be bug-free, but at least JSP code generation error free (i.e. the JSP doesn't blow up during the code generation process -- as these are easy to detect, almost impossible to workaround.). I'm just trying to help out. Not trying to start any type of personal war. Thanks again for all your contributions to Struts-EL, JOHN -Original Message----- From: David Graham [mailto:[EMAIL PROTECTED] Sent: Fri 2/28/2003 8:05 PM To: [EMAIL PROTECTED] Cc: Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release I don't understand. You say that David fixed the problem but you're still unhappy? RC1 != 1.1 final. There will be bugs until the final version. You say that using nightlies is risky but you're using RC1 (which is a nightly)! Furthermore, Struts-EL is still in the contrib folder which gives it a different status than the standard code base. FYI, putting a word in quotes normally implies sarcasm. David >From: "Hohlen, John" <[EMAIL PROTECTED]> >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> >To: Struts Users Mailing List <[EMAIL PROTECTED]> >Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release >Date: Fri, 28 Feb 2003 19:54:45 -0600 > >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: '[EMAIL PROTECTED]' >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
RE: Struts-el NOT working with Struts 1.1 RC1 Release
I don't understand. You say that David fixed the problem but you're still unhappy? RC1 != 1.1 final. There will be bugs until the final version. You say that using nightlies is risky but you're using RC1 (which is a nightly)! Furthermore, Struts-EL is still in the contrib folder which gives it a different status than the standard code base. FYI, putting a word in quotes normally implies sarcasm. David From: "Hohlen, John" <[EMAIL PROTECTED]> Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> To: Struts Users Mailing List <[EMAIL PROTECTED]> Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release Date: Fri, 28 Feb 2003 19:54:45 -0600 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: '[EMAIL PROTECTED]' 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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: '[EMAIL PROTECTED]' 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts-el NOT working with Struts 1.1 RC1 Release
Hello John, I am using Weblogic 7, and I had similar problem with earlier Struts-el, but I switched to Struts-el from a nightly build and it worked fine. -Original Message- From: Hohlen, John [mailto:[EMAIL PROTECTED] Sent: 27 February 2003 13:51 To: Struts-User (E-mail) Cc: '[EMAIL PROTECTED]' 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts-el NOT working with Struts 1.1 RC1 Release
Looks like David Karr committed a fix for this last night or this morning. David From: "Hohlen, John" <[EMAIL PROTECTED]> Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> To: "Struts-User (E-mail)" <[EMAIL PROTECTED]> CC: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> Subject: Struts-el NOT working with Struts 1.1 RC1 Release Date: Thu, 27 Feb 2003 07:50:52 -0600 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts-el NOT working with Struts 1.1 RC1 Release
> "John" == John Hohlen writes: John> Is anyone able to use the Struts-EL subproject with the Struts 1.1 RC1 John> release? I'm encountering the following error using the "struts-el.jar" John> from the "contrib" folder in the RC1 release: John> /jsp/login/loginTile.jsp(12): Error in using tag library John> uri='/WEB-INF/struts-html-el.tld' prefix='html-el': The Tag class John> 'org.apache.strutsel.taglib.html.ELImgTag' has no setter method John> corresponding to TLD declared attribute 'onkeypress', (JSP 1.1 spec, 5.4.1) John> I'm currently using WebLogic 6.1 SP 2. I encountered problems similar to John> this when the beta 3 release first came out. It wasn't until about a week John> later that the Struts-EL project would work with the beta 3 release (for me John> at least). I just fixed a bug in the attribute mapping for that class. The fix will be in the nightly build, which will hopefully be bundled into the next RC or full release. -- === David M. Karr ; Java/J2EE/XML/Unix/C++ [EMAIL PROTECTED] ; SCJP; SCWCD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
