Nabble - Apache XML - General

XSD: Allow any combination of subelements

2009-11-15T06:35:47Z

Hallo!

I'm trying to represent a mathematical formula with XML and cannot
find the correct schema definition.

I.e:
<formula>
<plus>
<minus>
..
</minus>
<plus>
..
</plus>
<minus>
..
</minus>
</plus>
</formula>

What I want is that, for example, <plus> can have any number of
unordered <plus> and <minus> elements.

This does not work:
<xsd:complexType name="plus">
<xsd:sequence>
<xsd:choice>
<xsd:element name="plus" type="plus"></xsd:element>
<xsd:element name="minus" type="minus"></xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>

Thanks,
Ralph

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

assistance with Apache Forrest

2009-11-01T20:04:38Z

I did some research to find the ASF projects that
manage their websites with Apache Forrest, and am
sending similar email to each project's dev mail list.
Already sent to the Xindice sub-project.

The purposes of this email are to remind people
about some of the useful facilities of Forrest,
and also alert them to discussion about the status
and future directions of Forrest, and to appeal for
people to assist Forrest.

--- oOo ---

These are useful facilities to assist with developing
and managing a Forrest solution for your project's website.

"How to deploy documentation with the Forrestbot
svn workstage"
This explains how the Forrest project manages our
own documentation.
http://forrest.apache.org/howto-forrestbot-svn.html

"Generate an ASF mirrors page using interactive web form"
http://forrest.apache.org/docs/dev/howto/howto-asf-mirror.html

"ForrestBar - Firefox toolbar to ease navigation
and search of Forrest resources"
http://forrest.apache.org/tools/forrestbar.html

"How to do development with Apache Forrest"
http://forrest.apache.org/howto-dev.html

"Frequently Asked Questions"
http://forrest.apache.org/faq.html

"The Anakia output plugin"
This was developed to assist the old Incubator
website to stop using Forrest and export all content
to an Anakia "xdoc" format. From there it could used
by an Anakia-based build system, or be further transformed.
http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.output.Anakia/

As usual, if you need further assistance with anything
then please ask on the Forrest mail lists.

--- oOo ---

There is discussion currently underway on the Forrest
dev mail list about the current status and future
direction of Forrest.
http://thread.gmane.org/gmane.text.xml.forrest.devel/27325

If anyone can assist Forrest, in any capacity, then
please do.

-David

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: Query on crimson.jar

2009-10-16T13:28:12Z

Hi,

There hasn't been any development on Crimson in years. It is a dead project, replaced by Xerces-J. At this point you're better off switching (if you can) to Xerces-J or just relying on the JAXP API in a later JDK which likely contains Xerces-J or some derivative of it.

Thanks.

Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@...
E-mail: mrglavas@...

sayantan mitra <sayantanm@...> wrote on 10/15/2009 02:56:29 PM: > Hi,
>
> Wanted to check if the Crimson.jar issue as mentioned by http: > //bugs.sun.com/bugdatabase/view_bug.do?bug_id=4766061 has been > rectified ? If so can you please tell me which version of JDK has > the fix. Also can you send me a copy of the jar at my id. Many thanks.
> Regards,
> Sayantan

Query on crimson.jar

2009-10-15T11:56:29Z

Hi,

Wanted to check if the Crimson.jar issue as mentioned by http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4766061 has been rectified ? If so can you please tell me which version of JDK has the fix. Also can you send me a copy of the jar at my id. Many thanks.

Regards,

Sayantan

Moving Xang to the Attic

2009-10-12T01:38:24Z

Folks,

this is an heads-up to let you know that the XML PMC has voted to move
Xang to the Attic, and I am hereby requesting the Attic PMC to take
ownership of the issue and start the move in the upcoming days. In the
meantime, if you need any further information, please do not hesitate
to ask.

Thanks,

--
Gianugo Rabellino
Sourcesense, making sense of Open Source: http://www.sourcesense.com
(blogging at http://www.rabellino.it/blog/)

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: More AxKit Retirement

2009-08-30T23:02:38Z

Oops, two different distribution directories. Anyway, I've copied the
HEADER.html over so we have it in both places.

On 29.08.2009 00:24:29 Greg Reddin wrote:

> > On 26.08.2009 18:59:29 Greg Reddin wrote:
> >> On Thu, Aug 13, 2009 at 9:45 PM, Greg Reddin<gredbug@...> wrote:
> >> > I also have a HEADER.html file for the axkit dist directory, but I
> >> > would need permissions to copy it there. It is attached to this
> >> > ticket.
> >> >
> >> > https://issues.apache.org/jira/browse/ATTIC-37
> >> >
> >> > If you would place this file in
> >> > /www/www.apache.org/dist/xml/axkit/HEADER.html and let me know I'd
> >> > appreciate it.
>
> Hmm, sorry to bother again, but it looks like the file made it into
> /www/xml.apache.org/dist/xml/axkit/HEADER.html, and not
> /www/www.apache.org/dist/xml/axkit/HEADER.html. I think you'll have to
> update it in the www.apache.org directory for it to sync to the dist
> site. Am I misdirected?
>
> Thanks,
> Greg

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: More AxKit Retirement

2009-08-28T15:24:29Z

> On 26.08.2009 18:59:29 Greg Reddin wrote:
>> On Thu, Aug 13, 2009 at 9:45 PM, Greg Reddin<gredbug@...> wrote:
>> > I also have a HEADER.html file for the axkit dist directory, but I
>> > would need permissions to copy it there. It is attached to this
>> > ticket.
>> >
>> > https://issues.apache.org/jira/browse/ATTIC-37
>> >
>> > If you would place this file in
>> > /www/www.apache.org/dist/xml/axkit/HEADER.html and let me know I'd
>> > appreciate it.

Hmm, sorry to bother again, but it looks like the file made it into
/www/xml.apache.org/dist/xml/axkit/HEADER.html, and not
/www/www.apache.org/dist/xml/axkit/HEADER.html. I think you'll have to
update it in the www.apache.org directory for it to sync to the dist
site. Am I misdirected?

Thanks,
Greg

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: More AxKit Retirement

2009-08-28T00:37:06Z

Sorry, Grep, I missed that. Should be fixed now.

On 26.08.2009 18:59:29 Greg Reddin wrote:

> On Thu, Aug 13, 2009 at 9:45 PM, Greg Reddin<gredbug@...> wrote:
> > I also have a HEADER.html file for the axkit dist directory, but I
> > would need permissions to copy it there. It is attached to this
> > ticket.
> >
> > https://issues.apache.org/jira/browse/ATTIC-37
> >
> > If you would place this file in
> > /www/www.apache.org/dist/xml/axkit/HEADER.html and let me know I'd
> > appreciate it.
>
> *ping*
>
> Sorry to be a pest, but best I can tell, this hasn't been done yet.
> Can someone with appropriate permissions please add this file to the
> /www/www.apache.org/dist/xml/axkit/ directory on people.a.o?
>
> Thanks much!
> Greg
>

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: More AxKit Retirement

2009-08-26T09:59:29Z

On Thu, Aug 13, 2009 at 9:45 PM, Greg Reddin<gredbug@...> wrote:
> I also have a HEADER.html file for the axkit dist directory, but I
> would need permissions to copy it there. It is attached to this
> ticket.
>
> https://issues.apache.org/jira/browse/ATTIC-37
>
> If you would place this file in
> /www/www.apache.org/dist/xml/axkit/HEADER.html and let me know I'd
> appreciate it.

*ping*

Sorry to be a pest, but best I can tell, this hasn't been done yet.
Can someone with appropriate permissions please add this file to the
/www/www.apache.org/dist/xml/axkit/ directory on people.a.o?

Thanks much!
Greg

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: AxKit Retirement

2009-08-17T13:07:44Z

Awesome. Thanks!

Greg

On Mon, Aug 17, 2009 at 2:06 PM, Jeremias Maerki<dev@...> wrote:

> Done in SVN. I'll see that the website is updated from there.
>
> On 17.08.2009 20:46:45 Greg Reddin wrote:
>> On Fri, Aug 14, 2009 at 1:56 AM, Jeremias Maerki<dev@...> wrote:
>> > Hi Greg
>> >
>> > Please just reply
>> > here and attach the patch. I'll try to address the XML website changes
>> > within the next couple of days.
>>
>> Sorry for the delayed response. I've attached the patch for the site
>> to the Attic JIRA ticket linked below:
>>
>> https://issues.apache.org/jira/browse/ATTIC-36
>>
>> Please let me know when this is done or if you have any questions and
>> we'll proceed.
>>
>> Thanks,
>> Greg
>
>
>
> Jeremias Maerki
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: AxKit Retirement

2009-08-17T12:06:37Z

Done in SVN. I'll see that the website is updated from there.

On 17.08.2009 20:46:45 Greg Reddin wrote:

> On Fri, Aug 14, 2009 at 1:56 AM, Jeremias Maerki<dev@...> wrote:
> > Hi Greg
> >
> > Please just reply
> > here and attach the patch. I'll try to address the XML website changes
> > within the next couple of days.
>
> Sorry for the delayed response. I've attached the patch for the site
> to the Attic JIRA ticket linked below:
>
> https://issues.apache.org/jira/browse/ATTIC-36
>
> Please let me know when this is done or if you have any questions and
> we'll proceed.
>
> Thanks,
> Greg

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: AxKit Retirement

2009-08-17T11:46:45Z

On Fri, Aug 14, 2009 at 1:56 AM, Jeremias Maerki<dev@...> wrote:
> Hi Greg
>
> Please just reply
> here and attach the patch. I'll try to address the XML website changes
> within the next couple of days.

Sorry for the delayed response. I've attached the patch for the site
to the Attic JIRA ticket linked below:

https://issues.apache.org/jira/browse/ATTIC-36

Please let me know when this is done or if you have any questions and
we'll proceed.

Thanks,
Greg

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: AxKit Retirement

2009-08-13T23:56:25Z

Hi Greg

I don't think we have a tracker for XML in general. Please just reply
here and attach the patch. I'll try to address the XML website changes
within the next couple of days. Thanks for handling the mothballing of
AxKit!

On 13.08.2009 22:13:50 Greg Reddin wrote:
> Hi,
>
> I'm working on behalf of the Apache Attic to help with the AxKit
> retirement. I have a suggested patch for the xml.apache.org website
> that will help to note the AxKit project is retired. Should I submit
> the patch here or is there a tracking system you'd prefer me to use?
>
> Thanks,
> Greg Reddin

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

More AxKit Retirement

2009-08-13T19:45:19Z

I also have a HEADER.html file for the axkit dist directory, but I
would need permissions to copy it there. It is attached to this
ticket.

https://issues.apache.org/jira/browse/ATTIC-37

If you would place this file in
/www/www.apache.org/dist/xml/axkit/HEADER.html and let me know I'd
appreciate it.

Thanks,
Greg

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

AxKit Retirement

2009-08-13T13:13:50Z

Hi,

I'm working on behalf of the Apache Attic to help with the AxKit
retirement. I have a suggested patch for the xml.apache.org website
that will help to note the AxKit project is retired. Should I submit
the patch here or is there a tracking system you'd prefer me to use?

Thanks,
Greg Reddin

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

FOP - Escaped HTML

2009-08-11T17:31:09Z

Hi All

I need your help ... I am generating PDF out of my reports using Apache FOP. Following is the flow of actions ..

Report data => XML => XSL-FO => PDF ...

Now the report can have html formatted data ... and therefore XML generated out of it has ESCAPED html ... I use JAXB marshaller and the marshaller by default escapes all the angle brackets etc ...
Is there any way to either instruct marshaller so that it does not escape html OR if there is anyway I can UNSCAPE these in XSLT?

Thanks
-Zac

Re: Apache crimson 1.1

2009-06-08T19:16:29Z

Hi,

Like many open source projects there's "support" as long as there are volunteers maintaining the codebase. That dried up a long time ago for Crimson. The project has been dead / inactive for over 7 years. Xerces-J [1] is its successor and is actively maintained.

Thanks.

[1] http://xerces.apache.org/xerces2-j/

Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@...
E-mail: mrglavas@...

"Thomas Darren" <Darren.Thomas@...> wrote on 06/08/2009 05:26:21 AM: > HI,
>
> We are currently updating our database concerning software we have > in use, we require dates of when support finished for the software > or if the software is still live,
> It would be of great help if you could email me any details and > dates of apache crimson software regarding product end dates etc.
>
> Thanks
>
> Darren Thomas
>
> PactConfiguration Audit and Conformance
>
> Fujitsu
>
> Ffynnon Menter, Phoenix way, Enterprise Park, Swansea SA7 9HZ
>
> Tel: +44 (0)8703254167
>
> Email: Darren.thomas@...

Apache crimson 1.1

2009-06-08T02:26:21Z

HI,

We are currently updating our database concerning software we have in use, we require dates of when support finished for the software or if the software is still live,

It would be of great help if you could email me any details and dates of apache crimson software regarding product end dates etc.

Thanks

Darren Thomas

PactConfiguration Audit and Conformance

Fujitsu

Ffynnon Menter, Phoenix way, Enterprise Park, Swansea SA7 9HZ

Tel: +44 (0)8703254167

Email: Darren.thomas@...

Re: XML parse DOM Connection time out

2009-05-28T06:22:22Z

Looks like it is trying to obtain the declared DTD of the XML document and
can't access it. You should set up an XML catalog resolver to allow for
loading a local copy of the DTD rather than going out to the internet.

See:
http://xml.apache.org/commons/components/resolver/
http://xml.apache.org/mirrors.cgi#N1010F

Jake

On Thu, 28 May 2009 05:03:40 -0700 (PDT)
gnix infosoft noida <garg.mayur8@...> wrote:

>
> I created a document factory object and tried to parse an existing XML
> file....
>
> Here is my code
>
>File xmlFile = new File("C:/jboss-config.xml");
> DocumentBuilderFactory docFactory = DocumentBuilderFactory.newInstance();
> DocumentBuilder docBuilder = docFactory.newDocumentBuilder();
> Document doc = docBuilder.parse(xmlFile);
> int elementType = doc.getNodeType();
> switch(elementType)
> {
> case Node.ELEMENT_NODE:
> {
> String nodeElement = doc.getNodeName() ;
> if(nodeElement.equals("policy"))
> {
> Element policyElement = doc.createElement("policy_new");
> doc.appendChild(policyElement);
> break;
> }
> }
> }
>
> When I run the code I get the following error......
>
> java.net.ConnectException: Operation timed out: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at java.net.Socket.<init>(Unknown Source)
> at sun.net.NetworkClient.doConnect(Unknown Source)
> at sun.net.www.http.HttpClient.openServer(Unknown Source)
> at sun.net.www.http.HttpClient.openServer(Unknown Source)
> at sun.net.www.http.HttpClient.<init>(Unknown Source)
> at sun.net.www.http.HttpClient.<init>(Unknown Source)
> at sun.net.www.http.HttpClient.New(Unknown Source)
> at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
> Source)
> at java.net.URL.openStream(Unknown Source)
> at
> weblogic.apache.xerces.readers.DefaultReaderFactory.createReader(DefaultReaderFactory.java:149)
> at
> weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalEntity(DefaultEntityHandler.java:786)
> at
> weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalSubset(DefaultEntityHandler.java:583)
> at
> weblogic.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java:1161)
> at
> weblogic.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocumentScanner.java:2189)
> at
> weblogic.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScanner.java:2143)
> at
> weblogic.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatch(XMLDocumentScanner.java:856)
> at
> weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
> at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1147)
> at
> weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:203)
> at
> weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:144)
> at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:161)
>
> Please help
>
> --
> View this message in context:
>http://www.nabble.com/XML-parse-DOM-Connection-time-out-tp23760394p23760394.html
> Sent from the Apache XML - General mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
>For additional commands, e-mail: general-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

XML parse DOM Connection time out

2009-05-28T05:03:39Z

I created a document factory object and tried to parse an existing XML file....

Here is my code

File xmlFile = new File("C:/jboss-config.xml");
DocumentBuilderFactory docFactory = DocumentBuilderFactory.newInstance();
DocumentBuilder docBuilder = docFactory.newDocumentBuilder();
Document doc = docBuilder.parse(xmlFile);
int elementType = doc.getNodeType();
switch(elementType)
{
case Node.ELEMENT_NODE:
{
String nodeElement = doc.getNodeName() ;
if(nodeElement.equals("policy"))
{
Element policyElement = doc.createElement("policy_new");
doc.appendChild(policyElement);
break;
}
}
}

When I run the code I get the following error......

java.net.ConnectException: Operation timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.net.URL.openStream(Unknown Source)
at weblogic.apache.xerces.readers.DefaultReaderFactory.createReader(DefaultReaderFactory.java:149)
at weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalEntity(DefaultEntityHandler.java:786)
at weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalSubset(DefaultEntityHandler.java:583)
at weblogic.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java:1161)
at weblogic.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocumentScanner.java:2189)
at weblogic.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScanner.java:2143)
at weblogic.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatch(XMLDocumentScanner.java:856)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1147)
at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:203)
at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:144)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:161)

Please help

Re: Is Crimson compatible with JDK 1.5?

2009-03-12T00:35:38Z

Crimson is retired and horribly outdated. If there's a task to move to
JDK 1.5 and your question pops up, I can only recommend to migrate to a
new XML parser (like Apache Xerces-J) if you have to interact directly
with a particular XML parser. Better is to rely just on the JAXP API if
that's possible.

On 11.03.2009 17:51:20 ravish mody wrote:

> Hi,
>
> I want to know is Crimson compatible with JDK 1.5 or not?
>
> Regards,
> Oracle <http://www.oracle.com/>
> Ravish Mody | Support Engineer
> Oracle Global Support
> Green Oracle <http://www.oracle.com/commitment> Oracle is
> committed to developing practices and products that help protect the
> environment
>
>
>
>

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Is Crimson compatible with JDK 1.5?

2009-03-11T09:51:20Z

Hi,

I want to know is Crimson compatible with JDK 1.5 or not?

Regards,

Ravish Mody | Support Engineer
Oracle Global Support

Oracle is committed to developing practices and products that help protect the environment

oracle_sig_logo.gif (906 bytes) Download Attachment
green-for-email-sig_0.gif (490 bytes) Download Attachment

Re: XML website status

2009-01-29T23:16:43Z

Good point. If noone beats me to it, I'll touch up the Commons site in
the next few days and see to it that I can become usable once more. A
short test showed that there is something DocBook-related that might
need a second glance and never Forrest versions have a problem with the
sources.

On 30.01.2009 04:35:55 Michael Glavassevich wrote:

>
> Jeremias Maerki <dev@...> wrote on 01/29/2009 04:24:52 PM:
>
> > With the permissions fixed, I've now made a little progress cleaning up
> > some more directories. Still some way to go but getting there...
> >
> > Next step is figuring out if there's really still a cron job for
> > updating the XML Commons website as the readme says.
>
> Probably time that the XML Commons website moved under xerces.apache.org,
> with a redirect from the old site (http://xml.apache.org/commons/ ->
> http://xerces.apache.org/xml-commons/). I see it's already gone from the
> project list on the main xml.apache.org page.
>
> > I doubt it, but we'll see what happens now that I've made a few small
> > test modifications.
> >
> > On 03.01.2009 23:59:42 Michael Glavassevich wrote:
> > > Jeremias Maerki <dev@...> wrote on 01/01/2009 12:13:34
> PM:
> > >
> > > > I've tried to update the XML website today but was quite unlucky. I
> > > > currently can't do a "svn up" to update the XML website because
> various
> > > > things are in the way:
> > > > - files and directories with bad permissions from "apbackup"
> > > > - Missing .svn directories due to unclean website updates
> > > > - .svn directories that should not be there
> > > > - a mix of the above
> > > >
> > > > Anyway, I've notified the necessary people to do the necessary
> cleanups.
> > > > After that I'll ask infra to fix/remove the bad "apbackup"
> permissions.
> > >
> > > We have the same issue with the Xerces website (which I plan to update
> > > soon). Just opened a JIRA against infra for that.
> > >
> > > > Finally, I should be able to get the XML website back into a usable
> > > > state. I'll stay on it.
> > > >
> > > > Jeremias Maerki
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: general-unsubscribe@...
> > > > For additional commands, e-mail: general-help@...
> > >
> > > Thanks.
> > >
> > > Michael Glavassevich
> > > XML Parser Development
> > > IBM Toronto Lab
> > > E-mail: mrglavas@...
> > > E-mail: mrglavas@...
> >
> > Jeremias Maerki
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@...
> > For additional commands, e-mail: general-help@...
>
> Thanks.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@...
> E-mail: mrglavas@...

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: XML website status

2009-01-29T19:35:55Z

Jeremias Maerki <dev@...> wrote on 01/29/2009 04:24:52 PM: > With the permissions fixed, I've now made a little progress cleaning up > some more directories. Still some way to go but getting there... > > Next step is figuring out if there's really still a cron job for > updating the XML Commons website as the readme says.

Probably time that the XML Commons website moved under xerces.apache.org, with a redirect from the old site (http://xml.apache.org/commons/ -> http://xerces.apache.org/xml-commons/). I see it's already gone from the project list on the main xml.apache.org page.

> I doubt it, but we'll see what happens now that I've made a few small
> test modifications. > > On 03.01.2009 23:59:42 Michael Glavassevich wrote: > > Jeremias Maerki <dev@...> wrote on 01/01/2009 12:13:34 PM: > > > > > I've tried to update the XML website today but was quite unlucky. I > > > currently can't do a "svn up" to update the XML website because various > > > things are in the way: > > > - files and directories with bad permissions from "apbackup" > > > - Missing .svn directories due to unclean website updates > > > - .svn directories that should not be there > > > - a mix of the above > > > > > > Anyway, I've notified the necessary people to do the necessary cleanups. > > > After that I'll ask infra to fix/remove the bad "apbackup" permissions. > > > > We have the same issue with the Xerces website (which I plan to update > > soon). Just opened a JIRA against infra for that. > > > > > Finally, I should be able to get the XML website back into a usable > > > state. I'll stay on it. > > > > > > Jeremias Maerki > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: general-unsubscribe@... > > > For additional commands, e-mail: general-help@... > > > > Thanks. > > > > Michael Glavassevich > > XML Parser Development > > IBM Toronto Lab > > E-mail: mrglavas@... > > E-mail: mrglavas@... > > Jeremias Maerki > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@... > For additional commands, e-mail: general-help@...

Thanks.
Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@...
E-mail: mrglavas@...

Re: XML website status

2009-01-29T13:24:38Z

With the permissions fixed, I've now made a little progress cleaning up
some more directories. Still some way to go but getting there...

Next step is figuring out if there's really still a cron job for
updating the XML Commons website as the readme says. I doubt it, but
we'll see what happens now that I've made a few small test modifications.

On 03.01.2009 23:59:42 Michael Glavassevich wrote:

> Jeremias Maerki <dev@...> wrote on 01/01/2009 12:13:34 PM:
>
> > I've tried to update the XML website today but was quite unlucky. I
> > currently can't do a "svn up" to update the XML website because various
> > things are in the way:
> > - files and directories with bad permissions from "apbackup"
> > - Missing .svn directories due to unclean website updates
> > - .svn directories that should not be there
> > - a mix of the above
> >
> > Anyway, I've notified the necessary people to do the necessary cleanups.
> > After that I'll ask infra to fix/remove the bad "apbackup" permissions.
>
> We have the same issue with the Xerces website (which I plan to update
> soon). Just opened a JIRA against infra for that.
>
> > Finally, I should be able to get the XML website back into a usable
> > state. I'll stay on it.
> >
> > Jeremias Maerki
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@...
> > For additional commands, e-mail: general-help@...
>
> Thanks.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@...
> E-mail: mrglavas@...

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: XML website status

2009-01-03T14:59:42Z

Jeremias Maerki <dev@...> wrote on 01/01/2009 12:13:34 PM: > I've tried to update the XML website today but was quite unlucky. I > currently can't do a "svn up" to update the XML website because various > things are in the way: > - files and directories with bad permissions from "apbackup" > - Missing .svn directories due to unclean website updates > - .svn directories that should not be there > - a mix of the above > > Anyway, I've notified the necessary people to do the necessary cleanups. > After that I'll ask infra to fix/remove the bad "apbackup" permissions.

We have the same issue with the Xerces website (which I plan to update soon). Just opened a JIRA against infra for that.
> Finally, I should be able to get the XML website back into a usable > state. I'll stay on it. > > Jeremias Maerki > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@... > For additional commands, e-mail: general-help@...

Thanks.
Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@...
E-mail: mrglavas@...

XML website status

2009-01-01T09:13:34Z

I've tried to update the XML website today but was quite unlucky. I
currently can't do a "svn up" to update the XML website because various
things are in the way:
- files and directories with bad permissions from "apbackup"
- Missing .svn directories due to unclean website updates
- .svn directories that should not be there
- a mix of the above

Anyway, I've notified the necessary people to do the necessary cleanups.
After that I'll ask infra to fix/remove the bad "apbackup" permissions.
Finally, I should be able to get the XML website back into a usable
state. I'll stay on it.

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)

2008-11-11T22:45:38Z

Yes, Michael, I was the driving force behind that. I wanted to make sure
that we've made an informed decision before dropping support for one JDK
or another. Developers obviously like the new stuff but users are
sometimes stuck with old stuff. It often takes them a bit longer to
migrate although they usually skip a generation when they migrate.

Anyway. First, we talked about the questions we wanted to ask:
http://markmail.org/message/y6h6lfzcupbvuww3
Then I set up the survey with one of the online survey service providers.
I chose one that was free.
http://markmail.org/message/xz72bqpkqy6dg5l5
At the end of the survey, I downloaded the data and visualized selected
items with OpenOffice. All put together that resulted in the Wiki page
mentioned by Ludger Buenger:
http://wiki.apache.org/xmlgraphics/UserPollOct2007

I believe this survey, though took some time and effort to do, was worth
it and it wasn't difficult to do. And I'll push for one again when we
want to drop Java 1.4 support within the XML Graphics project. I expect
it won't take too long until we do another as Java 1.4 has reached EOL
last month. It's going to be interesting to see how the survey results
change over time. But given the small data base, don't assume the
results are 100% representative.

HTH

On 12.11.2008 06:42:33 Michael Glavassevich wrote:

>
> Any idea how this poll was done? A form you could submit on a website?
> Jeremias, seeing your name as the last editor on the Wiki I'm guessing you
> had something to do with it. Was this poll easy to set up?
>
> Thanks.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@...
> E-mail: mrglavas@...
>
> "Ludger Buenger" <ludger.buenger@...> wrote on 11/11/2008
> 09:34:08 AM:
>
> > Before Advancing beyond 1.3 I?d suggest to maybe initiate a usage
> > poll analogous to http://wiki.apache.org/xmlgraphics/UserPollOct2007
> > to get an overview which JDK version is still in use and required by
> > Xerces-J users.
> >
> > That would give the community a foundation to base a good decision upon.
> >
> >
> > From: Michael Glavassevich [mailto:mrglavas@...]
> > Sent: Monday, November 10, 2008 4:52 AM
> > To: j-dev@...; j-users@...
> > Cc: general@...
> > Subject: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.
> > 3? 1.4? in the future)
> >
> > Hi all,
> >
> > (including general@... on the cc list to hopefully reach
> > a wider audience)
> >
> > I would like to propose that we officially drop support for JDK 1.2
> > in the next release of Xerces-J. Though the documentation [1] states
> > that Xerces supports JDK 1.2 it has been years since we have built
> > or tested binaries with this level. All of the recent releases were
> > built and tested with JDK 1.3. It was brought to my attention that
> > the code [2] since at least 2006 has had a dependency on APIs
> > introduced in JDK 1.3. So we inadvertently moved on awhile ago. It
> > seems this has not been a practical issue for most users since we've
> > received no posts on these lists about it and received no other bug
> > reports. It's not clear that there would be much benefit in
> > restoring JDK 1.2 compatibility at this point. It's been out of
> > service for years and looking around Apache it seems most projects
> > run on JDK 1.4 or higher with some of the stragglers [3][4] below
> > that moving up soon.
> >
> > If you have serious concerns regarding Xerces abandoning JDK 1.2
> > support please send an email to the j-dev@... mailing
> > list, specifying why you can't use a higher level of JDK and what
> > parser features you are using.
> >
> > While on the subject I wonder what the community would think of us
> > eventually dropping support for JDK 1.3 and possibly 1.4. There were
> > features introduced in JDK 1.4 and 5 which Xerces could benefit from
> > (e.g. NIO, java.lang.CharSequence, exception chaining, java.lang.
> > StringBuilder, java.util.concurrent.*, etc...). That's not something
> > I'm proposing today (or thinking of proposing for awhile) but would
> > like to hear feedback from users (please send to j-dev@xerces.
> > apache.org) who may still need new versions of Xerces which run on
> > JDK 1.3 and 1.4. It would also be nice hear from folks who've long
> > since moved on to Java 5 and beyond and would like to see Xerces
> > take advantage of JDK 1.4 and 5 features.
> >
> > Thanks.
> >
> > [1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-11
> > [2] http://issues.apache.org/jira/browse/XERCESJ-1297
> > [3] http://marc.info/?l=ant-dev&m=122596549809889&w=2
> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
> >
> > Michael Glavassevich
> > XML Parser Development
> > IBM Toronto Lab
> > E-mail: mrglavas@...
> > E-mail: mrglavas@...
> >
> > --
> > This message was scanned by ESVA and is believed to be clean.
> > Click here to report this message as spam.

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)

2008-11-11T22:07:57Z

Shane Curcuru <asf@...> wrote on 11/11/2008 08:08:50 AM: > +1 to dropping 1.2 support. > > Please - be sure that the main website clearly lists the last release we > think that Xerces worked on JDK version x.y. Xerces is ubiquitous, and > is used directly or within other products virtually everywhere. While > we don't need to spend developer time worrying about ancient JDK > versions, we should make it clear where people who have to stay on > legacy systems can get an appropriate release.
There's already an FAQ [1] and release notes [2] which say where we moved from JDK 1.1 to 1.2. We'll just add to it.
> I'd love it if we ensured that we feature a prominent link and host the > download for the zip/targz plus it's key file for "the last known good > Xerces with JDK x.y" as we drop support for earlier releases.
If someone wants to pick up an old version they will always be in the archives [3].
> Thanks for bringing the item up! > > - Shane

Thanks.

[1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-11
[2] http://xerces.apache.org/xerces2-j/releases.html
[3] http://archive.apache.org/dist/xml/xerces-j/

Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@...
E-mail: mrglavas@...

RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)

2008-11-11T21:42:33Z

Any idea how this poll was done? A form you could submit on a website? Jeremias, seeing your name as the last editor on the Wiki I'm guessing you had something to do with it. Was this poll easy to set up?

Thanks.

Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@...
E-mail: mrglavas@...

"Ludger Buenger" <ludger.buenger@...> wrote on 11/11/2008 09:34:08 AM: > Before Advancing beyond 1.3 I’d suggest to maybe initiate a usage > poll analogous to http://wiki.apache.org/xmlgraphics/UserPollOct2007 > to get an overview which JDK version is still in use and required by > Xerces-J users.
>
> That would give the community a foundation to base a good decision upon.
>
>
> From: Michael Glavassevich [mrglavas@...] > Sent: Monday, November 10, 2008 4:52 AM > To: j-dev@...; j-users@... > Cc: general@... > Subject: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1. > 3? 1.4? in the future)
>
> Hi all, > > (including general@... on the cc list to hopefully reach > a wider audience) > > I would like to propose that we officially drop support for JDK 1.2 > in the next release of Xerces-J. Though the documentation [1] states > that Xerces supports JDK 1.2 it has been years since we have built > or tested binaries with this level. All of the recent releases were > built and tested with JDK 1.3. It was brought to my attention that > the code [2] since at least 2006 has had a dependency on APIs > introduced in JDK 1.3. So we inadvertently moved on awhile ago. It > seems this has not been a practical issue for most users since we've > received no posts on these lists about it and received no other bug > reports. It's not clear that there would be much benefit in > restoring JDK 1.2 compatibility at this point. It's been out of > service for years and looking around Apache it seems most projects > run on JDK 1.4 or higher with some of the stragglers [3][4] below > that moving up soon. > > If you have serious concerns regarding Xerces abandoning JDK 1.2 > support please send an email to the j-dev@... mailing > list, specifying why you can't use a higher level of JDK and what > parser features you are using. > > While on the subject I wonder what the community would think of us > eventually dropping support for JDK 1.3 and possibly 1.4. There were > features introduced in JDK 1.4 and 5 which Xerces could benefit from > (e.g. NIO, java.lang.CharSequence, exception chaining, java.lang. > StringBuilder, java.util.concurrent.*, etc...). That's not something > I'm proposing today (or thinking of proposing for awhile) but would > like to hear feedback from users (please send to j-dev@xerces. > apache.org) who may still need new versions of Xerces which run on > JDK 1.3 and 1.4. It would also be nice hear from folks who've long > since moved on to Java 5 and beyond and would like to see Xerces > take advantage of JDK 1.4 and 5 features. > > Thanks. > > [1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-11 > [2] http://issues.apache.org/jira/browse/XERCESJ-1297 > [3] http://marc.info/?l=ant-dev&m=122596549809889&w=2 > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2 > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: mrglavas@... > E-mail: mrglavas@...
> > -- > This message was scanned by ESVA and is believed to be clean. > Click here to report this message as spam.

Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)

2008-11-11T21:30:46Z

Worth nothing that although Java 1.4 may have passed Sun's EOL date there are other JDK vendors who may have end of service dates that are still in the future. So it may be that a user who is still stuck on that JDK level is still getting support and bug fixes that they wouldn't be getting anymore for the Sun version. I wouldn't assume that the eventual releases out of Apache Harmony would bind themselves to Sun's dates either (for when they'd stop maintenance).

Thanks.

Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@...
E-mail: mrglavas@...

Jeremias Maerki <dev@...> wrote on 11/11/2008 08:59:38 AM: > On 11.11.2008 14:52:52 sebb wrote: > > On 11/11/2008, Shane Curcuru <asf@...> wrote: > > > +1 to dropping 1.2 support. > > > > +1 to dropping 1.2 > > > > +0 to dropping 1.3 > > > > I think 1.4 support should be kept if possible for a while yet. > > Agreed. Xerces is such a basic library and so many companies are still > stuck with Java 1.4 even though it's past EOL. > > > > Please - be sure that the main website clearly lists the last release we > > > think that Xerces worked on JDK version x.y. Xerces is ubiquitous, and is > > > used directly or within other products virtually everywhere. > While we don't > > > need to spend developer time worrying about ancient JDK > versions, we should > > > make it clear where people who have to stay on legacy systems can get an > > > appropriate release. > > > > +1 > > > > > I'd love it if we ensured that we feature a prominent link and host the > > > download for the zip/targz plus it's key file for "the last known good > > > Xerces with JDK x.y" as we drop support for earlier releases. > > > > > > > +1 > > > > > Thanks for bringing the item up! > > > > > > - Shane > > Jeremias Maerki > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@... > For additional commands, e-mail: general-help@...

Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)

2008-11-11T21:05:03Z

Xerces doesn't have maintenance releases in the sense that we'll ever have a 2.[x].y release after a 2.[x+1].0. The codebase is constantly moving forward with new development. It just happens that over some periods of time the only changes were bug fixes and minor improvements and if we have a release before something significant hits the trunk it ends up being a point release instead of the next in the series of 2.x. With the limited resources we have on the project (I find myself with less and less time for Xerces each year; the other developers have less than that) I'd say -1 to creating and maintaining branches ahead of time for hypothetical maintenance releases we may never have. I remember someone asking for a branch for JDK 1.1 based releases when we dropped support for that level. The need to have such releases never materialized. If there were to be a compelling reason to have one in the future the tags from the previous Xerces releases will always be there and we could create a branch from them if necessary. If it's just for the benefit of a handful of users (namely the individuals asking for the release) I would expect them to chip in in some way with patches and/or testing. If they really need it they'll help. If they're not willing to lift a finger then they don't need it badly enough yet.

As for moving past Java 1.3, it's not just the features we could be using from later JDKs to improve the code and the user base still on old JDKs which would factor into a decision. I would expect a future version of JAXP [1] is going to start using generics [2] and APIs only available in Java 5 and beyond. So it may get to a point where Xerces just has to jump to Java 5, 6 or ??? in order to keep up with JAXP. This already happened to JAXB. The 2.0 version of that spec is impossible to implement and use without Java 5. As some of you know we're currently working on an implementation of XML Schema 1.1 and one of the significant features introduced in this new version of XML Schema is assertions [3]. For this feature to be of value to users you basically need a full-blown XPath 2.0 evaluator. Most likely we're going to have to rely on another processor for the XPath support and that other library may have a dependency on a later version of Java. So there are other things which could push Xerces past Java 1.3 and those may be coming sooner than some folks can move to later JDKs.

Anyway, in the immediate future I only recommend that we officially drop support for JDK 1.2. So far the folks who've been responding seem to be on board with that.

Thanks.

[1] http://wiki.glassfish.java.net/Wiki.jsp?page=JaxpNextDiscussion
[2] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6472193
[3] http://www.w3.org/TR/xmlschema11-1/#cAssertions

Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@...
E-mail: mrglavas@...

nbeyer@... wrote on 11/11/2008 09:46:52 PM: > I doubt maintenance for the current codebase running on Java 1.3 would > be completely removed. I interpreted the original question as aimed at > new and future development. I don't want to speak for Michael, but > that's the way I read it. > > -Nathan > > On Tue, Nov 11, 2008 at 9:08 AM, Jacob Kjome <hoju@...> wrote: > > On Tue, 11 Nov 2008 09:36:26 -0500 > > "David Ezell" <David_E3@...> wrote: > >> > >> Well, one person's 4 is another person's 3. > >> > >> We're stuck on 1.3 for the foreseeable future. > >> > >> So -1 to drop 1.3. > > > > I partially agree with this. There's no reason 1.3 needs to be dropped for > > the current 2.x.x codebase. Why not maintain 2.x.x at 1.3 and move on to > > 3.x development which would be 1.5+ (or even 1.6+). Xerces2 is very > > stable. 1.3 and 1.4 users can continue to depend on it. I maintain the > > XMLC project, which is currently limited to JDK 1.3 anway. If critical > > issues are found in Xerces2, they can be fixed on the Xerces2 branch where > > 1.3 and 1.4 users can benefit. Of course, we can also expect that 1.3 and > > 1.4 users are in maintenance mode and won't require fancy new features. All > > new feature development can take place on the trunk, which will represent > > the Xerces3 codebase, and will be able to take advantage of all the latest > > JDK features. Who knows, maybe Sun can eventually drop the > > com.sun.apache.xerces stuff and migrate back to the original, stable, Xerces > > product once it is not limited by old VM's. > > > > Jake > > > >> > >> David Ezell > >> VeriFone > >> Chair, XML Schema WG > >> > >>> -----Original Message----- > >>> From: Schmidlin, Franck [Franck.Schmidlin@...] Sent: > >>> Tuesday, November 11, 2008 5:35 AM > >>> To: j-dev@...; j-users@... > >>> Cc: general@... > >>> Subject: RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? > >>> 1.4? in the future) > >>> > >>> > a new infusion of activity and interest. > >>> > >>> you betcha, most of us would be up in arms! > >>> > >>> I personally am stuck on 1.4.2 for the foreseeable future. > >>> > >>> So +1 to drop 1.2/3 support, but let's not get too drastic please. > >>> > >>> > >>> ______________________________ > >>> Franck Schmidlin > >>> Corporate Integration Consultant > >>> Northgate Public Services > >>> > >>> Please consider the environment before printing this e-mail > >>> > >>> > >>> -----Original Message----- > >>> From: nbeyer@... [nbeyer@...] On Behalf Of Nathan > >>> Beyer > >>> Sent: 11 November 2008 02:25 > >>> To: j-users@... > >>> Cc: j-dev@...; general@... > >>> Subject: Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? > >>> 1.4? in the future) > >>> > >>> +1 > >>> > >>> I'd suggest just jumping to Java 5 library, source and target > >>> compilation. I think this would give the project a new infusion > of activity > >>> and interest. > >>> > >>> -Nathan > >>> > >>> On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich > >>> <mrglavas@...> wrote: > >>> > Hi all, > >>> > > >>> > (including general@... on the cc list to hopefully reach a > > >>> > wider > >>> > audience) > >>> > > >>> > I would like to propose that we officially drop support for JDK 1.2 in > >>> > >>> > the next release of Xerces-J. Though the documentation [1] states that > >>> > >>> > Xerces supports JDK 1.2 it has been years since we have built or > > >>> > tested binaries with this level. All of the recent releases were built > >>> > >>> > and tested with JDK 1.3. It was brought to my attention that the code > > >>> > [2] since at least 2006 has had a dependency on APIs introduced in JDK > >>> > >>> > 1.3. So we inadvertently moved on awhile ago. It seems this has not > > >>> > been a practical issue for most users since we've received no posts on > >>> > >>> > these lists about it and received no other bug reports. It's not clear > >>> > >>> > that there would be much benefit in restoring JDK 1.2 compatibility at > >>> > >>> > this point. It's been out of service for years and looking around > > >>> > Apache it seems most projects run on JDK 1.4 or higher with some of > >>> the stragglers [3][4] below that moving up soon. > >>> > > >>> > If you have serious concerns regarding Xerces abandoning JDK 1.2 > > >>> > support please send an email to the j-dev@... > mailing > list, > >>> > specifying why you can't use a higher level of JDK and what > parser > >>> > features you are using. > >>> > > >>> > While on the subject I wonder what the community would think of us > > >>> > eventually dropping support for JDK 1.3 and possibly 1.4. There were > > >>> > features introduced in JDK 1.4 and 5 which Xerces could benefit from > >>> (e.g. > >>> > NIO, java.lang.CharSequence, exception chaining, > > >>> > java.lang.StringBuilder, java.util.concurrent.*, etc...). That's not > > >>> > something I'm proposing today (or thinking of proposing for > awhile) > but > >>> > would like to hear feedback from users (please send to > >>> > j-dev@...) who may still need new versions of Xerces > > >>> > which run on JDK 1.3 and 1.4. It would also be nice hear from > folks > who've > >>> > long since moved on to Java 5 and beyond and would like to see > >>> Xerces take advantage of JDK 1.4 and 5 features. > >>> > > >>> > Thanks. > >>> > > >>> > [1]http://xerces.apache.org/xerces2-j/faq-general.html#faq-11> >>> > [2]http://issues.apache.org/jira/browse/XERCESJ-1297> >>> > [3]http://marc.info/?l=ant-dev&m=122596549809889&w=2> >>> > [4]http://marc.info/?l=fop-user&m=119244442600564&w=2> >>> > > >>> > Michael Glavassevich > >>> > XML Parser Development > >>> > IBM Toronto Lab > >>> > E-mail: mrglavas@... > >>> > E-mail: mrglavas@... > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: j-dev-unsubscribe@... > >>> For additional commands, e-mail: j-dev-help@... > >>> > >>> > >>> > >>> Scanned for viruses by BlackSpider MailControl > >>> > >>> > >>> This email is sent on behalf of Northgate Information Solutions Limited > >>> and its associated companies ("Northgate") and is strictly > confidential and > >>> intended solely for the addressee(s). > >>> If you are not the intended recipient of this email you must: (i) not > >>> disclose, copy or distribute its contents to any other person nor use its > >>> contents in any way or you may be acting unlawfully; (ii) > contact Northgate > >>> immediately on +44 (0)1442 232424 quoting the name of the sender and the > >>> addressee then delete it from your system. > >>> > >>> Northgate has taken reasonable precautions to ensure that no viruses are > >>> contained in this email, but does not accept any responsibility once this > >>> email has been transmitted. You should scan attachments (if any) for > >>> viruses. > >>> > >>> Northgate Information Solutions Limited. Registered in England no. > >>> 06442582 - Northgate Information Solutions UK Limited. Registered in > >>> England no. 968498 - NorthgateArinso UK Limited. Registered in > England no. > >>> 1587537 - Moorepay Limited. Registered in England no. 891686 - > >>> Northgate Land & Property Solutions Limited - Registered in England no. > >>> 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding > Estate, Maylands > >>> Avenue, Hemel Hempstead, Hertfordshire HP2 4NW > >>> Northgate Managed Services Limited (NI). Registered in Northern Ireland > >>> no. NI032979 - LearnServe Limited (NI). Registered in Northern Ireland > >>> no. NI043825 Registered Office: Hillview House, 61 Church Road, > >>> Newtownabbey, Co. Antrim, BT36 7LQ > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: j-users-unsubscribe@... > >>> For additional commands, e-mail: j-users-help@... > >>> > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: j-users-unsubscribe@... > >> For additional commands, e-mail: j-users-help@... > >> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: j-users-unsubscribe@... > > For additional commands, e-mail: j-users-help@... > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: j-users-unsubscribe@... > For additional commands, e-mail: j-users-help@...

RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)

2008-11-11T06:34:08Z

Before Advancing beyond 1.3 I’d suggest to maybe initiate a usage poll analogous to http://wiki.apache.org/xmlgraphics/UserPollOct2007 to get an overview which JDK version is still in use and required by Xerces-J users.

That would give the community a foundation to base a good decision upon.

From: Michael Glavassevich [mailto:mrglavas@...]
Sent: Monday, November 10, 2008 4:52 AM
To: j-dev@...; j-users@...
Cc: general@...
Subject: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)

Hi all,

(including general@... on the cc list to hopefully reach a wider audience)

I would like to propose that we officially drop support for JDK 1.2 in the next release of Xerces-J. Though the documentation [1] states that Xerces supports JDK 1.2 it has been years since we have built or tested binaries with this level. All of the recent releases were built and tested with JDK 1.3. It was brought to my attention that the code [2] since at least 2006 has had a dependency on APIs introduced in JDK 1.3. So we inadvertently moved on awhile ago. It seems this has not been a practical issue for most users since we've received no posts on these lists about it and received no other bug reports. It's not clear that there would be much benefit in restoring JDK 1.2 compatibility at this point. It's been out of service for years and looking around Apache it seems most projects run on JDK 1.4 or higher with some of the stragglers [3][4] below that moving up soon.

If you have serious concerns regarding Xerces abandoning JDK 1.2 support please send an email to the j-dev@... mailing list, specifying why you can't use a higher level of JDK and what parser features you are using.

While on the subject I wonder what the community would think of us eventually dropping support for JDK 1.3 and possibly 1.4. There were features introduced in JDK 1.4 and 5 which Xerces could benefit from (e.g. NIO, java.lang.CharSequence, exception chaining, java.lang.StringBuilder, java.util.concurrent.*, etc...). That's not something I'm proposing today (or thinking of proposing for awhile) but would like to hear feedback from users (please send to j-dev@...) who may still need new versions of Xerces which run on JDK 1.3 and 1.4. It would also be nice hear from folks who've long since moved on to Java 5 and beyond and would like to see Xerces take advantage of JDK 1.4 and 5 features.

Thanks.

[1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-11
[2] http://issues.apache.org/jira/browse/XERCESJ-1297
[3] http://marc.info/?l=ant-dev&m=122596549809889&w=2
[4] http://marc.info/?l=fop-user&m=119244442600564&w=2

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@...
E-mail: mrglavas@...

--
This message was scanned by ESVA and is believed to be clean.
Click here to report this message as spam.

Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)

2008-11-11T05:59:38Z

On 11.11.2008 14:52:52 sebb wrote:
> On 11/11/2008, Shane Curcuru <asf@...> wrote:
> > +1 to dropping 1.2 support.
>
> +1 to dropping 1.2
>
> +0 to dropping 1.3
>
> I think 1.4 support should be kept if possible for a while yet.

Agreed. Xerces is such a basic library and so many companies are still
stuck with Java 1.4 even though it's past EOL.

> > Please - be sure that the main website clearly lists the last release we
> > think that Xerces worked on JDK version x.y. Xerces is ubiquitous, and is
> > used directly or within other products virtually everywhere. While we don't
> > need to spend developer time worrying about ancient JDK versions, we should
> > make it clear where people who have to stay on legacy systems can get an
> > appropriate release.
>
> +1
>
> > I'd love it if we ensured that we feature a prominent link and host the
> > download for the zip/targz plus it's key file for "the last known good
> > Xerces with JDK x.y" as we drop support for earlier releases.
> >
>
> +1
>
> > Thanks for bringing the item up!
> >
> > - Shane
> >
> >

Jeremias Maerki

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)

2008-11-11T05:52:52Z

On 11/11/2008, Shane Curcuru <asf@...> wrote:
> +1 to dropping 1.2 support.

+1 to dropping 1.2

+0 to dropping 1.3

I think 1.4 support should be kept if possible for a while yet.

> Please - be sure that the main website clearly lists the last release we
> think that Xerces worked on JDK version x.y. Xerces is ubiquitous, and is
> used directly or within other products virtually everywhere. While we don't
> need to spend developer time worrying about ancient JDK versions, we should
> make it clear where people who have to stay on legacy systems can get an
> appropriate release.

+1

> I'd love it if we ensured that we feature a prominent link and host the
> download for the zip/targz plus it's key file for "the last known good
> Xerces with JDK x.y" as we drop support for earlier releases.
>

+1

> Thanks for bringing the item up!
>
> - Shane
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...