Application of XML in the development of BS architecture

Motivation:

1. JSP Construction page is too painful. Code embedded page causes the page to be bloated, logic complex, difficult to edit.

2. The interface between programmers and artists must be defined precisely. Complex nested output must construct a complex display class as an interface.

3. Debug JSP must wait until the end of the front-end program to see the effect.

3. Debugging JSP efficiency is very low, a little bit of modification will cause JSP recompile.

New XML Solution:

1. A servlet to do the unified management. Accept the URL request and map to the corresponding program bean.

2. The program bean produces only XML, which is unified by the servlet to convert the corresponding XSL to HTML.

Benefits:

1. JDK1.4 has its own XML APIs and XSLT, and supports the XSLT 1.0 standard. IE6 also supports the same standards.

2. Before the development of the first production interface with the demo XML, the programmer's output must conform to this format. The artist makes XSL from this format. Interface visualization, clearly defined.

3. As long as the interface XML is defined, there is little need for joint debugging on both sides. Using interface XML and IE6, the artist can see the effect directly.

4. Programmers just make sure that the output of the XML conforms to the interface, intuitive to do textual comparison.

5. A large number of reusable parts of the page can be easily abstracted and include/import in the XSL file. Highly reusable, standardized.

6. Write XSL can be a large number of template, structure clear, easy to modify, write pages into building blocks, no longer have the layer of JSP nesting.

7. For different terminal devices, you can customize different XSL, it is convenient to support the mobile phone, PDA

8. XML-enabled tools, such as sql2000, can be generated directly in the program without complex programming.