Just see the below link for usage of Annotations in validation,
Hope might be useful
http://intricatetips.blogspot.com
--
View this message in context:
http://www.nabble.com/Struts-2-Annotation-Validation-Problem-tp16990235p19592822.html
Sent from the Struts - User mailing list archive at
/annotation-validation-problem-tp17862211p17862211.html
Sent from the Struts - User mailing list archive at Nabble.com.
I could be wrong in my assumption, but I became suspicious when the
action class wasn't in the stacktrace...
On Tue, 2008-05-06 at 20:48 -0400, Jim Kiley wrote:
> It's weird and confusing that inherited methods don't make it into the proxy
> class. Took me an age to figure it out, in no small p
It's weird and confusing that inherited methods don't make it into the proxy
class. Took me an age to figure it out, in no small part because I couldn't
find an easy way to inspect the proxy class's methods. My workaround was to
eliminate the @Transactional annotation entirely, and I'm hoping tha
Sorry I didn't catch this earlier, but I had the exact same problem. It
would seem that when you use Spring's @Transactional annnotation, the
class gets proxied... Which I would think is okay, except for the fact
that inherited methods (such as ActionSupport.input()) do not make it
into the proxied
I solved this problem and I figure that nabble might want to record the end
reason for the bug.
Another method entirely, elsewhere on ProductDetailAction, had a
@Transactional annotation. It didn't need one -- I was using injected
transaction management and the OpenEntityManagerInViewFilter. Why
Hi folks,
I've run into a problem with Struts 2 validation annotations.
In short -- I have a VisitorFieldValidator on an action POJO named
ProductDetailAction. I have RequiredFieldValidator and
RequiredStringValidator on one field within the "visited" object.
Now -- ProductDetailAction did not
7 matches
Mail list logo
