::::::::::::::::::::::::::
Home
Home Page
Method of generation of a code
Displays
Result of binding of the data
Systems of patterns of pages
Data acquisition without use XML
Data acquisition without use XML
Use JSON on the party of the client
Improved online shop
Review Ajax
Departure XMLHttpRequest
Processing of search servleta
The search processing with help JavaScript
Problems of use Ajax
As it was more than once spoken, organization W3C is engaged mainly in development and creation of b
OASIS
Hands off PHP!
Automatic redirect (Auto Redirect) on PHP
Breaking of passwords becomes more accessible
Web2.0 Layout
Links
:::::::::::::::::::::::::

topic
 

Displays


Structures which create displays, are switched on in such programs, as Castor and Apache Commons Betwixt. Display usually more floppy and superficial decision, than generation of a code. First, you write a code of yours JavaBeans how you usually wrote, including any types and any methods convenient for you. Second, in execution time you cause the router based on introspection of structure, and he creates the XML-document based on types, names and values of components of your classes. Having defined{determined} display of files in your classes, you can copy strategy of linkage which is established by default, and to declare the router according to that as your classes will be submitted in XML.


This method is the optimum compromise between scale and flexibility. You can write your Java-classes how you want, and the router will rescue you from job with XML. However, in spite of the fact that it is easy to write definition of files of display and enough confidently to correlate, rules of display can vary only according to standard behaviour of linkage, and some degree of connectivity of structure of your objects and their XML-performances will always remain. Finally you, should be, can find the compromise or in your Java-performances, or in your XML-format of job of a method of display.