[PROPOSAL]: Upgrade XML Commons External to JAXP 1.4
|
View:
New views
13 Messages
—
Rating Filter:
Alert me
|
 |
[PROPOSAL]: Upgrade XML Commons External to JAXP 1.4
by Michael Glavassevich-3
::
Rate this Message:
Hi everyone,
The Xerces developers (myself included) have started planning for a Xerces-J release which will add support for JAXP 1.4 [1][2]. JAXP 1.4 is a minor update to JAXP 1.3; the largest technical change being the addition of StAX (JSR 173) [3] and new Source/Result classes (see the javax.xml.transform.stax package) which can be used with transformers and validators. I believe Apache Harmony will eventually require JAXP 1.4 to complete an implementation of Java SE 6.0. Other Apache projects (Axis2, XMLBeans, etc...) are already using StAX. With the JAXP 1.4 specification nearing finalization I propose that the main trunk of XML Commons External be upgraded to JAXP 1.4 and a branch be created for maintenance of JAXP 1.3 (which is what is currently on the main trunk). I noticed that a copy of the StAX API source is being distributed with XMLBeans here [4] (see jsr173_1.0_api_bundle.jar) and on Apache mirror sites. The source files contain Javadoc so it would be great if we could use them. The README contained in the jar states that the source and binary files are distributed under the Apache License 2.0, so it would appear to me that the source can be included [5] in XML Commons External. What do folks think? Thanks. [1] https://jaxp-sources.dev.java.net/nonav/docs/spec/html/ [2] https://jaxp-sources.dev.java.net/nonav/docs/api/ [3] http://jcp.org/en/jsr/detail?id=173 [4] http://www.apache.org/dist/java-repository/xmlbeans/jars/ [5] http://people.apache.org/~cliffs/3party.html#category-a Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@... E-mail: mrglavas@... |
|
|
Re: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4
by Jeremias Maerki-2
::
Rate this Message:
(cc'ing dev@...)
That's ok with me. The only thing bothering me is the XMLBeans' JAR file with the API sources. It does not contain any indication whether this is a clean-room reconstruction of the API sources based on the specification or if they have been taken from the java.net site and modified. The files there seem to be distributed under the CDDL [1] which is a Category B license (binary only). The sources at java.net [2] have Bea copyrights all over the place. Furthermore, I can't find the StAX API sources anywhere in XMLBeans' repository. The individual files in the API JAR do not contain the Apache license header as would be required by any source file published by the ASF (due to the current policy). The good thing on the other side is that Bea seems to be the driving force behind XMLBeans and could officially donate the API sources to the ASF for inclusion into XML Commons Externals. And Cliff is XMLBeans' PMC chair. :-) So, before the API sources can be included in XML Commons Externals a clarification will be necessary IMO. [1] https://jaxp-sources.dev.java.net/source/browse/jaxp-sources/jaxp-api/src/javax/xml/license.txt?rev=1.1&view=auto&content-type=text/vnd.viewcvs-markup [2] https://jaxp-sources.dev.java.net/source/browse/jaxp-sources/jaxp-api/src/javax/xml/stream/StreamFilter.java?rev=1.1&view=auto&content-type=text/vnd.viewcvs-markup On 29.03.2006 00:45:11 Michael Glavassevich wrote: > Hi everyone, > > The Xerces developers (myself included) have started planning for a > Xerces-J release which will add support for JAXP 1.4 [1][2]. JAXP 1.4 is a > minor update to JAXP 1.3; the largest technical change being the addition > of StAX (JSR 173) [3] and new Source/Result classes (see the > javax.xml.transform.stax package) which can be used with transformers and > validators. I believe Apache Harmony will eventually require JAXP 1.4 to > complete an implementation of Java SE 6.0. Other Apache projects (Axis2, > XMLBeans, etc...) are already using StAX. > > With the JAXP 1.4 specification nearing finalization I propose that the > main trunk of XML Commons External be upgraded to JAXP 1.4 and a branch be > created for maintenance of JAXP 1.3 (which is what is currently on the > main trunk). > > I noticed that a copy of the StAX API source is being distributed with > XMLBeans here [4] (see jsr173_1.0_api_bundle.jar) and on Apache mirror > sites. The source files contain Javadoc so it would be great if we could > use them. The README contained in the jar states that the source and > binary files are distributed under the Apache License 2.0, so it would > appear to me that the source can be included [5] in XML Commons External. > What do folks think? > > Thanks. > > [1] https://jaxp-sources.dev.java.net/nonav/docs/spec/html/ > [2] https://jaxp-sources.dev.java.net/nonav/docs/api/ > [3] http://jcp.org/en/jsr/detail?id=173 > [4] http://www.apache.org/dist/java-repository/xmlbeans/jars/ > [5] http://people.apache.org/~cliffs/3party.html#category-a > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: mrglavas@... > E-mail: mrglavas@... Jeremias Maerki |
|
|
Re: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4
by Michael Glavassevich-3
::
Rate this Message:
Jeremias Maerki <dev@...> wrote on 03/29/2006 02:08:32 AM:
> (cc'ing dev@...) > > That's ok with me. The only thing bothering me is the XMLBeans' JAR file > with the API sources. It does not contain any indication whether this is > a clean-room reconstruction of the API sources based on the > specification or if they have been taken from the java.net site and > modified. The files there seem to be distributed under the CDDL [1] > which is a Category B license (binary only). The sources at java.net [2] > have Bea copyrights all over the place. Furthermore, I can't find the > StAX API sources anywhere in XMLBeans' repository. The individual files > in the API JAR do not contain the Apache license header as would be > required by any source file published by the ASF (due to the current > policy). The good thing on the other side is that Bea seems to be the > driving force behind XMLBeans and could officially donate the API > sources to the ASF for inclusion into XML Commons Externals. And Cliff > is XMLBeans' PMC chair. :-) So, before the API sources can be included > in XML Commons Externals a clarification will be necessary IMO. I agree. > [1] https://jaxp-sources.dev.java.net/source/browse/jaxp- > sources/jaxp-api/src/javax/xml/license.txt?rev=1. > 1&view=auto&content-type=text/vnd.viewcvs-markup > [2] https://jaxp-sources.dev.java.net/source/browse/jaxp- > sources/jaxp-api/src/javax/xml/stream/StreamFilter.java?rev=1. > 1&view=auto&content-type=text/vnd.viewcvs-markup > > On 29.03.2006 00:45:11 Michael Glavassevich wrote: > > Hi everyone, > > > > The Xerces developers (myself included) have started planning for a > > Xerces-J release which will add support for JAXP 1.4 [1][2]. JAXP 1.4 > > minor update to JAXP 1.3; the largest technical change being the addition > > of StAX (JSR 173) [3] and new Source/Result classes (see the > > javax.xml.transform.stax package) which can be used with transformers and > > validators. I believe Apache Harmony will eventually require JAXP 1.4 to > > complete an implementation of Java SE 6.0. Other Apache projects (Axis2, > > XMLBeans, etc...) are already using StAX. > > > > With the JAXP 1.4 specification nearing finalization I propose that the > > main trunk of XML Commons External be upgraded to JAXP 1.4 and a branch be > > created for maintenance of JAXP 1.3 (which is what is currently on the > > main trunk). > > > > I noticed that a copy of the StAX API source is being distributed with > > XMLBeans here [4] (see jsr173_1.0_api_bundle.jar) and on Apache mirror > > sites. The source files contain Javadoc so it would be great if we could > > use them. The README contained in the jar states that the source and > > binary files are distributed under the Apache License 2.0, so it would > > appear to me that the source can be included [5] in XML Commons External. > > What do folks think? > > > > Thanks. > > > > [1] https://jaxp-sources.dev.java.net/nonav/docs/spec/html/ > > [2] https://jaxp-sources.dev.java.net/nonav/docs/api/ > > [3] http://jcp.org/en/jsr/detail?id=173 > > [4] http://www.apache.org/dist/java-repository/xmlbeans/jars/ > > [5] http://people.apache.org/~cliffs/3party.html#category-a > > > > Michael Glavassevich > > XML Parser Development > > IBM Toronto Lab > > E-mail: mrglavas@... > > E-mail: mrglavas@... > > > > Jeremias Maerki Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@... E-mail: mrglavas@... |
|
|
|
|
|
RE: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4
by Michael Glavassevich-3
::
Rate this Message:
Hi Radu,
That is reassuring though I wonder if the source files in their current form can be included in an ASF project. As Jeremias mentioned, none of the source files have a license header on them. Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@... E-mail: mrglavas@... "Radu Preotiuc-Pietro" <radup@...> wrote on 03/30/2006 04:43:32 PM: > Here's some info on this. > > The XmlBeans team (esp Lawrence, with his Apache hat on ;-) ) have > worked with BEA (represented by the BEA legal team) to clarify the > licensing status of jsr173 APIs. The jar that we have made available at > http://www.apache.org/dist/java-repository/xmlbeans/jars/jsr173_1.0_api_ > bundle.jar is totally legit, as provided by BEA, licensed under the > Apache License 2.0 and with no modifications on our part. It is NOT > something that we just downloaded, changed a few things and commited. > It's also been oked by Cliff (with his legal affairs hat on), see this > thread for details: > http://mail-archives.apache.org/mod_mbox/xmlbeans-dev/200510.mbox/%3c113 > 0357486.13564.0.camel@...%3e > > There are two points that are worth mentioning: > 1. Is this .jar available from anywhere else other than the Apache > address above? Answer: not that I know of; BEA has said that they are > interested in making it available for download in a more "public" place, > but this has not happened yet, I guess it's just a lack of leadership on > their part, but we'll keep pinging them > 2. Why is another .jar still available at dev.java.net with the same > classes in it and different license? Answer: because of BEA's agreement > with Sun on the JCP, they can't modify what's already there AFAIK. Cliff > probably knows exactly what are the rules regarding code that companies > decided to make available under Apache license which was previously > licensed under different terms. > > So obviously each project has to decide for itself what to use and what > not to use, but for XmlBeans we have taken the steps to ensure that what > we use is completely within the legal constraints of the ASF. > > Hope this helps, > Radu > > -----Original Message----- > From: Michael Glavassevich [mailto:mrglavas@...] > Sent: Wednesday, March 29, 2006 10:30 AM > To: commons-dev@... > Cc: dev@... > Subject: Re: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4 > > Jeremias Maerki <dev@...> wrote on 03/29/2006 02:08:32 > AM: > > > (cc'ing dev@...) > > > > That's ok with me. The only thing bothering me is the XMLBeans' JAR > > file with the API sources. It does not contain any indication whether > > this is a clean-room reconstruction of the API sources based on the > > specification or if they have been taken from the java.net site and > > modified. The files there seem to be distributed under the CDDL [1] > > which is a Category B license (binary only). The sources at java.net > > [2] have Bea copyrights all over the place. Furthermore, I can't find > > the StAX API sources anywhere in XMLBeans' repository. The individual > > files in the API JAR do not contain the Apache license header as would > > > be required by any source file published by the ASF (due to the > > current policy). The good thing on the other side is that Bea seems to > > > be the driving force behind XMLBeans and could officially donate the > > API sources to the ASF for inclusion into XML Commons Externals. And > > Cliff is XMLBeans' PMC chair. :-) So, before the API sources can be > > included in XML Commons Externals a clarification will be necessary > IMO. > > I agree. > > > [1] https://jaxp-sources.dev.java.net/source/browse/jaxp- > > sources/jaxp-api/src/javax/xml/license.txt?rev=1. > > 1&view=auto&content-type=text/vnd.viewcvs-markup > > [2] https://jaxp-sources.dev.java.net/source/browse/jaxp- > > sources/jaxp-api/src/javax/xml/stream/StreamFilter.java?rev=1. > > 1&view=auto&content-type=text/vnd.viewcvs-markup > > > > On 29.03.2006 00:45:11 Michael Glavassevich wrote: > > > Hi everyone, > > > > > > The Xerces developers (myself included) have started planning for a > > > Xerces-J release which will add support for JAXP 1.4 [1][2]. JAXP > > > 1.4 > is a > > > minor update to JAXP 1.3; the largest technical change being the > addition > > > of StAX (JSR 173) [3] and new Source/Result classes (see the > > > javax.xml.transform.stax package) which can be used with > > > transformers > and > > > validators. I believe Apache Harmony will eventually require JAXP > > > 1.4 > to > > > complete an implementation of Java SE 6.0. Other Apache projects > (Axis2, > > > XMLBeans, etc...) are already using StAX. > > > > > > With the JAXP 1.4 specification nearing finalization I propose that > the > > > main trunk of XML Commons External be upgraded to JAXP 1.4 and a > branch be > > > created for maintenance of JAXP 1.3 (which is what is currently on > > > the > > > > main trunk). > > > > > > I noticed that a copy of the StAX API source is being distributed > > > with > > > > XMLBeans here [4] (see jsr173_1.0_api_bundle.jar) and on Apache > > > mirror > > > > sites. The source files contain Javadoc so it would be great if we > could > > > use them. The README contained in the jar states that the source and > > > > binary files are distributed under the Apache License 2.0, so it > > > would > > > > appear to me that the source can be included [5] in XML Commons > External. > > > What do folks think? > > > > > > Thanks. > > > > > > [1] https://jaxp-sources.dev.java.net/nonav/docs/spec/html/ > > > [2] https://jaxp-sources.dev.java.net/nonav/docs/api/ > > > [3] http://jcp.org/en/jsr/detail?id=173 > > > [4] http://www.apache.org/dist/java-repository/xmlbeans/jars/ > > > [5] http://people.apache.org/~cliffs/3party.html#category-a > > > > > > Michael Glavassevich > > > XML Parser Development > > > IBM Toronto Lab > > > E-mail: mrglavas@... > > > E-mail: mrglavas@... > > > > > > > > Jeremias Maerki > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: mrglavas@... > E-mail: mrglavas@... > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > > _______________________________________________________________________ > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual > or entity named in this message. If you are not the intended recipient, > and have received this message in error, please immediately return this > by email and then delete it. |
|
|
Re: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4
by Henry Zongaro
::
Rate this Message:
Hi, Michael.
Michael Glavassevich/Toronto/IBM@IBMCA wrote on 2006-03-28 05:45:11 PM: > With the JAXP 1.4 specification nearing finalization I propose that the > main trunk of XML Commons External be upgraded to JAXP 1.4 and a branch be > created for maintenance of JAXP 1.3 (which is what is currently on the > main trunk). I probably ought to know the answer to this, but are there any changes to APIs that would break the Xalan-J GUMP build - for instance, new abstract methods on classes in the transform or xpath packages that Xalan-J's implementation classes fail to implement? Thanks, Henry ------------------------------------------------------------------ Henry Zongaro Xalan development IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044 mailto:zongaro@... |
|
|
Re: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4
by Michael Glavassevich-3
::
Rate this Message:
Hi Henry,
Henry Zongaro/Toronto/IBM@IBMCA wrote on 03/31/2006 03:46:19 PM: > Hi, Michael. > > Michael Glavassevich/Toronto/IBM@IBMCA wrote on 2006-03-28 05:45:11 PM: > > With the JAXP 1.4 specification nearing finalization I propose that the > > main trunk of XML Commons External be upgraded to JAXP 1.4 and a branch > be > > created for maintenance of JAXP 1.3 (which is what is currently on the > > main trunk). > > I probably ought to know the answer to this, but are there any > changes to APIs that would break the Xalan-J GUMP build - for instance, > new abstract methods on classes in the transform or xpath packages that > Xalan-J's implementation classes fail to implement? No. The only (signature) changes to existing classes in the transform/xpath packages are the addition of static newInstance(String, ClassLoader) methods to TransformerFactory and XPathFactory. newInstance(String, ClassLoader) methods were also added to DocumentBuilderFactory, SAXParserFactory, SchemaFactory and DatatypeFactory. > Thanks, > > Henry > ------------------------------------------------------------------ > Henry Zongaro Xalan development > IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044 > mailto:zongaro@... Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@... E-mail: mrglavas@... |
|
|
|
|
|
Re: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4
by Aleksander Slominski
::
Rate this Message:
Radu Preotiuc-Pietro wrote:
> Do you need to check them into your svn repository or a Maven > dependency, say, would be better? I would think in the later case, you > would just be using it the same way we do, which would be ok. But let's > find out, if we can do it quickly, if the current format is legal-wise > safe for your intended use. > few months ago on request of Ron Benson (see below; it seems though he no longer works in BEA?) i have put the jar file (jsr173_1.0_src.jar) into StAX RI SVN repository at codehaus. is it official enough for Apache XML purposes? thanks, alek -------- Original Message -------- Subject: API and RI bundles Date: Mon, 28 Nov 2005 17:25:23 -0800 From: Ron Benson <rbenson@...> To: Chris Fry <chris_l_fry@...>, Aleksander Slominski <aslom@...> CC: Peter Dapkus <pdapkus@...>, Jim Barnett <jimb@...> Hi Chris and Alek, Here are the updated bundles including the new ASF 2.0 licensing. Would you mind posting the included bundles to codehaus as I'm having problems getting access to the site? Please send any comments to me if you would like anything in the bundles to change. Then feel free to open access to the site. Thanks, Ron > -----Original Message----- > From: Michael Glavassevich [mailto:mrglavas@...] > Sent: Friday, March 31, 2006 12:10 PM > To: commons-dev@... > Cc: dev@... > Subject: RE: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4 > > Hi Radu, > > That is reassuring though I wonder if the source files in their current > form can be included in an ASF project. As Jeremias mentioned, none of > the source files have a license header on them. > > Thanks. > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: mrglavas@... > E-mail: mrglavas@... > > "Radu Preotiuc-Pietro" <radup@...> wrote on 03/30/2006 04:43:32 PM: > > >> Here's some info on this. >> >> The XmlBeans team (esp Lawrence, with his Apache hat on ;-) ) have >> worked with BEA (represented by the BEA legal team) to clarify the >> licensing status of jsr173 APIs. The jar that we have made available >> at >> http://www.apache.org/dist/java-repository/xmlbeans/jars/jsr173_1.0_ap >> i_ bundle.jar is totally legit, as provided by BEA, licensed under the >> > > >> Apache License 2.0 and with no modifications on our part. It is NOT >> something that we just downloaded, changed a few things and commited. >> It's also been oked by Cliff (with his legal affairs hat on), see this >> > > >> thread for details: >> http://mail-archives.apache.org/mod_mbox/xmlbeans-dev/200510.mbox/%3c1 >> 13 0357486.13564.0.camel@...%3e >> >> There are two points that are worth mentioning: >> 1. Is this .jar available from anywhere else other than the Apache >> address above? Answer: not that I know of; BEA has said that they are >> interested in making it available for download in a more "public" >> place, but this has not happened yet, I guess it's just a lack of >> leadership on their part, but we'll keep pinging them 2. Why is >> another .jar still available at dev.java.net with the same classes in >> it and different license? Answer: because of BEA's agreement with Sun >> on the JCP, they can't modify what's already there AFAIK. Cliff >> probably knows exactly what are the rules regarding code that >> companies decided to make available under Apache license which was >> previously licensed under different terms. >> >> So obviously each project has to decide for itself what to use and >> what not to use, but for XmlBeans we have taken the steps to ensure >> that what we use is completely within the legal constraints of the >> > ASF. > >> Hope this helps, >> Radu >> >> -----Original Message----- >> From: Michael Glavassevich [mailto:mrglavas@...] >> Sent: Wednesday, March 29, 2006 10:30 AM >> To: commons-dev@... >> Cc: dev@... >> Subject: Re: [PROPOSAL]: Upgrade XML Commons External to JAXP 1.4 >> >> Jeremias Maerki <dev@...> wrote on 03/29/2006 02:08:32 >> AM: >> >> >>> (cc'ing dev@...) >>> >>> That's ok with me. The only thing bothering me is the XMLBeans' JAR >>> file with the API sources. It does not contain any indication >>> whether this is a clean-room reconstruction of the API sources based >>> > > >>> on the specification or if they have been taken from the java.net >>> site and modified. The files there seem to be distributed under the >>> CDDL [1] which is a Category B license (binary only). The sources at >>> > > >>> java.net [2] have Bea copyrights all over the place. Furthermore, I >>> can't find the StAX API sources anywhere in XMLBeans' repository. >>> The individual files in the API JAR do not contain the Apache >>> license header as would >>> >>> be required by any source file published by the ASF (due to the >>> current policy). The good thing on the other side is that Bea seems >>> to >>> >>> be the driving force behind XMLBeans and could officially donate the >>> > > >>> API sources to the ASF for inclusion into XML Commons Externals. And >>> > > >>> Cliff is XMLBeans' PMC chair. :-) So, before the API sources can be >>> included in XML Commons Externals a clarification will be necessary >>> >> IMO. >> >> I agree. >> >> >>> [1] https://jaxp-sources.dev.java.net/source/browse/jaxp- >>> sources/jaxp-api/src/javax/xml/license.txt?rev=1. >>> 1&view=auto&content-type=text/vnd.viewcvs-markup >>> [2] https://jaxp-sources.dev.java.net/source/browse/jaxp- >>> sources/jaxp-api/src/javax/xml/stream/StreamFilter.java?rev=1. >>> 1&view=auto&content-type=text/vnd.viewcvs-markup >>> >>> On 29.03.2006 00:45:11 Michael Glavassevich wrote: >>> >>>> Hi everyone, >>>> >>>> The Xerces developers (myself included) have started planning for >>>> a Xerces-J release which will add support for JAXP 1.4 [1][2]. >>>> JAXP >>>> 1.4 >>>> >> is a >> >>>> minor update to JAXP 1.3; the largest technical change being the >>>> >> addition >> >>>> of StAX (JSR 173) [3] and new Source/Result classes (see the >>>> javax.xml.transform.stax package) which can be used with >>>> transformers >>>> >> and >> >>>> validators. I believe Apache Harmony will eventually require JAXP >>>> 1.4 >>>> >> to >> >>>> complete an implementation of Java SE 6.0. Other Apache projects >>>> >> (Axis2, >> >>>> XMLBeans, etc...) are already using StAX. >>>> >>>> With the JAXP 1.4 specification nearing finalization I propose >>>> that >>>> >> the >> >>>> main trunk of XML Commons External be upgraded to JAXP 1.4 and a >>>> >> branch be >> >>>> created for maintenance of JAXP 1.3 (which is what is currently on >>>> > > >>>> the >>>> >>>> main trunk). >>>> >>>> I noticed that a copy of the StAX API source is being distributed >>>> with >>>> >>>> XMLBeans here [4] (see jsr173_1.0_api_bundle.jar) and on Apache >>>> mirror >>>> >>>> sites. The source files contain Javadoc so it would be great if we >>>> >> could >> >>>> use them. The README contained in the jar states that the source >>>> and >>>> >>>> binary files are distributed under the Apache License 2.0, so it >>>> would >>>> >>>> appear to me that the source can be included [5] in XML Commons >>>> >> External. >> >>>> What do folks think? >>>> >>>> Thanks. >>>> >>>> [1] https://jaxp-sources.dev.java.net/nonav/docs/spec/html/ >>>> [2] https://jaxp-sources.dev.java.net/nonav/docs/api/ >>>> [3] http://jcp.org/en/jsr/detail?id=173 >>>> [4] http://www.apache.org/dist/java-repository/xmlbeans/jars/ >>>> [5] http://people.apache.org/~cliffs/3party.html#category-a >>>> >>>> Michael Glavassevich >>>> XML Parser Development >>>> IBM Toronto Lab >>>> E-mail: mrglavas@... >>>> E-mail: mrglavas@... >>>> >>> >>> Jeremias Maerki >>> >> Michael Glavassevich >> XML Parser Development >> IBM Toronto Lab >> E-mail: mrglavas@... >> E-mail: mrglavas@... >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@... >> For additional commands, e-mail: dev-help@... >> >> ______________________________________________________________________ >> _ >> Notice: This email message, together with any attachments, may >> contain information of BEA Systems, Inc., its subsidiaries and >> affiliated entities, that may be confidential, proprietary, >> copyrighted and/or legally privileged, and is intended solely for the >> > > >> use of the individual or entity named in this message. If you are not >> the intended recipient, and have received this message in error, >> please immediately return this by email and then delete it. >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > > _______________________________________________________________________ > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual > or entity named in this message. If you are not the intended recipient, > and have received this message in error, please immediately return this > by email and then delete it. > > -- The best way to predict the future is to invent it - Alan Kay |
|
|
|
