Hi all!
I've just been playing with the new Xerces 3.0 code from SVN and
realised that Xalan does not appear to build against it on a *NIX system.
Am I missing something (I generally am :>)? Or has this just not been
implemented yet?
Cheers,
Berin
I've only tried
with a couple of versions.
I think it may need a test in configure, but I think it may be a bit of
a bugger to write - although we could just try compiling this file I
suppose :>.
Cheers,
Berin
Missed this!
+1
Cheers,
Berin
Matthew Hoyt wrote:
Hi all,
Over the past 10+ months, Dmitry Hayes has made many contributions to the
Xalan-C project including:
- message localization feature.
- additional EXSLT function implementations.
- assisting users on the mailing lists
?
Nagoya gives us Solaris 2.8, with gcc 3.1 and CC 5.4.
Moof gives us Mac OS X 10.3, but I've never got myself access.
I have some systems that I am setting up to autobuild my own stuff,
which gives us Linux (gcc 2.95.4 - Debian stable and gcc 3.3.3 - Debian
Unstable), FreeBSD (4.9) and NetBSD (1.6.1).
Cheers,
Berin
like this might be caught as it occurred, rather than after a release.
It's very primitive, but it might be useful?
Cheers,
Berin
[EMAIL PROTECTED] wrote:
Hi Holger,
Yes, this is a major bug in Xerces-C, but I don't know what else we can do.
I will post a note on the Xerces-C
Done (and this is a test...)
Cheers,
Berin
[EMAIL PROTECTED] wrote:
Hi Berin,
Feel free to add the header -- that would be great.
Thanks!
Dave
Absolutely +1!
(Do you mind if I add a Reply-To: header to the list?)
Cheers,
Berin
[EMAIL PROTECTED] wrote:
Hi all,
Over the past 6 months, Matthew Hoyt has been contributing to the Xalan-C
project
by submitting patches, answering questions on the mailing lists and helping
test
the
David,
+1 from me. (Xerces 2.4 build would be a very good thing.)
I can do Net/FreeBSD testing of release archives if that's of use?
Cheers,
Berin
[EMAIL PROTECTED] wrote:
Hi folks,
It's time to start thinking about doing a Xalan-C release
that is compatible with the latest Xe
- not quite 1.3.4 but close.
See :
http://nagoya.apache.org/~blautenb/xml-security-c/apiDocs/
For the xml-security docs (of no real interest other than to show how it
looks on nagoya).
Cheers,
Berin
Don McClimans wrote:
By the way...
I have built the xalan api docs into a windows compressed
Jaspreet,
See
http://xml.apache.org/xalan-c/usagepatterns.html#xercesdomwrapperparsedsource
Cheers,
Berin
>
> From: Jaspreet Singh <[EMAIL PROTECTED]>
> Subject: converting a DOMNode to XalanNode
> Date: 11/09/2003 16:42:01
> To: xalan-c-users@xml.apache.org
>
&
can
get a couple of people set up to approve the legitimate e-mails that
come through from non-subscribed people?
Cheers,
Berin
WayOfLife wrote:
*àÅ×Í¡ÊÔ觷Õè´Õ·ÕèÊØ´ ÊÓËÃѺ¤¹·Õè¤Ø³ÃÑ¡ áÅÐà¾×è͵ÑǤسàͧ
* µÑé§áµèà¡Ô´ÁÒ àÃÒÍÂÙè¡ÑºÃèÒ§¡ÒÂàÃÒàͧÁÒ¡¡ÇèÒÍÂÙè·Õèã´æ
äÁèÇèÒ¨Ðà»ç¹Ã¶Â¹µì ºéÒ¹ ËÃ
And I'm a particular fan of the docs split out into a separate package.
On a modem connection it has made my life much easier - many thanks indeed!
Cheers,
Berin
[EMAIL PROTECTED] wrote:
Hi all,
Xalan-C 1.6 is now officially available. Highlights include:
1. "Sane include
er look at the configure system.
Thoughts?
Cheers,
Berin
Bjoern A. Zeeb wrote:
On Mon, 14 Jul 2003 [EMAIL PROTECTED] wrote:
Hi,
It's about time we do a 1.6 release, for compatibility with Xerces-C 2.3.
So, if there are any open bugs you would like fixed before the release, or
there&#x
Colin Paul Adams wrote:
What are the include files called now?
E.g. instead of -I$XALANCROOT/src, use -I$XALANCROOT/src/xalanc, or
prepend xalanc on all your include directives :
#include
Cheers,
Berin
Just learnt something new :>.
Done.
Cheers,
Berin
[EMAIL PROTECTED] wrote:
Hi Berin,
Can you just do a chmod on those two repository files? That will save
multiple emails about this when people check out from CVS. The previous
versions of runConfigure and configure did have th
only when you do a clean checkout that you get
this problem.
Cheers,
Berin
>
> From: Colin Paul Adams <[EMAIL PROTECTED]>
> Subject: Re: CVS
> Date: 02/07/2003 15:27:57
> To: xalan-c-users@xml.apache.org
>
> >>>>> "david" == david
Bjoern,
Definitely a +1 from here! I didn't get a chance to look at it this
weekend, but I did see your bugzilla attachment.
Will try to incorporate in the near future :>.
Cheers,
Berin
Bjoern A. Zeeb wrote:
On Wed, 25 Jun 2003, Berin Lautenbach wrote:
Hi,
What I might do (if
esDOM sample code for outputting a transform to Xerces DOM.
Cheers,
Berin
Shirish Kulkarni wrote:
Hi,
I am trying to use both Xerces and Xalan together in
my application. Is it possible to us the DOM tree and
hence APIs in Xalan & Xerces interchangably ? How ?
Thanks,
ld be good to have a generic test.
The only problem is that this might break the port that you have done,
but hopefully we can keep the breakage to an easily defined subset.
Cheers (and thanks!),
Berin
Bjoern A. Zeeb wrote:
Hi,
on http://sources.zabbadoz.net/freebsd/ports/experimental
NSCODERS
to bypass this call to mbstowcs during the build
process.
I will setup your patches on my FreeBSD system
as soon as you post them. Would love to be able
to get it to work properly.
Great stuff!
Cheers,
Berin
This message was sent through MyMail http://www.mymail.com.au
others. My understanding is that once the basic stuff is set up it
should be reasonably easy to port from version to version.
I reckon a big +1 from here. My spare bandwidth is rather limited at
the moment, but I'd be happy to help where I can.
Thoughts? +/-?
Cheers,
Bjoern,
To follow up.
Bit the bullet today and did the upgrade to 4.8. Still gcc 2.95.4 but
looks to have been recompiled.
Re-compiled all of Xerces - DOMPrint still crashes. So I think we can
safely say that anything < 5.0 (at least) crashes.
Cheers,
Berin
Bjoern A. Zeeb wrote:
initialised. although I haven't fully verified that yet).
Am thinking about grabbing the gcc 3.2 package and trying it out.
Cheers,
Berin
> From: Alexei Dets <[EMAIL PROTECTED]>
> > What exactly are your problems with FreeBSD and xerces-c ?
>
> All Xerces applications are crashing (at least on FreeBSD-4.7) with
> segmentation fault immediately after XML convertions - I mean all supplied
> demo applications. My applications are usi
Alexei,
I've found the same problem with Xerces 2.2. I
think it may be something to do with the FreeBSD
transcoding routines. Something I've been meaning
to play with and sort out.
Have not yet tried Xerces 2.3.
Cheers,
Berin
>
> From: Alexei Dets <[EMAIL PROTEC
ting the xalanc directory during build time. This is what is done
in the xml-security-c library, but it's a pain in the proverbial because
of what it does to VC++.
Cheers,
Berin
get rather large executables.
Cheers,
Berin
sindhur wrote:
Hi everyone,
I have created an application using Xalan APIs and when I use the exe
file generated to run the application on a different machine without
Xalan installed on that machine it pops up a message saying it requires
som .dll
Erik,
The classes involved in wrapping the DOM_Nodes are
probably not really that "thick". However, they
are still standalone within the library, so if
you wanted to pull them out there shouldn't be
any great problem.
Cheers,
Berin
>
> From: "Erik Rydgren"
Erik,
(You may have already received something - having
some great problems with e-mail clients today.)
Yes - one of the new features in Xalan 1.5 was a
set of wrapper clases for DOMNodes that corresponds
to the bridge classes for DOM_Nodes.
Cheers,
Berin
>
> From: "Erik Rydgr
(E.g. "//wmnc:GreatGrandParent")
You could also use the derivative of PrefixResolver to define wmnc.
Cheers,
Berin
Michael Hughes wrote:
Thanks David, I tried that and it worked ok.
Next problem :-)
My document looks something like this:-
http://www.michael_namespace.com/sch
near future.
Cheers,
Berin
>
> From: Per Jessen <[EMAIL PROTECTED]>
> Subject: recent cvs snapshot not building?
> Date: 22/05/2003 5:30:26
> To: xalan-c-users@xml.apache.org
>
> Hi,
>
> I've just tried building the latest snapshot, xalan and xerces both
gainst the .so, ld.so
will always run it against the full version name.
That's Debian rules, but it's also the cleanest
way to manage dynamic libraries under linux.
Cheers,
Berin
>
> From: [EMAIL PROTECTED]
> Subject: Re: co-existence of multiple versions
> Date: 01/05/
David/Chandu,
Firstly - apologies. Have been baby-sitting the sick family.
Have had a quick run through - looks good!
Only question - is the initial para in index.html correct? It still
reads like an intro to 1.4?
Cheers,
Berin
[EMAIL PROTECTED] wrote:
Hi Chandu,
The source, except
David,
I have been most lax here. I will take a look
tonight and tomorrow and let you know when I am
done.
Cheers,
Berin
>
> From: [EMAIL PROTECTED]
> Subject: RE: Xalan 1.4 with Xerces 2.2???
> Date: 17/04/2003 4:34:00
> To: xalan-c-users@xml.apache.org
>
>
Does your XALANCROOT environment var end in /c?
I.e.
XALANCROOT=/opt/local/sanxius/works/xml-xalan-1.5/c
rather than
XALANCROOT=/opt/local/sanxius/works/xml-xalan-1.5
Cheers,
Berin
SanZ wrote:
Hello,
i tried to run xalan 1.5rc1 with xerces 2.2 on gentoo linux.
it makes correctly the
David,
That's exactly the solution I used to get past the problem :>.
The reason it took so long is that I didn't make the jump to it being a
problem in their libc code for a while. Once I did it was plain
sailing. (They re-wrote that part of the library for 1.6.)
Cheers,
ression
in soap:Envelope of xmlns:tc="http://trade.com";
and then use the expression
SimpleXPathAPI mysoap.xml / //tc:username
you will select all the "username" nodes in
the document that exist in the trade.com
namespace.
Cheers,
Berin
>
> From: Suzanne Dirkers <[EMAIL
eeBSD is
supported in the Xerces build, this seemed to
make more sense than continuing down the NetBSD
path for my stuff.
Cheers,
Berin
>
> From: David N Bertoni/Cambridge/IBM <[EMAIL PROTECTED]>
> Subject: Re: Upcoming Xalan-C++ 1.5 release
> Date: 27/03/2003 9:18
code to determine how to install an external function.
I wonder if it might be worth going through the example programs and
providing some details around them? What does a FormatterListener do?
Why is it there, how does it work?
Don't know if that helps?
Cheers,
Berin
Rachael Lu
http:g ; for validating parsers
| http://a/b/c/g ; for backwards compatibility"
So it's arguably OK, even if not encouraged.
However there is also an implication there that
not supporting it is OK.
Cheers,
Berin
>
> From: David N Bertoni/Cambrid
pression needs to find all nodes under .
The problem is I always know the URI of the namespace, but I don't
know the prefix - this was arbitrarily set by the writer of the doc.
Do I "pre-seed" the document with
http://www.w3.org/the-dsig-path
xmlns:berin-dsig="http://www.w3.or
Richard,
Not intuitive until you think in the same way as you would in the style
sheet :>.
Try using the command line
... -PARAM Resort "'Blackpool'"
(I think there is some stuff in the archives around this.)
Cheers,
Berin
richard work wrote:
Hi,
Excuse me if m
Nick,
You could also try Xerces-dev. However, a few
quick questions.
I'm not clear from your e-mail what version of
Xerces/Xalan?
Did you download the binary versions?
What compiler?
Cheers,
Berin
>
> From: Nick Bastin <[EMAIL PROTECTED]>
> Subject: Linking on w
it's normal.
Cheers,
Berin
>
> From: SanZ <[EMAIL PROTECTED]>
> Subject: Re: Xalan c building troubles.
> Date: 25/02/2003 0:59:19
> To: xalan-c-users@xml.apache.org
>
> I resolved the Xalan Trouble by setting the XALANCROOT as
>
> export XALANCROOT=
Peoples,
There has been a small discussion going on about what version of gcc
(or even Intel compiler) should be used for the linux binary release
files for Xalan 1.5.
The current thinking, assuming we go with gcc, is version 3.2.2, but
we would be interested in what is of most use to most peopl
Tony,
I think the rough idea at the moment is end of this month/early next.
Cheers,
Berin
Tony Chen wrote:
Could anyone give me a rough idea when xalan 1.5 will be available? Thanks
Tony Chen
9138952313
This transmission (and any information attached to it) may be confidential
and is intended
DOMDocument.
For your middle para, can you send us a bit more
info about what you are trying to do? It looks
like you are trying to get a UTF-16 character
into an document that is encoded with a lesser
width character (unless I am reading the code
incorrectly).
Cheers,
Berin
>
>
lan.
Hope it's usefull.
Cheers,
Berin
Russell C. Hadley wrote:
Berin,
Thanks! Are there any code samples of this kind of
transformation around? Specificly mapping back and forth.
And your point about the ::Initialize() calls is well taken.
Thanks again. -R
Berin Lautenbach writ
n and continue, I've found it best to build and modify the
document using straight Xerces calls, wrap in Xalan when I want to do
XPath and then map back to Xerces and continue. If I need to do another
XPath - I re-map to ensure any changes I have done are caught.
Cheers,
Berin
Russell
iting
detailed doco for it is somewhat daunting. I'd agree that there is work
that could be done here, but at the same time there is only a limited
number of resources available.
A bit rambling - but I hope of use.
Cheers,
Berin
Howard Kapustein wrote:
OK, I think I'm finally startin
Galen,
I have been using latest CVS against Xerces 2.1
release for a few months. Works very well.
Cheers,
Berin
>
> From: Galen S Swint <[EMAIL PROTECTED]>
> Subject: Xerces 2.1 and interim build
> Date: 07/02/2003 1:46:33
> To: xalan-c-users@xml.apache.org
>
th a BOM. If you don't start with a BOM
then you cannot use UTF-16 (in a naming sense),
you must be using UTF-16LE or UTF-16BE and this
must be defined in the encoding declaration.
Cheers,
Berin
>
> From: David N Bertoni/Cambridge/IBM <[EMAIL PROTECTED]>
> Subject: RE:
Colin,
Forgive the stupid question - have you passed
the update command a -d to create directories
that are in the repository but not in the local
copy?
I.e. cvs -z3 update -d
Cheers,
Berin
>
> From: Colin Paul Adams <[EMAIL PROTECTED]>
> Subject: Re: Xerc
rget.
Or am I right off the mark :>.
Cheers,
Berin
David N Bertoni/Cambridge/IBM wrote:
>
>
>Hi Berin/Colin,
>
>Just to clarify -- we _do_ have a new wrapper, we just don't support
>_modifying_ the underlying Xerces DOMDocument instance. through it. I
>thin
Colin/David,
Quick patch to provide an overload for XalanTransformer::transform with
parsed XML containing stylesheet in PI node.
(Diff is against CVS at time of sending.)
Cheers,
Berin
David N Bertoni/Cambridge/IBM wrote:
Hi Berin,
At one point, I think I took a step back and tried to keep
e what you want tho?
Your other option (if you have to have a Xerces document at the end)
might be to output to a stream and then use Xerces to re-parse the stream?
Cheers,
Berin
David N Bertoni/Cambridge/IBM wrote:
Hi Berin,
That's correct, and I just don't want to go there
Will see if I can put a patch on the list tonight.
Cheers,
Berin
David N Bertoni/Cambridge/IBM wrote:
Hi Berin,
At one point, I think I took a step back and tried to keep the transform()
overloads from exploding into every possible combination. We could add
another one for this case, but the
XSLTInputSource
- ie.
transform(theParsedSource, XSLTInputSource(), theResultTarget);
Cheers,
Berin
Colin Paul Adams wrote:
Looking through the documentation , and the header file, I cannot see
a version of XalanTransformer::transform that takes a
XalanParsedSource as input, and allows you to miss
wrapper classes will throw a NO_MODIFICATION_ALLOWED_ERR exception.
My reading is that fixing this will require the Wrapper classes be
updated to allow modification?
Cheers,
Berin
Colin Paul Adams wrote:
"David" == David N Bertoni/Cambridge/IBM <[EMAIL PROTECTED]> writes:
Thomas,
The following usage pattern might help :
http://xml.apache.org/xalan-c/usagepatterns#xercesdomwrapperparsedsource
Some previous correspondance :
http://marc.theaimsgroup.com/?l=xalan-c-users&m=102800880824935&w=2
Cheers,
Berin
FPO Chat wrote:
Hi
I'm using xalan-c++ v
Oliver,
I have been getting around these complexities by
building the AllInOne project which puts everything
in one library. Have found it much easier, and
given it's in line with the plan for the next
release it worked well.
Cheers,
Berin
>
> From: David N Bertoni/Cambridge/
an CVS and all works like magic
with Solaris and Linux (Debian). (Using both
Xerces and Xalan looked a little too much like
walking on the wild side for me.)
Cheers
Berin
>
> From: Colin Paul Adams <[EMAIL PROTECTED]>
> Subject: Re: How do I build from CVS?
> Date: 29/0
parser->setDoSchema(true);
// Create an input source
MemBufInputSource* memIS = new MemBufInputSource ((const XMLByte*)
txoh.buffer.rawBuffer(), txoh.offset, "XSECMem");
int errorCount = 0;
parser->parse(*memIS);
--SNIP--
+ some error
David,
Out of curiosity, is there actually a plan to do
the overhaul? It seems to be something of
interest to a number of people?
Cheers,
Berin
>
> From: David N Bertoni/Cambridge/IBM <[EMAIL PROTECTED]>
> Subject: RE: Getting the line and column number of an error
> Dat
e
ordering issue you mentioned? The suggestion
about parsing twice seems sensible, although
could you build two lists at once and then append
one to t'other?
I'm having a look at the namespace issue
(although have left the bug as unassigned as am
not sure of the protocol).
Cheers,
/cgi-bin/bugreport.cgi?bug=143419
(Not closed because I have not fully adopted yet.)
Cheers,
Berin
David N Bertoni/Cambridge/IBM wrote:
Hi Berin,
Actually, these options are very old, and I don't believe we should
continue to support them, so I'm tempted to remove them. Can you describ
David,
Apologies - ignore previous - just found out about cdata-section-elements.
Cheers,
Berin
>
> From: <[EMAIL PROTECTED]>
> Subject: STRIPCDATA option in testXSLT
> Date: 03/01/2003 13:53:41
> To: xalan-c-users@xml.apache.org
>
> David,
>
> There a
XSLT doesn't really have a concept of CDATA - so will there ever be
a CDATA to output?
Cheers,
Berin
This message was sent through MyMail http://www.mymail.com.au
patches.
Happy new year!
Cheers,
Berin
viewing patch updates is
never fun.)
Cheers,
Berin
>
> From: David N Bertoni/Cambridge/IBM <[EMAIL PROTECTED]>
> Subject: Re: Latest CVS
> Date: 17/11/2002 5:46:16
> To: xalan-c-users@xml.apache.org
>
>
>
>
>
> Hi Berin,
>
> > P
ns about the underlying implementation of the XercesNode?
Cheers,
Berin
David N Bertoni/Cambridge/IBM wrote:
Hi Berin,
You're probably working in the mode were the wrapper is "pre-built," which
yields reasonable performance, but doesn't allow mapping from a Xerces node
front of me, but from memory I use a
xercesParserLiason->getDocument to get a document, and I then use the
ParserLiason to get a wrapper from which I build a wrapperNavigator. Is
there something important I have missed?
Cheers,
Berin
David N Bertoni/Cambridge/IBM wrote:
<[EMAIL PRO
installed versions according to the
thread).
Cheers,
Berin
>
> From: <[EMAIL PROTECTED]>
> Subject: Latest CVS
> Date: 15/11/2002 13:01:11
> To: xalan-c-users@xml.apache.org
>
> David,
>
> I am converting some code over to the "new" DOM implementat
ferent threads might
want to install slightly different versions of the same function at any given
time.
I realise the code is all in development and I am jumping the gun on the
questions. Was really just curious on both counts.
Cheers,
Berin
This message was sent through MyMail http://www.mymail.com.au
74 matches
Mail list logo
