2013/7/2 Paul Benedict :
> My first idea was to add an "actions" attribute on the validator
> annotations. For example:
>
> @RequredStringValidator(key="firstName", actions={ "execute", "forward" })
Or maybe method names? But then the same validation could be executed
for different actions which m
My first idea was to add an "actions" attribute on the validator
annotations. For example:
@RequredStringValidator(key="firstName", actions={ "execute", "forward" })
Lacking the attribute means all methods, of course.
Thoughts?
On Tue, Jul 2, 2013 at 1:37 AM, Lukasz Lenart wrote:
> 2013/6/29
2013/6/28 Umesh Awasthi :
> I worked quite a bit on JSR 303 validations (Both with Hibernate Validation
> as well Apache Bval) and also worked on creating plugin to integrate it
> with Struts2, since with version 2.5/3.0 , we are looking to have some
> major changes so was wondering if i should wai
2013/6/29 Paul Benedict :
> This is the best proposed solution and I am surprised it didn't become part
> of Struts:
> https://issues.apache.org/jira/browse/WW-1967
You can do it yourself right away ;-)
> We should add another level of XML filename checking to to be
> --.xml
What about Annotatio
This is the best proposed solution and I am surprised it didn't become part
of Struts:
https://issues.apache.org/jira/browse/WW-1967
We should add another level of XML filename checking to to be
--.xml
Thoughts?
On Fri, Jun 28, 2013 at 10:17 AM, Paul Benedict wrote:
> I am glad you're familiar
I am glad you're familiar with validation groups -- because that's exactly
what I was alluding to. I see the Struts 2 documentation allows me to
target validation on a particular method through XML only; Struts 2 simply
lacks the annotation counterpart. If today I have to use XML, okay, but
just wa
I worked quite a bit on JSR 303 validations (Both with Hibernate Validation
as well Apache Bval) and also worked on creating plugin to integrate it
with Struts2, since with version 2.5/3.0 , we are looking to have some
major changes so was wondering if i should wait for Struts 2.5/ 3.0.
On Fri,
This sounds a bit like "inversion of control". As for me, I'd rather not
like to have my model (which is to validate) to have knowledge about the
business side validation is triggered from. When I develop from the action
perpective, I know if the current method is better off triggering
validation o
Hi Paul,
actually there is one way: using @SkipValidation combined with @Validation
Or maybe I miss the point. Is there something better in your approach?
On 28 June 2013 05:38, Paul Benedict wrote:
> I was thinking it would be a good idea to add "String[] actions" on the
> validations. When emp
On Fri, Aug 21, 2009 at 11:53 AM, Wes Wannemacher wrote:
> Before I actually release, I want to make sure that I'm clear on this
> one... Martin, you mentioned that if struts-annotations was built
> against the unreleased struts-master (version 5) build that we should
> hold struts-annotations back
On Sun, Aug 16, 2009 at 11:53 AM, Wes Wannemacher wrote:
> On Sunday 16 August 2009 02:40:38 pm Martin Cooper wrote:
>> On Sun, Aug 16, 2009 at 11:31 AM, Wes Wannemacher wrote:
>> > On Sunday 16 August 2009 02:13:26 pm Martin Cooper wrote:
>> >> If this was built against a new and unreleased struts
On Sunday 16 August 2009 02:40:38 pm Martin Cooper wrote:
> On Sun, Aug 16, 2009 at 11:31 AM, Wes Wannemacher wrote:
> > On Sunday 16 August 2009 02:13:26 pm Martin Cooper wrote:
> >> If this was built against a new and unreleased struts-master, then my
> >> vote is -1. We need to vote to release t
On Sun, Aug 16, 2009 at 11:31 AM, Wes Wannemacher wrote:
> On Sunday 16 August 2009 02:13:26 pm Martin Cooper wrote:
>> If this was built against a new and unreleased struts-master, then my
>> vote is -1. We need to vote to release the new struts-master before we
>> can vote on the new struts-annot
That doesn't make any difference or have any impact, I say we keep it.
musachy
On Sun, Aug 16, 2009 at 11:31 AM, Wes Wannemacher wrote:
> On Sunday 16 August 2009 02:13:26 pm Martin Cooper wrote:
>> If this was built against a new and unreleased struts-master, then my
>> vote is -1. We need to vo
On Sunday 16 August 2009 02:13:26 pm Martin Cooper wrote:
> If this was built against a new and unreleased struts-master, then my
> vote is -1. We need to vote to release the new struts-master before we
> can vote on the new struts-annotations build.
>
http://people.apache.org/builds/struts/struts
If this was built against a new and unreleased struts-master, then my
vote is -1. We need to vote to release the new struts-master before we
can vote on the new struts-annotations build.
--
Martin Cooper
On Wed, Aug 12, 2009 at 10:29 AM, Wes Wannemacher wrote:
> The Struts Annotations 1.0.5 test
+1 GA
Cheers, Rainer
Von meinem iPhone gesendet
Am 12.08.2009 um 19:29 schrieb Wes Wannemacher :
The Struts Annotations 1.0.5 test build is now available as a Maven
artifact. Functionality was added, but Struts releases do not
currently
use the new features.
The test build is available in
+1 GA
Wes Wannemacher schrieb:
> The Struts Annotations 1.0.5 test build is now available as a Maven
> artifact. Functionality was added, but Struts releases do not currently
> use the new features.
>
> The test build is available in the Struts snapshot repository located
> here -
>
> http://peo
Here is my +1 GA, binding
-W
On Wed, Aug 12, 2009 at 1:29 PM, Wes Wannemacher wrote:
> The Struts Annotations 1.0.5 test build is now available as a Maven
> artifact. Functionality was added, but Struts releases do not currently
> use the new features.
>
> The test build is available in the Strut
+1 GA
On Wed, Aug 12, 2009 at 10:29 AM, Wes Wannemacher wrote:
> The Struts Annotations 1.0.5 test build is now available as a Maven
> artifact. Functionality was added, but Struts releases do not currently
> use the new features.
>
> The test build is available in the Struts snapshot repository l
On 3/11/07, Martin Cooper <[EMAIL PROTECTED]> wrote:
Unless I'm missing something, it's because we want to be able to release
some pieces (e.g. plugins) without requiring a corresponding release of
'core'. If a plugin depends on an updated version of struts-annotations (or
whatever), it shouldn'
On 3/11/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
I believe Don said Plug-ins could be used in other projects...
theoretically even Struts 1. So it's technically a separate project with
its own build cycle.
Unless and until an actual community forms around Struts Annotations
and other people
On 3/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> Unfortunately, until we start using Maven to do releases,
I don't know what that means. What else would we need to do?
Some variation on "mvn release:prepare" and "mvn release:perform" with
-P whatever-profiles-struts2-needs and probably a f
For Struts 2, we decided not to make plugins separate subprojects.
Why can't POM, Archetype, and Annotation be on the same build tree
with Core and Plugins?
I believe Don said Plug-ins could be used in other projects...
theoretically even Struts 1. So it's technically a separate project with
On 3/11/07, Martin Cooper <[EMAIL PROTECTED]> wrote:
The POM needs to be published to the standard Maven repo, so that it's there
as a versioned dependency that can be relied upon by other parts of the
project.
Do we have multiple parts for Struts 2?
We tried subprojects for Struts 1, and ulti
On 3/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
On 3/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> > No one objects to releasing the struts-master pom, and it's the same
> > situation.
And, I don't understand why we do that either (which is why I've never
voted on the Struts pom).
The POM
On 3/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
On 3/11/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On 3/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
>
> > It's still not clear to me why it needs to be released separately. The
> > justification for the archetypes almost makes sense, but creat
On 3/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> No one objects to releasing the struts-master pom, and it's the same
> situation.
And, I don't understand why we do that either (which is why I've never
voted on the Struts pom).
-Ted.
On 3/11/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 3/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> It's still not clear to me why it needs to be released separately. The
> justification for the archetypes almost makes sense, but creating a
> separate distribution for Struts Annotations still
On 3/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
It's still not clear to me why it needs to be released separately. The
justification for the archetypes almost makes sense, but creating a
separate distribution for Struts Annotations still seems like busy
work.
No one objects to releasing the
On 3/11/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
By the way, I've been making changes to it that I wouldn't be comfortable
getting together with the 2.0 branch.
Then maybe we should bump SA to a 1.1.0-SNAPSHOT. Otherwise, things
could get sticky if for some reason we need to bring a new S
Jim, if you do find the "discussion", can you please create a wiki
page or something for it?
It's still not clear to me why it needs to be released separately. The
justification for the archetypes almost makes sense, but creating a
separate distribution for Struts Annotations still seems like bus
By the way, I've been making changes to it that I wouldn't be comfortable
getting together with the 2.0 branch.
musachy
On 3/11/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 3/11/07, James Mitchell <[EMAIL PROTECTED]> wrote:
> Why is struts-annotations under struts/maven if it is required in
On 3/11/07, James Mitchell <[EMAIL PROTECTED]> wrote:
Why is struts-annotations under struts/maven if it is required in
core and dojo.
I'm sure I missed that discussion.
Yes. Check the archives. :) It's apparently not Struts 2 specific.
Also, like the master pom, it has to be released prior
34 matches
Mail list logo
