One: When the Modal box is opened Showmodual () method does not provide the open form of the title of the parameter, title to be written in the Open modal box of the JSP page
and put the <TITLE></TITLE> label at the top of the <HEAD></HEAD>.
Analysis:
The 1 Mode window is very special, so it is sensitive to the position of title.
2 title tags should have been placed at the top of the <HEAD></HEAD>, but ordinary
The window allows or ignores the wrong title not on top
Two: In the development of the discovery of a problem, as follows:
Cannot find bean under name Org.apache.struts.taglib.html.BEAN
The information found on the network is as follows:
1. You tried to use the child elements of a form outside of the form tag of struts. Use the HTML tags of struts later, and so on
2. Inadvertently used without a body tag, such as a Web server resolution as a tag without a body, then the tag used is considered to be outside of this tag
3. Also, when using Taglib to introduce an HTML tag library, the prefix value you use is not HTML
4. The property must match an attribute in the Formbean that corresponds to the action to be submitted (must have a formbean)
5. To use labels, the outer layer must use a label and cannot use HTML
Three. Questions about Java Reference jars:
1. In the case of multiple engineering development, if you want to refer to another project's class, you can put another project into a Jar pack in a publishing service such as the JBoss release of the directory (such as Jboss-4.0.5.ga\server\default\lib), and in the engineering code to lead another project So that the code does not report an error that cannot find the class.
2. At the same time, note that if you do not make the project into a jar package, you can also put the project published directory in the JBoss release of the directory, in the project to introduce the project jar bag on it.
3. When the project and JBoss's lib directory has a duplicate jar package, running the application will be an error, the prompt class can not be found, so, two directories can only exist one jar package.
Four: When you send an AJAX request, if the amount of data in a form is very large, then if you use method: "Get", the request will not be sent to the action end, there is no return results, this time need to use method: "Get" instead of method: "POST" will not be.
Five:
Would like to write a JSP in a public project, this JSP has called the project in the servlet code, this time to other projects are referencing this JSP, but there is a problem: other projects in the public works in the JSP introduced the class. For now, my practice is to put this introduction class in every project. In fact, the best way to do this is to create a jar of this common class, put it under each project, or put it in the server's published directory. This is different from JS, the public JS can be placed in a project, other projects to reference it is good.