Q:	Q: OK, I’m thinking that the Container code is doing some kind of Integer.parseInt(“343”), so wouldn’t you get a NumberFormatException if the user doesn’t type in something that can be parsed to an int? Like, what if the user types “three” in the employee ID field?
A:	A: Good catch. Yes, something will definitely go wrong if the request parameter for the empID property can’t be parsed into an int. You need to validate the contents of that field, to make sure it contains only numeric characters. You could send the form data to a servlet first, instead of sending it straight to the JSP. But if you’re committed to going from the form straight to the JSP, and you don’t want scripting, just use JavaScript in the HTML form to check the field before sending the request. If you’re not familiar with JavaScript (which of course has virtually NOTHING to do with Java), it’s a simple scripting language that’s processed on the client side. In other words, by the browser. A quick Google search on “JavaScript validate input field” should turn up some scripts you can use to stop users from entering, say, anything but numbers into an input field.
Q:	Q: If a bean property doesn’t have to be a String or a primitive, then HOW can you set the property without scripting? The value attribute of the tag is always a String, right?
A:	A: It is possible (but potentially a *lot* of extra work) to create a special class, called a custom property editor, that supports the bean. It takes your String value and figures out how to parse that into something that can be used to set a more complex type. This is part of the JavaBeans spec, though, not the JSP spec. Also, if the value attribute in the <jsp:setProperty> tag is an expression rather than a String literal, then IF that expression evaluates to an object that’s compatible with bean property type, then it will probably work. If you pass in an expression that evaluates to a Dog, for example, the Person bean’s setDog(Dog) method will be called. But think about it—this means the Dog object must already exist. Anyway, you’re way better off NOT trying to construct new things in your JSP! Trying to get away with constructing and setting even marginally complex data types is gonna be tough without scripting. (And none of that is on the exam).