Skip parsing of property for json plugin

[Dimitris Mouchritsas]

Hi all,

I'm using struts2-core 2.3.16.3 along with struts2-json-plugin and I 
have the following problem:


I have an entity bean, say Event which has the following 3 properties:
id, dateCreated and data

data is already a json string saved in the database.
e.g.:
Event data: 
{"id":1003,"username":"admin3","email":"t...@example.com","lastname":"Lastname","f_user_type":1,"firstname":"Firstname","password":"fdhfdfh"}


Now in my struts2 action I have a List gridModel which I feed to 
a jquery grid.


My problem is that the data property string is being escaped, e.g:

{"JSON":"success","actionErrors":[],"actionMessages":[],"someId":"3","destination":null,"errorMessages":[],"errors":{},"fieldErrors":{},"gridModel":[{"data":"{\"id\":1,\"username\":\"admin\",\"email\":\"ad...@example.com\",\"lastname\":\"Lastname\",\"f_user_type\":1,\"firstname\":\"Firstname\",\"password\":\"***\"}","dateCreated":"2014-05-30T18:15:10","id":46009},{"data":"{\"id\":1002,\"username\":\"admin2\",\"email\":\"t...@example.com\",\"lastname\":\"Lastname\",\"f_user_type\":1,\"firstname\":\"Firstname\",\"password\":\"\"}","dateCreated":"2014-05-30T18:15:10","id":46010},{"data":"{\"id\":1004,\"username\":\"admin4\",\"email\":\"t...@example.com\",\"lastname\":\"Lastname\",\"f_user_type\":1,\"


Is there any way to avoid this escaping? What alternatives do I have?
One idea is to just return a tiles plugin and create the json string by 
hand in a jsp.


From what I've seen @JSON annotation does not have the option to skip 
escaping. This might be nice.


Regards
Dimitris

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

Problem with validation

[Dimitris Mouchritsas]

Hi all,
in my project we're using Struts 1.3.8. I have a case of editing an
organisation. Because we have two types of organisations, I'm using a
BaseOrganisationForm (extends ValidatorForm) as a form bean where I've
put the validation as xdoclet tags. Then I inherit this class from
OrganisationForm.

OrganisationForm has the fields for both types of organisations and
depending on the organisation type I do custom validation of the fields
in the validate method.

In the action classes I have a PrepareEditOrganisationAction and
EditOrganisationAction with the later doing the real work of course. In
the Prepare action I set some request attributes so I can enable or
disable some form elements in the GUI. Thus I've also set the xdoclet
tag for my edit action as follows:

 * @struts.action name="organisationForm" path="/editOrganisation"
 *validate="true" input="/prepareEditOrganisation.do"
 *cancellable="true"

So that upon an error, I first go to the prepare action again and set
the request attributes. However the problem is that if I put an invalid
organisation name which is declared in BaseOrganisationForm everything
seems to work ok. The form fields that should remain enabled are enabled
(from the request attributes). If I put an invalid field at one of the
OrganisationForm fields it seems to go to the prepare action but calls
the input of that, without really setting the request attributes, thus
the fields are shown disabled.

Any ideas how I can fix this? Sorry for the long post.
Regards
Dimitris



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

Problem with validation

[Dimitris Mouchritsas]

Hi all,
in my project we're using Struts 1.3.8. I have a case of editing an
organisation. Because we have two types of organisations, I'm using a
BaseOrganisationForm (extends ValidatorForm) as a form bean where I've
put the validation as xdoclet tags. Then I inherit this class from
OrganisationForm.

OrganisationForm has the fields for both types of organisations and
depending on the organisation type I do custom validation of the fields
in the validate method.

In the action classes I have a PrepareEditOrganisationAction and
EditOrganisationAction with the later doing the real work of course. In
the Prepare action I set some request attributes so I can enable or
disable some form elements in the GUI. Thus I've also set the xdoclet
tag for my edit action as follows:

 * @struts.action name="organisationForm" path="/editOrganisation"
 *validate="true" input="/prepareEditOrganisation.do"
 *cancellable="true"

So that upon an error, I first go to the prepare action again and set
the request attributes. However the problem is that if I put an invalid
organisation name which is declared in BaseOrganisationForm everything
seems to work ok. The form fields that should remain enabled are enabled
(from the request attributes). If I put an invalid field at one of the
OrganisationForm fields it seems to go to the prepare action but calls
the input of that, without really setting the request attributes, thus
the fields are shown disabled.

Any ideas how I can fix this? Sorry for the long post.
Regards
Dimitris


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

Problem with validation

[Dimitris Mouchritsas]

Hi all,
in my project we're using Struts 1.3.8. I have a case of editing an 
organisation. Because we have two types of organisations, I'm using a 
BaseOrganisationForm (extends ValidatorForm) as a form bean where I've 
put the validation as xdoclet tags. Then I inherit this class from 
OrganisationForm.


OrganisationForm has the fields for both types of organisations and 
depending on the organisation type I do custom validation of the fields 
in the validate method.


In the action classes I have a PrepareEditOrganisationAction and 
EditOrganisationAction with the later doing the real work of course. In 
the Prepare action I set some request attributes so I can enable or 
disable some form elements in the GUI. Thus I've also set the xdoclet 
tag for my edit action as follows:


 * @struts.action name="organisationForm" path="/editOrganisation"
 *validate="true" input="/prepareEditOrganisation.do"
 *cancellable="true"

So that upon an error, I first go to the prepare action again and set 
the request attributes. However the problem is that if I put an invalid 
organisation name which is declared in BaseOrganisationForm everything 
seems to work ok. The form fields that should remain enabled are enabled 
(from the request attributes). If I put an invalid field at one of the 
OrganisationForm fields it seems to go to the prepare action but calls 
the input of that, without really setting the request attributes, thus 
the fields are shown disabled.


Any ideas how I can fix this? Sorry for the long post.
Regards
Dimitris

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

Re: Different error messages for client and server side validation

[Dimitris Mouchritsas]

Kawczynski, David wrote:

Your Action classes can add ActionMessages for a specific property, not
just GLOBAL_MESSAGES.  
Then, display GLOBAL_MESSAGES at the top of the page, and field-specific

ones relative to the field.
(this will work in 1.3.8)

See
http://struts.apache.org/1.2.7/api/org/apache/struts/action/ActionMessag
es.html 


Specifically:
add(java.lang.String, org.apache.struts.action.ActionMessage)
get(java.lang.String)

-Original Message-
From: Dimitris Mouchritsas [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2008 11:23 AM

To: Struts Users Mailing List
Subject: Re: Different error messages for client and server side
validation

Dimitris Mouchritsas wrote:
  

Hi all,
we are using  elements in our error messages to allow the user to 
go to the form field when the error message shows up.
Obviously this messes up the client side javascript popup message 
which shows like: Username is missing.
Is there a way to use a different error message or should we abandon 
the idea of client side validation?


Regards
Dimitris Mouchritsas

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



BTW Struts v1.3.8

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Notice:  This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or
MSD and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and
then delete it from your system.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  

Can you please elaborate with a small example? I don't get it.
Thanks

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Different error messages for client and server side validation

[Dimitris Mouchritsas]

Dimitris Mouchritsas wrote:

Hi all,
we are using  elements in our error messages to allow the user to 
go to the form field when the error message shows up.
Obviously this messes up the client side javascript popup message 
which shows like: Username is missing.
Is there a way to use a different error message or should we abandon 
the idea of client side validation?


Regards
Dimitris Mouchritsas

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


BTW Struts v1.3.8

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Different error messages for client and server side validation

[Dimitris Mouchritsas]

Hi all,
we are using  elements in our error messages to allow the user to go 
to the form field when the error message shows up.
Obviously this messes up the client side javascript popup message which 
shows like: Username is missing.
Is there a way to use a different error message or should we abandon the 
idea of client side validation?


Regards
Dimitris Mouchritsas

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Define specific .properties file for

[Dimitris Mouchritsas]

Hi all,
we have a disclaimer page in our application (using struts 1.3.8) and we 
want to display a possibly rather large legal text.
So the thought is to create a disclaimer.properties file with only one 
key in it and for that specific jsp have a
 to load this disclaimer.properties and get the key from 
there.

Is this possible?

Thanks
Dimitris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Disable validation when clicking back

[Dimitris Mouchritsas]

Hi all,

I have a multi-page form bean for a 2 step registration form. In the 
second page I have a back button like this:


   
   
   

and in my action I check if it was pressed similarly to the cancel button:

   if (isCancelled(request)) {
   targetUrl = "goHome";
   } else if (isBack(request)) {
   targetUrl = "goRegisterOrg";
   } else {
.
   private boolean isBack(HttpServletRequest request) {
   String back = (String)request.getParameter(EDConstants.BACK_BUTTON);

   return (back != null);
   }


My problem is, how do I disable validator from checking the form? 
Currently the user presses the back
button and validation errors show up, so he has to enter some valid 
values to go back. Any ideas?


Thanks
Dimitris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Form Submission of arrays

[Dimitris Mouchritsas]

Hi all,
we've got a form where there's a table. In each row there's a hidden 
field for the id, a comment (text field) and a select box.
What's the best way to submit this form? Create a form bean that will 
accept arrays as input?

e.g.

public class CommentForm {
 private String[] orgIds;
 private String[] comments;
 private String[] types;

 ...getters/setters

 public String getRow(int num) {
   return orgIds[num] + "$" + comments[num] + "$" + types[num];
 }
}

Is the above class correct?
Does struts guarantee that the order in which the rows are declared is 
the same order in the array when the form bean is submitted?


Thanks
Dimitris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Javascript validation error

[Dimitris Mouchritsas]

Hi all,
I'm trying to use javascript validation with validator, as well as 
server side validation.
Server side validation works just great. But when I try to use client 
side validation I

get a validateRequired not found error.

This is my jsp:

   
   

and this is the result produced from the tags:

.


//

   var bCancel = false; 

   function validateLoginForm(form) { 
   if (bCancel) { 
   return true; 
   } else { 
   var formValidationResult; 
   formValidationResult = validateRequired(form); 
   return (formValidationResult == 1); 
   } 
   } 

   function LoginForm_required () { 
this.a0 = new Array("username", "Username is required.", new Function ("varName", " return this[varName];"));
this.a1 = new Array("password", "Password is required.", new Function ("varName", 
" return this[varName];"));
   } 


//]]>




...
Now I understand why the error happens, but where do I locate this 
validateRequired function? How do I include it in my jsp?

Thanks
Dimitris


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]