Hi Mukul,
Sorry if I hadnt been clear enough, but I wasnt proposing this to
abide by SAX architecture .
This is just another way of doing things that SAX does in its own way.
cheers!
Menon
On 8/10/05, Mukul Gandhi <gandhi(_dot_)mukul(_at_)gmail(_dot_)com> wrote:
On 8/10/05, Ramkumar Menon <ramkumar(_dot_)menon(_at_)gmail(_dot_)com> wrote:
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.]
Hi Menon,
SAX does'nt have this architecture.
Regards,
Mukul
rgds,
Menon
--
Shift to the left, shift to the right!
Pop up, push down, byte, byte, byte!
-Ramkumar Menon
A typical Macroprocessor
--~------------------------------------------------------------------
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>
--~--
--
Shift to the left, shift to the right!
Pop up, push down, byte, byte, byte!
-Ramkumar Menon
A typical Macroprocessor
--~------------------------------------------------------------------
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>
--~--