[ 
https://issues.apache.org/jira/browse/XALANJ-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mukul Gandhi resolved XALANJ-2767.
----------------------------------
    Resolution: Fixed

I'm resolving this jira issue as fixed. The implementation of this jira issue 
has been committed to xalan-j xsl3 dev repos branch.

> implementation of xml input document validation via xalan-j command-line 
> option, and access of schema types within xsl 3 transformation context
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: XALANJ-2767
>                 URL: https://issues.apache.org/jira/browse/XALANJ-2767
>             Project: XalanJ2
>          Issue Type: New Feature
>      Security Level: No security risk; visible to anyone(Ordinary problems in 
> Xalan projects.  Anybody can view the issue.) 
>          Components: Xalan-CmdLine, Xalan-interpretive
>            Reporter: Mukul Gandhi
>            Assignee: Mukul Gandhi
>            Priority: Major
>
> I think it'll be useful (as is also defined by XSLT 3 spec for schema-aware 
> XSL transformation), if we've Xalan-J command line option 
> (suggest name for this option is -VAL) to request validation of an XML input 
> document used for XSL transformation.
> If the user invokes a command-line Xalan-J XSL transformation with this 
> option, XML Schema validation will be done of an XML input document.
> The schema used for validation with this option, will be retrieved as 
> referred by XSLT xsl:import-schema instruction 
> (either xsl:import-schema's attribute schema-location, or literal schema 
> information available as child contents of xsl:import-schema element).
> If the schema validation passes when using this command-line option, the 
> schema's compiled representation as an XSModel object instance will be kept 
> active until the XSL transformation is complete. This stored schema XSModel 
> object instance shall be used for all XPath expression type checking.
> If the user invokes an XSL transformation not using this option, and the XSL 
> stylesheet refers to user-defined schema types (for e.g as values of various 
> "as" attributes), then schema types will still be available by using XML 
> Schema document information provided by an xsl:import-schema instruction.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org

Reply via email to