[jira] Commented: (JELLY-112) Create Script from SAX events

[co...@jakarta.apache.org]

The following comment has been added to this issue:

     Author: Hans Gilde
    Created: Thu, 26 Aug 2004 6:54 PM
       Body:
So... if you want this functionality, why not just sublass JellyContext and do whatever you want?

I'm not in favor of making JellyContext less encapsulated, just so that people don't have to subclass it. It's so easy to subclass that I must vote a -1 on "fixing" this issue.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/JELLY-112?page=comments#action_37506

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JELLY-112

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JELLY-112
    Summary: Create Script from SAX events
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: jelly
 Components: 
             core / taglib.core

   Assignee: 
   Reporter: Michael Lipp

    Created: Fri, 25 Jun 2004 7:37 AM
    Updated: Thu, 26 Aug 2004 6:54 PM
Environment: All

Description:
Currently, there is no possibility to feed a SAX event stream through Jelly. There is no ContentHandler for the Jelly script.

Currently we use a work-around: we define a class derived from XMLParser, for the sole purpose of being able to invoke configure() :-(
Then we use this parser as ContentHandler and send all SAX events to it.

>From the parser we get the script (getScript()) and invoke compile() and run(...). While all this works, it is not really nice.

The funny thing is that XMLParser uses SAX events internally. I'd propose to make getXMLParser() public and to automatically invoke compile() when the end document event is received (removing the invocations from JellyContext).

 - Michael



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org