My opinions:
1. First of all, one minor correction: SAX is not a W3C standard.
2. I don't think this is a practical idea, because as someone has
mentioned, it is going to involve too much of reflection overheads and
messy code generations. But, even if we do that, what are we going to
achieve by that? If your idea is to generate strongly typed application
specific Xml datastructure for an Xml instance, you can take a look at JAXB.
Thanks,
Prakash
Ramkumar Menon wrote:
Hi All,
W3C defines specific methods witihn a SA ContentHandler like
startElement(), endElement() etc... that would be called back when
elements are encountered within the XML Document.
User overrides these methods to define the logic within each of these
callback methods.
As an alternative, what if the User defines explicit methods like
public void startEmployee() [simplified here- ignoting namespace mappings]
public void endEmployee()
public void onEmptyAdddress()
public void onAttr_Employee_Name() [this is just illustrative of the
attributes scenario.]
Advantage
-----------------
Cleaner separation of logic.
<<add here>>
Disadvantages
---------------------
No Clear contract.
<<add here>>
This is only an ilustrative subset of the functionalty.
What do you folks think of this ? Is this a better alternative ?
rgds,
Menon
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--