You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Elena Litani <el...@ca.ibm.com> on 2004/01/19 23:22:41 UTC
[ANN]: Next Xerces Release...
I wanted to let you know that the next Xerces release is planned for Jan.
28.
This release will be the last one that supports JDK 1.1 (a note will be
added to the docs to specify that). After this release, we plan to start
checking in code that relies on JDK 1.2.
This week the committers are working on the following:
- Adding support for XML Catalogs
- Fixing DOM Level 3 bugs (including adding well-formed feature for
serializer)
- Applying XML Schema errata and fixing some schema bugs.
If you are willing to help out with the release, please look into Bugzilla
and assign bugs you want to fix to yourself.
We should aim to check in all the code by Jan. 27.
Thank you,
--
Elena Litani/ IBM Toronto
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: [ANN]: Next Xerces Release...
Posted by Elliotte Rusty Harold <el...@metalab.unc.edu>.
At 5:22 PM -0500 1/19/04, Elena Litani wrote:
>I wanted to let you know that the next Xerces release is planned for Jan.
>28.
>
>This release will be the last one that supports JDK 1.1 (a note will be
>added to the docs to specify that). After this release, we plan to start
>checking in code that relies on JDK 1.2.
>
Is there any possibility to getting a branch that will apply bug
fixes for Java 1.1 in the future? I'm certainly OK with not adding
new features for 1.1. However, I'd very much like to be able to merge
in any fixes for bugs that are discovered after the 28th.
--
Elliotte Rusty Harold
elharo@metalab.unc.edu
Effective XML (Addison-Wesley, 2003)
http://www.cafeconleche.org/books/effectivexml
http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Serializer questions
Posted by Michael Glavassevich <mr...@apache.org>.
Hi Lucian,
I've put a fix in CVS for Bugzilla 26157. I don't know what the plans are
for 'format-pretty-print' but given that we want to release Xerces next
week it's not likely to be in this release.
On Fri, 23 Jan 2004, Lucian Holland wrote:
> Hi,
>
> We're using Xerces as part of a product we're developing, and we'd ideally
> like to be able to use the DOM3 Serialization code to handle serialization
> rather than going through the Xerces-specific classes. There are currently
> a couple of issues that are preventing us from doing this, and I was just
> wondering if it was possible to get an indication of whether these were
> likely to be addressed for the upcoming release, so that we can decide
> whether or not to switch back to using the Xerces-specific serialization
> code.
>
> The first is one that I have raised as a bug (26157) - writeToURI and
> write methods don't appear to be able to handle file URIs. I have
> submitted a patch of sorts for this.
>
> The second is that the "format-pretty-print" configuration does not
> currently appear to be supported, although the XMLSerializer does seem to
> support something like this through the OutputFormat object. Is this
> likely to be supported at any time in the near future?
>
> Many thanks,
>
> Lucian
---------------------------
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Serializer questions
Posted by Lucian Holland <le...@decisionsoft.com>.
Hi,
We're using Xerces as part of a product we're developing, and we'd ideally
like to be able to use the DOM3 Serialization code to handle serialization
rather than going through the Xerces-specific classes. There are currently
a couple of issues that are preventing us from doing this, and I was just
wondering if it was possible to get an indication of whether these were
likely to be addressed for the upcoming release, so that we can decide
whether or not to switch back to using the Xerces-specific serialization
code.
The first is one that I have raised as a bug (26157) - writeToURI and
write methods don't appear to be able to handle file URIs. I have
submitted a patch of sorts for this.
The second is that the "format-pretty-print" configuration does not
currently appear to be supported, although the XMLSerializer does seem to
support something like this through the OutputFormat object. Is this
likely to be supported at any time in the near future?
Many thanks,
Lucian
--
Lucian Holland, Software Engineer +44-1865-203192
DecisionSoft Limited http://www.decisionsoft.com
XML Development and Services
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org