Ud Naik

Is it not possible to have a boolean variable in the custom validator class and have your validation method for the other fields check that before performing the validation?

If this is not your requirement, maybe I am not able to understand exactly.

So you want the following things to happen (?)
1) If data entered in 5th field ONLY that field to be validated OR
2) If data entered in any one of first 4 fields ALL 4 fields have to be validated.

Write 2 custom validator functions, one for each of the 2 cases above. You can define these validator functions in validation-rules.xml and validator.xml.

Hope that helps.

looks like i will never get any help on this forum ..ummm

Dom Lassy has already replied to your question. If you want pertinent help, please state problems/requirements clearly.

You can give more 'interactive' messages through javascript. Dont use the struts validations, write your own javascript error handlers for those fields and use the onKeyPress() event (or something similar; I cant remember exactly) for your validation.

Wont a simpler way would be to just use the available 'mask' validator (though ultimately that's what you are doing here), like so:

field property="zip" depends="required,mask"> <msg name="required" key="userRegistration.zip"/> <msg name="zip" key="userRegistration.zip"/> <var> <var-name>mask</var-name> <var-value>^[0-9]{5}$</var-value> </var> </field>

I havent tried the above though. If you do, let us know how it worked out.

Dont know if this fits your requirement, but it's worth a try

1) Write a class that does the validation for you:

package package.blahblah; import necessary stuff; public class [B]ArrayFieldsValidator[/B] { public static boolean [B]validateArrayFields[/B](Object bean, ValidatorAction va, Field field, ActionMessages errors, Validator validator,HttpServletRequest request) { String[] firstValue = ValidatorUtils.getValueAsString(bean, field.getProperty()); String[] secondValue = ValidatorUtils.getValueAsString(bean, field.getVarValue("[B]compareWith[/B]"));; /* Do the restof the validation here */ }


2) Add a new validator to validation-rules.xml with the above class as the validator
<validator name="[B]arrayFieldsValidate[/B]" classname="package.blahblah.[B]ArrayFieldsValidator[/B]" method="[B]validateArrayFields[/B]" methodParams="java.lang.Object, org.apache.commons.validator.ValidatorAction, org.apache.commons.validator.Field, org.apache.struts.action.ActionMessages, org.apache.commons.validator.Validator, javax.servlet.http.HttpServletRequest" depends="" msg="[B]errors.arrayFieldsNotMatch[/B]"/>

3) Use this validator in validation.xml
<form name="myArrayForm"> <field property="arrayField" depends="required,[B]arrayFieldsValidate[/B]"> <arg0 key="yourChoice"/> <arg1 key="oneMoreChoice"/> <var> <var-name>[B]compareWith[/B]</var-name> <var-value>anotherArrayField</var-value> </var> </field>


Hope this has been clear. Good luck.

For the 2006-2007 year, the open category 65K H1B's quota was filled late May. For the special higher education category 20k quota, it was filled sometime in July (if memory serves me right).

The quotas I mentioned are for accepting applications. Once the quota is filled, no more applications are entertained. For 2006-2007, I personally know people who filed in May and their application was accepted.

Originally posted by Rahul Bhattacharjee

I would have tried for an MS from US of A ,rahter then H1B and H1B would have automatically followed my way.

At best, that's misleading advice. There's a lot of factors that influence H1B approval and a Masters degree does not automatically guarantee a H1B visa. Besides, getting a Masters from a good school is in itself a big venture, in terms of time, effort and expenses.

Is the string only for display or do you need the value later for processing?

One way could be to extend the reset() method of the ActionForm, change the value of that string; in your case, truncate the string to whatever length you want and append dots to it.

Maybe the html:link tag is what you are looking for.

Same kind of an issue I had with "Enemy of the State". Guy puts cameras in the smoke detector and next thing you know, the images are being seen on the TV (and not just in the same house). That's some nice wireless capabilities the television has. I wonder where I can get such a TV so I can wirelessly watch...er, never mind.

Mark Spritzler

What? You have the exact same issue on every device that is out there from Game Boys to DS Lite to PSP to IPods to everything that has a display that is portable. That is why you get one of those screen covers, so that they don't scratch.

Will that cover not affect the user interface? (and I was talking about smudging, not scratching, but that's another thing to watch out for). I'm not much of a gamer so I dont know anything about the GameBoys and PSPs. I do own an iPod (and like it) but sure dont touch the screen for using it.

Personally, I think it wont be as popular as the iPod. Screen smudging probably will be a factor. Battery life could be another; playing music, watching movies and making calls, how many of those could we do before the battery runs low?

I'm just guessing here since I am not an auto insurance expert.

If the car was stationary, I would say comprehensive. If you hit the cart while driving your vehicle, it's probably collision. Neither if the cost to fix the scratch is less than your deductible.

Adding to the list of gripes about Hollywood movie computer technology:

1) The movie-picture-zoom technology: A shot of the bad guy(s) is taken from what looks like far away. The guy then clicks and the main bad guy's face comes into focus, zooming in, without any loss of detail whatsoever.

2) Over simplified hacking commands: The 'hacker' uses commands that have names literally match their actions e.g. 'Send Blocking Signal' or 'Send Spike'. What's up with that?

I am trying to test some webservices by writing Junit tests for them. These tests run through Eclipse, but when run executed using maven, they through a SOAPFaultException, the root cause of which java.lang.AssertionError.

This AssertionError is probably being thrown on the WebLogic 9.1 side, but then I should be seeing the same problem when running through Eclipse too. Has anyone come across this?