logo       
Google Custom Search

Related Msgs: audio.musicbrai...    enbd.general/20...    ietf.idr/2002-0...    java.ant-contri...    gnu.make.genera...    qplus.devel/200...    video.freevo.cv...    os.netbsd.ports...    yellowdog.gener...    xfree86.cvs/200...    search.nutch.us...    freedesktop.xse...    programming.swi...    capabilities.ge...    telephony.pbx.a...    mail.sylpheed.c...    db.firebase.por...    boot-loaders.u-...    recreation.radi...    netbsd.bugs/200...    web.zope.plone....    user-groups.lin...   

[jira] Commented: (XERCESJ-1247) Incorrect location information on SAX when: msg#00000

Subject: [jira] Commented: (XERCESJ-1247) Incorrect location information on SAX when using XInclude
    [ 
https://issues.apache.org/jira/browse/XERCESJ-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492846
 ] 

George Cristian Bina commented on XERCESJ-1247:
-----------------------------------------------

Thanks Michael! 
It works ok now.

Regards,
George

> Incorrect location information on SAX when using XInclude
> ---------------------------------------------------------
>
>                 Key: XERCESJ-1247
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1247
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: XInclude 1.0
>    Affects Versions: 2.9.0
>            Reporter: George Cristian Bina
>         Assigned To: Michael Glavassevich
>
> Hi,
> If there is a file that includes another one with xi:include Xerces will 
> report to a content handler events from the included file (startElement, 
> characters, endElement, etc.). However the locator that is set in the content 
> handler does does not report the locations in the included file, instead it 
> remains at the xi:include location in the master file.
> Looking inside the XIncludeHandler class I see that there is some code that 
> tries to deal with this:
>         // we do this to ensure that the proper location is reported in errors
>         // otherwise, the locator from the root document would always be used
>         fErrorReporter.setDocumentLocator(locator);
> but the locator is updated only on the error reporter.
> The problem is that if one registers a content handler there is no 
> possibility to know the location of the notified SAX events.
> Thanks,
> George

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Try Searching:
servers, voip, java, networking, microsoft ...
<Prev in Thread] Current Thread [Next in Thread>