Lacks of start of own realization

It is interesting, that the code in listing 7 shows one of the main lacks of serialization JavaBeans manually in XML. Present, as if this document was used for performance to the buyer of history Order. In this case you, most likely, do not want, that on the screen there was a full description of each thing past{last} turns or that his{its} full name was spoken the user. But if at the application was ProductSearch a class which returns results of search as list Item beans, it would be rather useful, that descriptions were included in Item, a representing level of a drain at present, could be the helpful information for a conclusion to the screen in the list " Search of a product " (Product Search). However, this field could be then serializovano from other circuit of objects including Item, despite of irrelevance of a level of a drain at present for history Order of the buyer.

From the point of view of development, it is the classical problem of model of the data connected to generation of performance. Everyone bean can serializovat` itself(himself) only in one way, and the universal method designates, that interactions in Ajax will end with data exchange which is not necessary for them, complicating job of a code of the client at localization of the information which it will request from the document, and also increases in volume of working off and time of analysis XML by the machine of the client. Other consequence{investigation} of this connection is that XML cannot be created irrespective of Java-classes. For example, to make changes in the document of the circuit of the buyer, the group of several Java-classes which then should be modified and perekompilirovat` could be demanded.

I rassmotrju these details hardly later, and now let's look at the decision of expansion of blocks of start of own serializations: XML-structure of linkage.

XML-structure of linkage

Lately a little Java interfaces (API) have been developed for simplification of process of linkage of XML-documents and performances of circuits of Java-objects. In most cases routing XML both is provided, and not provided: in both cases bilaterial conversion of Java-circuits of objects in performance XML are carried out. These structures conclude in themselves all job on support XML, designating, that now it is necessary to write a code of the application only for usual Java-objects. Most likely, they also intend for maintenance of useful applied functions, such as validirovanie. In general these structures contain two various approaches: generation of a code and display "XML-object". I shall explain both these of the approach.