A method, apparatus, and computer instructions for a configurable JAVASERVER pages processing framework to process JAVASERVER pages (JSP). A JSP document or page is translated into a document object model (DOM) object that encapsulates elements of the JSP. The syntax of the JSP is validated by a JSP translator with built-in classes and errors are returned if necessary. A JSP visitor configuration file, which defines user configured classes and sequence of execution, is used by the JSP translator to invoke methods of user-defined classes in the order specified by the user to process or visit elements of the DOM object. Result of user-defined class processing may be passed from one class to another within the set.

An invention is provided for incorporating web services into JSP tag libraries for use in JSP pages. As a result, web page authors can develop JSP pages, which utilize web services from WSDL enabled servers, without an in-depth knowledge of WSDL. In general, a web services based document is received, which defines a set of web service operations. Each web service operation is translated into a custom action, and the custom actions are grouped into a tag library. Generally, the web services based document can be a WSDL document, and the custom actions can be JSP custom actions. Also, the tag library can be a JSP custom tag library. Particular custom actions from the custom actions that are grouped in the JSP custom tag library can be incorporated in a JSP page. Once the JSP page is created, content for the JSP page can be obtained from a web service using the JSP custom tag library. The JSP page can then generate a document based on the content. The document can be an HTML document, an XML document, or any other type document as needed for the particular situation.

Under the present invention, computer program code is analyzed to determine whether messages are needed. The analysis is typically conducted based upon a stored resource such as policies, rules, etc., and certain characteristics of the computer program code such as flags and the like. In any event, sections of the computer program code are then uniquely formatted according to the types of messages that are needed. Thereafter, a quantity of each needed type of message is determined based on the uniquely formatted sections. These results can be displayed to a developer and optionally saved to a file.

Various embodiments of a system and method for generating software documentation are disclosed. A software documentation generator may input a variety of information sources. In one embodiment, these information sources may include various types of files such as application source code files, tag library files, tag library descriptors (TLD), library source code, web services description language (WSDL) files, configuration files, defect reports, and text files. The software documentation generator may analyze each source to determine its type and use this information to extract documentation data from the source according to the format of the data included in that source. The software documentation generator may reformat the documentation data extracted from each source into a uniform format and aggregate the uniformly formatted data into a uniformly formatted aggregate input document. The software documentation generator may transform this document into one or more sets of software documentation in a specified format.