David Bertoni wrote:
Ivan Bogouchev / Иван Богушев wrote:
Hi David,
2005/9/8, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
Tthanks for the reply, Dave, it that made the stylesheet work.
Just one more question: what about the str:replace() function?
It seems it is not implemented in xalan-c 1.9.
[EMAIL PROTECTED] wrote:
Hello,
I am able to install my own EntityResolver using
theXalanTransformer.setEntityResolver() and Xerces is invoking the customer
EntityResolver's resolveEntity method. Is it possible to obtain the baseURI
of the document (xml or xsd) in which this entity was
This is one of the mirrors listed for the Xalan download -- tells me:
Forbidden
You don't have permission to access
/dist/xml/xalan-c/Xalan-C_current-src.zip.sig on this server.
(for all of the files). A random sampling of other mirrors seemed ok.
Mark
> I'm trying to trap all errors produced by Xalan using a problem listener.
> The problem is that this misses errors that get thrown as exceptions
> sometimes. I _think_ but I'm not sure (this is only from experimentation)
> that this only happens if an extension functions throws the error.
> Gene
I'm trying to trap all errors produced by Xalan using a problem listener.
The problem is that this misses errors that get thrown as exceptions
sometimes. I _think_ but I'm not sure (this is only from experimentation)
that this only happens if an extension functions throws the error.
Generally, the
> Hi Mark,
>
> Thanks for the patch. This defect was recently fixed and is available in
> the latest CVS and will be in upcoming Xalan release.
>
Ah, I've got a stick tag for 1.7. Keep forgetting about that! Will check
properly next time...
in XalanEXST/XalanEXSLTString.cpp.
if (byte2 & 0x80 == 0)
...
There are a few of these. This comes out as:
if (byte2 & (0x80 == 0))
if (byte2 & 0)
if (0)
which is presumably not was intended. The compiler picked this one up, not
me :)
cvs diff attached.
XalanEXSLTString.cpp.patch
Descripti
> You can do this by compiling the stylesheet and querying that information.
> The only caveat is that if there is no output method specified in the
> stylesheet, and the initial element generated is "html", the
> processor will
> use the html method, rather than the xml method. So, perhaps we
> c
> One thing we could do would be to put another accessor on XalanTransformer
> to return the actual encoding of the last transformation. If that sounds
> reasonable to you, please file a bugzilla request for an enhancement.
Yes, that's about the only reasonable way that I could think of. I'd like
Both of these pieces of information would be very useful to me as I'm
squirting the output back from a webserver, and it would be ideal to add
text/html, text/xml to the Content-Type: header, along with the appropriate
charset parameter. getOutputEncoding does exist, but it is the pair to
setOutpu
> "Mark Weaver" <[EMAIL PROTECTED]> wrote:
> > > However, if I understand you code correctly, the following is the
> > > equivalent of what you were doing before:
> > >
> > >theNodeList->addNode(&(*it).second->rtree());
> >
doesn't own any of the nodes and won't clean them up
> when it's
> destroyed.
>
Presumably then, clone is wrong because the clone won't be cleaned up? In
that case, I'm kind of stuck!
> Thanks!
>
> Dave
>
>
>
> |-+---
>
> Hi,
>
> I am trying to compile Xalan 1.7 on .NET 2003. I have a couple of
> questions:
>
> Is Xerces 2.5 the right version to use?
> I am getting compilation errors as follows:
>
> ..\..\..\..\src\xalanc\PlatformSupport\XalanMessageLoader.hpp(67) :
> fatal error C1083: Cannot open include file:
;
Should the deep flag be set? Does the nodelist then own (and therefore
ultimately cleanup) the cloned tree?
Thanks,
Mark
> Dave
>
>
>
> |-+--->
&g
I've recently moved up to Xalan 1.7 and it seems that the getNodeSetRoot()
function has disappeared from XalanDocumentFragment. This was used in one
of my (nasty) extension functions that implements a dictionary.
Basically, I'm trying to stick the RTF to a nodeset in the following code:
> Hi Mark,
>
> I apologize again for forgetting about this _again_. I wanted to
> make some
> changes so that it can be more flexible than it is, and also, I can't
> really see the utility in having a dynamic result tree fragment
> option when
> node-sets are more powerful. Do you agree? Would i
> Subject: [VOTE} Xalan 1.7 release plan
Any chance of my dynamic nodeset builder being added in?
> But for the second part of my question...
> How can i know the xpath i'm evaluting has 'failed'?
>
It throws an exception (probably XPathException). I tend to do:
catch (const XSLException &e)
{
e.defaultFormat(errorMessage);
}
where errorMessage is a XalanDOMString.
#include "extfnapi.h"
This seems to be missing.
> -Original Message-
> From: David Fishburn [mailto:[EMAIL PROTECTED]
> Sent: 08 October 2003 14:58
> To: xalan-c-users@xml.apache.org
> Subject: Memory problems with Release version and a DLL
>
>
>
> Good Morning Dave.
>
> You reviewed
>
> Hello,
>
> I forgot to remove the prefix TL. It is not the real problem however.
> Regard it as:
>
>
> ...
>
> ...
>
> What do you mean with: "the XML document snippet you provided contains an
> illegal UTF-8 byte sequence"
>
It's still much easier if you provide a test case -- this means at
meant this to go here, bah...
-Original Message-
From: Mark Weaver [mailto:[EMAIL PROTECTED]
Sent: 05 September 2003 14:40
To: Borislav Stoyanov
Subject: RE: Xalan-C 1.4 special character question
> ok,on Win2000 I have:
>
> in XML:
>
>
> http://www.w3.org/2001/
Hello,
I'm pleased to announce the first public release of gnomon, which is
offered under an open source license basically identical to that of
Apache. Gnomon is an ISAPI extension that provides server side XSLT
support to IIS. Gnomon is (of course!) based on Xalan-C. You can
download binaries
You could install an EntityResolver, and return a MemBufInputSource when
your external location is matched.
It's looking like I've got a case of when all you have is a hammer... ;)
Mark
-Original Message-
From: Matthew Berry [mailto:[EMAIL PROTECTED]
Sent: 30 July 2003 10:08
To: xalan-c-
I've been fiddling around with docbook, and applying the
XalanTransformerCallback sample (unmodified this time) to a simple document
gives the following assertion:
Assertion failed: subQueryResults.getDocumentOrder(), file
\cvs\3rdparty\xml-xalan\c\src\XPath\XPath.cpp, line 3415.
It's in XPath::f
mailto:[EMAIL PROTECTED]
> Sent: 29 July 2003 16:05
> To: 'Mark Weaver'; xalan-c-users@xml.apache.org
> Subject: RE: Xsl:include support - how to enable it?
>
>
>
> Right, but where (what directory), do I create this class in:
> entity resolver class.
>
>
> After that, I am not sure how to enable the EntityResolver.
> I am using the following sample that I have based everything on:
> C:\OpenSrc\xalan\C\xml-xalan\c\samples\XalanTransformerCallback
>
> So I am not sure where I need to put the code to enable this.
> I am putting it in my XalanTransfor
>
> > Specifically:
> >
> >
> > For Java Xalan, I had to create a XSLTURIResolver.java.
> > When a xsl:include is found, the resolver tells xalan how to find the
> > genericHead.xsl document.
> >
> > Is this supported in the C++ Xalan?
> > I have looked around the C++ API docs, but it is quite d
for the digression.
>
> Note: The XObjectPtr returned from the XPathEvaluator must be
> cloned upon returning it from the
> extension function (but you all know this kind of stuff already... :)
>
> Regards
> /Rob
>
> > -Original Message-
> > From: Mark Weaver
t off, I may send some user-code
> snippets for feedback.
>
> Emmanuel
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 25, 2003 8:38 AM
> To: xalan-c-users@xml.apache.org
> Subject: RE: Best way to create a XalanNode inside a
That's because Xalan's source trees are read only. If you need to
read/modify a source tree, using a Xerces document is probably the way to
go. If you just need to build a document, you can use a
FormatterToSourceTree and build with SAX events.
> -Original Message-
> From: Ashay Shende [
An EntityResolver is correct. They aren't that hard, you only need to
implement one function! An entity resolver is a Xerces object, but Xalan
allows you to set them on various objects, notably the XalanTransformer if
you are using that.
Note that there is a problem (as I see it anyway) with Ent
Yes, that seems correct to me. URI imports should be resolved relative to
the base URI.
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] Behalf Of Per Jessen
> Sent: 14 April 2003 10:18
> To: xalan-c-users@xml.apache.org
> Subject: how document() resolves a relative path
>
>
>
> Here is a CVS diff against the latest (intended to go into the
> 1.6 dev try).
With brain on...
<>
ons
>
>
>
>
>
>
> Hi Jürgen,
>
> No, this did not make it in.
>
> Dave
>
>
>
>
>
> "Juergen
>
> Hermann" To: "Mark
> Weaver" <[EMAIL PROTECTED]>
Try:
http://exslt.org/common";
extension-element-prefixes="exsl"
Then:
select="exsl:node-set($listTitles)/li[$rowPos = @row]"
Mark
> -Original Message-
> From: CP Hennessy [mailto:[EMAIL PROTECTED]
> Sent: 30 March 2003 12:57
> To: xalan-c-users@xml.apache.org
> Subject: probl
The transformer caches both sources and compiled stylesheets. You could get
around this by having a global instance of the transformer and using both
compiled stylesheets and sources from that (application permitting of
course), or you could extract code from XalanTransformer, or copy/hack up
the
> This may just be some broken assumptions we're making in the Xalan code
> about what's in a node-set, and whether or not it can always be ordered.
> Another thing to remember about result tree fragments is they each must
> have a separate owner document if they are going to be turned into a
> nod
One of the changes I've noticed with 1.5 is that my naughty dictionary
function is broken. This is a bad thing, because it's not XSLT like (i.e. not
strictly functional), but it's very handy.
Essentially it goes:
class FunctionDictionary : public Function
{
virtual XObjectPtr
exe
legacy documents, then send a patch with the change, or new
> copies of the XalanParsedURI files.
>
> Thanks!
>
> Dave
>
>
>
>
>
> "Mark Weaver"
>
> <[EMAIL PROTECTED]
Relative URI references are distinguished from absolute URI in that
> >they do not begin with a scheme name. Instead, the scheme
> is inherited
> >from the base URI, as described in Section 5.2"
> >
> > Unfortunately, it looks like the Java processors (which
> Mark, can you make sure your patch is compatible with the latest CVS and
> provide a CVS diff? Also, actual copies of the new source files
> instead of
> diffs (XalanParsedURI.cpp and XalanParsedURI.hpp) would be much easier to
> deal with.
>
OK, the included zip is a cvs diff against the curren
Whoops, looks like I've missed my opportunity to get the URI fixes in. In
retrospect, I've finally gotten around to posting my patch for this:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16737
which has both the patch and a test application. It's against the 1.4
release, but will probably
> Are there any examples of using EXSLT with XalanC? I can't find any in
> the distribution.
>
> Incidentally, the 1.4 documentation says:
>
> * installExternalFunction() makes the function available in
> the current instance of XalanTransformer. Use
> uninstallExternalFunction() to remove the
Hi David,
OK, I finally something for you to look at. This is a patch against the
Xalan 1.4 release to add support for returning nodesets and result tree
fragments from extension functions. The hacked up ExternalFunction sample
shows how this works. Roughly, things are as discussed, but I'll go
> Hi Mark,
>
> It's good to hear back from you!
>
Yup, and sorry once again for the (vast) delays. Hopefully I'll be able
to get this rounded off finally!
> I think you've uncovered a bug in the code. There's no way an external
> function should get a reference to the XPathExecutionContextDefaul
Hi David.
Well I realise this was back in October but (once again) I managed to run
out of time on it (sadly, the way that the company works is as follows: do
work on core stuff. Find someone who is willing to pay money. Immediately
drop everything for money. Return to core stuff. Repeat until
OK, one more stab before this gets somewhere ;)
I'm happy with the two class/base class concept, i.e.
class XalanDynamicBuilder {
void reset()=0;
ContentHandler *getContentHandler()=0;
LexicalHandler *getLexicalHandler()=0;
DocumentHandler *getDocumentHandler()=0
Two unrelated questions. The first is that I would like to transform a DOM
into a DOM, the reason for this is that there may be a number of stylesheets
applied to a single input XML document, thus giving a general procedure:
input --styleA--> DOM output #1
DOM output #1 --styleB--
This is fixed in the Xerces 1.5.2 release, you might want to consider
upgrading to that if you really need this support. However, Init/Term are
not thread-safe (there is an open bug for this).
Mark
> -Original Message-
> From: David_N_Bertoni@lotus.com [mailto:[EMAIL PROTECTED]
> Sent: 3
start would be great!
Thanks,
Mark
> -Original Message-
> From: Juergen Hermann [mailto:[EMAIL PROTECTED]
> Sent: 24 October 2001 03:58
> To: Mark Weaver; Xalan-C-Users
> Subject: Re: regexp in xsl:value-of?
>
>
> On Wed, 24 Oct 2001 00:10:14 +0100, Mark Wea
Hi,
I'm currently in the process of shifting my company over from MSXML to
Xalan. As part of this, some of them have (annoyingly) written stylesheets
including VBspit. Most of these are easily replaced, but one of the things
that they tried to do is thus:
> The one thing javascript / vb access
> I also keep my own (mutex protected) map of stylesheet path->compiled
> > stylesheets; the stylesheet is effectively compiled & stored on
> the first
> > usage. Thread safety of STL containers is a bit of a pain, for maximum
> > efficiency you need a multiple readers/single writer locking
> mech
e compiled stylesheets and parsed source documents
> directly, but you'll need to manage things. It's pretty
> straightforward --
> just see the code in XalanTransformer::compileStylesheet() and
> XalanTransformer::parseSource(). For information on cre
smime.p7m
Description: S/MIME encrypted message
54 matches
Mail list logo
