Hi Berin,
For the ELF platforms (linux, solaris, HP), we should definitely do this.
AIX is slightly different, but we'll just have to accomodate it in the
Makefile.
This should be a high priority for 1.5.x, if we do a point release, or 1.6
if we don't.
Dave
We probably should be using -soname on linux to
embed the full name into the library. It's
cleaner and a bit more standard.
In the debian distribution I've renamed
the library to libxalan-c.so.14.0 and use -soname
to embed this name into libxalan-c.so so that
when you link a program against the
Hi Suzanne,
Usually, this is a symptom of building and linking with different versions
of GCC. Are you sure you're using the exact same version of GCC that we
used to build Xalan-C? If not, you'll need to.
If you are using the same version, more output would help. In particular,
a cut-and-
Hi Ravin,
Can you create a _minimal_ standalone set of inputs that we can use to
test? If so, please create a Bugzilla report and attach the files.
Thanks!
Dave
Hi,
Does anybody know why one might get such an error as
XalanDOMSTirng.hpp:202...undefined reference for
TranscodeToLocalCodePage ( unsigned short const*, vector ,
allocator>&, bool)
at Xalan 1.3? on Linux? This same error doesn't seem to be present on
zOS at Xalan 1.3. ??
Sorry, if this has been answered previously. I checked the archives and sample
code and could not find the answer.
Is this the right pattern to execute a XPath Query on Xerces DOM? This code
used to work with the source in CVS repository that I downloaded couple of
months back. The official
Thanks for the response. I'll be getting 1.5 over the next few days.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 30 April 2003 16:51
To: xalan-c-users@xml.apache.org
Subject: RE: problem with XSLT tranformation using Xalan
Hi Michael,
Please download
Hi Michael,
Please download Xalan-C++ 1.5. It has support for the new Xerces DOM. The
old DOM is now deprecated because the performance of the new DOM is much
better.
Just to re-iterate here -- it looks like you're using the Xerces DOM for
the sake of using it, not because you need to. Mak
Hi Tony,
It's fairly easy because the libraries have different names. You will need
to manage the PATH/LD_LIBRARY_PATHS/LIBPATH/SHLIB_PATH environment
variables, if you truly want to isolate all of the Xerces and Xalan
versions from each other.
Dave
> Does anyone have any suggestion on running multiple version of xerces/xalan
> on one system?
Options (kind of unix-centric):
(1) Put in different directories and have applications have different search
paths and/or build paths (i.e. LD_LIBRARY_PATH and -L link directories).
(2) Make the shar
Could different version of xerces-c/xalan-c run on the same system? We have
lots of applications using older version of xerces/xalan. However some new
applications are using the latest. We really do not want to wait till we
port all to the latest version to put the new app in. Does anyone have
Please correct me if I'm wrong, but the useage pattern you referred to
is the following...
#include
#include
void parseWithXerces(XalanTransformer &xalan,
const XSLTInputSource &xmlInput,
const XalanCompiledStylesheet* styleSheer,
"¤Ø³¾ÃéÍÁ·Õè¨Ðà»ÅÕè¹µÑÇàͧ áÅÐ͹Ҥµ¨ÃÔ§æ ËÃ×ÍÂѧ???"
ÃÒÂÅÐàÍÕ´ ¤ÅÔ¡ http://www.geocities.com/jobonline9211
¡Ò÷ӧҹ»ÃШӤ×Í ¡ÒÃá¡é»ÑËÒÃÐÂÐÊÑé¹
·Ø¡¤¹¤Ô´á¤è Çѹà§Ô¹à´×͹ÍÍ¡
»ÅèÍÂãËéà§Ô¹ÁÕÍÓ¹Ò¨à˹×ͪÕÇÔµ
¾Ç¡à¢Ò ¨Ö§ÁÕÅѡɳФÅéÒ¡ѹ¤×͵×è¹àªéÒä»
·Ó§Ò¹ äÁèà¤ÂËÂØ´¤Ô´àÅÂÇèÒ
14 matches
Mail list logo
