[ 
https://issues.apache.org/jira/browse/XERCESC-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Boris Kolpackov updated XERCESC-1769:
-------------------------------------

    Component/s: Utilities
        Summary: ICU message loader broken due to deprecated API usage and 
various other problems  (was: xerces-c++ 2.8.0 ICU message loader broken due to 
deprecated API usage and various other problems)

> ICU message loader broken due to deprecated API usage and various other 
> problems
> --------------------------------------------------------------------------------
>
>                 Key: XERCESC-1769
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1769
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Utilities
>    Affects Versions: 2.8.0
>         Environment: Gentoo Linux 2007.0 AMD64, ICU 3.6 and 3.8
>            Reporter: Tiziano Müller
>             Fix For: 2.9.0, 3.1.0
>
>         Attachments: xerces-c-2.8.0-icu_ressource_fix.patch
>
>
> a) the .res-file can't be used as a fallback if the memory-blob can't be 
> loaded, but it should be the .dat-file (as far as I understood it)
> b) loading the messages using a full file-path is deprecated (according to 
> http://www.icu-project.org/apiref/icu4c/ures_8h.html#c4d72fc9f7cc63a05f646cabee4be167)
>  and it really doesn't work
> c) When using "make install" to install the library, the library 
> libXercesMessages.so.28.0 doesn't get installed which leads to a unresolved 
> symbol error when linking against libxerces-c.so.28.0
> d) When trying to run a test or a sample linked against xerces-c++ built with 
> ICU message loader support, xerces-c++ panics with the error "Cannot load 
> message domain", whether or not libXercesMessages and the .res/.dat-file in 
> /usr/msg are available or not. The patch I'm going to attach fixes this.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to