DO NOT REPLY [Bug 36200] New: - [shale] Clay HTML templates doesn't work with myFaces

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: New Shale Regex Validation Tag

Le 05-08-12 à 13:40, Craig McClanahan a écrit : On 8/12/05, Romero, Ron <[EMAIL PROTECTED]> wrote: [snip] This would also mean you don't need a new tag ... the existing Shale tags for integrating validators would work. Ah, but I want a new tag! :-) Seriously, a new tag would make it easi

Re: JSF vs. Struts

Hmm... I'm just about to post a reply to that entry. Basically, I feel that although JSF itself can be great view-tier technology, it isn't really a full replacement for Struts. JSF+Shale *is* a replacement for Struts, but I think that's a point which is often lost. An interesting thing abou

Re: [ti] first crack at Page Flow support

Great! Thanks for all the hard work Rich; I'm looking forward to getting this into Ti ASAP. Don Rich Feit wrote: Quick correction: In both of the sample apps, you need to run 'ant build' in WEB-INF/src. No maven yet. Rich Feit wrote: Hi all, Attached is a patch that contains a first cut

Re: 1.3.0 Release - Next Steps

At 2:01 PM -0400 8/15/05, Ted Husted wrote: On 8/15/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: Where are the source files, and how were both the HTML files and the TLDs getting generated originally? If someone explains how it used to work, I can probably make it work again. Under the "mono

Re: 1.3.0 Release - Next Steps

On 8/15/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > Where are the source files, and how were both the HTML files and the TLDs > getting generated originally? If someone explains how it used to work, I > can probably make it work again. Under the "monolithic" distribution, everything was in the o

Re: 1.3.0 Release - Next Steps

From: "Ted Husted" <[EMAIL PROTECTED]> How are we doing on mavenizing the web site I'll get the internal links/anchors done this week. At least it should be good enough for 1.3.0, though I'm not sure how we intend to distribute the documentation this time around. The users don't really nee

DO NOT REPLY [Bug 30401] - ActionMessage should include option for bundle

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: 1.3.0 Release - Next Steps

On 8/15/05, Hubert Rabago <[EMAIL PROTECTED]> wrote: > For deprecations, it's a good news/bad news thing. > > Core deprecations are done. There is one item that is left because I > wasn't sure if now is the right time to remove it. The method is > DynaActionFormClass.clear(). From what I can fi

Re: 1.3.0 Release - Next Steps

Oh, btw, ResponseUtils has a filter() method that's been deprecated for 1.2.x because the functionality was moved to TagUtils. Now that TagUtils is in another project, the filter code is back in ResponseUtils. It's still marked deprecated, and someone asked why in the javadoc. If no one objects,

Re: 1.3.0 Release - Next Steps

For deprecations, it's a good news/bad news thing. Core deprecations are done. There is one item that is left because I wasn't sure if now is the right time to remove it. The method is DynaActionFormClass.clear(). From what I can find, this was deprecated 14 months ago. It's easy to take out i

DO NOT REPLY [Bug 35127] - [taglib] All Javascript validation fails when is present

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: 1.3.0 Release - Next Steps

How are we doing on mavenizing the web site and removing the deprecations? When these two items are stable, I'll apply the remaining patches and try rolling a distribution. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For a

[Struts Wiki] Update of "StrutsClassicRelease130" by TedHusted

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification. The following page has been changed by TedHusted: http://wiki.apache.org/struts/StrutsClassicRelease130 The comment on the change is: Update status

DO NOT REPLY [Bug 36124] - [tiles] Attributes in ComponentContext set via Controller not availiabe in JSP

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

[EMAIL PROTECTED]: Project struts-core (in module struts) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project struts-core has an issue affecting its community integration. This issue affects

[EMAIL PROTECTED]: Project struts-core (in module struts) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project struts-core has an issue affecting its community integration. This issue affects

Re: [ti] first crack at Page Flow support

Quick correction: In both of the sample apps, you need to run 'ant build' in WEB-INF/src. No maven yet. Rich Feit wrote: Hi all, Attached is a patch that contains a first cut at Page Flow support within Struts Ti (sandbox). It's basically Beehive Page Flow, minus Struts 1.x, minus Servlet,

[ti] first crack at Page Flow support

Hi all, Attached is a patch that contains a first cut at Page Flow support within Struts Ti (sandbox). It's basically Beehive Page Flow, minus Struts 1.x, minus Servlet, plus XWork, plus some refactoring. And minus a bunch of functionality that I had to disable in the process. There are three