Datasources where deprecated in last versions of Struts 1.2, so I suppose they disappeared in 1.3 (as I've seen in the API). They did this because you can configure a datasource with nearly (maybe all) webservers. If you use Tomcat 5, take a look in the documentation, where they explain how to...
I've followed your instructions and I get the file .class file generated in the same dir as the source without problems... I normally use and IDE, that's why I had to try it. Are you sure the .class file is not generated and you don't get any error?
Have you looked at Sun's documentation? They have great tutorials for newbies if you go to Java home page (java.sun.com) and it's on the right pannel, under resources->Tutorials.
By the way, I've found (inside these tutorials) something it will help you (I hope...) Learning the Java Language
the depends tag declares which validations you will do in that field. If In validator-rules.xml there isn't any rule named extends, then it's incorrect code...
How do you access the JSP in the browser? In order to an Action to execute, the link must point to the Action defined in struts-config.xml (you can use <html:link action="blabla.do">link text</html:link>). If that's not your case, please provide more data.
If you're accessing the messages from an Action using different locales, you must pass the user locale (with Action.getLocale or something like this) to the getMessage. If you don't do it, it takes always the system locale.
It seems it doesn't recognize the bean tag... Have you included it in this JSP before using @taglib tag? I've been working for long with Struts and nowadays I still forget it some times... :)
First of all, in this line if(court1List != null){
request.setAttribute("SportsHall", court1List);
} you're putting the result in an attribute in the request, so if this line <%
java.util.ArrayList court1List=(java.util.ArrayList)
session.getAttribute("sports_hall_1");
%> is to look for that...
Well, it's not strange that this happens... In this line of code in your action request.setAttribute("courses", courses); you're putting the object in the request, not the session.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.