Hey Mark,
Sorry, I've been incredibly busy with work these days, so I haven't had
lots of time to look at possible patches.
A pain isn't it! I guess you haven't had chance to take a look yet?
Is there any chance you could adapt the exslt-regexp patch to work with
Xerces-C's regular express
tion I could find -- that of the EXSL.NET implementation.
Since Jira seems to be working again I'll open bugs for the bugs
mentioned below.
Mark
Original Message
Subject: Xalan-C: dynamic nodesets from XPath functions
Date: Mon, 17 Apr 2006 01:42:13 +0100
From: Mark
Reporter: Mark Weaver
Priority: Minor
Attachments: function-pairs-past-end.patch
Patch attached to correct
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
leak in XalanTransformer
Key: XALANC-617
URL: http://issues.apache.org/jira/browse/XALANC-617
Project: XalanC
Type: Bug
Components: XalanC
Versions: 1.10
Reporter: Mark Weaver
Attachments: function-pairs-leak.patch
The
seems to be working again I'll open bugs for the bugs
mentioned below.
Mark
Original Message
Subject: Xalan-C: dynamic nodesets from XPath functions
Date: Mon, 17 Apr 2006 01:42:13 +0100
From: Mark Weaver <[EMAIL PROTECTED]>
To: xalan-dev@xml.apache.org
I'd like
> The exception is actually returning the value of errno, which ought to
> contain the appropriate error code. This may be a case where we need some
> Windows-specific call to get an error code.
>
Confirmed, this class is using the Win32 file API (CreateFile, etc) and
throwing an exception based
times so there is not
> chance of a target file getting locked.
>
> -Original Message-
> From: Mark Weaver [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 02, 2003 11:29 PM
> To: [EMAIL PROTECTED]
> Subject: RE: XalanTransformer::transform fails in Xalan 1.5
>
> I tried the same call with Xalan 1.5 built with SP3 ( DownLoaded
> from Site).
> In that case fails sporadically in the ratio of 80 Failures / 8
> Attempts.
>
> The function call returns -1 and getlasterror returns
> "XalanFileOutputStreamOpenException: Error opening file:
> c:\temp\Validat
This is against 1.6 release -- the only changes from the previous patch are
for the sane includes.
Any chance of getting this applied for 1.7?
Thanks,
Mark
Dynamic1.6.zip
Description: Zip compressed data
ils -- I've just been horribly backed up at work. I'd like to
> get the dynamic node set creation stuff into 1.6 (it's a bit too late for
> 1.5), and would also like to get the URI/URL stuff cleaned up as well.
>
>
David - are you currently the only committer?
> -Original Message-
> From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]]
> Sent: 07 February 2003 22:44
> To: [EMAIL PROTECTED]
> Subject: Re: Nomination of Berin Lautenbach for committer status
>
>
>
>
>
>
> > Hi all,
> >
>
That sounds really handy, I'm very keen to see it!
Thanks,
Mark
> -Original Message-
> From: Joseph Kesselman [mailto:[EMAIL PROTECTED]]
> Sent: 04 February 2003 14:31
> To: [EMAIL PROTECTED]
> Subject: Re: [PATCH] for Issue# 7946
>
>
> Can I vote -.5 on this proposed patch? It's not a b
Ok, I've been doing some fixing up on this. Firstly, what I've done is
written a separate class, XalanParsedURI (can change the name if someone can
think of a better one). Roughly this goes:
class XalanParsedURI
{
public:
// accessors for:
scheme
authority
path
qu
ll
> not be trivial, so I have no idea how long it will take to fix it.
>
> Dave
>
>
>
>
>
> "Mark Weaver"
>
> <[EMAIL PROTECTED] To:
> <[EMAIL PR
IBM [mailto:[EMAIL PROTECTED]]
> Sent: 03 February 2003 16:52
> To: [EMAIL PROTECTED]
> Subject: Re: XalanC: bug in relative URI resolving or my brain?
>
>
>
>
>
>
> Hi Mark,
>
> Have you tried using a URI?
>
>file:///somewhere/somethingorother.foo
>
Xalan-C 1.4 on w2k.
At some point, I'm calling
XPathExecutionContext::parseXML("/somewhere/somethingorother.foo",
"http://localhost/blah/blah/blah.foo";). The URI is then resolved to
http://localhost/blah/blah/somewhere/somethingorother.foo. This seems wrong
to me - RFC2396 has "5) If the path
> Might be a good idea to get in the habit of changing the subject line (as
> I've done here) once we realize that folks are getting the two
> implementations confused.
>
> Might also be time to split xalan-j-dev and xalan-c-dev.
I agree with this wholeheartedly.
AFAICT Xalan doesn't use shared memory. Presumably this is something that
your apps/service are doing?
If this is the case, what's mucking you up will most likely be the security
on the shared memory section you have created. A simple solution is to
create the section with a NULL DACL:
SECU
18 matches
Mail list logo
