You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@struts.apache.org by Jay Sheth <sh...@gmail.com> on 2005/08/08 21:31:07 UTC

validate() not called

Hi,
I am trying to use the validate() by extending the
org.apache.struts.validator.ValidatorForm class.

The problem is that the validate() is being called for one form class
which I have created, however it is not being called for another
similar form class. There are no errors which compiling etc...so i
dont get to know why it is not being called.

Any hints on how to debug as to why it is not called ?

The snippet struts-config.xml is : 
<action
            path="/maintainRecurringTasks"
            type="tasks.action.MaintainRecurringTasksPageAction"
            scope="request"
            name="MaintainRecurringTasksPageForm"
            attribute="MaintainRecurringTasksPageForm"  
            parameter="maintainRecurringTasks"
            validate="true">
            <forward name="success" 
               path="/jsp/tasks/MaintainRecurringTasks.jsp" />            
        </action>

Thanks,

Jay

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: Struts, JSP 2.0 and Jasper2 compiler error

Posted by Clark Wright <cw...@liquidmachines.com>.

At 12:58 PM 9/13/2005, you wrote:
>At 11:10 AM 9/13/2005, Martin Gainty wrote:
>>Clark-
>>
>>Ant has not upgraded the JSPC task for the JSP Servlet 2.0 spec as of yet 
>>to quote
>>"There are known problems with Tomcat 5.x that won't get fixed in Ant, 
>>please use Tomcat's jspc task instead."
>
>Yup, been there, gotten it to work for a while now.
>
>The real issue seems to be backwards compatibility when generating the 
>java code for taglibs that are adhering to version 1.1 of the JSP spec 
>while using the Tomcat 5.5 version of JasperC, which implements the 2.0 spec.
>
>For instance,
>using JasperC from Tomcat 4.x (which also required the custom ant config), 
>the following class would be generated:
>
>   private boolean
>_jspx_meth_html_img_0(javax.servlet.jsp.tagext.Tag _jspx_th_html_link_0,
>  javax.servlet.jsp.PageContext pageContext)
>           throws Throwable
>
>Now, using the Tomcat 5.5 jasperC, you get this class:
>
>private boolean
>_jspx_meth_html_link_0 (javax.servlet.jsp.tagext.JspTag _jspx_th_html_html_0,
>PageContext _jspx_page_context)
>           throws Throwable
>
>Now, same jsp, same taglib, same backing jar.  The only difference is that 
>the version of JasperC changed.

What I failed to explicitly point out is that the first argument of the 
generated call has changed.

javax.servlet.jsp.tagext.JspTag is new has of JSP 2.0
(see 
http://java.sun.com/j2ee/1.4/docs/api/javax/servlet/jsp/tagext/JspTag.html)

Any tags that are not compiled against the J2EE 1.4 libraries appear to not 
be useable with the latest version of JasperC.

- clark.

>g


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

[TEST] Test please ignore

Posted by Leon Rosenberg <ro...@googlemail.com>.

Test please ignore, switched account to gmail and somehow my mails
seems to be ignored...

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: Struts, JSP 2.0 and Jasper2 compiler error

Posted by Clark Wright <cw...@liquidmachines.com>.

At 09:03 PM 9/13/2005, you wrote:
>I'm not sure about this; at worst, wouldn't it be sufficient to recompile 
>just the Struts taglibs against the Servlet 2.4 / JSP 2.0 APIs? There 
>should be no need to upgrade to J2SE 5 or to recompile any other part of 
>Struts as far as I can see.
>
>That being said, I'm not sure any of this is necessary. I'm using Struts 
>1.2.7 on Tomcat 5.x without any problem what-so-ever. Perhaps Jasperc2 has 
>options to control which level of JSP spec it targets and defaults to 
>something backwards-compatible when called during normal operation of the 
>Tomcat?
>
>Clark, I suggest you look into that before going to the effort of 
>recompiling everything, especially since you'd then be running a 
>non-standard Struts build and would presumably have to repeat the effort 
>every time you upgrade...

Found the culprit - a reference to a v1.3 j2ee jar on the build path...

cleaned up the build path, its all good.

- clark.


>L.
>
>Martin Gainty wrote:
>>Clark-
>>The only way I know you can achieve 100% compatibility would be if
>>You recompile the entire struts package library with J2SE 5.0
>>which means compiling
>>TagLibs, JSP Pages and Servlet, external providers and jars (basically 
>>everything) with the 5.0 JDK to conform to the 2.0 JSP Servlet spec
>>Peronally I would feel more comfortable if the original authors did this but
>>I think this could also be a fun weekend project..
>>In any case let me know how you make out or if I can help out in any way,
>>Does anyone else have a solution for this??
>>Martin-
>>617-852-7822
>>----- Original Message ----- From: "Clark Wright" 
>><cw...@liquidmachines.com>
>>To: "Martin Gainty" <mg...@hotmail.com>
>>Cc: "Struts Users Mailing List" <us...@struts.apache.org>
>>Sent: Tuesday, September 13, 2005 12:58 PM
>>Subject: Re: Struts, JSP 2.0 and Jasper2 compiler error
>>
>>>At 11:10 AM 9/13/2005, Martin Gainty wrote:
>>>
>>>>Clark-
>>>>
>>>>Ant has not upgraded the JSPC task for the JSP Servlet 2.0 spec as of 
>>>>yet to quote
>>>>"There are known problems with Tomcat 5.x that won't get fixed in Ant, 
>>>>please use Tomcat's jspc task instead."
>>>
>>>
>>>Yup, been there, gotten it to work for a while now.
>>>
>>>The real issue seems to be backwards compatibility when generating the 
>>>java code for taglibs that are adhering to version 1.1 of the JSP spec 
>>>while using the Tomcat 5.5 version of JasperC, which implements the 2.0 spec.
>>>
>>>For instance,
>>>using JasperC from Tomcat 4.x (which also required the custom ant 
>>>config), the following class would be generated:
>>>
>>>   private boolean
>>>_jspx_meth_html_img_0(javax.servlet.jsp.tagext.Tag _jspx_th_html_link_0,
>>>  javax.servlet.jsp.PageContext pageContext)
>>>           throws Throwable
>>>
>>>Now, using the Tomcat 5.5 jasperC, you get this class:
>>>
>>>private boolean
>>>_jspx_meth_html_link_0 (javax.servlet.jsp.tagext.JspTag 
>>>_jspx_th_html_html_0,
>>>PageContext _jspx_page_context)
>>>           throws Throwable
>>>
>>>Now, same jsp, same taglib, same backing jar.  The only difference is 
>>>that the version of JasperC changed.
>>>
>>>The first example adheres to JSP 1.1, the second to JSP 2.0.
>>>
>>>But, since the taglib, and its jar, where generated/compiled for jsp 
>>>1.1, you get a "cannot be applied error" since the class hierarchy for 
>>>the tags themselves changed with jsp 2.0.
>>>
>>>Since Tomcat 5.5 has been out for a year, I can not be the first person 
>>>to run into this, so what am I missing?
>>>
>>>Thanks,
>>>- clark.,
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>>>For additional commands, e-mail: user-help@struts.apache.org
>>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>For additional commands, e-mail: user-help@struts.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: Struts, JSP 2.0 and Jasper2 compiler error

Posted by Laurie Harper <la...@holoweb.net>.

I'm not sure about this; at worst, wouldn't it be sufficient to 
recompile just the Struts taglibs against the Servlet 2.4 / JSP 2.0 
APIs? There should be no need to upgrade to J2SE 5 or to recompile any 
other part of Struts as far as I can see.

That being said, I'm not sure any of this is necessary. I'm using Struts 
1.2.7 on Tomcat 5.x without any problem what-so-ever. Perhaps Jasperc2 
has options to control which level of JSP spec it targets and defaults 
to something backwards-compatible when called during normal operation of 
the Tomcat?

Clark, I suggest you look into that before going to the effort of 
recompiling everything, especially since you'd then be running a 
non-standard Struts build and would presumably have to repeat the effort 
every time you upgrade...

L.

Martin Gainty wrote:
> Clark-
> 
> The only way I know you can achieve 100% compatibility would be if
> You recompile the entire struts package library with J2SE 5.0
> which means compiling
> TagLibs, JSP Pages and Servlet, external providers and jars (basically 
> everything) with the 5.0 JDK to conform to the 2.0 JSP Servlet spec
> Peronally I would feel more comfortable if the original authors did this 
> but
> I think this could also be a fun weekend project..
> 
> In any case let me know how you make out or if I can help out in any way,
> 
> Does anyone else have a solution for this??
> Martin-
> 617-852-7822
> 
> ----- Original Message ----- From: "Clark Wright" 
> <cw...@liquidmachines.com>
> To: "Martin Gainty" <mg...@hotmail.com>
> Cc: "Struts Users Mailing List" <us...@struts.apache.org>
> Sent: Tuesday, September 13, 2005 12:58 PM
> Subject: Re: Struts, JSP 2.0 and Jasper2 compiler error
> 
> 
>> At 11:10 AM 9/13/2005, Martin Gainty wrote:
>>
>>> Clark-
>>>
>>> Ant has not upgraded the JSPC task for the JSP Servlet 2.0 spec as of 
>>> yet to quote
>>> "There are known problems with Tomcat 5.x that won't get fixed in 
>>> Ant, please use Tomcat's jspc task instead."
>>
>>
>> Yup, been there, gotten it to work for a while now.
>>
>> The real issue seems to be backwards compatibility when generating the 
>> java code for taglibs that are adhering to version 1.1 of the JSP spec 
>> while using the Tomcat 5.5 version of JasperC, which implements the 
>> 2.0 spec.
>>
>> For instance,
>> using JasperC from Tomcat 4.x (which also required the custom ant 
>> config), the following class would be generated:
>>
>>   private boolean
>> _jspx_meth_html_img_0(javax.servlet.jsp.tagext.Tag _jspx_th_html_link_0,
>>  javax.servlet.jsp.PageContext pageContext)
>>           throws Throwable
>>
>> Now, using the Tomcat 5.5 jasperC, you get this class:
>>
>> private boolean
>> _jspx_meth_html_link_0 (javax.servlet.jsp.tagext.JspTag 
>> _jspx_th_html_html_0,
>> PageContext _jspx_page_context)
>>           throws Throwable
>>
>> Now, same jsp, same taglib, same backing jar.  The only difference is 
>> that the version of JasperC changed.
>>
>> The first example adheres to JSP 1.1, the second to JSP 2.0.
>>
>> But, since the taglib, and its jar, where generated/compiled for jsp 
>> 1.1, you get a "cannot be applied error" since the class hierarchy for 
>> the tags themselves changed with jsp 2.0.
>>
>> Since Tomcat 5.5 has been out for a year, I can not be the first 
>> person to run into this, so what am I missing?
>>
>> Thanks,
>> - clark.,
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>> For additional commands, e-mail: user-help@struts.apache.org
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: Struts, JSP 2.0 and Jasper2 compiler error

Posted by Martin Gainty <mg...@hotmail.com>.

Clark-

The only way I know you can achieve 100% compatibility would be if
You recompile the entire struts package library with J2SE 5.0
which means compiling
TagLibs, JSP Pages and Servlet, external providers and jars (basically 
everything) with the 5.0 JDK to conform to the 2.0 JSP Servlet spec
Peronally I would feel more comfortable if the original authors did this but
I think this could also be a fun weekend project..

In any case let me know how you make out or if I can help out in any way,

Does anyone else have a solution for this??
Martin-
617-852-7822

----- Original Message ----- 
From: "Clark Wright" <cw...@liquidmachines.com>
To: "Martin Gainty" <mg...@hotmail.com>
Cc: "Struts Users Mailing List" <us...@struts.apache.org>
Sent: Tuesday, September 13, 2005 12:58 PM
Subject: Re: Struts, JSP 2.0 and Jasper2 compiler error


> At 11:10 AM 9/13/2005, Martin Gainty wrote:
>>Clark-
>>
>>Ant has not upgraded the JSPC task for the JSP Servlet 2.0 spec as of yet 
>>to quote
>>"There are known problems with Tomcat 5.x that won't get fixed in Ant, 
>>please use Tomcat's jspc task instead."
>
> Yup, been there, gotten it to work for a while now.
>
> The real issue seems to be backwards compatibility when generating the 
> java code for taglibs that are adhering to version 1.1 of the JSP spec 
> while using the Tomcat 5.5 version of JasperC, which implements the 2.0 
> spec.
>
> For instance,
> using JasperC from Tomcat 4.x (which also required the custom ant config), 
> the following class would be generated:
>
>   private boolean
> _jspx_meth_html_img_0(javax.servlet.jsp.tagext.Tag _jspx_th_html_link_0,
>  javax.servlet.jsp.PageContext pageContext)
>           throws Throwable
>
> Now, using the Tomcat 5.5 jasperC, you get this class:
>
> private boolean
> _jspx_meth_html_link_0 (javax.servlet.jsp.tagext.JspTag 
> _jspx_th_html_html_0,
> PageContext _jspx_page_context)
>           throws Throwable
>
> Now, same jsp, same taglib, same backing jar.  The only difference is that 
> the version of JasperC changed.
>
> The first example adheres to JSP 1.1, the second to JSP 2.0.
>
> But, since the taglib, and its jar, where generated/compiled for jsp 1.1, 
> you get a "cannot be applied error" since the class hierarchy for the tags 
> themselves changed with jsp 2.0.
>
> Since Tomcat 5.5 has been out for a year, I can not be the first person to 
> run into this, so what am I missing?
>
> Thanks,
> - clark.,
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: Struts, JSP 2.0 and Jasper2 compiler error

Posted by Clark Wright <cw...@liquidmachines.com>.

At 11:10 AM 9/13/2005, Martin Gainty wrote:
>Clark-
>
>Ant has not upgraded the JSPC task for the JSP Servlet 2.0 spec as of yet 
>to quote
>"There are known problems with Tomcat 5.x that won't get fixed in Ant, 
>please use Tomcat's jspc task instead."

Yup, been there, gotten it to work for a while now.

The real issue seems to be backwards compatibility when generating the java 
code for taglibs that are adhering to version 1.1 of the JSP spec while 
using the Tomcat 5.5 version of JasperC, which implements the 2.0 spec.

For instance,
using JasperC from Tomcat 4.x (which also required the custom ant config), 
the following class would be generated:

   private boolean
_jspx_meth_html_img_0(javax.servlet.jsp.tagext.Tag _jspx_th_html_link_0,
  javax.servlet.jsp.PageContext pageContext)
           throws Throwable

Now, using the Tomcat 5.5 jasperC, you get this class:

private boolean
_jspx_meth_html_link_0 (javax.servlet.jsp.tagext.JspTag _jspx_th_html_html_0,
PageContext _jspx_page_context)
           throws Throwable

Now, same jsp, same taglib, same backing jar.  The only difference is that 
the version of JasperC changed.

The first example adheres to JSP 1.1, the second to JSP 2.0.

But, since the taglib, and its jar, where generated/compiled for jsp 1.1, 
you get a "cannot be applied error" since the class hierarchy for the tags 
themselves changed with jsp 2.0.

Since Tomcat 5.5 has been out for a year, I can not be the first person to 
run into this, so what am I missing?

Thanks,
- clark., 

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: Struts, JSP 2.0 and Jasper2 compiler error

Posted by Martin Gainty <mg...@hotmail.com>.

Clark-

Ant has not upgraded the JSPC task for the JSP Servlet 2.0 spec as of yet to 
quote
"There are known problems with Tomcat 5.x that won't get fixed in Ant, 
please use Tomcat's jspc task instead."

The latest version of Tomcat 5.x supports JSP Servlet 2.0 via the Jasper2 
task from Tomcat
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/jasper-howto.html#Web%20Application%20Compilation

if you are implementing your webapp with JBoss 2.4 on Tomcat 5.x
http://www.cowsultants.com/phpBB/posting.php?mode=topicreview&t=699&sid=2947bd47cbfdb129abe867ec8bbb9e44

HTH,
Martin-
617-852-7822

----- Original Message ----- 
From: "Clark Wright" <cw...@liquidmachines.com>
To: "Struts Users Mailing List" <us...@struts.apache.org>
Sent: Tuesday, September 13, 2005 9:35 AM
Subject: Struts, JSP 2.0 and Jasper2 compiler error


>
> I am running into a class hierarchy mismatch with taglibs and jasper2 out 
> of tomcat 5.5 and precompiling jsp pages built with the struts taglibs.
>
> I have:
> Jboss AS 4.0.2
> Tomcat 5.5 (bundled)
> Struts 1.2.4
>
> The error I am getting at compile time is:
>
> [javac] 
> F:\Sandboxes\Projects\rainier-1\cudgel\tmp\jsp-java\com\lqmi\admin\contact_jsp.java:119:
> 
> _jspx_meth_html_link_0(javax.servlet.jsp.tagext.JspTag,javax.servlet.jsp.PageContext)
> in com.lqmi.admin.contact_jsp
> cannot be applied to 
> (org.apache.struts.taglib.html.HtmlTag,javax.servlet.jsp.PageContext)
>
> The issue is that JBoss AS 4/Tomcat 5.5 is conforming to JSP 2.0.
> Struts confirms to JSP 1.x.
>
> In 2.0, a new base interface is defined (JspTag) for all tag classes, and 
> that is causing the compile error.
>
> Has anyone run into this, and if so, what is the work around?
>
> Thank you.
>
> - clark.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Struts, JSP 2.0 and Jasper2 compiler error

Posted by Clark Wright <cw...@liquidmachines.com>.

I am running into a class hierarchy mismatch with taglibs and jasper2 out 
of tomcat 5.5 and precompiling jsp pages built with the struts taglibs.

I have:
Jboss AS 4.0.2
Tomcat 5.5 (bundled)
Struts 1.2.4

The error I am getting at compile time is:

[javac] 
F:\Sandboxes\Projects\rainier-1\cudgel\tmp\jsp-java\com\lqmi\admin\contact_jsp.java:119:
  _jspx_meth_html_link_0(javax.servlet.jsp.tagext.JspTag,javax.servlet.jsp.PageContext) 

in com.lqmi.admin.contact_jsp
cannot be applied to 
(org.apache.struts.taglib.html.HtmlTag,javax.servlet.jsp.PageContext)

The issue is that JBoss AS 4/Tomcat 5.5 is conforming to JSP 2.0.
Struts confirms to JSP 1.x.

In 2.0, a new base interface is defined (JspTag) for all tag classes, and 
that is causing the compile error.

Has anyone run into this, and if so, what is the work around?

Thank you.

- clark. 


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

validate() finally called !!!!!!!

Posted by Jay Sheth <sh...@gmail.com>.

Hi,
Thanks for all the help. Any1 wont believe what a silly mistake. I
forgot to add the <html:errors /> tag in the jsp page.

I found out by when reading doc for the addErrors().

Thanks once again.

Jay

On 8/10/05, GRamani@intellicare.com <GR...@intellicare.com> wrote:
> Gareth Evans <ga...@msoft.co.uk> wrote on 08/10/2005 10:28:31 AM:
> 
> > You could manually set the errors in the page within your action
> > with the method
> >
> > addErrors( request , form.update(mapping,request) );
> >
> > the addErrors method is already defined in the class Action.
> 
> It is saveErrors(request,..etc. isn't it?
> Also, I think you're supposed to ActionMessages instead of ActionErrors..
> 
> Geeta
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: Re: Re: validate() not called haunts

Posted by Kjersti Berg <kj...@gmail.com>.

On 11/08/05, GRamani@intellicare.com <GR...@intellicare.com> wrote:
> Re. the "Spam" thing, i really do apologize. I totally understand because
> it probably bugs me more than it bugs anybody else. We are supposed to use
> Lotus notes for mail in our company and I absolutely *hate* it. This
> "spam" thing is just one more annoying "feature". I guess I can look into
> it, but I have a feeling I'll get nowhere.. Only thing I can do is
> remember to manually remove it from the subject every time I write, or
> just use another mail client. But that's another can of worms...
> 

You have my sympathies. I'm also stuck with Lotus Notes at work. I
solved it by getting a gmail account for mailing lists.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: Re: Re: validate() not called haunts

Posted by GR...@intellicare.com.

That was a good link - thanks! 

Re. the "Spam" thing, i really do apologize. I totally understand because 
it probably bugs me more than it bugs anybody else. We are supposed to use 
Lotus notes for mail in our company and I absolutely *hate* it. This 
"spam" thing is just one more annoying "feature". I guess I can look into 
it, but I have a feeling I'll get nowhere.. Only thing I can do is 
remember to manually remove it from the subject every time I write, or 
just use another mail client. But that's another can of worms... 

Sorry about the rant, but it's a sore point with me. I'll look into it 
tomorrow..

Geeta

Jeff Beal <jb...@gmail.com> wrote on 08/10/2005 04:04:45 PM:

> addErrors() is a new method in 1.2.7.  addErrors() and addMessages()
> are both valid, and both accept ActionMessages as arguments.  For more
> on the difference between ActionErrors and ActionMessages, see
> http://wiki.apache.org/struts/ActionErrorsAndActionMessages.  Also,
> please get rid of the 'Re: {Spam?}' in your subject lines.  It's
> annoying in general, but also causes GMail to think you are starting a
> new "Conversation".  I imagine that other mail readers have similar
> issues.
> 
> -- Jeff
> 
> On 8/10/05, GRamani@intellicare.com <GR...@intellicare.com> wrote:
> > Gareth Evans <ga...@msoft.co.uk> wrote on 08/10/2005 10:28:31 
AM:
> > 
> > > You could manually set the errors in the page within your action
> > > with the method
> > >
> > > addErrors( request , form.update(mapping,request) );
> > >
> > > the addErrors method is already defined in the class Action.
> > 
> > It is saveErrors(request,..etc. isn't it?
> > Also, I think you're supposed to ActionMessages instead of 
ActionErrors..
> > 
> > Geeta
> > 
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

> 
> CONFIDENTIALITY NOTICE:This email is intended solely for the person 
> or entity to which it is addressed and may contain confidential 
> and/or protected health information.  Any duplication, 
> dissemination, action taken in reliance upon, or other use of this 
> information by persons or entities other than the intended recipient
> is prohibited and may violate applicable laws.  If this email has 
> been received in error, please notify the sender and delete the 
> information from your system.  The views expressed in this email are
> those of the sender and may not necessarily represent the views of 
> IntelliCare.

Re: {Spam?} Re: validate() not called haunts

Posted by Jeff Beal <jb...@gmail.com>.

addErrors() is a new method in 1.2.7.  addErrors() and addMessages()
are both valid, and both accept ActionMessages as arguments.  For more
on the difference between ActionErrors and ActionMessages, see
http://wiki.apache.org/struts/ActionErrorsAndActionMessages.  Also,
please get rid of the 'Re: {Spam?}' in your subject lines.  It's
annoying in general, but also causes GMail to think you are starting a
new "Conversation".  I imagine that other mail readers have similar
issues.

-- Jeff

On 8/10/05, GRamani@intellicare.com <GR...@intellicare.com> wrote:
> Gareth Evans <ga...@msoft.co.uk> wrote on 08/10/2005 10:28:31 AM:
> 
> > You could manually set the errors in the page within your action
> > with the method
> >
> > addErrors( request , form.update(mapping,request) );
> >
> > the addErrors method is already defined in the class Action.
> 
> It is saveErrors(request,..etc. isn't it?
> Also, I think you're supposed to ActionMessages instead of ActionErrors..
> 
> Geeta
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: {Spam?} Re: validate() not called haunts

Posted by GR...@intellicare.com.

Gareth Evans <ga...@msoft.co.uk> wrote on 08/10/2005 10:28:31 AM:

> You could manually set the errors in the page within your action 
> with the method
> 
> addErrors( request , form.update(mapping,request) );
> 
> the addErrors method is already defined in the class Action.

It is saveErrors(request,..etc. isn't it?
Also, I think you're supposed to ActionMessages instead of ActionErrors..

Geeta

Re: validate() not called haunts

Posted by Gareth Evans <ga...@msoft.co.uk>.

You could manually set the errors in the page within your action with the method

addErrors( request , form.update(mapping,request) );

the addErrors method is already defined in the class Action.

Jay Sheth wrote:

> Hi,
> Thanks for all the help. Now i have got the debugging working. But
> still the problem remains, validate() not being called. I tried all
> combinations...I made a simple action and form without any business
> logic etc...but i dont understand why validate method is being called
> in only a single form and not being called for any other forms.
> 
> Most weird error. 
> 
> Even if I call validate from the corresponding action, it does not get
> called. However if I rename the validate method by another method e..g
> update then I can call the update method from action.
> 
> Is there a way that the action errors created can be shown as error by
> jsp page ?
> 
> Heres the code ; 
> **action
> form.update(mapping,request); // form.validate() doesnt get called so i renamed
>                                                 to update()
> 
> **form
> public ActionErrors update(ActionMapping mapping, ServletRequest request) {
>      super.validate(mapping,servlet);
>     errors = new ActionErrors();
> if (nullOrBlank(m_location)) {							errors.add("Location",new
> ActionError("errors.location.required"));
> 			}
>     return new ActionErrors();
> } 
> 
> So basically the action class can get the errors, but how should i
> display that errors on jsp (This is all because validate() not being
> called).
> 
> Jay
> 
> On 8/9/05, GRamani@intellicare.com <GR...@intellicare.com> wrote:
> 
>>oh ok I see where you are coming from.. I didn't know about this remote
>>debugging thing so it's good info..:) However, I didn't think the original
>>poster had this situation at all.. or maybe i grossly
>>misunderstood...(been known to happen..;))
>>
>>
>>
>>
>>Ed Griebel <ed...@gmail.com>
>>08/09/2005 01:43 PM
>>Please respond to
>>"Struts Users Mailing List" <us...@struts.apache.org>
>>
>>
>>To
>>Struts Users Mailing List <us...@struts.apache.org>
>>cc
>>
>>Subject
>>{Spam?} Re: {Spam?} Re: {Spam?} Re: {Spam?} Re: {Spam?} validate() not
>>called
>>
>>
>>
>>
>>
>>
>>No, not at all, it doesn't matter where tomcat is started from. As
>>long as tomcat was started with JDWP debugging, you can connect up
>>with any recent java debugger. Your tomcat can be in China and your
>>debugging session in NYC, it just doesn't matter, and it certainly
>>doesn't have to be in the same JVM.
>>
>>Try googling for JDWP and/or JPDA, or see
>>http://java.sun.com/products/jpda/ or
>>http://jakarta.apache.org/tomcat/faq/development.html
>>
>>-ed
>>
>>On 8/9/05, GRamani@intellicare.com <GR...@intellicare.com> wrote:
>>
>>>Well, not only that, if you want eclipse to play nice with tomcat (and
>>>have eclipse obey break points and what not), then you in fact start
>>>tomcat from within eclipse, right? I have been doing this for a while
>>
>>now
>>
>>>so I don't see what the problem could be..?
>>>
>>>Would something like this link help:
>>>
>>
>>http://plato.acadiau.ca/courses/comp/dsilver/2513/EclipseAndTomcatTutorial/
>>
>>
>>>Geeta
>>>
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>>For additional commands, e-mail: user-help@struts.apache.org
>>
>>
>>--
>>This message has been scanned for viruses and
>>dangerous content by MailScanner, and is
>>believed to be clean.
>>
>>
>>
>>CONFIDENTIALITY NOTICE:This email is intended solely for the person or
>>entity to which it is addressed and may contain confidential and/or
>>protected health information.  Any duplication, dissemination, action
>>taken in reliance upon, or other use of this information by persons or
>>entities other than the intended recipient is prohibited and may violate
>>applicable laws.  If this email has been received in error, please notify
>>the sender and delete the information from your system.  The views
>>expressed in this email are those of the sender and may not necessarily
>>represent the views of IntelliCare.
>>
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 

-- 
Gareth Evans

MSoft eSolutions Limited
Technology Centre
Inward Way
Rossmore Business Park
Ellesmere Port
Cheshire
CH65 3EN

-- 
Tel:    +44 (0)870 0100 704
Fax:    +44 (0)870 9010 705
E-Mail: gareth@msoft.co.uk
Web:    www.msoft.co.uk

----------------------------------------------
Terms:
Please note that any prices quoted within this e-mail are subject to VAT.
All program details and code described in this e-mail are subject to
copyright © of MSoft eSolutions Limited and remain the intellectual
property of MSoft eSolutions Limited.
Any proposal or pricing information contained within this e-mail are
subject to MSoft eSolutions' Terms and Conditions
----------------------------------------------
Disclaimer:
This message is intended only for use of the addressee. If this message
was sent to you in error, please notify the sender and delete this
message. MSoft eSolutions Limited cannot accept responsibility for viruses,
so please scan attachments. Views expressed in this message do not
necessarily reflect those of MSoft eSolutions Limited who will not
necessarily be bound by its contents.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org