[ 
http://issues.apache.org/jira/browse/XALANJ-2100?page=comments#action_62814 ]
     
Henry Zongaro commented on XALANJ-2100:
---------------------------------------

That's a problem with the way the Xalan-J Interpretive processor breaks an 
XPath expression into its component tokens.  It replaces any prefix that 
appears in the expression with the corresponding URI, causing itself later 
problems if that URI begins with something that looks like some other token - / 
in this case.

> Unrecognised Namespace beginning with '//'
> ------------------------------------------
>
>          Key: XALANJ-2100
>          URL: http://issues.apache.org/jira/browse/XALANJ-2100
>      Project: XalanJ2
>         Type: Bug
>   Components: Xalan
>     Versions: 2.6
>     Reporter: Jan Rihak
>     Priority: Minor

>
> The namespace declaration in the following line seems to pose problems to 
> xalan:
> <XMI xmi.version = '1.1' xmlns:UML = '//org.omg/UML/1.3'>
> running xalan on a XMI file generated by the modeling tool borland together 
> 6.2, the xslt processor output the following error message: 
> SystemId Unknown; Line #135; Column #43; XSLT Error 
> (javax.xml.transform.TransformerConfigurationException): 
> javax.xml.transform.TransformerException: 
> javax.xml.transform.TransformerException: A location step was expected 
> following the '/' or '//' token.
> where line #135 is: 
> <xsl:for-each select="//UML:Association">
> I posted the issue on [EMAIL PROTECTED] , tried out the XSL transformation 
> file with the Saxon XSLT processor and experienced no problems.

-- 
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]

Reply via email to