[ http://issues.apache.org/jira/browse/XALANJ-2264?page=comments#action_12373106 ]
Brian Minchau commented on XALANJ-2264: --------------------------------------- Comments from JIRA bug Triage on Febrary 7, 2006: > Patch needs to be more robust to be taken into Xalan-J > Other parer options need to be considered, such as validating > This is the Process command. If someone really needs these APIs they can use JAXP APIs. Do we need to support every possibility through the Process command? > Entity resolver is the only real parser option that we handle with "Process" > This impacts the products APIs and documentation, so we are hesitant to do this. > Brian M. will look at existing parser options. > Supporting xi:include (and other factory features) on xalan Process > command-line > -------------------------------------------------------------------------------- > > Key: XALANJ-2264 > URL: http://issues.apache.org/jira/browse/XALANJ-2264 > Project: XalanJ2 > Type: New Feature > Components: Xalan-CmdLine > Versions: Latest Development Code > Environment: all > Reporter: Rudolf Weber > Attachments: xalan-xi.patch.txt > > The xi:include-awareness should be specifiable on the command-line. > The default is on, since I think in the normal case it is useful. > In the special case, the default has to be swiched off with -NIA. > (Of course, it may be good keep the current behavior on default. I think, > that the xi:include is not in wide use, so I want to risk to change the > default. ) > In our project we want to include declarations in a programming language > in the xslt-file, so the option -XSLIA. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
