[
https://issues.apache.org/jira/browse/XALANJ-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437112#comment-15437112
]
Michael Glavassevich commented on XALANJ-2603:
----------------------------------------------
This is written more like a question than a bug report. I would suggest asking
your question on the mailing list. If you suspect that Xalan has a defect,
please provide sufficient information (for example a test case) that a
developer could attempt to reproduce it.
> Xalan 2.7.1
> -----------
>
> Key: XALANJ-2603
> URL: https://issues.apache.org/jira/browse/XALANJ-2603
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: Xalan
> Affects Versions: 2.7.1
> Reporter: HITESH MEHRA
> Assignee: Steven J. Hathaway
>
> Hi Team,
> We were using the Xalan 2.7.1 in our Java application which was deployed in
> Solaris with JDK 1.7, 32 bit. The XSL were also compiled in JDK 1.7, 32 bit.
> We are parsing our XML and using the node() function in some conditions like
> below:
> [descendant::node() != '']
> But we recently moved our application to CentOS with JDK 1.8 64 bit. The XSL
> were compiled in JDK 1.8, 64 bit. After this migration/upgrade in production
> , we are now having issues with the above condition (yes, we missed to test
> this corner scenario in QA environment) . The above condition is always
> returning false.
> And due to this, our XML is not getting properly parsed.
> Do we know if this feature is OS/JDK dependent.
> Any pointers will be extremely helpful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
