Re: S2 validation without API ties

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wes, Sorry for the delay in replying... I hadn't noticed that your reply was here. On 4/28/2010 11:49 AM, Wes Wannemacher wrote: > I can understand your desire to remove the dependency of struts, > making your actions reusable. But at the same time,

Re: S2 validation without API ties

Chris, There are a few non-struts/xwork-validation plugins that integrate with general purpose validation mechanisms. Off the top of my head, I remember this - https://cwiki.apache.org/confluence/display/WW/OVal+Plugin But, I think there are two distinctly different things you are considering he

Re: S2 validation without API ties

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rahul, On 4/27/2010 1:09 AM, Rahul Mohan wrote: > I think the fundamental mechanism of S2 is the configurable interceptor > stack where each interceptor applies itself to the current action based on > the interfaces the action implements. You can st

Re: S2 validation without API ties

validation without API ties -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, Bump: does anyone have any ideas? Thanks, - -chris On 4/12/2010 4:48 PM, Christopher Schultz wrote: > All, > > It's been a long time since I've posted, and I've got my eye on S2 for > s

Re: S2 validation without API ties

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, Bump: does anyone have any ideas? Thanks, - -chris On 4/12/2010 4:48 PM, Christopher Schultz wrote: > All, > > It's been a long time since I've posted, and I've got my eye on S2 for > some upcoming work that will share code with a non-web-base

S2 validation without API ties

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, It's been a long time since I've posted, and I've got my eye on S2 for some upcoming work that will share code with a non-web-based interface so I'd like to re-use as much code as possible without tying myself to the S2 API. The issue is with fi