2007/4/22, Ted Husted <[EMAIL PROTECTED]>:
On 4/22/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
> If all integrations were projects on themselves, this would not happen.
> This is due probably to the fact that Struts 2 did not use the Maven
> release plugin, and I think that we need to use it
On 4/22/07, Ted Husted <[EMAIL PROTECTED]> wrote:
On 4/22/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
> If all integrations were projects on themselves, this would not happen.
> This is due probably to the fact that Struts 2 did not use the Maven
> release plugin, and I think that we need to
I have this working, but I want to give it a little more time to anyone to
object before committing it :), just to review, these are the different
validation options:
1. regular form, regular submit button (normal validation)
2. css_html form, or xhtml form (validate="true"), regular submit but
On 4/22/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
If all integrations were projects on themselves, this would not happen.
This is due probably to the fact that Struts 2 did not use the Maven
release plugin, and I think that we need to use it since it forces us
to follow the correct way of d
On 4/22/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
We already have a plug-in system in 1.x. I don't think I want to develop
plugins -- but I do want to provide a standard community library for
integration classes.
We have a filter-like interface that we named "plugin", but I wouldn't
call it
2007/4/21, Paul Benedict <[EMAIL PROTECTED]>:
I am proposing a new module for Struts 1.x called "modules" which would
contain integration classes into popular open source libraries. For
starters, it would contain a new command to let Spring wire up the CRP
using a command.
Sorry for jumping in
