Re: RoadMap [was Re: ViewUtils ... ]

Why is JSF looking for help? Because it is superior or because it is failing? Why there is any *shame* in choices is really beyond me. I would like someone explain to me what JSF is doing involved with Struts other than raiding the name and goodwill. Struts and JSF are inherently incompatible.

Re: Shale for 2.x? (was Re: RoadMap)

How can Struts which is inherenlty incompatible with JSF be a "better fit" than MyFaces which is a JSF implementation? I would prefer Darwin rather than Machievelli resolve the Struts v. JSF choice and think that Ted as usual is right on the mark. Jack On Wed, 29 Dec 2004 12:56:35 -0800, Craig

Re: RoadMap [was Re: ViewUtils ... ][Slightly OT]

Sometimes Martin just hits the nail on the head. The House of Lords once debated putting up neon "FOG" signs in London for those that could not see the obvious. We have Martin to help us. My hats are off to this bit of very important bit of common sense. Jack On Wed, 29 Dec 2004 14:39:27 -080

Re: Shale for 2.x? (was Re: RoadMap)

On Wed, 29 Dec 2004 16:28:32 -0800, Martin Cooper wrote: >> > Back in the day, it might have been better if we had placed >> most of our taglibs with Jakarta Taglibs, rather than keep them >> all here. I think this is the same sort of thing. >> >> The problem with this theory relates to a similar i

Basic workflow engine

I have developed a basic workflow engine that I have found to be extremely useful in my current Struts applications. I developed it after finding shortcomings in the open source workflow stuff that was available at the time. I know Craig mentioned a possible need for workflow stuff for Shale. I'

Re: Basic workflow engine

On Thu, 30 Dec 2004 12:47:04 -0500, Sean Schofield <[EMAIL PROTECTED]> wrote: > I have developed a basic workflow engine that I have found to be > extremely useful in my current Struts applications. I developed it > after finding shortcomings in the open source workflow stuff that was > available

Re: Basic workflow engine

> I'd be interested in seeing what you've come up with. Most likely you will not be able to use much of it (for your specific itch) but you never know. I might have come up with some general concepts that you could find useful. I will send it to you once I'm done refactoring (I'm rewriting my fa

Re: Basic workflow engine

On Thu, 30 Dec 2004 10:18:54 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On Thu, 30 Dec 2004 12:47:04 -0500, Sean Schofield > <[EMAIL PROTECTED]> wrote: > > I have developed a basic workflow engine that I have found to be > > extremely useful in my current Struts applications. I developed

Re: Basic workflow engine

A good way to get started is to put the code under the Apache License * http://apache.org/licenses/ But with your own copyright, and then post it somewhere so that people can download it. This is how Validator and Tiles, among others, got their start. -Ted. On Thu, 30 Dec 2004 12:47:04 -0500,

Re: Basic workflow engine

Just to add to the list of general tools out there for workflow I think this one is fairly nice, though I haven't really used it extensively...works with JSF too Craig http://wfnm.sourceforge.net Michael On Thu, 30 Dec 2004 10:25:52 -0800, Martin Cooper <[EMAIL PROTECTED]> wrote: > On Thu, 30 De

Any reason not to delete Jakarta Struts web site?

Folks, The old Struts web site within the Jakarta site is still hanging around. We've been redirecting from there to our struts.a.o site for quite some time now, so I think we should be able to zap the old one. Just wanted to ping the list to see if anyone knows of anything we need to save from it

svn commit: r123761 - /struts/faces/trunk/build.properties.sample /struts/faces/trunk/core-library/src/conf/struts-tld.xsl

Author: craigmcc Date: Thu Dec 30 18:53:29 2004 New Revision: 123761 URL: http://svn.apache.org/viewcvs?view=rev&rev=123761 Log: Fix typos in system URL (in the generated tag library) and base variable name in build.properties.sample. PR: Bugzilla #32666 Submitted by: Mike Gratsas Modified:

svn commit: r123763 - /struts/faces/trunk/README.txt

Author: craigmcc Date: Thu Dec 30 19:01:49 2004 New Revision: 123763 URL: http://svn.apache.org/viewcvs?view=rev&rev=123763 Log: Document the limitation that you cannot use to forward to a JSF page. Modified: struts/faces/trunk/README.txt Modified: struts/faces/trunk/README.txt Url: http://

DO NOT REPLY [Bug 32666] - Struts-Faces integration

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

svn commit: r123764 - /struts/faces/trunk/core-library/src/java/org/apache/struts/faces/application/FacesRequestProcessor.java /struts/faces/trunk/core-library/src/java/org/apache/struts/faces/application/FacesTilesRequestProcessor.java

Author: craigmcc Date: Thu Dec 30 19:13:18 2004 New Revision: 123764 URL: http://svn.apache.org/viewcvs?view=rev&rev=123764 Log: Wrap lifecycle.render(context) calls in try/finally so the request can be cleaned up even if rendering throws an exception. PR: Bugzilla #32370 Submitted By: Chris Fras

DO NOT REPLY [Bug 32370] - FacesRequestProcessor call to lifecycle.render(context) needs to be wrapped in a try, finally

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: Where should the build system live?

Hmm..this raises an interesting issue. When you mention build dependencies, do you really mean build one project then another in the same process, or just that one project would depend on a jar from another? In the case of StrutsTestCase, 1) I don't like Core being dependent on a subproject,

svn commit: r123769 - in struts/core/trunk: doc doc/faqs doc/proposals doc/userGuide src/share/org/apache/struts/upload xdocs xdocs/faqs

Author: martinc Date: Thu Dec 30 21:29:52 2004 New Revision: 123769 URL: http://svn.apache.org/viewcvs?view=rev&rev=123769 Log: Replace references to nagoya (which is going away) with the appropriate logical DNS names. Modified: struts/core/trunk/doc/faqs/index.xml struts/core/trunk/doc/faq

svn commit: r123770 - /struts/el/trunk/doc/proposals/release-plan-1.0b1.xml /struts/el/trunk/doc/proposals/release-plan-1.1b1.xml

Author: martinc Date: Thu Dec 30 21:30:27 2004 New Revision: 123770 URL: http://svn.apache.org/viewcvs?view=rev&rev=123770 Log: Replace references to nagoya (which is going away) with the appropriate logical DNS names. Modified: struts/el/trunk/doc/proposals/release-plan-1.0b1.xml struts/el

svn commit: r123771 - /struts/sandbox/trunk/struts-jericho/README.txt

Author: martinc Date: Thu Dec 30 21:31:45 2004 New Revision: 123771 URL: http://svn.apache.org/viewcvs?view=rev&rev=123771 Log: Replace references to nagoya (which is going away) with the appropriate logical DNS names. Modified: struts/sandbox/trunk/struts-jericho/README.txt Modified: struts/

Re: Basic workflow engine

This one is super, Michael. Thanks! Jack On Thu, 30 Dec 2004 12:54:16 -0600, Michael Rasmussen <[EMAIL PROTECTED]> wrote: > Just to add to the list of general tools out there for workflow I > think this one is fairly nice, though I haven't really used it > extensively...works with JSF too Craig

Re: Basic workflow engine

I would be interested, always, in looking at code, Sean. Jack On Thu, 30 Dec 2004 12:47:04 -0500, Sean Schofield <[EMAIL PROTECTED]> wrote: > I have developed a basic workflow engine that I have found to be > extremely useful in my current Struts applications. I developed it > after finding sho