DO NOT REPLY [Bug 16794] New: - assertion failed if we set apostrophy as xslt parameter

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16794>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16794

assertion failed if we set apostrophy as xslt parameter

           Summary: assertion failed if we set apostrophy as xslt parameter
           Product: XalanC
           Version: 1.4.x
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Other
         Component: XalanC
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: ohtani@ariel-networks.com


Hi,

If we set only one apostrophy value as xslt parameter using 
setStylesheetParam, the assertion is failed.
Do we have some workaround to set apostrophy as xslt paramter.


the sample code is...


XSLTInputSource xmlId = new XSLTInputSource( "test.xml");
XSLTInputSource xslId = new XSLTInputSource( "test.xsl");
XSLTResultTarget resultTarget = new XSLTResultTarget( out);

XSLTProcessor processor = XSLTProcessorFactory.getProcessor();
processor.setStylesheetParam( "p", "'''");
processor.process( xmlId, xslId, resultTarget);


The stacktrace is 
_NMSG_WRITE(int 10) line 221
abort() line 44 + 7 bytes
_assert(void * 0x0086a4e0, void * 0x0086a494, unsigned int 523) line 267
substring(const XalanDOMString & {...}, XalanDOMString & {...}, unsigned int 
2, unsigned int 4) line 523 + 34 bytes
XPathProcessorImpl::tokenize(const XalanDOMString & {...}) line 288 + 24 bytes
XPathProcessorImpl::initXPath(XPath & {...}, const XalanDOMString & {...}, 
const PrefixResolver & {...}, const Locator * 0x00000000) line 131
XSLTEngineImpl::evalXPathStr(const XalanDOMString & {...}, XalanNode * 
0x01a33580, const PrefixResolver & {...}, XPathExecutionContext & {...}) line 
3056 + 48 bytes
StylesheetExecutionContextDefault::pushVariable(const XalanQName & {...}, 
const ElemTemplateElement * 0x00000000, const XalanDOMString & {...}, 
XalanNode * 0x01a33580, const PrefixResolver & {...}) line 672 + 35 bytes
Stylesheet::pushTopLevelVariables(StylesheetExecutionContext & {...}, const 
std::vector<TopLevelArg,std::allocator<TopLevelArg> > & {...}) line 1281 + 88 
bytes
StylesheetExecutionContextDefault::pushTopLevelVariables(const 
std::vector<TopLevelArg,std::allocator<TopLevelArg> > & {...}) line 626
XSLTEngineImpl::resolveTopLevelParams(StylesheetExecutionContext & {...}) line 
3348 + 25 bytes
StylesheetExecutionContextDefault::resolveTopLevelParams() line 746 + 23 bytes
StylesheetExecutionContext::ResolveAndClearTopLevelParams::ResolveAndClearTopLe
velParams(StylesheetExecutionContext & {...}) line 798 + 20 bytes
StylesheetRoot::process(XalanNode * 0x01a33580, XSLTResultTarget & {...}, 
StylesheetExecutionContext & {...}) line 235 + 12 bytes
XSLTEngineImpl::process(const XSLTInputSource & {...}, XSLTResultTarget & 
{...}, StylesheetExecutionContext & {...}) line 443