Re: Integrating Tiles with Struts 2

George, again for the third time, please ask this question to the Struts USERS mailing list: http://struts.apache.org/mail.html Antonio 2007/8/9, GEDA <[EMAIL PROTECTED]>: > > > Hi. Regarding the integration of tiles plugin, I have two questions: > > 1) where should I put de tiles-defs.xml file ?

Re: Resolving/Closing JIRA issues

On Thu, Aug 09, 2007 at 03:32:43PM +1000, Don Brown wrote: > I believe the traditional purpose of the "closed" state is for a QA > department, so they can mark the issues they have verified to be > fixed. In Struts, I don't think we really do that, and while we do > informal code reviews (commit e

Integrating Tiles with Struts 2

Hi. Regarding the integration of tiles plugin, I have two questions: 1) where should I put de tiles-defs.xml file ? 2) Where should I put the element in order to include the plugin in my web app ? Thanks. -- View this message in context: http://www.nabble.com/Integrating-Tiles-with-Struts-

Re: Resolving/Closing JIRA issues

I believe the traditional purpose of the "closed" state is for a QA department, so they can mark the issues they have verified to be fixed. In Struts, I don't think we really do that, and while we do informal code reviews (commit emails), we certainly don't require formal test documents that verif

Re: Voting Process -- Recap

I'll volunteer to add this unless someone else wants to. On 8/7/07, Martin Cooper <[EMAIL PROTECTED]> wrote: > > Have we codified this somewhere? I didn't see a commit go by, but then I'm > still catching up. > > -- > Martin Cooper > > > On 8/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: > > >

Re: Resolving/Closing JIRA issues

According to JIRA: *Resolved = *A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed. ***Closed = *The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened. That seems pretty pr

Re: Resolving/Closing JIRA issues

Is there any practical advantage to closing a resolved issue after a release? On 8/7/07, Paul Benedict <[EMAIL PROTECTED]> wrote: > Don, the PITA truth is the only reason why I use Resolved up to a release. > :-) > > On 8/7/07, Don Brown <[EMAIL PROTECTED]> wrote: > > > > My 2c is I don't see any

Re: Override interceptors in struts-default from plugin

YikesSounds like there's more than a simple fix needed... Maybe it's safer (for now, I'm pretty sure that I will bump into this problem later) to just modify the workflow interceptors? What I need is a simple check for a Boolean request attribute indicating if it should be skipped or not. It's

Re: Are there any struts generated error messages?

Please ask this questions to the Struts Users Mailing List: http://struts.apache.org/mail.html Antonio 2007/8/8, ojasrege <[EMAIL PROTECTED]>: > > > When I make an error in my struts logic, the HTML page generation stops at > that point and I see truncated HTML pages. However, I cannot find an >

Are there any struts generated error messages?

When I make an error in my struts logic, the HTML page generation stops at that point and I see truncated HTML pages. However, I cannot find an error message anywhere. For example, I recently didn't define a setter/getter in an ActionForm for an html:hidden field I added to a JSP page, and so st

Re: svn commit: r563238 [1/6] - in /struts/struts2/trunk/apps: ./ blank/ blank/src/main/java/example/ blank/src/main/resources/ blank/src/main/resources/example/ blank/src/main/webapp/ blank/src/main/

2007/8/7, James Mitchell <[EMAIL PROTECTED]>: > I agree, please remove it. Ok pals, I think that, for the moment, I should revert the change to remove the licenses from the examples, leaving it only in the pom. Anyway the licenses must stay in the core/api/plugin code, right? Antonio ---