Subject Re: [Firebird-Architect] Re: Strategic Replacement for Services API
Author Jim Starkey
Roman Rokytskyy wrote:

>>It's called an XML parser, Roman. It parses XML. The idea of using
>>XML is so we don't have to create a parser for each new request type.
>Do you have a universal parser that takes XML on one side and returns
>my domain objects on the other? In general case this issue is not
>solved in Java, did you manage that in C++?
We have an XML parse that takes a text XML document and return a tree of
elements. After parsing, navigating the tree is trivial. In my admin
server, the infrastructure parses the XML request then dispatches off
the "operation" attribute of the top level request element. Each
operation is passed the parse tree to who what it wishes and returns a
response tree that is serialized into XML and sent to the front end.

Parsers don't create domain objects in any case. Parsers parse.
Semantics come later.


Jim Starkey
Netfrastructure, Inc.
978 526-1376