[ http://issues.apache.org/jira/browse/JELLY-192?page=comments#action_57438 ] Marc DeXeT commented on JELLY-192: ----------------------------------
The main difficulty is about jexl expression parsing. If you create expression with a factory, you have just access to text or sub expression list (if it's a CompositeExpression). So if you want to identify reference, you have to parsed back the expression text, as Expression doesn't let this kind of information to be known. > Graphical jelly script viewer > ----------------------------- > > Key: JELLY-192 > URL: http://issues.apache.org/jira/browse/JELLY-192 > Project: jelly > Type: New Feature > Reporter: Marc DeXeT > Priority: Minor > > Jelly script can be very hard to read if there several instructions. > I think it would be interesting for users as developers to get a graphical > user-friendly viewer. > Each jelly script is an XML well formed document, and each tag is associated > to library. > They are designed to get parsed and associated to any alternativ > representation. > It's just an idea now. > But what about creating an functional representation of each tag : > We have already library associated to namespace. > Usually 'var' attribute value is an object reference. > With instropection tools we can get setters and object type. > So we have almost everything to establish control graph, reference usage and > type maps. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
