Re: [PATCH] MalformedURIException illegal host (Registry-based Naming Authority)

It may make sense to have a XML utility sub-project if there were a collection of classes which would be of use for multiple projects. Not sure if this is worth doing for just one class or if a community would develop behind a utility sub-project considering how inactive xml-commons has been as

Re: [PATCH] MalformedURIException illegal host (Registry-based Naming Authority)

Would it make any sense for the URI code be factored out into XML-Commons so we aren't maintaining it in parallel across these two projects? __ Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more. "The world changed profoundly and unpredictabl

Re: [PATCH] MalformedURIException illegal host (Registry-based Naming Authority)

The URI code in Xalan seems to have been duplicated from Xerces2 at a time when its conformance to the URI spec (RFC 2396) wasn't very good. In the Xerces version of this class we've patched up many of the holes, including missing support for registry-based authority. Not sure how much the code

Re: [PATCH] MalformedURIException illegal host (Registry-based Naming Authority)

Hi, Dieter In order to track bugs, please open a bug report and attach your patch @ http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10584 thanks, Christine Li XSLT Development IBM Toronto Lab Tel: (905)413-2601 Email: [EMAIL PROTECTED]

RE: [PATCH] for Issue# 7946

>That sounds really handy, I'm very keen to see it! OK, I'll try to finish off the article and get it posted some time soon. The stylesheet itself is working; I just need to document it better so folks know how to adapt it for their own needs. It isn't a new concept, but there haven't been a lo

RE: [PATCH] for Issue# 7946

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 th

Re: [PATCH] for Issue# 7946

Can I vote -.5 on this proposed patch? It's not a bad concept, but I don't think it's the right answer. The requested behavior can be obtained _without_ modifying Xalan by writing a stylesheet that preprocesses your stylesheet to add that behavior to each template. And the annotation-via-styles

Re: Patch for Issue 15636 [ XSLTC translets ignore parameters with dots in their names when they are set with Transformer.setParameter ]

Hi Revathi,    Strictly speaking, the replacement of "-" and "." is needed only for variables (since variables are stored as either instance variables or local variables in a class and a Java identifier cannot contain those chars). However, since vars and params share a lot of code, it was ea

Re: [PATCH] For allowing xalan to read property files without opening up container permissions

if you are satisfied ). Thanks -Ramesh >From: [EMAIL PROTECTED] >Subject: Re: [PATCH] For allowing xalan to read property files without opening upcontainer permissions >To: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED] >Date: Mon, 18 Nov 2002 10:40:53 -0500 >X-MIMETrack: Seriali

Re: [PATCH] For allowing xalan to read property files without opening upcontainer permissions

cc: Subject: Re: [PATCH] For allowing xalan to read property files without opening 11/15/2002 08:30 upcontainer

Re: [PATCH] For allowing xalan to read property files without opening upcontainer permissions

To: [EMAIL PROTECTED] M> cc: [EMAIL PROTECTED] Sent by: Subject: Re: [PATCH] For allowing xalan to read property files without opening up [EMAIL PROTECTED] container

Re: [PATCH] For allowing xalan to read property files without opening upcontainer permissions

EMAIL PROTECTED]To: [EMAIL PROTECTED] > M> cc: [EMAIL PROTECTED] > Sent by: Subject: Re: [PATCH] For allowing >xalan to read property files without opening up > [EMAIL PROTECTE

Re: [PATCH] For allowing xalan to read property files without opening up container permissions

TECTED] Sent by: Subject: Re: [PATCH] For allowing xalan to read property files without opening up [EMAIL PROTECTED] container permi

Re: [PATCH] For allowing xalan to read property files without opening up container permissions

[EMAIL PROTECTED] M> cc: [EMAIL PROTECTED] Sent by: Subject: Re: [PATCH] For allowing xalan to read pro

Re: [PATCH] For allowing xalan to read property files without opening up container permissions

Hi, I remember running into this problem with the Petstore application and getting around it by opening up the permissions. But we, Santiago and I, discussed changing Xalan so it would use reasonable defaults if it couldn't read the output properties file. For some reason, we never got around to

Re: patch

Even though I'm in the process of replacing that code, I would really like to see these patches applied. Unfortunately I won't have any time to do it myself for the next couple of weeks. Is it possible one of the other developers might be able to do it? -scott

Re: [PATCH] Bug 4603 (long)

I just wrote: [[ I've just submitted a patch for Bugzilla bug 4603 . Thanks to Ilene Seeleman and Morris Kwan who helped by reviewing the patch. ]] With apologies to Ilene, that should be "Seelemann"! Thanks, Henry

Re: [Patch-XalanJ] patch for bug #10009

Hi Pavani, Sorry I didn't follow up on this on xalan-j-users right away. I've read section 16.1 of XSLT 1.0 ("XML Output Method") [1] a little more carefully, and there's one passage that I'm a little concerned about; it reads as follows: [[ The xml output method should use an algorithm

Re: [PATCH] build.xml missing parser.jar for xsltc

Hi Scott, Try using build.bat, it does some initial setup, if your not using build.bat let us know. I've been building and using XSLTC for sometime without problems. What build target do you specify? You need to buid XSLTC separately, it does not automatically get build with Xalan. "

RE: [PATCH] fixed imports/includes mixup

that for these last two patches. Cheers, - Gulli > -Original Message- > From: John Howard [mailto:[EMAIL PROTECTED]] > Sent: 4. september 2001 17:31 > To: '[EMAIL PROTECTED]' > Subject: RE: [PATCH] fixed imports/includes mixup > > > Hi Gulli! &g

Re: [PATCH] fixed imports/includes mixup

Hi, John's point is well taken. Even though I have commit permission, I'd like to wait for one of our engineers to check the patch. Tom John Howard wrote: > Hi Gulli! > > I'm a fellow xsltc contributor - the kind that doesn't have commit > priviliges. > > Right now I think a couple of the comm

RE: [PATCH] fixed imports/includes mixup

Hi Gulli! I'm a fellow xsltc contributor - the kind that doesn't have commit priviliges. Right now I think a couple of the commiters are on vacation so your mailing-list posted patch might get lost (I went away for 2 weeks in August and had ~700 posts to sort through). My experience is that if y

RE: [PATCH] fixed property names and other typos -- oops!

Well, it's attached this time anyway! :) Sorry about the double posting. - Gulli > -Original Message- > From: Gunnlaugur Thor Briem [mailto:[EMAIL PROTECTED]] > Sent: 2. september 2001 13:57 > To: [EMAIL PROTECTED] > Subject: [PATCH] fixed property names and other typos > > > H

Re: PATCH: xalan portability fix

Cool -- I'll add it to the CVS repository. Thanks! Dave Jeff Garzik cc:

RE: PATCH for 2343 - typecheck error invoking name(...) with templat e parameter arg

); +_type = Type.NodeSet; +} return Type.String; } But is a conversion to a NodeSet better than a Node? > -Original Message- > From: Ovidiu Predescu [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 28, 2001 7:54 PM > To: John Howard > C

Re: PATCH for 2343 - typecheck error invoking name(...) with templat e parameter arg

Somebody else, more knowledgeable with XSLTC than me, should comment on your patch. However after looking at your patch, I don't understand why would we do a cast to NodeSet for ReferenceType nodes, but not for the other types? And another thing, really a style issue, why not writing the code li

Re: [PATCH] org.apache.xalan.templates.OutputProperties.java : Fixes setting for JDK 1.x

Padraig -- I did see this before and it is on my list. I've been having a few challenges here in getting my PC upgraded but that seems to be behind me so I should get to this in the near future. Could you please enter this into bugzilla so that it can be tracked? Thanks, Gary Padraig O'hIcead