test

pls ignore - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

On Tue, 23 Mar 2004 20:52:03 -0800 (PST), Martin Cooper wrote: > So, there are pros and cons both ways, of course. Now we just need > to make a decision and move on it. ;- If all the deliverables are in a single module, is there a way that we can generate a separate changelog for each one? http:

Re: Counting down to the 1.2.1 release (was RE: Making Struts Build Easier)

This is really a "counting down to the 1.3.0 release" issue, but I've started on a version of the MailReader application for Commons Chain. The idea being, instead of using conventional Struts Actions, we can use Command and pass what's needed through a Context. I setup the infrastructure last n

DO NOT REPLY [Bug 27943] New: - resource files for non-default modules not loading correctly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Counting down to the 1.2.1 release (was RE: Making Struts Build Easier)

--- Martin Cooper <[EMAIL PROTECTED]> wrote: > On Thu, 25 Mar 2004, [EMAIL PROTECTED] wrote: > > > > > > -Original Message- > > > Do we want to wait for a Validator 1.1.2, or roll it with 1.1.1? > > > > I just fixed a show stopper bug today in validator in CVS and made an > accompaning ch

Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

> Whether the "classic" and "el" taglibs are one chunk or two isn't hugely important to me either -- I would prefer that this decision be made by developers who've done more work on that code to date. However, I did find that when I patched o.a.s.t.html.JavascriptValidator, I had to go and mak

Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

--- Joe Germuska <[EMAIL PROTECTED]> wrote: > > > Whether the "classic" and "el" taglibs are one chunk or two isn't > >> hugely important to me either -- I would prefer that this decision > be > >> made by developers who've done more work on that code to date. > >> However, I did find that whe

Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

At 6:30 AM -0800 3/25/04, David Graham wrote: Yep, notice I mentioned removing "many" tags and not *all* tags :-). There are certainly tags we should keep around but I just don't see a need for most of the logic and bean tags in Struts 2.0. Whoops. I read >Is there any reason that the EL tags wo

Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

At 7:44 AM -0500 3/25/04, Ted Husted wrote: On Tue, 23 Mar 2004 20:52:03 -0800 (PST), Martin Cooper wrote: So, there are pros and cons both ways, of course. Now we just need to make a decision and move on it. ;- If all the deliverables are in a single module, is there a way that we can generate

RE: struts-workflow (Re: OT: Struts JSR?)

>>1:There is no overlap as there does not seem to be any development >>going on about WorkFlow area in struts. >I think you are correct; people seem to be gravitating to struts-workflow. This makes my life easier now that I know there is no overlap. >I'm not sure which of the above you'd like t

Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Joe Germuska wrote: > Whether the "classic" and "el" taglibs are one chunk or two isn't hugely important to me either -- I would prefer that this decision be made by developers who've done more work on that code to date. However, I did find that when I patched o.a.s.t.html.JavascriptValidator

Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Quoting "Peter A. Pilgrim" <[EMAIL PROTECTED]>: > Joe Germuska wrote: > >> > Whether the "classic" and "el" taglibs are one chunk or two isn't > >> > >>> hugely important to me either -- I would prefer that this decision be > >>> made by developers who've done more work on that code to date. >

Re: Future Struts evolution: look at elements of BEA Page Flows

Hi All-- As David put on flame-retardant gloves, I'll provide full disclosure and tell you what I know. I'm a dev on the team that wrote the Java Page Flow (JPF) code, and open sourcing JPF is something we've been discussing for some time now. I'd definitely be interested in talking about h

DO NOT REPLY [Bug 27961] New: - struts.jsl patch so that Maven build will create taglib documentation pages

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 27961] - struts.jsl patch so that Maven build will create taglib documentation pages

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 27964] New: - struts.jsl patch so that Maven build includes contributors box

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 27964] - struts.jsl patch so that Maven build includes contributors box

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

> --- Joe Germuska <[EMAIL PROTECTED]> wrote: > > > > Whether the "classic" and "el" taglibs are one chunk or two isn't > > >> hugely important to me either -- I would prefer that this decision > > be > > >> made by developers who've done more work on that code to date. > > >> However, I did fi

Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

--- Arron Bates <[EMAIL PROTECTED]> wrote: > > --- Joe Germuska <[EMAIL PROTECTED]> wrote: > > > > > Whether the "classic" and "el" taglibs are one chunk or two > isn't > > > >> hugely important to me either -- I would prefer that this > decision > > > be > > > >> made by developers who've done