Abhilash George

yes you need to have the client jar file for the created EJBs . At the same time you need to create the reference so as to create an alias so that you can use a local reference for the global jndi so that your code remains safe from changes in global jndi name

Another way of solving this is that you have a variable in your form which says what page nos it is . And when you submit the first page , using a hidden variable you set that variables value to 1 and 2 respectively .
And in the validation.xml you decide upon what validations are to be done for one form based on the page nos. That is if it is page 1 then these are required . I hope you get the idea

a) See the default scope of any formbean is session . So the contents of the form would be available in your session as long as you want them. This means that you could have two different forms for different jsp and in the end create a third formbean and fill it with data from the first two.
But as it is its not a good idea keeping the whole form in a session so you can keep the form in request , and on submit push those values into a Value object which has been kept in session and use it to populate the third page formbean

b) if the form is in request scope it will go anyways with a submit but if in session then you might need to call reset to clear things you want

a) See the default scope of any formbean is session . So the contents of the form would be available in your session as long as you want them. This means that you could have two different forms for different jsp and in the end create a third formbean and fill it with data from the first two.
But as it is its not a good idea keeping the whole form in a session so you can keep the form in request , and on submit push those values into a Value object which has been kept in session and use it to populate the third page formbean

b) if the form is in request scope it will go anyways with a submit but if in session then you mite need to call reset to clear things you want

The no collection found exception is coming since your jsp displays some
list or collection on the page and it is coming empty .
You need to ensure either one of the two
a)that the action which is forwarding to this page fills the collection field of the form associated with the jsp page
or
b) The jsp page should have a check for null condition of the collection
using <logic resent>.

yes it can be done ,
you need to ensure that for the onchange of the list call an action
by calling the javascript function.

regards

J2EE Level 1.2 includes a Servlet Specification level of 2.2 and a JSP Specification level of 1.1. Features such as Servlet Filters and Life Cycle Event Listeners cannot be be used if this level is chosen. Applications developed for this J2EE level 1.2 typically target a WAS version 4.x server.
In such cases you can add filters but they would only get execute after your ActionServlet

If you are using J2EE Level 1.3 includes a Servlet Specification level of 2.3 and a JSP Specification level of 1.2 then first filter and then ActionServlet get executed..


regards

Its not at all clear as to what you are trying to ask and your problem!

hey
try using <html:errors /> in your jsp page.
Whatever Actionerror objects that get created because of validation failure would get displayed here.

Well it seems that the scope of the form you are talking of ie the one associated with second page is session and thats why it is retaining across action calls.
The default scope of formbeans is session and not request .
let me know if this helps. If you want to look it in a different way , at the submit of first button you create an object of the formbean , (optional put values inside it) and then put that formbean object in the request.
regards

hi
just make sure that each time a file is selected you make a call to you action class and put this selected file into a hashmap of Formfiles. Anytime you want to check the attached files just iterate through this hashmap. I have implemented such a scenario let me know if you need more details

I believe that in any web application there always has to be first page which has to be a physical page . ie a jsp or html and it cannot be an action.

hi there
Yes your assumption regarding field names in request getting mapped to formbean property with the same name is correct . I used
<INPUT type="text" name="meter" value="caloriemeter" size="20"> in my jsp
with meter being a field in my form . I could check the value getting set in the setMeter(String mtr) method of my formbean. I am not sure about the JSTL part of your code. You can check the value that is coming into the set"Parametername" method in your form..