You could use expat, but since we require Xerces to be there, I doubt
there's any benefit to it. You'll end up writing and testing a bunch of
integration code and that seem to me a waste of time.
I'm curious as to why you think the Xalan-C++ sources are "split across
several platforms". There is one set of sources for all platforms, so
there is no need for any sort of integration. The only thing we require is
a compiler configuration file which contains the necessary #defines.
We don't currently have an SGI port, although we're willing to work with
you to integrate any necessary changes back into the sources.
You should use the class XalanTransformer for all of your interaction with
Xalan. It's our public API and we make much stronger guarantees with
regard to compatibility changes. All other APIs are subject to change at
our whim ;-)
At any rate, you might want to want to wait a few weeks, since we'll be
doing a new release. Or at least start with the latest sources from CVS.
Dave
roger.day@globalgr
aphics.com To: [EMAIL PROTECTED]
cc: (bcc: David N Bertoni/CAM/Lotus)
08/01/2001 03:45 Subject: RE: integration with other
products
AM
Please respond to
xalan-dev
Actually, I was looking for more in-depth details than just the
usage-patterns.
Maybe I should have added more detail. We're using xalan-c. The product
will be
compiled across the usual suspects as well as SGI. For example, I notice
that
the Xalan-c source is split across across several platforms; I suspect that
we'll want to integrate the source back into one tree. How easy would that
be?
At 31/07/01 18:50:26, "Gunnlaugur Thor Briem" <[EMAIL PROTECTED]> wrote:
# Hi Roger,
#
# > I'm about to embark on integrating Xalan with one of our products
(yes,
# I've
# > read the licence agreement and we will be adhering to it) and I was
# wondering if
# > there were any FAQs/advice on the topic anywhere.
#
# One approach might be to ... try the website!
#
# http://xml.apache.org/xalan-c/usagepatterns.html
# http://xml.apache.org/xalan-j/usagepatterns.html
#
# (never would have thought of looking there
# without asking the mailing list, right? ;)
Still doesn't answer the question: can I use Expat instead of Xerces in
xalan-c?
Roger
