Hi Santiago,
How much time do you think is required to address 1, 2 & 3?
I know that there are performance issues for XSLTC that have been fixed in
cvs but
have not been officially published yet, so one motivation for doing a
release now is
to get those fixes out there. Also, looking at the description of the
changes you're
working on, we might want to do a Xalan Java 2.5.2 now, then a Xalan Java
2.6 down
the road (end of year?) where we would publish this new function and also
move up
to the latest Xerces Java.
What do you think?
Sarah McNamara
----- Forwarded by Sarah McNamara/Toronto/IBM on 10/16/2003 07:07 PM -----
Santiago
Pericas-Geertsen To: [EMAIL PROTECTED]
<Santiago.PericasGeerts cc:
[EMAIL PROTECTED]> Subject: Re: Xalan Java
2.5.2
10/16/2003 05:59 PM
Please respond to
xalan-dev
Sarah,
I think there are some outstanding bugs/enhancements that I would like
to see fixed in XSLTC 2.5.2. We are at a point where we are encouraging
people to use XSLTC, however there's important functionally missing when
compared to Xalan. Off top of my head:
1. Dynamic support to resolve external Java calls (i.e. dynamic
alternative to xsltc:cast()).
2. Support for DOM and DOM fragments as parameters to a stylesheet.
3. URIResolvers and general mechanism to resolve relative URIs is not
compatible with Xalan.
I have developers looking at 1 and 2, and I have personally been
working on 3.
One possibility is do a 2.5.2 followed by a 2.5.3 in the near future.
However, it is not clear to me that we should do this simply because
it's due.
To summarize, I believe we should not miss the opportunity to address
1-3 in the next release, even if that means waiting a bit more.
-- Santiago
On Thu, 2003-10-16 at 17:32, Sarah McNamara wrote:
>
> Back in August there was a question posted to xalan-j-users regarding
> another
> release. Henry Zongaro responded to the query and suggested a
mid-October
> release
> (http://marc.theaimsgroup.com/?l=xalan-j-users&m=106193733114926&w=2)
>
> So....seeing as it is mid-October and there has been quite a number of
> patches
> applied and bugs fixed in cvs, we'd like to see if we can put out a Xalan
> Java
> maintenance release early next week. The release would be called Xalan
> Java 2.5.2.
>
> We'd like to freeze the content of this release tomorrow, October 17, at
> 19:00 UTC
> (15:00 PM EDT) if there are no concerns from any of the committers. Then
> we'll tag
> the files and start the test and packaging process.
>
> Sarah McNamara
>
