Martin, Thanks for the information.
Posting an issue with JIRA XALANC will help us research and resolve a solution to this problem. I know that some exception handling has changed when I tried to use upgrade my custom XPath functions from V1.10 to V1.11. I have applied some code in my XPath sources to accommodate the change of exception handling and error reporting. I am not sure where your issue lies in the mix. It may be totally unrelated. If you post the Issue, it will give us a benchmark for doing the necessary research. You should not include the proprietary Usoft code. If the problem can be fixed without Usoft code dependencies, then a patch for distribution can be created. Any Usoft specific code would need to be contributed as required by the Apache Software Licensing. Sincerely, Steven J.Hathaway Xalan Documentation Project > Hi all, > > A while ago two of the other USoft developers here that sometimes work with Xalan found an issue with the SVN-version of Xalan as of 15 march 2011. > I've known about this and regularly apply their patch here, but there's a > problem. My colleagues' repro-path (when they have one) requires using USoft developer, > and I can't just hand those out to anyone on the 'net. So... We believe > the current SVN code has an issue, but we can't prove it outside of USoft. > > I still feel kind of new to this whole open source thing, so I'll just ask: how is this kind of thing usually handled? > > FYI, the code we patch is lines 44-48 of > src/xalanc/PlatformSupport/XSLException.cpp (the first constructor). The > (incorrect, we think) code is: > > m_uri( > XalanLocator::getSystemId( > theLocator, > &s_dummy), > theManager), > > > which we change to: > m_uri(XalanLocator::getSystemId(theLocator, &s_dummy) ? > XalanLocator::getSystemId(theLocator, &s_dummy) : &s_dummy, > theManager), > > > If you diff the 1.10 version with the 1.11 SVN version, the > according-to-us-correct-code was present in 1.10, but got removed for whatever reason. > AFAIR there were perhaps also other repeats of the same kind of > error-handling... > > > Should I just go ahead and add a ticket to Xalan-c's issue-tracker? > > > Sincerely, > Martin > > > > The information contained in this communication is intended solely for the > use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in > error, please notify us immediately by forwarding this email to > [email protected] and then delete it from your system. > > USoft is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
