can you supply
1)all jsps
2)struts-default.xml specifically everything between
<interceptor-stack name="paramsPrepareParamsStack">
</interceptor-stack>
and everything between
<interceptors>
</interceptors>
<default-interceptor-ref name="?"/>
<default-class-ref class="?" />
3)relevant action classes
4)relevant pojos such as backing beans etc.
thanks,
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Mon, 3 May 2010 13:14:30 -0500
> Subject: Re: Validate without submit?
> From: ozu.na...@gmail.com
> To: d...@newfield.org
> CC: user@struts.apache.org; cimba...@cimballi.net
>
> More info... This is getting more confusing to me by the minute.
>
> If I use these interceptors as such in my action:
>
> <interceptor-ref name="params"/>
> <interceptor-ref name="actionMappingParams"/>
> <interceptor-ref name="staticParams"/>
>
> It appears that the parameters are not being parsed correctly. I
> don't know that for sure, but I suspect that is the case because all
> validation fails and all messages are returned. The success method of
> the ajax call is never fired, instead the completed method is fired
> with the parseerrror as the textstatus.
>
> If I use the basicStack and include the "paramsPrepareParamsStack",
> the success method of the ajax is called, and no errors are returned
> -- even though there should be an error for a missing field. If I
> then supply the value to the missing field and try to revalidate, the
> ajax call never fires success, instead it fires complete with a
> parseerror. In both cases with the paramsPrepareParamsStack, no
> validation errors are being returned correctly.
>
> I'm quite confused with this and would appreciate any advice or help
> anyone has to offer.
>
>
> On Mon, May 3, 2010 at 12:08 PM, Ozu Natsu <ozu.na...@gmail.com> wrote:
> > The params interceptor is in the stack, I had included the basicStack
> > -- but also expressly included it as well to see if there was a
> > difference in behavior. In FF I can see the query string of the form
> > elements for the request, so I am sure that they are being passed.
> > The paramter string looks like I would expect:
> > object.attribute=value&object.attribute2=value....
> >
> > Where is the best way to verify that the action is getting and parsing
> > the parameters in the action?
> >
> > On Sat, May 1, 2010 at 8:45 PM, Dale Newfield <d...@newfield.org> wrote:
> >> On 5/1/10 11:58 AM, Ozu Natsu wrote:
> >>>
> >>> I'm also puzzled why the JSONValidationInterceptor
> >>> validationAware.hasErrors() is always returning the entire validation
> >>> rule set.
> >>
> >> Is params in the interceptor stack?
> >> Are the arguments being passed? (Look at the request from the client side
> >> with firefox.) Are the arguments arriving at the server? Are they being
> >> processed correctly?
> >>
> >> -Dale
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your
inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2
