Re: one more prepopulate question
Perhaps populating at least 2 forms on the same page could be an example for the struts distribution (or maybe in the FAQ). Given that I will be setting up my two forms soon, perhaps I can do a short writeup on it after I collect the information, but given my short experience with struts, maybe this would be better addressed by a more veteraned user. I just see this whole multiple-form prepopulate question cropping up time and again on this list if we don't have something in the FAQ about it. Dan -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Daniel Allen, [EMAIL PROTECTED] http://www.mojavelinux.com/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - When you're raised by the Jesuits, you become either obedient or impertinent -- Jack McCoy, Law and Order - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[OT], Please Help.
i know that this is off topic , but would like your advice in the same, i am generating a table from values in the database . we have a ro code for which land options are to be generated. for a ro code the land options could range from 1-12 (i.e A, B,C , D and so on) , this is not fixed, am attaching the format in which the table is to displayed. could you please suggest a way out of this. (See attached file: sample.htm) any suggessions will be welcomed , regards, amit malhotra - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts Sub-modules
ta for the zip james ive unzipped it and added the lib directory however when i come to run it and click on the link to go to mod1 it errors with HTTP Status 400 - Invalid path /Index was requested type Status report message Invalid path /Index was requested description The request sent by the client was syntactically incorrect (Invalid path /Index was requested). On Friday 28 February 2003 4:18 pm, James Mitchell wrote: Ok, here ya go. Only thing missing is the lib directory. -- James Mitchell Web Developer/Struts Evangelist http://jakarta.apache.org/struts/ -Original Message- From: Stephen Smithstone [mailto:[EMAIL PROTECTED] Sent: Friday, February 28, 2003 10:53 AM To: Struts Users Mailing List Subject: Re: Struts Sub-modules James Mitchell or anyone ive just uploaded an example i made to www.skullboxhouse.co.uk/downloads/smt.war it would be great if u can download and run and help me solve the problem :-) Ta Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Validator] Conditional Validations
Hi Amit,
I haven't tried this, so it is total speculation, but I wonder if you
could put a hidden field on the form, and use just one
'requiredif' rule for it, only requiring it when the others
were NULL.
Since the resource message would be:
errors.required={0} is a required field.
you'd need a message resource that was something like
At least one of name, date, foo, bar, grill
for the message presented to the user to make sense.
(Then, of course, you'd still have the separate
type-specific depends for each of the individual fields).
If that didn;t work, I suppose you could use the 'requiredif' rule
for each of the 5-6 input fields, requiring a given field if ALL the
others were NULL. If you did that for all 6, it should generate the
correct check, but you'd be glad you didn't have 10-12 search
fields when you got through setting it up that way :)
HTH,
-jeff
On Friday, February 28, 2003, at 03:55 AM, Amit Keshav Kulkarni wrote:
Hi All,
I need to Validate the inputs on a Search Page
I have 5-6 input fields for Seach Criteria
I have to validate that at least one field has to be not null
and if some value is entered in a field, it should be validated..
Say, numeric or alphanumeric fields.
How can I set up my validation.xml in such a case?
Thanks and regards,
Amit
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: one more prepopulate question
On Sat, Mar 01,'03 (02:23 AM GMT-0600), Dan wrote: ore veteraned user. I just see this whole multiple-form prepopulate question cropping up time and again on this list if we don't have something in the FAQ about it. Coupled with the tidbits someone posted from Craig's snipet what would be wrong with this approach: You have an Action class that you want to use to prepopulate three Action Forms and then forward to a JSP page and set up three separate forms. So you might have a mapping... action path=/setupMultipleForms type=foo.bar.SetUpFormsAction name=form1 scope=request validate=false forward name=continue path=/severalFormsOnAPage.jsp/ /action So now in the SetUpFormsAction you can easily put Form1 into scope by: Form1 form1 = (Form1)form; form1.setFoo(hello); request.setAttribute(mapping.getAttribute(), form1 ); But now for another ActionForm (Form2) to put into scope you could do: But probably better would be to use what I think I gleamed Craig mention: (assuming form2 is tied to /foo in mapping): ApplicationConfig appConfig = (ApplicationConfig) request.getAttribute(Globals.APPLICATION_KEY); ActionConfig actionConfig = appConfig.findActionConfig(/foo); String name = actionConfig.getName(); // Form bean name Form2 form2 = new Form2(); form2.setFooBar(BLA); request.setAttribute( name, form2 ); for form3... actionConfig = appConfig.findActionConfig(/fooForm3Action); name = actionConfig.getName(); // Form bean name Form3 form3 = new Form3(); form3.setBoo(hello world); request.setAttribute( name, form3 ); Then on the JSP page you just use the html:form tags as you normally would if there was just one form on the page. -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Question using transactional tokens
Dear struts people !
What am i doing wrong - must be some sort of double submit, but why ?
Let me sketch my problem to you - using for the first time transactional
tokens, i have the following setup :
1. in my jsp :
html:form action=/parameter
.
html:link page='' onclick=submitSelect('save') transaction='true'
styleClass=button
bean:message key=label.buttons.WF.submit/
/html:link
...
/html:form
2. where submitSelect is a javascript function:
function submitSelect(method) {
document.forms[0].method.value = method;
document.forms[0].submit();
}
3. and in my action class subclassing dispatch action there is method
save().
Following strange behaviour (to me) occurs :
1.) having beakpoint inside save(...) method in action class shows it
hit the right method and is working.
2.) but after return mapping.findForward(WF_PARAMETER_CHOOSE); from
my action, struts complains with status 404 :
message Request[/parameter] does not contain handler parameter
named method
description The request sent by the client was syntactically
incorrect (Request[/parameter] does not contain handler parameter named
method).
3.)it worked before deciding to use transactional tokens with :
html:link
href=javascript:submitSelect('save') styleClass=button
bean:message
key=label.buttons.WF.save/
/html:link
So your help is appreciated, thanks Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Multi select boxes
Hello all, I am currently working on a web app, where unfortunately, the client wants to use several multi select boxes. The form works as follows: 1) User decides to create a new group by accessing the form. 2) User searches for items via the search button. Search results are populated in the available select boxes. 3) User selects the items to assign and places in them in the selected box. 4) User repeates steps 2-3 until satisfied. 5) User saves by submitting and info is saved into db. 6) User can also edit the group info, where the selected items are retrieved from db and placed in the selected box (use logic:iterate to iterate the the ArrayList of Transfer objects). I have already developed the app and it works. Every time the user invokes the search or save submit action, I use Javascript to select the items and have the appropriate Select[] get/set methods. The only visual drawback is seeing the items highlighted when submitting the information upon a search or save. Is there a way to submit the form without having to show the items highlighted? Thanks for you help. Sincerely, Rich Dedeyan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[struts-layout] struts 1.1 b3
Hi does anyone have user correcty struts-layout (latest one) and the b3 ? When I add these lib and compile my project I got many deprecated errors. Thanks for your help. /** * Alexandre Jaquet */ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Form bean pre-population and validation
What is the elegant way of specifying default values for a form and not validate the form until the user has had a chance to input data? I have some fields in the form that needs to shown as nulls but the user cannot leave these fields blank and I have other fields that have default values. __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [struts-layout] struts 1.1 b3
Hi does anyone have use correcty struts-layout (latest one) and the b3 ? When I add these lib and compile my project I got many deprecated errors. Thanks for your help. /** * Alexandre Jaquet */ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Form bean pre-population and validation
I'd say a DynaValidatorForm is pretty elegant. Use the initial=your value for each form-property that has a default. -jeff On Saturday, March 1, 2003, at 11:26 AM, harish krishnaswamy wrote: What is the elegant way of specifying default values for a form and not validate the form until the user has had a chance to input data? I have some fields in the form that needs to shown as nulls but the user cannot leave these fields blank and I have other fields that have default values. __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Question using transactional tokens
I had a problem where if i declared a hidden field like:
html:hidden name=foo ...
and in java script i write a function
function tryit ( foo ) {
document.forms[0].foo.value = foo;
the value of foo would be an object that represents the
hidden field foo, not the value passed in in the argument
I fixed it by rewriting the function
function tryit ( bar ) {
document.forms[0].foo.value = bar;
im not sure - but this could be a problem for you.
-Original Message-
From: Jörg Maurer [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 01, 2003 8:21 AM
To: Struts Users Mailing List (E-mail)
Subject: Question using transactional tokens
Dear struts people !
What am i doing wrong - must be some sort of double submit, but why ?
Let me sketch my problem to you - using for the first time transactional
tokens, i have the following setup :
1. in my jsp :
html:form action=/parameter
.
html:link page='' onclick=submitSelect('save') transaction='true'
styleClass=button
bean:message key=label.buttons.WF.submit/
/html:link
...
/html:form
2. where submitSelect is a javascript function:
function submitSelect(method) {
document.forms[0].method.value = method;
document.forms[0].submit();
}
3. and in my action class subclassing dispatch action there is method
save().
Following strange behaviour (to me) occurs :
1.) having beakpoint inside save(...) method in action class shows it
hit the right method and is working.
2.) but after return mapping.findForward(WF_PARAMETER_CHOOSE); from
my action, struts complains with status 404 :
message Request[/parameter] does not contain handler parameter
named method
description The request sent by the client was syntactically
incorrect (Request[/parameter] does not contain handler parameter named
method).
3.)it worked before deciding to use transactional tokens with :
html:link
href=javascript:submitSelect('save') styleClass=button
bean:message
key=label.buttons.WF.save/
/html:link
So your help is appreciated, thanks Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts-el NOT working with Struts 1.1 RC1 Release
Craig, I guess I made other assumptions about the process. I thought that there were people on the list that volunteered to test just like you volunteer to write code. I would have been more apt to run my project on the nightly builds had I knew you were counting on us. I appreciate you clearing that up for me. I am relatively new to struts - have been here about three weeks. Thanks and I do appreciate all you do and am willing to contribute where I can. Ray Madigan -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] Sent: Friday, February 28, 2003 7:59 PM To: Struts Users Mailing List Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release On Fri, 28 Feb 2003, Hohlen, John wrote: Date: Fri, 28 Feb 2003 19:54:45 -0600 From: Hohlen, John [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Subject: RE: Struts-el NOT working with Struts 1.1 RC1 Release David Karr said he fixed this problem in last night's Struts-EL build. This means in order to pick up the fix, you have to migrate from the RC1 version of Struts to a nightly build version (due to other changes made to the regular Struts tags since the RC1 release -- otherwise you'll have incompatability issues -- I think). Many projects are reluctant to use nightly builds (for obvious reasons). Therefore, this hurts the overall likelihood of other projects incorporating Struts-EL. I would think that the Struts-EL team would want to provide a version of their project that's compatible with RC1. This will allow for wider user base which would be good for the overall project. Doesn't this make sense or am I missing something? The other side of that coin is also important -- if nobody tests the nightly builds, then we developers never find out about the bugs until after a release build is published, which harms the reputation for quality that we would all prefer. I get somewhat depressed about the for obvious reasons reason that people give for not at least *trying* your app against the nightly builds. After all, the day that Struts 1.1 final is released, guess what -- it will have exactly the same classes as that night's nightly build :-). There is nothing magical about the label final release that makes it any better (or worse) other than marginally more testing. Going into production is a different story -- but the harsh reality is the only reason RC1 was called RC1 instead of beta 4 was to get at least a *few* more people to test it. Fortunately for the quality of the final release, that goal was achieved. Unfortunately, many of the bugs could have been found and fixed quite a while ago, with more testing. Thanks, JOHN Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ValidatorUtil.getActionError (RE: [Validator] Anyone have a fields match rule?)
I'm trying to do this as well, but that code doesn't compile any more. I could override form.validate() and check there, but it would be nice to keep everything clean. I'm using the Validator nightly out of commons, in the download process for the rest of the Struts tree. My problem seems to be that ValidatorUtil.getActionError() does not seem to exist, and if it was deprecated, I'm having problems finding the method that it was deprecated in favor of. Anyone have info they could share? thanks! Brian -Original Message- From: Giri Alwar [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 21, 2003 3:15 PM To: Struts Users Mailing List Subject: Re: [Validator] Anyone have a fields match rule? Check out the Comparing Two Fields section in the link below: http://jakarta.apache.org/struts/userGuide/dev_validator.html - Original Message - From: James Higginbotham [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 21, 2003 2:57 PM Subject: [Validator] Anyone have a fields match rule? Hi, Anyone out there written the validator and Javascript for validating 2 fields, say a password and confirm password, to ensure that they match? I am using the Dec 12th CVS of Struts and related validation jars and haven't found anything yet. CVS diffs show that nothing new has been added to validation-rules.xml yet. Seems like a nice rule to have by default in Struts, since we all do lots of Create a New User pages that often require a confirm of a password or email. I'm looking for both server and client validators, but will take what I can get ;) Thanks, James --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.435 / Virus Database: 244 - Release Date: 12/31/2002 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Whoops! RE: ValidatorUtil.getActionError (RE: [Validator] Anyone have a fields match rule?)
Whoops, found it!
For those of you looking, the validateTwoFields example code should be:
public static boolean validateTwoFields(
Object bean,
ValidatorAction va,
Field field,
ActionErrors errors,
HttpServletRequest request,
ServletContext application) {
String value = ValidatorUtil.getValueAsString(
bean,
field.getProperty());
String sProperty2 = field.getVarValue(secondProperty);
String value2 = ValidatorUtil.getValueAsString(
bean,
sProperty2);
if (!GenericValidator.isBlankOrNull(value)) {
try {
if (!value.equals(value2)) {
errors.add(field.getKey(),
Resources.getActionError(request, va, field));
return false;
}
} catch (Exception e) {
errors.add(field.getKey(),
Resources.getActionError(request, va, field));
return false;
}
}
return true;
}
}
-Original Message-
From: Brian Topping
Sent: Saturday, March 01, 2003 5:09 PM
To: Struts Users Mailing List
Subject: ValidatorUtil.getActionError (RE: [Validator] Anyone have a
fields match rule?)
I'm trying to do this as well, but that code doesn't compile any more. I
could override form.validate() and check there, but it would be nice to keep
everything clean. I'm using the Validator nightly out of commons, in the
download process for the rest of the Struts tree.
My problem seems to be that ValidatorUtil.getActionError() does not seem to
exist, and if it was deprecated, I'm having problems finding the method that
it was deprecated in favor of.
Anyone have info they could share? thanks!
Brian
-Original Message-
From: Giri Alwar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 21, 2003 3:15 PM
To: Struts Users Mailing List
Subject: Re: [Validator] Anyone have a fields match rule?
Check out the Comparing Two Fields section in the link below:
http://jakarta.apache.org/struts/userGuide/dev_validator.html
- Original Message -
From: James Higginbotham [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 21, 2003 2:57 PM
Subject: [Validator] Anyone have a fields match rule?
Hi,
Anyone out there written the validator and Javascript for validating 2
fields, say a password and confirm password, to ensure that they match?
I am using the Dec 12th CVS of Struts and related validation jars and
haven't found anything yet. CVS diffs show that nothing new has been
added to validation-rules.xml yet. Seems like a nice rule to have by
default in Struts, since we all do lots of Create a New User pages that
often require a confirm of a password or email. I'm looking for both
server and client validators, but will take what I can get ;)
Thanks,
James
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.435 / Virus Database: 244 - Release Date: 12/31/2002
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
processPreprocess hook
Hi, We have been overriding the processPreprocess method in ActionServlet of Struts 1.0 in an extended class to do some custom processing like session expiry handling etc. I noticed that this method is not present in the ActionServlet of Struts 1.1. So now I guess we can't migrate from Struts 1.0 to Struts 1.1. unless we make some changes in our extended class. Am i right or am I missing something here? Thanks, Gaurav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: processPreprocess hook
That method has been moved to the RequestProcessor class. David From: [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: processPreprocess hook Date: Sat, 1 Mar 2003 21:07:58 -0600 Hi, We have been overriding the processPreprocess method in ActionServlet of Struts 1.0 in an extended class to do some custom processing like session expiry handling etc. I noticed that this method is not present in the ActionServlet of Struts 1.1. So now I guess we can't migrate from Struts 1.0 to Struts 1.1. unless we make some changes in our extended class. Am i right or am I missing something here? Thanks, Gaurav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts-el NOT working with Struts 1.1 RC1 Release
On Fri, Feb 28,'03 (07:59 PM GMT-0800), Craig wrote: I get somewhat depressed about the for obvious reasons reason that people give for not at least *trying* your app against the nightly builds. After all, the day that Struts 1.1 final is released, guess what -- it will have exactly the same classes as that night's nightly build :-). There is nothing magical about the label final release that makes it any better (or worse) other than marginally more testing. Thanks for the reminder Craig. I'm going to start making sure to use the latest nightly builds in all of my development. I think I'll also send out a reminder on the list occasionally about this since it is important these nightly builds get tested since the entire Struts community as a whole suffers when there are bugs in final releases. -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [update] nested tags...
Sri, Don't know how the other one clapped out, but i made another one, tested out okay (JDK Jar tool). Try this one (link for convenience)... http://www.keyboardmonkey.com/downloads/km-nested-v2.03.jar not lazy I understand that people aren't lazy, just pragmatic. :) /not lazy Arron. Can you please re-build the jar? Tomcat 4.1.18 throws a java.util.zip.ZipException: invalid END header (bad central directory offset) Error. Methinks, well I'll just unzip it and put it in WEB-INF/classes; unfortunately, Winzip too has problems with it. not.lazy I don't want to change too many things at once and so am trying to stick with Struts 1.1b3 than move to the nightly. /not.lazy Sri - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
just curious, shouldn't maybe message=true use error=true instead?
Nothing major here, I'm just curious why the messages:present tag uses message=true in order to check if ActionMessages are present. I was thinking since ActionMessages is the base class of ActionErrors that it might make more sense if messages:present would show all messages, or at least ActionMessages by default, and that maybe adding something like error=true would look for ActionErrors (or maybe having errorsOnly=true would show just ActionErrors). I could of course be totally missing the way the messages:present tag is working since it's way past my bed time:) -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
