You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xml.apache.org by Neeraj Bajaj <Ne...@Sun.COM> on 2004/10/12 14:02:14 UTC
Donation of JAXP 1.3 Sources to Apache
Hello All,
As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
1.3 adds lots of new features in the area of XML processing.
It introduces new Schema independent validation framework which
decouples the validation as a process independent from parsing.
It allows to compile Schema to an immutable memory representation of
Grammar which can validate different instances of XML document thus
greatly improving the performance of XML processing. XPath language
provides a simple, concise syntax for accessing individual parts of an
XML document. JAXP 1.3 defines XPath APIs which provides access to the
XPath evaluation environment and expression results independent
of the underlying data object model. JAXP 1.3 also adds new Datatypes to
the Java platform which maps to some of the W3C XML Schema
Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
the ability to reset XML Parser and Transformer instance , allowing
application to reuse the same instance to process multiple XML
documents. This also helps in increasing XML processing performance.
JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
1.1, XInclude.
Sun Microsystems would like to donate JAXP 1.3 sources (API s +
Reference Implementation) to Apache.
Details of JAXP 1.3 sources to be donated:
JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
Implementation). RI has been done using
Xerces/Xalan as code base. RI contains the implementation of newly
introduced Validation Framework [2], XPath APIs [3]
, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
Reset changes, Secured XML Processing changes.
Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
already exist on Apache Xerces. So in the next
section I have also proposed the way to merge rest of the JAXP 1.3 RI
changes into Apache Xerces & Xalan project. I have also
suggested where implementation component should reside i.e. Xerces or
Xalan. Any idea or feedback for the smoother and
expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
Xalan is very welcome.
JAXP 1.3 APIs:
JAXP APIs has been at xml-commons for a long time as these set of APIs
are used by many different projects.
With JSR 206 declared as final and many new standards emerging, we
should update xml-commons to JAXP 1.3
APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
and apply a tag.
JAXP 1.3 RI: (Implementation components that should be part of Xerces)
JAXP 1.3 RI contains the implementation of following packages
javax.xml.datatype
javax.xml.validation
javax.xml.parsers ( reset(), xinclude, etc.)
which should reside at Xerces.
I propose that we create a branch, and merge JAXP 1.3 RI changes into
that branch. This will help
other Xerces active committers to have a chance to look at it before
these changes being finally
committed to main trunk. This process would require merging changes to
the branch and then committing
changes to main trunk, i seek help of active Xerces committers.
JAXP 1.3 RI: (Implementation components that should be part of Xalan)
JAXP 1.3 RI also has the implementation of newly developed XPath
(javax.xml.xpath.*) APIs which i think, should be part of
Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
done in "javax.xml.transform" package
for ex. now application can use the same Transformer instance by
invoking reset().
I propose the same for the Xalan/XSLTC project that we create a branch
and JAXP 1.3 Reference Implementation changes are
put there. This will help other Xalan active committers to have a chance
to look at it before these changes being finally
committed to main trunk. Again i seek help of Xalan committers for this
process.
As always, all feedbacks are more than welcome.
Thanks,
Neeraj
[1] http://www.jcp.org/en/jsr/detail?id=206
[2]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/validation/package-summary.html
[3]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
[4]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-summary.html
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Paul Libbrecht <pa...@activemath.org>.
I would like to encourage such a move at least for all the license
clean-up this could bring in!! xml-apis, e.g. as distributed by maven,
would finally come with an easy to use pack of licenses!
(and a safe one!)
paul
Le 12 oct. 04, à 14:02, Neeraj Bajaj a écrit :
> Hello All,
>
>
> As most of you already know JSR 206 [1] JAXP 1.3 has become final.
> JAXP 1.3 adds lots of new features in the area of XML processing.
> It introduces new Schema independent validation framework which
> decouples the validation as a process independent from parsing.
> It allows to compile Schema to an immutable memory representation of
> Grammar which can validate different instances of XML document thus
> greatly improving the performance of XML processing. XPath language
> provides a simple, concise syntax for accessing individual parts of an
> XML document. JAXP 1.3 defines XPath APIs which provides access to
> the XPath evaluation environment and expression results independent
> of the underlying data object model. JAXP 1.3 also adds new Datatypes
> to the Java platform which maps to some of the W3C XML Schema
> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also
> adds the ability to reset XML Parser and Transformer instance ,
> allowing
> application to reuse the same instance to process multiple XML
> documents. This also helps in increasing XML processing performance.
> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S,
> XML 1.1, XInclude.
>
> Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> Reference Implementation) to Apache.
>
>
> Details of JAXP 1.3 sources to be donated:
>
> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
> Implementation). RI has been done using
> Xerces/Xalan as code base. RI contains the implementation of newly
> introduced Validation Framework [2], XPath APIs [3]
> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
> Transformer Reset changes, Secured XML Processing changes.
> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
> XInclude already exist on Apache Xerces. So in the next
> section I have also proposed the way to merge rest of the JAXP 1.3 RI
> changes into Apache Xerces & Xalan project. I have also
> suggested where implementation component should reside i.e. Xerces or
> Xalan. Any idea or feedback for the smoother and
> expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces
> & Xalan is very welcome.
>
>
>
> JAXP 1.3 APIs:
>
> JAXP APIs has been at xml-commons for a long time as these set of
> APIs are used by many different projects.
> With JSR 206 declared as final and many new standards emerging, we
> should update xml-commons to JAXP 1.3
> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
> trunk and apply a tag.
>
>
> JAXP 1.3 RI: (Implementation components that should be part of Xerces)
>
>
> JAXP 1.3 RI contains the implementation of following packages
>
> javax.xml.datatype
> javax.xml.validation
> javax.xml.parsers ( reset(), xinclude, etc.)
>
> which should reside at Xerces.
>
> I propose that we create a branch, and merge JAXP 1.3 RI changes into
> that branch. This will help
> other Xerces active committers to have a chance to look at it before
> these changes being finally
> committed to main trunk. This process would require merging changes
> to the branch and then committing
> changes to main trunk, i seek help of active Xerces committers.
>
>
> JAXP 1.3 RI: (Implementation components that should be part of Xalan)
>
>
> JAXP 1.3 RI also has the implementation of newly developed XPath
> (javax.xml.xpath.*) APIs which i think, should be part of
> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
> done in "javax.xml.transform" package
> for ex. now application can use the same Transformer instance by
> invoking reset().
>
> I propose the same for the Xalan/XSLTC project that we create a
> branch and JAXP 1.3 Reference Implementation changes are
> put there. This will help other Xalan active committers to have a
> chance to look at it before these changes being finally
> committed to main trunk. Again i seek help of Xalan committers for
> this process.
>
>
> As always, all feedbacks are more than welcome.
>
>
> Thanks,
> Neeraj
>
>
> [1] http://www.jcp.org/en/jsr/detail?id=206
> [2]
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/validation/package-
> summary.html
> [3]
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-
> summary.html
> [4]
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> summary.html
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Paul Libbrecht <pa...@activemath.org>.
I would like to encourage such a move at least for all the license
clean-up this could bring in!! xml-apis, e.g. as distributed by maven,
would finally come with an easy to use pack of licenses!
(and a safe one!)
paul
Le 12 oct. 04, à 14:02, Neeraj Bajaj a écrit :
> Hello All,
>
>
> As most of you already know JSR 206 [1] JAXP 1.3 has become final.
> JAXP 1.3 adds lots of new features in the area of XML processing.
> It introduces new Schema independent validation framework which
> decouples the validation as a process independent from parsing.
> It allows to compile Schema to an immutable memory representation of
> Grammar which can validate different instances of XML document thus
> greatly improving the performance of XML processing. XPath language
> provides a simple, concise syntax for accessing individual parts of an
> XML document. JAXP 1.3 defines XPath APIs which provides access to
> the XPath evaluation environment and expression results independent
> of the underlying data object model. JAXP 1.3 also adds new Datatypes
> to the Java platform which maps to some of the W3C XML Schema
> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also
> adds the ability to reset XML Parser and Transformer instance ,
> allowing
> application to reuse the same instance to process multiple XML
> documents. This also helps in increasing XML processing performance.
> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S,
> XML 1.1, XInclude.
>
> Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> Reference Implementation) to Apache.
>
>
> Details of JAXP 1.3 sources to be donated:
>
> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
> Implementation). RI has been done using
> Xerces/Xalan as code base. RI contains the implementation of newly
> introduced Validation Framework [2], XPath APIs [3]
> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
> Transformer Reset changes, Secured XML Processing changes.
> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
> XInclude already exist on Apache Xerces. So in the next
> section I have also proposed the way to merge rest of the JAXP 1.3 RI
> changes into Apache Xerces & Xalan project. I have also
> suggested where implementation component should reside i.e. Xerces or
> Xalan. Any idea or feedback for the smoother and
> expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces
> & Xalan is very welcome.
>
>
>
> JAXP 1.3 APIs:
>
> JAXP APIs has been at xml-commons for a long time as these set of
> APIs are used by many different projects.
> With JSR 206 declared as final and many new standards emerging, we
> should update xml-commons to JAXP 1.3
> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
> trunk and apply a tag.
>
>
> JAXP 1.3 RI: (Implementation components that should be part of Xerces)
>
>
> JAXP 1.3 RI contains the implementation of following packages
>
> javax.xml.datatype
> javax.xml.validation
> javax.xml.parsers ( reset(), xinclude, etc.)
>
> which should reside at Xerces.
>
> I propose that we create a branch, and merge JAXP 1.3 RI changes into
> that branch. This will help
> other Xerces active committers to have a chance to look at it before
> these changes being finally
> committed to main trunk. This process would require merging changes
> to the branch and then committing
> changes to main trunk, i seek help of active Xerces committers.
>
>
> JAXP 1.3 RI: (Implementation components that should be part of Xalan)
>
>
> JAXP 1.3 RI also has the implementation of newly developed XPath
> (javax.xml.xpath.*) APIs which i think, should be part of
> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
> done in "javax.xml.transform" package
> for ex. now application can use the same Transformer instance by
> invoking reset().
>
> I propose the same for the Xalan/XSLTC project that we create a
> branch and JAXP 1.3 Reference Implementation changes are
> put there. This will help other Xalan active committers to have a
> chance to look at it before these changes being finally
> committed to main trunk. Again i seek help of Xalan committers for
> this process.
>
>
> As always, all feedbacks are more than welcome.
>
>
> Thanks,
> Neeraj
>
>
> [1] http://www.jcp.org/en/jsr/detail?id=206
> [2]
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/validation/package-
> summary.html
> [3]
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-
> summary.html
> [4]
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> summary.html
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Eduardo Pelegri-Llopart <Ed...@Sun.COM>.
The bottom line for the APIs is "yes for this case, but don't assume it
will necessarily continue to be so". For our specific implementation,
it certainly works for J2SE 1.4, but don't know about 1.3 and below.
Some more details on the API situation. JAXP is bundled in J2SE and in
J2EE. There are rules in the platforms that keep versions of their
specs in sync, so that developers know what they are getting. Now, JAXP
1.3 is in J2SE 1.5, JAXP 1.1 is in J2SE 1.4, but there is no JAXP in
J2SE 1.3. So the rules say that JAXP 1.3 can be used in J2SE 1.5
(duh!), and in J2SE 1.3 and lesser J2SEs, but not in j2SE 1.4.
The rules exist for a reason, but in this case, we (Sun) recognized that
the disadvantages of this would seem to outweight the benefits, so some
time ago I requested and received from the J2SE group permision to
change the rules for this particular release. This means it is legal
for JAXP 1.3 to be used with J2SE 1.4 too.
Moving forward, though, I would not expect the exception to the rule to
be continued as the penalty is too heavy. For example, I expect JAXP
1.4 to take want to advantage of features in Tiger and Mustang. That is
a different discussion but I didn't want to mislead you.
Hope this helps,
- eduard/o
Elliotte Harold wrote:
> Are these APIs and implementation thereof independent of Java 1.5? i.e.
> can they be compiled and used in a Java 1.2/1.3/1.4 environment? If not,
> could they be backported to work in such environments?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Eduardo Pelegri-Llopart <Ed...@Sun.COM>.
The bottom line for the APIs is "yes for this case, but don't assume it
will necessarily continue to be so". For our specific implementation,
it certainly works for J2SE 1.4, but don't know about 1.3 and below.
Some more details on the API situation. JAXP is bundled in J2SE and in
J2EE. There are rules in the platforms that keep versions of their
specs in sync, so that developers know what they are getting. Now, JAXP
1.3 is in J2SE 1.5, JAXP 1.1 is in J2SE 1.4, but there is no JAXP in
J2SE 1.3. So the rules say that JAXP 1.3 can be used in J2SE 1.5
(duh!), and in J2SE 1.3 and lesser J2SEs, but not in j2SE 1.4.
The rules exist for a reason, but in this case, we (Sun) recognized that
the disadvantages of this would seem to outweight the benefits, so some
time ago I requested and received from the J2SE group permision to
change the rules for this particular release. This means it is legal
for JAXP 1.3 to be used with J2SE 1.4 too.
Moving forward, though, I would not expect the exception to the rule to
be continued as the penalty is too heavy. For example, I expect JAXP
1.4 to take want to advantage of features in Tiger and Mustang. That is
a different discussion but I didn't want to mislead you.
Hope this helps,
- eduard/o
Elliotte Harold wrote:
> Are these APIs and implementation thereof independent of Java 1.5? i.e.
> can they be compiled and used in a Java 1.2/1.3/1.4 environment? If not,
> could they be backported to work in such environments?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Ramesh Mandava <Ra...@Sun.COM>.
Hi Elliotte:
> Are these APIs and implementation thereof independent of Java 1.5?
> i.e. can they be compiled and used in a Java 1.2/1.3/1.4 environment?
> If not, could they be backported to work in such environments?
>
JAXP 1.3 API and RI sources
-Can be compiled with J2SE 1.4 , J2SE 5.0
- Run on J2SE 1.3, J2SE 1.4, J2SE 5.0
- JAXP 1.3 TCK qualify these sources on J2SE 1.3, J2SE 1.4 and J2SE 5.0
Base JDK requirement for JAXP 1.3 is J2SE 1.3
Regards
-Ramesh
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Ramesh Mandava <Ra...@Sun.COM>.
Hi Elliotte:
> Are these APIs and implementation thereof independent of Java 1.5?
> i.e. can they be compiled and used in a Java 1.2/1.3/1.4 environment?
> If not, could they be backported to work in such environments?
>
JAXP 1.3 API and RI sources
-Can be compiled with J2SE 1.4 , J2SE 5.0
- Run on J2SE 1.3, J2SE 1.4, J2SE 5.0
- JAXP 1.3 TCK qualify these sources on J2SE 1.3, J2SE 1.4 and J2SE 5.0
Base JDK requirement for JAXP 1.3 is J2SE 1.3
Regards
-Ramesh
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Eduardo Pelegri-Llopart <Ed...@Sun.COM>.
The bottom line for the APIs is "yes for this case, but don't assume it
will necessarily continue to be so". For our specific implementation,
it certainly works for J2SE 1.4, but don't know about 1.3 and below.
Some more details on the API situation. JAXP is bundled in J2SE and in
J2EE. There are rules in the platforms that keep versions of their
specs in sync, so that developers know what they are getting. Now, JAXP
1.3 is in J2SE 1.5, JAXP 1.1 is in J2SE 1.4, but there is no JAXP in
J2SE 1.3. So the rules say that JAXP 1.3 can be used in J2SE 1.5
(duh!), and in J2SE 1.3 and lesser J2SEs, but not in j2SE 1.4.
The rules exist for a reason, but in this case, we (Sun) recognized that
the disadvantages of this would seem to outweight the benefits, so some
time ago I requested and received from the J2SE group permision to
change the rules for this particular release. This means it is legal
for JAXP 1.3 to be used with J2SE 1.4 too.
Moving forward, though, I would not expect the exception to the rule to
be continued as the penalty is too heavy. For example, I expect JAXP
1.4 to take want to advantage of features in Tiger and Mustang. That is
a different discussion but I didn't want to mislead you.
Hope this helps,
- eduard/o
Elliotte Harold wrote:
> Are these APIs and implementation thereof independent of Java 1.5? i.e.
> can they be compiled and used in a Java 1.2/1.3/1.4 environment? If not,
> could they be backported to work in such environments?
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by David Crossley <cr...@apache.org>.
I dropped most of the Cc because this part is now an
issue for XML-Commons and the XML PMC.
Neeraj Bajaj wrote:
> David Crossley wrote:
> > One thing that we must have this time around, is a
> > version number on the xml-apis.jar filename. [1]
> > I suppose that is an Xml-commons "build" issue.
> > By the way, that build system is seriously in need
> > of improvement,
>
> This is something i can work with you when upgrading
> to JAXP 1.3 APIs.
That would be good. However, don't address anything to me
personally, rather all of XML-Commons. I don't know much
about the build or what is required, and just managed to
tweak it, so as to build the website and package some docs.
I would be pleased to help and learn.
--
David Crossley
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by David Crossley <cr...@apache.org>.
I dropped most of the Cc because this part is now an
issue for XML-Commons and the XML PMC.
Neeraj Bajaj wrote:
> David Crossley wrote:
> > One thing that we must have this time around, is a
> > version number on the xml-apis.jar filename. [1]
> > I suppose that is an Xml-commons "build" issue.
> > By the way, that build system is seriously in need
> > of improvement,
>
> This is something i can work with you when upgrading
> to JAXP 1.3 APIs.
That would be good. However, don't address anything to me
personally, rather all of XML-Commons. I don't know much
about the build or what is required, and just managed to
tweak it, so as to build the website and package some docs.
I would be pleased to help and learn.
--
David Crossley
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
David Crossley wrote:
>One thing that we must have this time around, is a
>version number on the xml-apis.jar filename. [1]
>I suppose that is an Xml-commons "build" issue.
>By the way, that build system is seriously in need
>of improvement,
>
This is something i can work with you when upgrading to JAXP 1.3
APIs.
>
>
>>As the sources would be put in a branch so it won't affect normal
>>development but it would be good if we can restrict
>>large chunk of changes to the main trunk and fix only critical changes.
>>It would help merging the changes back to main
>>trunk. What do others think ?
>>
>>
>
>I am a little confused about your planned procedure.
>Are you suggesting to add a copy of the core code
>to Xerces/Xalan then moving it to Xml-commons later?
>
No. We are donating JAXP 1.3 APIs + JAXP 1.3 (Reference Implmentation) RI.
JAXP 1.3 API will reside only at xml-commons.
JAXP 1.3 RI components will reside either on xerces/xalan.
>It worries me that we end up with copies.
>
I hope it is clear. Let me know if you see any issues.
Thanks,
Neeraj
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
David Crossley wrote:
>One thing that we must have this time around, is a
>version number on the xml-apis.jar filename. [1]
>I suppose that is an Xml-commons "build" issue.
>By the way, that build system is seriously in need
>of improvement,
>
This is something i can work with you when upgrading to JAXP 1.3
APIs.
>
>
>>As the sources would be put in a branch so it won't affect normal
>>development but it would be good if we can restrict
>>large chunk of changes to the main trunk and fix only critical changes.
>>It would help merging the changes back to main
>>trunk. What do others think ?
>>
>>
>
>I am a little confused about your planned procedure.
>Are you suggesting to add a copy of the core code
>to Xerces/Xalan then moving it to Xml-commons later?
>
No. We are donating JAXP 1.3 APIs + JAXP 1.3 (Reference Implmentation) RI.
JAXP 1.3 API will reside only at xml-commons.
JAXP 1.3 RI components will reside either on xerces/xalan.
>It worries me that we end up with copies.
>
I hope it is clear. Let me know if you see any issues.
Thanks,
Neeraj
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
David Crossley wrote:
>One thing that we must have this time around, is a
>version number on the xml-apis.jar filename. [1]
>I suppose that is an Xml-commons "build" issue.
>By the way, that build system is seriously in need
>of improvement,
>
This is something i can work with you when upgrading to JAXP 1.3
APIs.
>
>
>>As the sources would be put in a branch so it won't affect normal
>>development but it would be good if we can restrict
>>large chunk of changes to the main trunk and fix only critical changes.
>>It would help merging the changes back to main
>>trunk. What do others think ?
>>
>>
>
>I am a little confused about your planned procedure.
>Are you suggesting to add a copy of the core code
>to Xerces/Xalan then moving it to Xml-commons later?
>
No. We are donating JAXP 1.3 APIs + JAXP 1.3 (Reference Implmentation) RI.
JAXP 1.3 API will reside only at xml-commons.
JAXP 1.3 RI components will reside either on xerces/xalan.
>It worries me that we end up with copies.
>
I hope it is clear. Let me know if you see any issues.
Thanks,
Neeraj
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
David Crossley wrote:
>One thing that we must have this time around, is a
>version number on the xml-apis.jar filename. [1]
>I suppose that is an Xml-commons "build" issue.
>By the way, that build system is seriously in need
>of improvement,
>
This is something i can work with you when upgrading to JAXP 1.3
APIs.
>
>
>>As the sources would be put in a branch so it won't affect normal
>>development but it would be good if we can restrict
>>large chunk of changes to the main trunk and fix only critical changes.
>>It would help merging the changes back to main
>>trunk. What do others think ?
>>
>>
>
>I am a little confused about your planned procedure.
>Are you suggesting to add a copy of the core code
>to Xerces/Xalan then moving it to Xml-commons later?
>
No. We are donating JAXP 1.3 APIs + JAXP 1.3 (Reference Implmentation) RI.
JAXP 1.3 API will reside only at xml-commons.
JAXP 1.3 RI components will reside either on xerces/xalan.
>It worries me that we end up with copies.
>
I hope it is clear. Let me know if you see any issues.
Thanks,
Neeraj
Re: Donation of JAXP 1.3 Sources to Apache
Posted by David Crossley <cr...@apache.org>.
(I notice that some individuals got dropped from the
original posting. Are they on the *.apache mailing lists?)
Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow.
> What is the general procedure ? Is there any formality that needs to be
> completed first ?
Others have mentioned the legal side, so my comments
are about code and community issues.
> What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I am an xml-commons committer and user of this stuff
in Apache Cocoon and Apache Forrest. So i am looking
forward to more people working at Xml-commons to
provide reliability.
One thing that we must have this time around, is a
version number on the xml-apis.jar filename. [1]
I suppose that is an Xml-commons "build" issue.
By the way, that build system is seriously in need
of improvement, but it gets us by.
You would have noticed that there is very little
activity with the xml-commons CVS, so it would be
fine to work on trunk.
At some stage soon, we need to move xml-commons to SVN.
Hopefully that will not disrupt progress.
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
I am a little confused about your planned procedure.
Are you suggesting to add a copy of the core code
to Xerces/Xalan then moving it to Xml-commons later?
It worries me that we end up with copies.
On related matters, there is past discussion, e.g.
[1] http://marc.theaimsgroup.com/?t=106739445900002
--
David Crossley
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Berin Lautenbach wrote:
> Neeraj Bajaj wrote:
>
>> Hello All,
>>
>> I was wondering when can we start merging the JAXP 1.3 sources ?
>> Merging the code in branch/review/testing/committing to main trunk
>> would take time so at least from my side i would like to see this
>> work started as early as possible say from tomorrow. What is the
>> general procedure ? Is there any formality that needs to be completed
>> first ? What is the opinion of
>> (Xml-commons/Xerces/Xalan) committers ?
>
>
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
>
> I've CCd general@incubator as well, as I'd like Noel's opinion, but my
> feeling is that *if* the Xerces/Xalan and/or XML-Commons community
> want this code to be imported (and it sounds like they do - but I'd
> like to see that formalised), then the community side is already there.
From the response so far it seems that there is general acceptance and
community wants this code.
>
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a
> code grant from Sun (we can't take something into our repository until
> we are sure we have appropriate legal rights to do so) + someone needs
> to fill out the incubation docs to show that everything is AOK.
I believe legal aspect was cleared but i am not sure if some form or
document has been filled. Eduardo will be the right person to comment
on this issue.
Thanks,
Neeraj
> I'm happy to help out with the latter part.
>
> Code grant details can be found at :
>
> http://www.apache.org/licenses/#grants
>
>>
>> As the sources would be put in a branch so it won't affect normal
>> development but it would be good if we can restrict
>> large chunk of changes to the main trunk and fix only critical
>> changes. It would help merging the changes back to main
>> trunk. What do others think ?
>>
>> Thanks,
>> Neeraj
>>
>>
>> Neeraj Bajaj wrote:
>>
>>>
>>>
>>> Ramesh Mandava wrote:
>>>
>>>>>
>>>>>
>>>>> - Both Elliotte's and Clay's questions below are important. If
>>>>> someone
>>>>> familiar with the code could comment on: For either the main
>>>>> trunk, or
>>>>> a temporary working branch for integration:
>>>>>
>>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>>
>>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>>> sources should run on other JVMs as well.
>>>>
>>>>>
>>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>>
>>>>
>>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources
>>>> on Sun JVM. But as there is no Sun JVM specific codem these
>>>> sources should work on other JVMs without modification ( we have to
>>>> try it out though :-) ).
>>>
>>>
>>>
>>>
>>> Right. This hasn't been tried but i don't see any reason why it
>>> shouldn't work on any other JVM as there isn't any Sun JVM specific
>>> code.
>>>
>>> In other mail i have suggested that active Xerces/Xalan committers
>>> can try this before committin on main truck as the plan is to put
>>> the code
>>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>>> xml-commons main trunk but i am totally fine with creating a branch
>>> first to test
>>> the compatibility with other JVM.
>>>
>>> Neeraj
>>>
>>>>
>>>>
>>>>>
>>>>> We need to *clearly* document which versions this stuff works on, and
>>>>> should conditionally compile or something if it won't compile on at
>>>>> least 1.3
>>>>
>>>>
>>>>
>>>>
>>>> Right now we face compilation problems in couple of file with J2SE
>>>> 1.3, but these should be worked around though. We can atleast have
>>>> a switch to achieve the requirement of compiling on J2SE 1.3.
>>>>
>>>>> (since we still have a lot of older JDK version users here).
>>>>>
>>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>>> both recent Sun and IBM JVMs at least before we put this on the main
>>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> I agree.
>>>>
>>>> Regards
>>>> -Ramesh
>>>>
>>>>> (anyone still
>>>>> working on kaffe? 8-)
>>>>>
>>>>
>>>>
>>>>>
>>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>>
>>>>>
>>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>>
>>>>>>
>>>>>>> Are these APIs and implementation thereof independent of Java
>>>>>>> 1.5? i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> environment?
>>>>>>
>>>>>>> If not, could they be backported to work in such environments?
>>>>>>>
>>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>>> ref%3Dnosim
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>>
>>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>>> non-Sun implementation of Java...)?
>>>>>>
>>>>>> Web Maestro Clay
>>>>>>
>>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>>> Sun! Love your logo!
>>>>>> --
>>>>>> Clay Leeds - <cl...@medata.com>
>>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> =====
>>>>> - Shane
>>>>>
>>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.apache.org
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.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
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Berin Lautenbach wrote:
> Neeraj Bajaj wrote:
>
>> Hello All,
>>
>> I was wondering when can we start merging the JAXP 1.3 sources ?
>> Merging the code in branch/review/testing/committing to main trunk
>> would take time so at least from my side i would like to see this
>> work started as early as possible say from tomorrow. What is the
>> general procedure ? Is there any formality that needs to be completed
>> first ? What is the opinion of
>> (Xml-commons/Xerces/Xalan) committers ?
>
>
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
>
> I've CCd general@incubator as well, as I'd like Noel's opinion, but my
> feeling is that *if* the Xerces/Xalan and/or XML-Commons community
> want this code to be imported (and it sounds like they do - but I'd
> like to see that formalised), then the community side is already there.
From the response so far it seems that there is general acceptance and
community wants this code.
>
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a
> code grant from Sun (we can't take something into our repository until
> we are sure we have appropriate legal rights to do so) + someone needs
> to fill out the incubation docs to show that everything is AOK.
I believe legal aspect was cleared but i am not sure if some form or
document has been filled. Eduardo will be the right person to comment
on this issue.
Thanks,
Neeraj
> I'm happy to help out with the latter part.
>
> Code grant details can be found at :
>
> http://www.apache.org/licenses/#grants
>
>>
>> As the sources would be put in a branch so it won't affect normal
>> development but it would be good if we can restrict
>> large chunk of changes to the main trunk and fix only critical
>> changes. It would help merging the changes back to main
>> trunk. What do others think ?
>>
>> Thanks,
>> Neeraj
>>
>>
>> Neeraj Bajaj wrote:
>>
>>>
>>>
>>> Ramesh Mandava wrote:
>>>
>>>>>
>>>>>
>>>>> - Both Elliotte's and Clay's questions below are important. If
>>>>> someone
>>>>> familiar with the code could comment on: For either the main
>>>>> trunk, or
>>>>> a temporary working branch for integration:
>>>>>
>>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>>
>>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>>> sources should run on other JVMs as well.
>>>>
>>>>>
>>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>>
>>>>
>>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources
>>>> on Sun JVM. But as there is no Sun JVM specific codem these
>>>> sources should work on other JVMs without modification ( we have to
>>>> try it out though :-) ).
>>>
>>>
>>>
>>>
>>> Right. This hasn't been tried but i don't see any reason why it
>>> shouldn't work on any other JVM as there isn't any Sun JVM specific
>>> code.
>>>
>>> In other mail i have suggested that active Xerces/Xalan committers
>>> can try this before committin on main truck as the plan is to put
>>> the code
>>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>>> xml-commons main trunk but i am totally fine with creating a branch
>>> first to test
>>> the compatibility with other JVM.
>>>
>>> Neeraj
>>>
>>>>
>>>>
>>>>>
>>>>> We need to *clearly* document which versions this stuff works on, and
>>>>> should conditionally compile or something if it won't compile on at
>>>>> least 1.3
>>>>
>>>>
>>>>
>>>>
>>>> Right now we face compilation problems in couple of file with J2SE
>>>> 1.3, but these should be worked around though. We can atleast have
>>>> a switch to achieve the requirement of compiling on J2SE 1.3.
>>>>
>>>>> (since we still have a lot of older JDK version users here).
>>>>>
>>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>>> both recent Sun and IBM JVMs at least before we put this on the main
>>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> I agree.
>>>>
>>>> Regards
>>>> -Ramesh
>>>>
>>>>> (anyone still
>>>>> working on kaffe? 8-)
>>>>>
>>>>
>>>>
>>>>>
>>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>>
>>>>>
>>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>>
>>>>>>
>>>>>>> Are these APIs and implementation thereof independent of Java
>>>>>>> 1.5? i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> environment?
>>>>>>
>>>>>>> If not, could they be backported to work in such environments?
>>>>>>>
>>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>>> ref%3Dnosim
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>>
>>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>>> non-Sun implementation of Java...)?
>>>>>>
>>>>>> Web Maestro Clay
>>>>>>
>>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>>> Sun! Love your logo!
>>>>>> --
>>>>>> Clay Leeds - <cl...@medata.com>
>>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> =====
>>>>> - Shane
>>>>>
>>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.apache.org
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by Davanum Srinivas <da...@gmail.com>.
Ramesh, Neeraj,
I'd happily jump in if you find a work around for the changes to
org.apache.xpath.operations.Variable class...I know very little about
xalan internals to help with this specific problem. Could you ping
some folks on the xalan-dev team to see if they can review the code
changes and help port it to shipping versions of xalan.
thanks,
dims
On 4/13/05, ramesh mandava <Ra...@sun.com> wrote:
> Hi Dims:
>
> > My apologies dims. Somehow this mail was skipped.
> >
> > Davanum Srinivas wrote:
> >
> >> Neeraj,
> >>
> >> Do you think it will be possible/useful to somehow extract/use
> >> javax.xml.xpath and org.apache.xpath.jaxp with existing shipping
> >> versions of Xalan+Xerces?
> >>
> >>
> > I think it should be possible. New functionality has been added into
> > org.apache.xpath.jaxp package. So by extracting that package &
> > javax.xml.xpath
> > it should be possible. I have cc'ed this mail to Ramesh Mandava who
> > has worked on the implementation of java.xml.xpath.
> > Ramesh, What is your opinion ?
>
> We needed few changes ( specially in
> org.apache.xpath.operations.Variable class ) for implementating JAXP 1.3
> XPath
> functionality. So we need to find out a way to override this class (
> or find out some other workaround ) for using the shipped version of
> Xalan. Shipped version of Xerces should be ok though.
>
> >
> >> Reason for asking, current code in apache xml-security (and even
> >> cocoon for that matter) has fixed dependency on xalan's API for XPath
> >
> >> and i'd like to investigate if we can change that to use the
> >> javax.xml.xpath instead.
> >>
> >>
> As JAXP 1.3 RI is based on Xalan XPath API you can easily make the
> switch to javax.xml.xpath. One thing to aware of here is that
> 'javax.xml.xpath' API won't provide you facility to add extension
> functions without namespace prefix ( i.e. in default xpath namespace).
> If you need to do this then you have to use the native XPath processor
> provided facility ( in this case Xalan ).
>
> Anyway we would love to see you use javax.xml.xpath API and can assist
> you in anyway we can.
>
> Regards
> -Ramesh
>
> > That's good. Let us know if you would like to know more.
> > I would be happy to help.
> >
> > - Neeraj
> >
> >> thanks,
> >> dims
> >>
> >> On 4/11/05, Davanum Srinivas <da...@gmail.com> wrote:
> >>
> >>
> >>> Neeraj,
> >>>
> >>> Spotted a few typos:
> >>> XPathFactory factory = XpathFactory.newInstnace();
> >>> XPathFactory factory = XpathFactory.newInstance(object_model_uri);
> >>>
> >>> Should be:
> >>> XPathFactory factory = XPathFactory.newInstance();
> >>> XPathFactory factory = XPathFactory.newInstance(object_model_uri);
> >>>
> >>> Right?
> >>>
> >>> -- dims
> >>>
> >>> On 4/11/05, Neeraj Bajaj <Ne...@sun.com> wrote:
> >>>
> >>>
> >>>> Hello All,
> >>>>
> >>>> Sometimes back i wrote an article on JAXP 1.3 which explains the new
> >>>> concepts and important features introduced in JAXP 1.3
> >>>> Especially the new
> >>>>
> >>>> - Schema Validation Framework
> >>>> - Object model neutral XPath APIs
> >>>> - XML Schema Datatypes etc.
> >>>>
> >>>> Advantages of New Schema Validation Framework and how the new API
> >>>> works
> >>>> has been explained with code snippets and diagram.
> >>>> New XPath APIs have also been explained. Article is available at
> >>>> https://jaxp.dev.java.net/article/jaxp-1_3-article.html
> >>>>
> >>>> - Neeraj
> >>>>
> >>>> Neeraj Bajaj wrote:
> >>>>
> >>>>
> >>>>
> >>>>> Hello All,
> >>>>>
> >>>>> xml-commons has been upgraded to JAXP 1.3 APIs.
> >>>>> If anyone could try and confirm that would be great.
> >>>>>
> >>>>> - Neeraj
> >>>>>
> >>>>> Neeraj Bajaj wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>> I tagged xml-commons module yesterday with tag name
> >>>>>> '*before-jaxp13-upgradation*'.
> >>>>>>
> >>>>>> I plan to do the following but i will wait till tomorrow so as to
> >>>>>> give chance to the community
> >>>>>> to correct me if i am doing something wrong.
> >>>>>>
> >>>>>> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
> >>>>>> xml-commons/java/external/src directory
> >>>>>> with JAXP 1.3 API sources.
> >>>>>>
> >>>>>> Currently in xml-commons there are sources like org.w3c.dom.views.*
> >>>>>> which are not part of JAXP 1.3
> >>>>>> I won't remove those sources. they will be as it is.
> >>>>>>
> >>>>>> * Make changes in xml-commons/java/external/build.xml file so as to
> >>>>>> upgrade
> >>>>>> JAXP 1.1 --> JAXP 1.3
> >>>>>> DOM2 --> DOM3
> >>>>>> SAX2 --> (SAX) 2.0.2 (sax2r3)
> >>>>>>
> >>>>>> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
> >>>>>> available as xml-apis.jar.
> >>>>>>
> >>>>>> Anything else i should take care ?
> >>>>>>
> >>>>>> - Neeraj
> >>>>>>
> >>>>>>
> >>>>>> Neeraj Bajaj wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> Geir, I have uploaded sources at the same location
> >>>>>>> (xml-commons/contrib/jaxp13)
> >>>>>>> with Apache 2.0 license on every source file.
> >>>>>>>
> >>>>>>> - Neeraj
> >>>>>>>
> >>>>>>> Neeraj Bajaj wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> Ok, So i will add it and upload again.
> >>>>>>>>
> >>>>>>>> - Neeraj
> >>>>>>>>
> >>>>>>>> Geir Magnusson Jr. wrote:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Hi Neeraj,
> >>>>>>>>>>
> >>>>>>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip
> >>>>>>>>>> have no
> >>>>>>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the
> >>>>>>>>>> Apache
> >>>>>>>>>> license. Will this still be the case for JAXP 1.3?
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> yes - these files must be available under the apache license v2.
> >>>>>>>>> And the license grantor should be the one that adds it.
> >>>>>>>>>
> >>>>>>>>> Sorry Neeraj :)
> >>>>>>>>>
> >>>>>>>>> geir
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Thanks.
> >>>>>>>>>>
> >>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005
> >>>>>>>>>> 06:48:30 AM:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> Ok I just finished uploading JAXP 1.3 sources in
> >>>>>>>>>>> "*xml-commons/contrib/jaxp13"* directory.
> >>>>>>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
> >>>>>>>>>>> xalan-src.zip which
> >>>>>>>>>>> corresponds to jaxp-api,
> >>>>>>>>>>> xerces & xalan sources respectively.
> >>>>>>>>>>>
> >>>>>>>>>>> - Neeraj
> >>>>>>>>>>>
> >>>>>>>>>>> Neeraj Bajaj wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> That really sounds good to me.. so i would try to finish it
> >>>>>>>>>>>> today.
> >>>>>>>>>>>> I will send mail to the community when i am done.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks dims for the suggestion.
> >>>>>>>>>>>>
> >>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>> Davanum Srinivas wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Neeraj,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> my 2 cents...upload the whole thing say in
> >>>>>>>>>>>>> xml-commons/contrib/jaxp13
> >>>>>>>>>>>>> cvs so everyone can take a look (and then pick on the bits
> >>>>>>>>>>>>> they
> >>>>>>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP
> >>>>>>>>>>>>> (after
> >>>>>>>>>>>>> tagging the current code in the main trunk there) and it's
> >>>>>>>>>>>>> upto the
> >>>>>>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they
> >>>>>>>>>>>>> fit.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> thanks,
> >>>>>>>>>>>>> dims
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> Thanks Michael for your response.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I was just wondering what would be idle time to wait
> >>>>>>>>>>>>>> before i
> >>>>>>>>>>>>>> start
> >>>>>>>>>>>>>> work
> >>>>>>>>>>>>>> on this ?
> >>>>>>>>>>>>>> Does anyone has an opinion, Is there any other list where i
> >>>>>>>>>>>>>> should
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>> send
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>> this mail
> >>>>>>>>>>>>>> before making changes ?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Michael Glavassevich wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Hi Neeraj,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk,
> >>>>>>>>>>>>>>> tagging it
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>> and
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>> making a branch for the old JAXP sources on the current
> >>>>>>>>>>>>>>> main trunk.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
> >>>>>>>>>>>>>>> other
> >>>>>>>>>>>>>>> updates
> >>>>>>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
> >>>>>>>>>>>>>>> branch we've
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> used
> >>>>>>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and
> >>>>>>>>>>>>>>> Xalan. I
> >>>>>>>>>>>>>>> assume a
> >>>>>>>>>>>>>>> similar branch will exist for 1.3.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
> >>>>>>>>>>>>>>> 03:40:57
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>> AM:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
> >>>>>>>>>>>>>>>> attached as
> >>>>>>>>>>>>>>>> zip but
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> mail bounced back with the following message
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> <error>
> >>>>>>>>>>>>>>>> ----- The following addresses had permanent fatal
> >>>>>>>>>>>>>>>> errors -----
> >>>>>>>>>>>>>>>> <ge...@xml.apache.org>
> >>>>>>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
> >>>>>>>>>>>>>>>> </error>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
> >>>>>>>>>>>>>>>> Apache
> >>>>>>>>>>>>>>>> server somewhere ?
> >>>>>>>>>>>>>>>> Can anyone guide me what is the procedure for such code
> >>>>>>>>>>>>>>>> grants ?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I am looking help from the active committers of Xerces
> >>>>>>>>>>>>>>>> & Xalan
> >>>>>>>>>>>>>>>> community
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> to help put it in a
> >>>>>>>>>>>>>>>> a branch and make it work there. As i think due to large
> >>>>>>>>>>>>>>>> number of
> >>>>>>>>>>>>>>>> changes it would be a considerable
> >>>>>>>>>>>>>>>> amount of work. This will also help the committers &
> >>>>>>>>>>>>>>>> community to
> >>>>>>>>>>>>>>>> have a
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> look at the code before
> >>>>>>>>>>>>>>>> it is merged into the main stream work.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I think i have commit access at xml-commons so i can
> >>>>>>>>>>>>>>>> commit
> >>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>> sources
> >>>>>>>>>>>>>>>> in xml-commons branch
> >>>>>>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
> >>>>>>>>>>>>>>>> What is
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> the
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> opinion of community ? I can
> >>>>>>>>>>>>>>>> start this as soon as i get a consensus from the
> >>>>>>>>>>>>>>>> community. My
> >>>>>>>>>>>>>>>> preference is to put the sources on
> >>>>>>>>>>>>>>>> xml-commons main trunk.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Please let me know how should i proceed.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3
> >>>>>>>>>>>>>>>> APIs +
> >>>>>>>>>>>>>>>> implementation to Apache XML.*
> >>>>>>>>>>>>>>>> JAXP 1.3 (JSR 206
> >>>>>>>>>>>>>>>> <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>>>>>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole
> >>>>>>>>>>>>>>>> lot of
> >>>>>>>>>>>>>>>> new
> >>>>>>>>>>>>>>>> functionalities.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> * New Schema Validation Framework
> >>>>>>>>>>>>>>>> * New Object Model neutral XPath APIs
> >>>>>>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
> >>>>>>>>>>>>>>>> * Reuse parser instance
> >>>>>>>>>>>>>>>> * Security enhancements
> >>>>>>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3
> >>>>>>>>>>>>>>>> Load &
> >>>>>>>>>>>>>>>> Save, SAX
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> 2, XML 1.1 and XInclude)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Due to large size of code base i will be sending different
> >>>>>>>>>>>>>>>> mails
> >>>>>>>>>>>>>>>> for the
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> source code of Xerces & Xalan.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I have attached the original mail where i proposed the
> >>>>>>>>>>>>>>>> process of
> >>>>>>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
> >>>>>>>>>>>>>>>> integrating this donation into the main stream work of
> >>>>>>>>>>>>>>>> Xerces &
> >>>>>>>>>>>>>>>> Xalan.
> >>>>>>>>>>>>>>>> There was a general consensus to my proposal
> >>>>>>>>>>>>>>>> and we can discuss more about the technicalities of
> >>>>>>>>>>>>>>>> merging
> >>>>>>>>>>>>>>>> with
> >>>>>>>>>>>>>>>> in the
> >>>>>>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
> >>>>>>>>>>>>>>>> community.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Neeraj Bajaj wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Geir Magnusson Jr. wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
> >>>>>>>>>>>>>>>>>>> up the
> >>>>>>>>>>>>>>>>>>> ball
> >>>>>>>>>>>>>>>>>>> on this one.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
> >>>>>>>>>>>>>>>>>>> presume that
> >>>>>>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
> >>>>>>>>>>>>>>>>>>> xalan-dev, and
> >>>>>>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has
> >>>>>>>>>>>>>>>>>> been
> >>>>>>>>>>>>>>>>>> achieved.
> >>>>>>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't
> >>>>>>>>>>>>>>>>>> let the
> >>>>>>>>>>>>>>>>>> process
> >>>>>>>>>>>>>>>>>> hold things up.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>> ---------------------------------------------------------------------
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>>> To unsubscribe, e-mail:
> >>>>>>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>> ----------------------------------------------------------------------
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> Subject:
> >>>>>>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
> >>>>>>>>>>>>>>>> From:
> >>>>>>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
> >>>>>>>>>>>>>>>> Date:
> >>>>>>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> To:
> >>>>>>>>>>>>>>>> general@xml.apache.org
> >>>>>>>>>>>>>>>> CC:
> >>>>>>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >>>>>>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>>>>>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >>>>>>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> <Je...@Sun.COM>,
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has
> >>>>>>>>>>>>>>>> become
> >>>>>>>>>>>>>>>> final. JAXP
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> 1.3 adds lots of new features in the area of XML
> >>>>>>>>>>>>>>>> processing.
> >>>>>>>>>>>>>>>> It introduces new Schema independent validation framework
> >>>>>>>>>>>>>>>> which
> >>>>>>>>>>>>>>>> decouples the validation as a process independent from
> >>>>>>>>>>>>>>>> parsing.
> >>>>>>>>>>>>>>>> It allows to compile Schema to an immutable memory
> >>>>>>>>>>>>>>>> representation
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> of
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> Grammar which can validate different instances of XML
> >>>>>>>>>>>>>>>> document
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> thus
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> greatly improving the performance of XML processing.
> >>>>>>>>>>>>>>>> XPath
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> language
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> provides a simple, concise syntax for accessing individual
> >>>>>>>>>>>>>>>> parts
> >>>>>>>>>>>>>>>> of an
> >>>>>>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
> >>>>>>>>>>>>>>>> access to
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>> XPath evaluation environment and expression results
> >>>>>>>>>>>>>>>> independent
> >>>>>>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds
> >>>>>>>>>>>>>>>> new
> >>>>>>>>>>>>>>>> Datatypes to
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> the Java platform which maps to some of the W3C XML
> >>>>>>>>>>>>>>>> Schema
> >>>>>>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
> >>>>>>>>>>>>>>>> 1.3 also
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> adds
> >>>>>>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> allowing
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> application to reuse the same instance to process
> >>>>>>>>>>>>>>>> multiple XML
> >>>>>>>>>>>>>>>> documents. This also helps in increasing XML processing
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> performance.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
> >>>>>>>>>>>>>>>> DOM L3
> >>>>>>>>>>>>>>>> L/S, XML
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> 1.1, XInclude.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
> >>>>>>>>>>>>>>>> (API s +
> >>>>>>>>>>>>>>>> Reference Implementation) to Apache. *
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> (Reference
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> Implementation). RI has been done using
> >>>>>>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
> >>>>>>>>>>>>>>>> of newly
> >>>>>>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
> >>>>>>>>>>>>>>>> , Datatypes [4] implementation, SAXParser,
> >>>>>>>>>>>>>>>> DocumentBuilder,
> >>>>>>>>>>>>>>>> Transformer
> >>>>>>>>>>>>>>>> Reset changes, Secured XML Processing changes.
> >>>>>>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S,
> >>>>>>>>>>>>>>>> XML 1.1,
> >>>>>>>>>>>>>>>> XInclude
> >>>>>>>>>>>>>>>> already exist on Apache Xerces. So in the next
> >>>>>>>>>>>>>>>> section I have also proposed the way to merge rest of the
> >>>>>>>>>>>>>>>> JAXP 1.3
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> RI
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
> >>>>>>>>>>>>>>>> suggested where implementation component should reside
> >>>>>>>>>>>>>>>> i.e. Xerces
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> or
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
> >>>>>>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache
> >>>>>>>>>>>>>>>> xml-commons,
> >>>>>>>>>>>>>>>> Xerces &
> >>>>>>>>>>>>>>>> Xalan is very welcome.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> *JAXP 1.3 APIs: *
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
> >>>>>>>>>>>>>>>> set of
> >>>>>>>>>>>>>>>> APIs
> >>>>>>>>>>>>>>>> are used by many different projects.
> >>>>>>>>>>>>>>>> With JSR 206 declared as final and many new standards
> >>>>>>>>>>>>>>>> emerging, we
> >>>>>>>>>>>>>>>> should update xml-commons to JAXP 1.3
> >>>>>>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to
> >>>>>>>>>>>>>>>> xml-commons main
> >>>>>>>>>>>>>>>> trunk
> >>>>>>>>>>>>>>>> and apply a tag.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
> >>>>>>>>>>>>>>>> part of
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Xerces)*
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following
> >>>>>>>>>>>>>>>> packages
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> javax.xml.datatype
> >>>>>>>>>>>>>>>> javax.xml.validation
> >>>>>>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> which should reside at Xerces.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
> >>>>>>>>>>>>>>>> changes
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> into
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> that branch. This will help
> >>>>>>>>>>>>>>>> other Xerces active committers to have a chance to look
> >>>>>>>>>>>>>>>> at it
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> before
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> these changes being finally
> >>>>>>>>>>>>>>>> committed to main trunk. This process would require
> >>>>>>>>>>>>>>>> merging
> >>>>>>>>>>>>>>>> changes to
> >>>>>>>>>>>>>>>> the branch and then committing
> >>>>>>>>>>>>>>>> changes to main trunk, i seek help of active Xerces
> >>>>>>>>>>>>>>>> committers.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
> >>>>>>>>>>>>>>>> part of
> >>>>>>>>>>>>>>>> Xalan)*
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
> >>>>>>>>>>>>>>>> XPath
> >>>>>>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
> >>>>>>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also
> >>>>>>>>>>>>>>>> contains
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> changes
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> done in "javax.xml.transform" package
> >>>>>>>>>>>>>>>> for ex. now application can use the same Transformer
> >>>>>>>>>>>>>>>> instance by
> >>>>>>>>>>>>>>>> invoking reset().
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we
> >>>>>>>>>>>>>>>> create a
> >>>>>>>>>>>>>>>> branch
> >>>>>>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
> >>>>>>>>>>>>>>>> put there. This will help other Xalan active committers to
> >>>>>>>>>>>>>>>> have a
> >>>>>>>>>>>>>>>> chance
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> to look at it before these changes being finally
> >>>>>>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan
> >>>>>>>>>>>>>>>> committers
> >>>>>>>>>>>>>>>> for this
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> process.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> As always, all feedbacks are more than welcome.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>> Neeraj
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
> >>>>>>>>>>>>>>>> [2]
> >>>>>>>>>>>>>>>> http://java.sun.com/j2se/1.5.
> >>>>>>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
> >>>>>>>>>>>>>>>> [3]
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> http://java.sun.com/j2se/1.5.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> [4]
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> summary.html
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>> ---------------------------------------------------------------------
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>>> To unsubscribe, e-mail:
> >>>>>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Michael Glavassevich
> >>>>>>>>>>>>>>> XML Parser Development
> >>>>>>>>>>>>>>> IBM Toronto Lab
> >>>>>>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
> >>>>>>>>>>>>>>> E-mail: mrglavas@apache.org
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>> ---------------------------------------------------------------------
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>>>>> To unsubscribe, e-mail:
> >>>>>>>>>>>>>>> xalan-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>>>>>>> xalan-dev-help@xml.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
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>> Michael Glavassevich
> >>>>>>>>>> XML Parser Development
> >>>>>>>>>> IBM Toronto Lab
> >>>>>>>>>> E-mail: mrglavas@ca.ibm.com
> >>>>>>>>>> E-mail: mrglavas@apache.org
> >>>>>>>>>>
> >>>>>>>>>> ---------------------------------------------------------------------
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>> general-help@incubator.apache.org
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>> ---------------------------------------------------------------------
> >>>>>>>
> >>>>>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> >>>>>>> For additional commands, e-mail: general-help@xml.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
> >>>>>>
> >>>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> >>>>> For additional commands, e-mail: general-help@xml.apache.org
> >>>>>
> >>>>>
> >>>>
> >>> --
> >>> Davanum Srinivas - http://webservices.apache.org/~dims/
> >>>
> >>>
> >>
> >>
> >>
> >>
> >>
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3
complete [Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by ramesh mandava <Ra...@Sun.COM>.
Hi Dims:
> My apologies dims. Somehow this mail was skipped.
>
> Davanum Srinivas wrote:
>
>> Neeraj,
>>
>> Do you think it will be possible/useful to somehow extract/use
>> javax.xml.xpath and org.apache.xpath.jaxp with existing shipping
>> versions of Xalan+Xerces?
>>
>>
> I think it should be possible. New functionality has been added into
> org.apache.xpath.jaxp package. So by extracting that package &
> javax.xml.xpath
> it should be possible. I have cc'ed this mail to Ramesh Mandava who
> has worked on the implementation of java.xml.xpath.
> Ramesh, What is your opinion ?
We needed few changes ( specially in
org.apache.xpath.operations.Variable class ) for implementating JAXP 1.3
XPath
functionality. So we need to find out a way to override this class (
or find out some other workaround ) for using the shipped version of
Xalan. Shipped version of Xerces should be ok though.
>
>> Reason for asking, current code in apache xml-security (and even
>> cocoon for that matter) has fixed dependency on xalan's API for XPath
>
>> and i'd like to investigate if we can change that to use the
>> javax.xml.xpath instead.
>>
>>
As JAXP 1.3 RI is based on Xalan XPath API you can easily make the
switch to javax.xml.xpath. One thing to aware of here is that
'javax.xml.xpath' API won't provide you facility to add extension
functions without namespace prefix ( i.e. in default xpath namespace).
If you need to do this then you have to use the native XPath processor
provided facility ( in this case Xalan ).
Anyway we would love to see you use javax.xml.xpath API and can assist
you in anyway we can.
Regards
-Ramesh
> That's good. Let us know if you would like to know more.
> I would be happy to help.
>
> - Neeraj
>
>> thanks,
>> dims
>>
>> On 4/11/05, Davanum Srinivas <da...@gmail.com> wrote:
>>
>>
>>> Neeraj,
>>>
>>> Spotted a few typos:
>>> XPathFactory factory = XpathFactory.newInstnace();
>>> XPathFactory factory = XpathFactory.newInstance(object_model_uri);
>>>
>>> Should be:
>>> XPathFactory factory = XPathFactory.newInstance();
>>> XPathFactory factory = XPathFactory.newInstance(object_model_uri);
>>>
>>> Right?
>>>
>>> -- dims
>>>
>>> On 4/11/05, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>
>>>
>>>> Hello All,
>>>>
>>>> Sometimes back i wrote an article on JAXP 1.3 which explains the new
>>>> concepts and important features introduced in JAXP 1.3
>>>> Especially the new
>>>>
>>>> - Schema Validation Framework
>>>> - Object model neutral XPath APIs
>>>> - XML Schema Datatypes etc.
>>>>
>>>> Advantages of New Schema Validation Framework and how the new API
>>>> works
>>>> has been explained with code snippets and diagram.
>>>> New XPath APIs have also been explained. Article is available at
>>>> https://jaxp.dev.java.net/article/jaxp-1_3-article.html
>>>>
>>>> - Neeraj
>>>>
>>>> Neeraj Bajaj wrote:
>>>>
>>>>
>>>>
>>>>> Hello All,
>>>>>
>>>>> xml-commons has been upgraded to JAXP 1.3 APIs.
>>>>> If anyone could try and confirm that would be great.
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Neeraj Bajaj wrote:
>>>>>
>>>>>
>>>>>
>>>>>> I tagged xml-commons module yesterday with tag name
>>>>>> '*before-jaxp13-upgradation*'.
>>>>>>
>>>>>> I plan to do the following but i will wait till tomorrow so as to
>>>>>> give chance to the community
>>>>>> to correct me if i am doing something wrong.
>>>>>>
>>>>>> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
>>>>>> xml-commons/java/external/src directory
>>>>>> with JAXP 1.3 API sources.
>>>>>>
>>>>>> Currently in xml-commons there are sources like org.w3c.dom.views.*
>>>>>> which are not part of JAXP 1.3
>>>>>> I won't remove those sources. they will be as it is.
>>>>>>
>>>>>> * Make changes in xml-commons/java/external/build.xml file so as to
>>>>>> upgrade
>>>>>> JAXP 1.1 --> JAXP 1.3
>>>>>> DOM2 --> DOM3
>>>>>> SAX2 --> (SAX) 2.0.2 (sax2r3)
>>>>>>
>>>>>> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
>>>>>> available as xml-apis.jar.
>>>>>>
>>>>>> Anything else i should take care ?
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>>
>>>>>> Neeraj Bajaj wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Geir, I have uploaded sources at the same location
>>>>>>> (xml-commons/contrib/jaxp13)
>>>>>>> with Apache 2.0 license on every source file.
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Neeraj Bajaj wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Ok, So i will add it and upload again.
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hi Neeraj,
>>>>>>>>>>
>>>>>>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip
>>>>>>>>>> have no
>>>>>>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the
>>>>>>>>>> Apache
>>>>>>>>>> license. Will this still be the case for JAXP 1.3?
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> yes - these files must be available under the apache license v2.
>>>>>>>>> And the license grantor should be the one that adds it.
>>>>>>>>>
>>>>>>>>> Sorry Neeraj :)
>>>>>>>>>
>>>>>>>>> geir
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005
>>>>>>>>>> 06:48:30 AM:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>>>>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>>>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
>>>>>>>>>>> xalan-src.zip which
>>>>>>>>>>> corresponds to jaxp-api,
>>>>>>>>>>> xerces & xalan sources respectively.
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> That really sounds good to me.. so i would try to finish it
>>>>>>>>>>>> today.
>>>>>>>>>>>> I will send mail to the community when i am done.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks dims for the suggestion.
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>> Davanum Srinivas wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Neeraj,
>>>>>>>>>>>>>
>>>>>>>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>>>>>>>> xml-commons/contrib/jaxp13
>>>>>>>>>>>>> cvs so everyone can take a look (and then pick on the bits
>>>>>>>>>>>>> they
>>>>>>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP
>>>>>>>>>>>>> (after
>>>>>>>>>>>>> tagging the current code in the main trunk there) and it's
>>>>>>>>>>>>> upto the
>>>>>>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they
>>>>>>>>>>>>> fit.
>>>>>>>>>>>>>
>>>>>>>>>>>>> thanks,
>>>>>>>>>>>>> dims
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks Michael for your response.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I was just wondering what would be idle time to wait
>>>>>>>>>>>>>> before i
>>>>>>>>>>>>>> start
>>>>>>>>>>>>>> work
>>>>>>>>>>>>>> on this ?
>>>>>>>>>>>>>> Does anyone has an opinion, Is there any other list where i
>>>>>>>>>>>>>> should
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>> send
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>> this mail
>>>>>>>>>>>>>> before making changes ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Neeraj,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk,
>>>>>>>>>>>>>>> tagging it
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>> and
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>> making a branch for the old JAXP sources on the current
>>>>>>>>>>>>>>> main trunk.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
>>>>>>>>>>>>>>> other
>>>>>>>>>>>>>>> updates
>>>>>>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
>>>>>>>>>>>>>>> branch we've
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> used
>>>>>>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and
>>>>>>>>>>>>>>> Xalan. I
>>>>>>>>>>>>>>> assume a
>>>>>>>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
>>>>>>>>>>>>>>> 03:40:57
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>> AM:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
>>>>>>>>>>>>>>>> attached as
>>>>>>>>>>>>>>>> zip but
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> <error>
>>>>>>>>>>>>>>>> ----- The following addresses had permanent fatal
>>>>>>>>>>>>>>>> errors -----
>>>>>>>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>>>>>>>> </error>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>>>>>>>> Apache
>>>>>>>>>>>>>>>> server somewhere ?
>>>>>>>>>>>>>>>> Can anyone guide me what is the procedure for such code
>>>>>>>>>>>>>>>> grants ?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I am looking help from the active committers of Xerces
>>>>>>>>>>>>>>>> & Xalan
>>>>>>>>>>>>>>>> community
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> to help put it in a
>>>>>>>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>>>>>>>> number of
>>>>>>>>>>>>>>>> changes it would be a considerable
>>>>>>>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>>>>>>>> community to
>>>>>>>>>>>>>>>> have a
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> look at the code before
>>>>>>>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I think i have commit access at xml-commons so i can
>>>>>>>>>>>>>>>> commit
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> sources
>>>>>>>>>>>>>>>> in xml-commons branch
>>>>>>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>>>>>>>> What is
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> the
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> opinion of community ? I can
>>>>>>>>>>>>>>>> start this as soon as i get a consensus from the
>>>>>>>>>>>>>>>> community. My
>>>>>>>>>>>>>>>> preference is to put the sources on
>>>>>>>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3
>>>>>>>>>>>>>>>> APIs +
>>>>>>>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>>>>>>>> JAXP 1.3 (JSR 206
>>>>>>>>>>>>>>>> <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole
>>>>>>>>>>>>>>>> lot of
>>>>>>>>>>>>>>>> new
>>>>>>>>>>>>>>>> functionalities.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>>>>>>>> * Reuse parser instance
>>>>>>>>>>>>>>>> * Security enhancements
>>>>>>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3
>>>>>>>>>>>>>>>> Load &
>>>>>>>>>>>>>>>> Save, SAX
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Due to large size of code base i will be sending different
>>>>>>>>>>>>>>>> mails
>>>>>>>>>>>>>>>> for the
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>>>>>>>> process of
>>>>>>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>>>>>>>> integrating this donation into the main stream work of
>>>>>>>>>>>>>>>> Xerces &
>>>>>>>>>>>>>>>> Xalan.
>>>>>>>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>>>>>>>> and we can discuss more about the technicalities of
>>>>>>>>>>>>>>>> merging
>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>> in the
>>>>>>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>>>>>>>> community.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
>>>>>>>>>>>>>>>>>>> up the
>>>>>>>>>>>>>>>>>>> ball
>>>>>>>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>>>>>>>> presume that
>>>>>>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has
>>>>>>>>>>>>>>>>>> been
>>>>>>>>>>>>>>>>>> achieved.
>>>>>>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't
>>>>>>>>>>>>>>>>>> let the
>>>>>>>>>>>>>>>>>> process
>>>>>>>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>> ----------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> Subject:
>>>>>>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>>>>>>>> From:
>>>>>>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>>>>>>>> Date:
>>>>>>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> To:
>>>>>>>>>>>>>>>> general@xml.apache.org
>>>>>>>>>>>>>>>> CC:
>>>>>>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> <Je...@Sun.COM>,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has
>>>>>>>>>>>>>>>> become
>>>>>>>>>>>>>>>> final. JAXP
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 1.3 adds lots of new features in the area of XML
>>>>>>>>>>>>>>>> processing.
>>>>>>>>>>>>>>>> It introduces new Schema independent validation framework
>>>>>>>>>>>>>>>> which
>>>>>>>>>>>>>>>> decouples the validation as a process independent from
>>>>>>>>>>>>>>>> parsing.
>>>>>>>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>>>>>>>> representation
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> of
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> Grammar which can validate different instances of XML
>>>>>>>>>>>>>>>> document
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> thus
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> greatly improving the performance of XML processing.
>>>>>>>>>>>>>>>> XPath
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> language
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> provides a simple, concise syntax for accessing individual
>>>>>>>>>>>>>>>> parts
>>>>>>>>>>>>>>>> of an
>>>>>>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>>>>>>>> access to
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> XPath evaluation environment and expression results
>>>>>>>>>>>>>>>> independent
>>>>>>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds
>>>>>>>>>>>>>>>> new
>>>>>>>>>>>>>>>> Datatypes to
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> the Java platform which maps to some of the W3C XML
>>>>>>>>>>>>>>>> Schema
>>>>>>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>>>>>>>> 1.3 also
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> adds
>>>>>>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> allowing
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> application to reuse the same instance to process
>>>>>>>>>>>>>>>> multiple XML
>>>>>>>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> performance.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
>>>>>>>>>>>>>>>> DOM L3
>>>>>>>>>>>>>>>> L/S, XML
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
>>>>>>>>>>>>>>>> (API s +
>>>>>>>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> (Reference
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
>>>>>>>>>>>>>>>> of newly
>>>>>>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>>>>>>>> , Datatypes [4] implementation, SAXParser,
>>>>>>>>>>>>>>>> DocumentBuilder,
>>>>>>>>>>>>>>>> Transformer
>>>>>>>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S,
>>>>>>>>>>>>>>>> XML 1.1,
>>>>>>>>>>>>>>>> XInclude
>>>>>>>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>>>>>>>> JAXP 1.3
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> RI
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>>>>>>>> suggested where implementation component should reside
>>>>>>>>>>>>>>>> i.e. Xerces
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> or
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache
>>>>>>>>>>>>>>>> xml-commons,
>>>>>>>>>>>>>>>> Xerces &
>>>>>>>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>>>>>>>> set of
>>>>>>>>>>>>>>>> APIs
>>>>>>>>>>>>>>>> are used by many different projects.
>>>>>>>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>>>>>>>> emerging, we
>>>>>>>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to
>>>>>>>>>>>>>>>> xml-commons main
>>>>>>>>>>>>>>>> trunk
>>>>>>>>>>>>>>>> and apply a tag.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>>>>>> part of
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Xerces)*
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following
>>>>>>>>>>>>>>>> packages
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> javax.xml.datatype
>>>>>>>>>>>>>>>> javax.xml.validation
>>>>>>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
>>>>>>>>>>>>>>>> changes
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> into
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> that branch. This will help
>>>>>>>>>>>>>>>> other Xerces active committers to have a chance to look
>>>>>>>>>>>>>>>> at it
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> before
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> these changes being finally
>>>>>>>>>>>>>>>> committed to main trunk. This process would require
>>>>>>>>>>>>>>>> merging
>>>>>>>>>>>>>>>> changes to
>>>>>>>>>>>>>>>> the branch and then committing
>>>>>>>>>>>>>>>> changes to main trunk, i seek help of active Xerces
>>>>>>>>>>>>>>>> committers.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>>>>>> part of
>>>>>>>>>>>>>>>> Xalan)*
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
>>>>>>>>>>>>>>>> XPath
>>>>>>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also
>>>>>>>>>>>>>>>> contains
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> changes
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>>>>>>>> for ex. now application can use the same Transformer
>>>>>>>>>>>>>>>> instance by
>>>>>>>>>>>>>>>> invoking reset().
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we
>>>>>>>>>>>>>>>> create a
>>>>>>>>>>>>>>>> branch
>>>>>>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>>>>>>>> have a
>>>>>>>>>>>>>>>> chance
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan
>>>>>>>>>>>>>>>> committers
>>>>>>>>>>>>>>>> for this
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> process.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>> Neeraj
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>>>>>>>> [2]
>>>>>>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>>>>>>>> [3]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [4]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> summary.html
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Michael Glavassevich
>>>>>>>>>>>>>>> XML Parser Development
>>>>>>>>>>>>>>> IBM Toronto Lab
>>>>>>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>>>> xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>>> xalan-dev-help@xml.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
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> Michael Glavassevich
>>>>>>>>>> XML Parser Development
>>>>>>>>>> IBM Toronto Lab
>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> general-help@incubator.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>>>>>> For additional commands, e-mail: general-help@xml.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
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: general-help@xml.apache.org
>>>>>
>>>>>
>>>>
>>> --
>>> Davanum Srinivas - http://webservices.apache.org/~dims/
>>>
>>>
>>
>>
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3
complete [Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
My apologies dims. Somehow this mail was skipped.
Davanum Srinivas wrote:
>Neeraj,
>
>Do you think it will be possible/useful to somehow extract/use
>javax.xml.xpath and org.apache.xpath.jaxp with existing shipping
>versions of Xalan+Xerces?
>
>
I think it should be possible. New functionality has been added into
org.apache.xpath.jaxp package. So by extracting that package &
javax.xml.xpath
it should be possible. I have cc'ed this mail to Ramesh Mandava who
has worked on the implementation of java.xml.xpath.
Ramesh, What is your opinion ?
>Reason for asking, current code in apache xml-security (and even
>cocoon for that matter) has fixed dependency on xalan's API for XPath
>and i'd like to investigate if we can change that to use the
>javax.xml.xpath instead.
>
>
That's good. Let us know if you would like to know more.
I would be happy to help.
- Neeraj
>thanks,
>dims
>
>On 4/11/05, Davanum Srinivas <da...@gmail.com> wrote:
>
>
>>Neeraj,
>>
>>Spotted a few typos:
>>XPathFactory factory = XpathFactory.newInstnace();
>>XPathFactory factory = XpathFactory.newInstance(object_model_uri);
>>
>>Should be:
>>XPathFactory factory = XPathFactory.newInstance();
>>XPathFactory factory = XPathFactory.newInstance(object_model_uri);
>>
>>Right?
>>
>>-- dims
>>
>>On 4/11/05, Neeraj Bajaj <Ne...@sun.com> wrote:
>>
>>
>>>Hello All,
>>>
>>>Sometimes back i wrote an article on JAXP 1.3 which explains the new
>>>concepts and important features introduced in JAXP 1.3
>>>Especially the new
>>>
>>>- Schema Validation Framework
>>>- Object model neutral XPath APIs
>>>- XML Schema Datatypes etc.
>>>
>>>Advantages of New Schema Validation Framework and how the new API works
>>>has been explained with code snippets and diagram.
>>>New XPath APIs have also been explained. Article is available at
>>>https://jaxp.dev.java.net/article/jaxp-1_3-article.html
>>>
>>>- Neeraj
>>>
>>>Neeraj Bajaj wrote:
>>>
>>>
>>>
>>>>Hello All,
>>>>
>>>>xml-commons has been upgraded to JAXP 1.3 APIs.
>>>>If anyone could try and confirm that would be great.
>>>>
>>>>- Neeraj
>>>>
>>>>Neeraj Bajaj wrote:
>>>>
>>>>
>>>>
>>>>>I tagged xml-commons module yesterday with tag name
>>>>>'*before-jaxp13-upgradation*'.
>>>>>
>>>>>I plan to do the following but i will wait till tomorrow so as to
>>>>>give chance to the community
>>>>>to correct me if i am doing something wrong.
>>>>>
>>>>>* update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
>>>>>xml-commons/java/external/src directory
>>>>>with JAXP 1.3 API sources.
>>>>>
>>>>>Currently in xml-commons there are sources like org.w3c.dom.views.*
>>>>>which are not part of JAXP 1.3
>>>>>I won't remove those sources. they will be as it is.
>>>>>
>>>>>* Make changes in xml-commons/java/external/build.xml file so as to
>>>>>upgrade
>>>>>JAXP 1.1 --> JAXP 1.3
>>>>>DOM2 --> DOM3
>>>>>SAX2 --> (SAX) 2.0.2 (sax2r3)
>>>>>
>>>>>* Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
>>>>>available as xml-apis.jar.
>>>>>
>>>>>Anything else i should take care ?
>>>>>
>>>>>- Neeraj
>>>>>
>>>>>
>>>>>Neeraj Bajaj wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Geir, I have uploaded sources at the same location
>>>>>>(xml-commons/contrib/jaxp13)
>>>>>>with Apache 2.0 license on every source file.
>>>>>>
>>>>>>- Neeraj
>>>>>>
>>>>>>Neeraj Bajaj wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Ok, So i will add it and upload again.
>>>>>>>
>>>>>>>- Neeraj
>>>>>>>
>>>>>>>Geir Magnusson Jr. wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Hi Neeraj,
>>>>>>>>>
>>>>>>>>>I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>>>>>>>license on them. The JAXP 1.2 sources in xml-commons carry the
>>>>>>>>>Apache
>>>>>>>>>license. Will this still be the case for JAXP 1.3?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>yes - these files must be available under the apache license v2.
>>>>>>>>And the license grantor should be the one that adds it.
>>>>>>>>
>>>>>>>>Sorry Neeraj :)
>>>>>>>>
>>>>>>>>geir
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Thanks.
>>>>>>>>>
>>>>>>>>>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>Ok I just finished uploading JAXP 1.3 sources in
>>>>>>>>>>"*xml-commons/contrib/jaxp13"* directory.
>>>>>>>>>>There are 3 files, jsr-206-src.zip, xml-xerces.zip,
>>>>>>>>>>xalan-src.zip which
>>>>>>>>>>corresponds to jaxp-api,
>>>>>>>>>>xerces & xalan sources respectively.
>>>>>>>>>>
>>>>>>>>>>- Neeraj
>>>>>>>>>>
>>>>>>>>>>Neeraj Bajaj wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>That really sounds good to me.. so i would try to finish it today.
>>>>>>>>>>>I will send mail to the community when i am done.
>>>>>>>>>>>
>>>>>>>>>>>Thanks dims for the suggestion.
>>>>>>>>>>>
>>>>>>>>>>>- Neeraj
>>>>>>>>>>>
>>>>>>>>>>>Davanum Srinivas wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>Neeraj,
>>>>>>>>>>>>
>>>>>>>>>>>>my 2 cents...upload the whole thing say in
>>>>>>>>>>>>xml-commons/contrib/jaxp13
>>>>>>>>>>>>cvs so everyone can take a look (and then pick on the bits they
>>>>>>>>>>>>want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>>>>>>>tagging the current code in the main trunk there) and it's
>>>>>>>>>>>>upto the
>>>>>>>>>>>>xml xerces/xalan folks to start picking up stuff as/when they
>>>>>>>>>>>>fit.
>>>>>>>>>>>>
>>>>>>>>>>>>thanks,
>>>>>>>>>>>>dims
>>>>>>>>>>>>
>>>>>>>>>>>>On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
>>>>>>>>>>>>wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>Thanks Michael for your response.
>>>>>>>>>>>>>
>>>>>>>>>>>>>I was just wondering what would be idle time to wait before i
>>>>>>>>>>>>>start
>>>>>>>>>>>>>work
>>>>>>>>>>>>>on this ?
>>>>>>>>>>>>>Does anyone has an opinion, Is there any other list where i
>>>>>>>>>>>>>should
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>send
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>this mail
>>>>>>>>>>>>>before making changes ?
>>>>>>>>>>>>>
>>>>>>>>>>>>>- Neeraj
>>>>>>>>>>>>>
>>>>>>>>>>>>>Michael Glavassevich wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>Hi Neeraj,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>+1 to putting the JAXP 1.3 sources on the main trunk,
>>>>>>>>>>>>>>tagging it
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>and
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>making a branch for the old JAXP sources on the current
>>>>>>>>>>>>>>main trunk.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>There exists a branch called tck-jaxp-1_2_0 where fixes and
>>>>>>>>>>>>>>other
>>>>>>>>>>>>>>updates
>>>>>>>>>>>>>>have been applied to the JAXP 1.2 sources. This is the
>>>>>>>>>>>>>>branch we've
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>used
>>>>>>>>>>>>>>for generating the xml-apis.jar shipped with Xerces and
>>>>>>>>>>>>>>Xalan. I
>>>>>>>>>>>>>>assume a
>>>>>>>>>>>>>>similar branch will exist for 1.3.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
>>>>>>>>>>>>>>03:40:57
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>AM:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>Hello All,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>I sent the mail below with JAXP 1.3 APIs source code
>>>>>>>>>>>>>>>attached as
>>>>>>>>>>>>>>>zip but
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>mail bounced back with the following message
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>><error>
>>>>>>>>>>>>>>>----- The following addresses had permanent fatal errors -----
>>>>>>>>>>>>>>><ge...@xml.apache.org>
>>>>>>>>>>>>>>>(reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>>>>>>></error>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>What should i do now ? Is there a way to upload sources on
>>>>>>>>>>>>>>>Apache
>>>>>>>>>>>>>>>server somewhere ?
>>>>>>>>>>>>>>>Can anyone guide me what is the procedure for such code
>>>>>>>>>>>>>>>grants ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>>>>>>>community
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>to help put it in a
>>>>>>>>>>>>>>>a branch and make it work there. As i think due to large
>>>>>>>>>>>>>>>number of
>>>>>>>>>>>>>>>changes it would be a considerable
>>>>>>>>>>>>>>>amount of work. This will also help the committers &
>>>>>>>>>>>>>>>community to
>>>>>>>>>>>>>>>have a
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>look at the code before
>>>>>>>>>>>>>>>it is merged into the main stream work.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>I think i have commit access at xml-commons so i can commit
>>>>>>>>>>>>>>>the
>>>>>>>>>>>>>>>sources
>>>>>>>>>>>>>>>in xml-commons branch
>>>>>>>>>>>>>>>or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>>>>>>>What is
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>the
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>opinion of community ? I can
>>>>>>>>>>>>>>>start this as soon as i get a consensus from the community. My
>>>>>>>>>>>>>>>preference is to put the sources on
>>>>>>>>>>>>>>>xml-commons main trunk.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>Please let me know how should i proceed.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>Thanks,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>- Neeraj
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>Hello All,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>>>>>>>implementation to Apache XML.*
>>>>>>>>>>>>>>>JAXP 1.3 (JSR 206
>>>>>>>>>>>>>>><http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>>>>>>>significant advancement over JAXP 1.2 and adds whole lot of
>>>>>>>>>>>>>>>new
>>>>>>>>>>>>>>>functionalities.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>* New Schema Validation Framework
>>>>>>>>>>>>>>>* New Object Model neutral XPath APIs
>>>>>>>>>>>>>>>* New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>>>>>>>* Reuse parser instance
>>>>>>>>>>>>>>>* Security enhancements
>>>>>>>>>>>>>>>* Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>>>>>>>Save, SAX
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>2, XML 1.1 and XInclude)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>*JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>Due to large size of code base i will be sending different
>>>>>>>>>>>>>>>mails
>>>>>>>>>>>>>>>for the
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>source code of Xerces & Xalan.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>I have attached the original mail where i proposed the
>>>>>>>>>>>>>>>process of
>>>>>>>>>>>>>>>upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>>>>>>>integrating this donation into the main stream work of
>>>>>>>>>>>>>>>Xerces &
>>>>>>>>>>>>>>>Xalan.
>>>>>>>>>>>>>>>There was a general consensus to my proposal
>>>>>>>>>>>>>>>and we can discuss more about the technicalities of merging
>>>>>>>>>>>>>>>with
>>>>>>>>>>>>>>>in the
>>>>>>>>>>>>>>>appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>>>>>>>community.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>- Neeraj
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>Neeraj Bajaj wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>Geir Magnusson Jr. wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>Excellent news! Thank to Sun folk and Geir for picking
>>>>>>>>>>>>>>>>>>up the
>>>>>>>>>>>>>>>>>>ball
>>>>>>>>>>>>>>>>>>on this one.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>>>>>>>presume that
>>>>>>>>>>>>>>>>>>Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>>>>>>>xalan-dev, and
>>>>>>>>>>>>>>>>>>xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>>>>>>>achieved.
>>>>>>>>>>>>>>>>>I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>>>>>>>process
>>>>>>>>>>>>>>>>>hold things up.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>Great... Thanks Geir. No more held up is good
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>- Neeraj
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>---------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>>To unsubscribe, e-mail:
>>>>>>>>>>>>>>>>xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>>>>>>For additional commands, e-mail:
>>>>>>>>>>>>>>>>xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>----------------------------------------------------------------------
>>>>>>>>>>--
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>Subject:
>>>>>>>>>>>>>>>Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>>>>>>>From:
>>>>>>>>>>>>>>>Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>>>>>>>Date:
>>>>>>>>>>>>>>>Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>To:
>>>>>>>>>>>>>>>general@xml.apache.org
>>>>>>>>>>>>>>>CC:
>>>>>>>>>>>>>>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>>>>>>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>>>>>>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>>>>>>><Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>><Je...@Sun.COM>,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>Hello All,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>>>>>>>final. JAXP
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>>>>>>>It introduces new Schema independent validation framework
>>>>>>>>>>>>>>>which
>>>>>>>>>>>>>>>decouples the validation as a process independent from
>>>>>>>>>>>>>>>parsing.
>>>>>>>>>>>>>>>It allows to compile Schema to an immutable memory
>>>>>>>>>>>>>>>representation
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>of
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>Grammar which can validate different instances of XML document
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>thus
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>greatly improving the performance of XML processing. XPath
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>language
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>provides a simple, concise syntax for accessing individual
>>>>>>>>>>>>>>>parts
>>>>>>>>>>>>>>>of an
>>>>>>>>>>>>>>>XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>>>>>>>access to
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>the
>>>>>>>>>>>>>>>XPath evaluation environment and expression results
>>>>>>>>>>>>>>>independent
>>>>>>>>>>>>>>>of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>>>>>>>Datatypes to
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>>>>>>>Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>>>>>>>1.3 also
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>adds
>>>>>>>>>>>>>>>the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>allowing
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>application to reuse the same instance to process multiple XML
>>>>>>>>>>>>>>>documents. This also helps in increasing XML processing
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>performance.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
>>>>>>>>>>>>>>>DOM L3
>>>>>>>>>>>>>>>L/S, XML
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>1.1, XInclude.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>*Sun Microsystems would like to donate JAXP 1.3 sources
>>>>>>>>>>>>>>>(API s +
>>>>>>>>>>>>>>>Reference Implementation) to Apache. *
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>/Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>(Reference
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>Implementation). RI has been done using
>>>>>>>>>>>>>>>Xerces/Xalan as code base. RI contains the implementation
>>>>>>>>>>>>>>>of newly
>>>>>>>>>>>>>>>introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>>>>>>>, Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>>>>>>>Transformer
>>>>>>>>>>>>>>>Reset changes, Secured XML Processing changes.
>>>>>>>>>>>>>>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>>>>>>>XInclude
>>>>>>>>>>>>>>>already exist on Apache Xerces. So in the next
>>>>>>>>>>>>>>>section I have also proposed the way to merge rest of the
>>>>>>>>>>>>>>>JAXP 1.3
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>RI
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>>>>>>>suggested where implementation component should reside
>>>>>>>>>>>>>>>i.e. Xerces
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>or
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>Xalan. Any idea or feedback for the smoother and
>>>>>>>>>>>>>>>expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>>>>>>>Xerces &
>>>>>>>>>>>>>>>Xalan is very welcome.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>*JAXP 1.3 APIs: *
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>>>>>>>set of
>>>>>>>>>>>>>>>APIs
>>>>>>>>>>>>>>>are used by many different projects.
>>>>>>>>>>>>>>>With JSR 206 declared as final and many new standards
>>>>>>>>>>>>>>>emerging, we
>>>>>>>>>>>>>>>should update xml-commons to JAXP 1.3
>>>>>>>>>>>>>>>APIs. I propose JAXP 1.3 APIs to be committed to
>>>>>>>>>>>>>>>xml-commons main
>>>>>>>>>>>>>>>trunk
>>>>>>>>>>>>>>>and apply a tag.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>*JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>>>>>part of
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>Xerces)*
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>javax.xml.datatype
>>>>>>>>>>>>>>>javax.xml.validation
>>>>>>>>>>>>>>>javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>which should reside at Xerces.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>I propose that we create a branch, and merge JAXP 1.3 RI
>>>>>>>>>>>>>>>changes
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>into
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>that branch. This will help
>>>>>>>>>>>>>>>other Xerces active committers to have a chance to look at it
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>before
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>these changes being finally
>>>>>>>>>>>>>>>committed to main trunk. This process would require merging
>>>>>>>>>>>>>>>changes to
>>>>>>>>>>>>>>>the branch and then committing
>>>>>>>>>>>>>>>changes to main trunk, i seek help of active Xerces
>>>>>>>>>>>>>>>committers.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>*JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>>>>>part of
>>>>>>>>>>>>>>>Xalan)*
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>JAXP 1.3 RI also has the implementation of newly developed
>>>>>>>>>>>>>>>XPath
>>>>>>>>>>>>>>>(javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>>>>>>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>changes
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>done in "javax.xml.transform" package
>>>>>>>>>>>>>>>for ex. now application can use the same Transformer
>>>>>>>>>>>>>>>instance by
>>>>>>>>>>>>>>>invoking reset().
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>I propose the same for the Xalan/XSLTC project that we
>>>>>>>>>>>>>>>create a
>>>>>>>>>>>>>>>branch
>>>>>>>>>>>>>>>and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>>>>>>>put there. This will help other Xalan active committers to
>>>>>>>>>>>>>>>have a
>>>>>>>>>>>>>>>chance
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>to look at it before these changes being finally
>>>>>>>>>>>>>>>committed to main trunk. Again i seek help of Xalan
>>>>>>>>>>>>>>>committers
>>>>>>>>>>>>>>>for this
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>process.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>As always, all feedbacks are more than welcome.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>Thanks,
>>>>>>>>>>>>>>>Neeraj
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>>>>>>>[2]
>>>>>>>>>>>>>>>http://java.sun.com/j2se/1.5.
>>>>>>>>>>>>>>>0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>>>>>>>[3]
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>http://java.sun.com/j2se/1.5.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>[4]
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>summary.html
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>---------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>To unsubscribe, e-mail:
>>>>>>>>>>>>>>>xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>>>>>For additional commands, e-mail:
>>>>>>>>>>>>>>>xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>Michael Glavassevich
>>>>>>>>>>>>>>XML Parser Development
>>>>>>>>>>>>>>IBM Toronto Lab
>>>>>>>>>>>>>>E-mail: mrglavas@ca.ibm.com
>>>>>>>>>>>>>>E-mail: mrglavas@apache.org
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>---------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>>>>For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>Michael Glavassevich
>>>>>>>>>XML Parser Development
>>>>>>>>>IBM Toronto Lab
>>>>>>>>>E-mail: mrglavas@ca.ibm.com
>>>>>>>>>E-mail: mrglavas@apache.org
>>>>>>>>>
>>>>>>>>>---------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>>>>>For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>---------------------------------------------------------------------
>>>>>>To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>>>>>For additional commands, e-mail: general-help@xml.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
>>>>>
>>>>>
>>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>>>For additional commands, e-mail: general-help@xml.apache.org
>>>>
>>>>
>>>>
>>--
>>Davanum Srinivas - http://webservices.apache.org/~dims/
>>
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by Davanum Srinivas <da...@gmail.com>.
Neeraj,
Do you think it will be possible/useful to somehow extract/use
javax.xml.xpath and org.apache.xpath.jaxp with existing shipping
versions of Xalan+Xerces?
Reason for asking, current code in apache xml-security (and even
cocoon for that matter) has fixed dependency on xalan's API for XPath
and i'd like to investigate if we can change that to use the
javax.xml.xpath instead.
thanks,
dims
On 4/11/05, Davanum Srinivas <da...@gmail.com> wrote:
> Neeraj,
>
> Spotted a few typos:
> XPathFactory factory = XpathFactory.newInstnace();
> XPathFactory factory = XpathFactory.newInstance(object_model_uri);
>
> Should be:
> XPathFactory factory = XPathFactory.newInstance();
> XPathFactory factory = XPathFactory.newInstance(object_model_uri);
>
> Right?
>
> -- dims
>
> On 4/11/05, Neeraj Bajaj <Ne...@sun.com> wrote:
> > Hello All,
> >
> > Sometimes back i wrote an article on JAXP 1.3 which explains the new
> > concepts and important features introduced in JAXP 1.3
> > Especially the new
> >
> > - Schema Validation Framework
> > - Object model neutral XPath APIs
> > - XML Schema Datatypes etc.
> >
> > Advantages of New Schema Validation Framework and how the new API works
> > has been explained with code snippets and diagram.
> > New XPath APIs have also been explained. Article is available at
> > https://jaxp.dev.java.net/article/jaxp-1_3-article.html
> >
> > - Neeraj
> >
> > Neeraj Bajaj wrote:
> >
> > > Hello All,
> > >
> > > xml-commons has been upgraded to JAXP 1.3 APIs.
> > > If anyone could try and confirm that would be great.
> > >
> > > - Neeraj
> > >
> > > Neeraj Bajaj wrote:
> > >
> > >> I tagged xml-commons module yesterday with tag name
> > >> '*before-jaxp13-upgradation*'.
> > >>
> > >> I plan to do the following but i will wait till tomorrow so as to
> > >> give chance to the community
> > >> to correct me if i am doing something wrong.
> > >>
> > >> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
> > >> xml-commons/java/external/src directory
> > >> with JAXP 1.3 API sources.
> > >>
> > >> Currently in xml-commons there are sources like org.w3c.dom.views.*
> > >> which are not part of JAXP 1.3
> > >> I won't remove those sources. they will be as it is.
> > >>
> > >> * Make changes in xml-commons/java/external/build.xml file so as to
> > >> upgrade
> > >> JAXP 1.1 --> JAXP 1.3
> > >> DOM2 --> DOM3
> > >> SAX2 --> (SAX) 2.0.2 (sax2r3)
> > >>
> > >> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
> > >> available as xml-apis.jar.
> > >>
> > >> Anything else i should take care ?
> > >>
> > >> - Neeraj
> > >>
> > >>
> > >> Neeraj Bajaj wrote:
> > >>
> > >>> Geir, I have uploaded sources at the same location
> > >>> (xml-commons/contrib/jaxp13)
> > >>> with Apache 2.0 license on every source file.
> > >>>
> > >>> - Neeraj
> > >>>
> > >>> Neeraj Bajaj wrote:
> > >>>
> > >>>> Ok, So i will add it and upload again.
> > >>>>
> > >>>> - Neeraj
> > >>>>
> > >>>> Geir Magnusson Jr. wrote:
> > >>>>
> > >>>>>
> > >>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
> > >>>>>
> > >>>>>> Hi Neeraj,
> > >>>>>>
> > >>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
> > >>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the
> > >>>>>> Apache
> > >>>>>> license. Will this still be the case for JAXP 1.3?
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> yes - these files must be available under the apache license v2.
> > >>>>> And the license grantor should be the one that adds it.
> > >>>>>
> > >>>>> Sorry Neeraj :)
> > >>>>>
> > >>>>> geir
> > >>>>>
> > >>>>>>
> > >>>>>> Thanks.
> > >>>>>>
> > >>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
> > >>>>>>
> > >>>>>>> Ok I just finished uploading JAXP 1.3 sources in
> > >>>>>>> "*xml-commons/contrib/jaxp13"* directory.
> > >>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
> > >>>>>>> xalan-src.zip which
> > >>>>>>> corresponds to jaxp-api,
> > >>>>>>> xerces & xalan sources respectively.
> > >>>>>>>
> > >>>>>>> - Neeraj
> > >>>>>>>
> > >>>>>>> Neeraj Bajaj wrote:
> > >>>>>>>
> > >>>>>>>> That really sounds good to me.. so i would try to finish it today.
> > >>>>>>>> I will send mail to the community when i am done.
> > >>>>>>>>
> > >>>>>>>> Thanks dims for the suggestion.
> > >>>>>>>>
> > >>>>>>>> - Neeraj
> > >>>>>>>>
> > >>>>>>>> Davanum Srinivas wrote:
> > >>>>>>>>
> > >>>>>>>>> Neeraj,
> > >>>>>>>>>
> > >>>>>>>>> my 2 cents...upload the whole thing say in
> > >>>>>>>>> xml-commons/contrib/jaxp13
> > >>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
> > >>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
> > >>>>>>>>> tagging the current code in the main trunk there) and it's
> > >>>>>>>>> upto the
> > >>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they
> > >>>>>>>>> fit.
> > >>>>>>>>>
> > >>>>>>>>> thanks,
> > >>>>>>>>> dims
> > >>>>>>>>>
> > >>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
> > >>>>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>> Thanks Michael for your response.
> > >>>>>>>>>>
> > >>>>>>>>>> I was just wondering what would be idle time to wait before i
> > >>>>>>>>>> start
> > >>>>>>>>>> work
> > >>>>>>>>>> on this ?
> > >>>>>>>>>> Does anyone has an opinion, Is there any other list where i
> > >>>>>>>>>> should
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>> send
> > >>>>>>
> > >>>>>>>>>> this mail
> > >>>>>>>>>> before making changes ?
> > >>>>>>>>>>
> > >>>>>>>>>> - Neeraj
> > >>>>>>>>>>
> > >>>>>>>>>> Michael Glavassevich wrote:
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>> Hi Neeraj,
> > >>>>>>>>>>>
> > >>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk,
> > >>>>>>>>>>> tagging it
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>> and
> > >>>>>>
> > >>>>>>>>>>> making a branch for the old JAXP sources on the current
> > >>>>>>>>>>> main trunk.
> > >>>>>>>>>>>
> > >>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
> > >>>>>>>>>>> other
> > >>>>>>>>>>> updates
> > >>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
> > >>>>>>>>>>> branch we've
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>
> > >>>>>>>>>>> used
> > >>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and
> > >>>>>>>>>>> Xalan. I
> > >>>>>>>>>>> assume a
> > >>>>>>>>>>> similar branch will exist for 1.3.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
> > >>>>>>>>>>> 03:40:57
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>> AM:
> > >>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> Hello All,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
> > >>>>>>>>>>>> attached as
> > >>>>>>>>>>>> zip but
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> mail bounced back with the following message
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> <error>
> > >>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
> > >>>>>>>>>>>> <ge...@xml.apache.org>
> > >>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
> > >>>>>>>>>>>> </error>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
> > >>>>>>>>>>>> Apache
> > >>>>>>>>>>>> server somewhere ?
> > >>>>>>>>>>>> Can anyone guide me what is the procedure for such code
> > >>>>>>>>>>>> grants ?
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
> > >>>>>>>>>>>> community
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> to help put it in a
> > >>>>>>>>>>>> a branch and make it work there. As i think due to large
> > >>>>>>>>>>>> number of
> > >>>>>>>>>>>> changes it would be a considerable
> > >>>>>>>>>>>> amount of work. This will also help the committers &
> > >>>>>>>>>>>> community to
> > >>>>>>>>>>>> have a
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> look at the code before
> > >>>>>>>>>>>> it is merged into the main stream work.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I think i have commit access at xml-commons so i can commit
> > >>>>>>>>>>>> the
> > >>>>>>>>>>>> sources
> > >>>>>>>>>>>> in xml-commons branch
> > >>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
> > >>>>>>>>>>>> What is
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> the
> > >>>>>>
> > >>>>>>>>>>>> opinion of community ? I can
> > >>>>>>>>>>>> start this as soon as i get a consensus from the community. My
> > >>>>>>>>>>>> preference is to put the sources on
> > >>>>>>>>>>>> xml-commons main trunk.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Please let me know how should i proceed.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Thanks,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> - Neeraj
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Hello All,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> > >>>>>>>>>>>> implementation to Apache XML.*
> > >>>>>>>>>>>> JAXP 1.3 (JSR 206
> > >>>>>>>>>>>> <http://www.jcp.org/en/jsr/detail?id=206>) is
> > >>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of
> > >>>>>>>>>>>> new
> > >>>>>>>>>>>> functionalities.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * New Schema Validation Framework
> > >>>>>>>>>>>> * New Object Model neutral XPath APIs
> > >>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
> > >>>>>>>>>>>> * Reuse parser instance
> > >>>>>>>>>>>> * Security enhancements
> > >>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
> > >>>>>>>>>>>> Save, SAX
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> 2, XML 1.1 and XInclude)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Due to large size of code base i will be sending different
> > >>>>>>>>>>>> mails
> > >>>>>>>>>>>> for the
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> source code of Xerces & Xalan.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I have attached the original mail where i proposed the
> > >>>>>>>>>>>> process of
> > >>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
> > >>>>>>>>>>>> integrating this donation into the main stream work of
> > >>>>>>>>>>>> Xerces &
> > >>>>>>>>>>>> Xalan.
> > >>>>>>>>>>>> There was a general consensus to my proposal
> > >>>>>>>>>>>> and we can discuss more about the technicalities of merging
> > >>>>>>>>>>>> with
> > >>>>>>>>>>>> in the
> > >>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
> > >>>>>>>>>>>> community.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> - Neeraj
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Neeraj Bajaj wrote:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>> Geir Magnusson Jr. wrote:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
> > >>>>>>>>>>>>>>> up the
> > >>>>>>>>>>>>>>> ball
> > >>>>>>>>>>>>>>> on this one.
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
> > >>>>>>>>>>>>>>> presume that
> > >>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
> > >>>>>>>>>>>>>>> xalan-dev, and
> > >>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
> > >>>>>>>>>>>>>> achieved.
> > >>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
> > >>>>>>>>>>>>>> process
> > >>>>>>>>>>>>>> hold things up.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> - Neeraj
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>> ---------------------------------------------------------------------
> > >>>>>>
> > >>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> To unsubscribe, e-mail:
> > >>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
> > >>>>>>>>>>>>> For additional commands, e-mail:
> > >>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>> ----------------------------------------------------------------------
> > >>>>>>> --
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Subject:
> > >>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
> > >>>>>>>>>>>> From:
> > >>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
> > >>>>>>>>>>>> Date:
> > >>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> To:
> > >>>>>>>>>>>> general@xml.apache.org
> > >>>>>>>>>>>> CC:
> > >>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> > >>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> > >>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> > >>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> <Je...@Sun.COM>,
> > >>>>>>
> > >>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Hello All,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
> > >>>>>>>>>>>> final. JAXP
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
> > >>>>>>>>>>>> It introduces new Schema independent validation framework
> > >>>>>>>>>>>> which
> > >>>>>>>>>>>> decouples the validation as a process independent from
> > >>>>>>>>>>>> parsing.
> > >>>>>>>>>>>> It allows to compile Schema to an immutable memory
> > >>>>>>>>>>>> representation
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> of
> > >>>>>>
> > >>>>>>>>>>>> Grammar which can validate different instances of XML document
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> thus
> > >>>>>>
> > >>>>>>>>>>>> greatly improving the performance of XML processing. XPath
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> language
> > >>>>>>
> > >>>>>>>>>>>> provides a simple, concise syntax for accessing individual
> > >>>>>>>>>>>> parts
> > >>>>>>>>>>>> of an
> > >>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
> > >>>>>>>>>>>> access to
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>
> > >>>>>>>>>>>> the
> > >>>>>>>>>>>> XPath evaluation environment and expression results
> > >>>>>>>>>>>> independent
> > >>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
> > >>>>>>>>>>>> Datatypes to
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
> > >>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
> > >>>>>>>>>>>> 1.3 also
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>
> > >>>>>>>>>>>> adds
> > >>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> allowing
> > >>>>>>
> > >>>>>>>>>>>> application to reuse the same instance to process multiple XML
> > >>>>>>>>>>>> documents. This also helps in increasing XML processing
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> performance.
> > >>>>>>
> > >>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
> > >>>>>>>>>>>> DOM L3
> > >>>>>>>>>>>> L/S, XML
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> 1.1, XInclude.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
> > >>>>>>>>>>>> (API s +
> > >>>>>>>>>>>> Reference Implementation) to Apache. *
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> (Reference
> > >>>>>>
> > >>>>>>>>>>>> Implementation). RI has been done using
> > >>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
> > >>>>>>>>>>>> of newly
> > >>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
> > >>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
> > >>>>>>>>>>>> Transformer
> > >>>>>>>>>>>> Reset changes, Secured XML Processing changes.
> > >>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
> > >>>>>>>>>>>> XInclude
> > >>>>>>>>>>>> already exist on Apache Xerces. So in the next
> > >>>>>>>>>>>> section I have also proposed the way to merge rest of the
> > >>>>>>>>>>>> JAXP 1.3
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> RI
> > >>>>>>
> > >>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
> > >>>>>>>>>>>> suggested where implementation component should reside
> > >>>>>>>>>>>> i.e. Xerces
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> or
> > >>>>>>
> > >>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
> > >>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
> > >>>>>>>>>>>> Xerces &
> > >>>>>>>>>>>> Xalan is very welcome.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> *JAXP 1.3 APIs: *
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
> > >>>>>>>>>>>> set of
> > >>>>>>>>>>>> APIs
> > >>>>>>>>>>>> are used by many different projects.
> > >>>>>>>>>>>> With JSR 206 declared as final and many new standards
> > >>>>>>>>>>>> emerging, we
> > >>>>>>>>>>>> should update xml-commons to JAXP 1.3
> > >>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to
> > >>>>>>>>>>>> xml-commons main
> > >>>>>>>>>>>> trunk
> > >>>>>>>>>>>> and apply a tag.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
> > >>>>>>>>>>>> part of
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> Xerces)*
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> javax.xml.datatype
> > >>>>>>>>>>>> javax.xml.validation
> > >>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> which should reside at Xerces.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
> > >>>>>>>>>>>> changes
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> into
> > >>>>>>
> > >>>>>>>>>>>> that branch. This will help
> > >>>>>>>>>>>> other Xerces active committers to have a chance to look at it
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> before
> > >>>>>>
> > >>>>>>>>>>>> these changes being finally
> > >>>>>>>>>>>> committed to main trunk. This process would require merging
> > >>>>>>>>>>>> changes to
> > >>>>>>>>>>>> the branch and then committing
> > >>>>>>>>>>>> changes to main trunk, i seek help of active Xerces
> > >>>>>>>>>>>> committers.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
> > >>>>>>>>>>>> part of
> > >>>>>>>>>>>> Xalan)*
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
> > >>>>>>>>>>>> XPath
> > >>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
> > >>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> changes
> > >>>>>>
> > >>>>>>>>>>>> done in "javax.xml.transform" package
> > >>>>>>>>>>>> for ex. now application can use the same Transformer
> > >>>>>>>>>>>> instance by
> > >>>>>>>>>>>> invoking reset().
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we
> > >>>>>>>>>>>> create a
> > >>>>>>>>>>>> branch
> > >>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
> > >>>>>>>>>>>> put there. This will help other Xalan active committers to
> > >>>>>>>>>>>> have a
> > >>>>>>>>>>>> chance
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> to look at it before these changes being finally
> > >>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan
> > >>>>>>>>>>>> committers
> > >>>>>>>>>>>> for this
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> process.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> As always, all feedbacks are more than welcome.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Thanks,
> > >>>>>>>>>>>> Neeraj
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
> > >>>>>>>>>>>> [2]
> > >>>>>>>>>>>> http://java.sun.com/j2se/1.5.
> > >>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
> > >>>>>>>>>>>> [3]
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> http://java.sun.com/j2se/1.5.
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
> > >>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>> [4]
> > >>>>>>>>>>>>
> > >>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> > >>>>>>
> > >>>>>>>>>>>> summary.html
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>> ---------------------------------------------------------------------
> > >>>>>>
> > >>>>>>
> > >>>>>>>>>>>> To unsubscribe, e-mail:
> > >>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
> > >>>>>>>>>>>> For additional commands, e-mail:
> > >>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> Michael Glavassevich
> > >>>>>>>>>>> XML Parser Development
> > >>>>>>>>>>> IBM Toronto Lab
> > >>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
> > >>>>>>>>>>> E-mail: mrglavas@apache.org
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>> ---------------------------------------------------------------------
> > >>>>>>
> > >>>>>>
> > >>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> > >>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
> > >>>>>>>>
> > >>>>>>
> > >>>>>> Michael Glavassevich
> > >>>>>> XML Parser Development
> > >>>>>> IBM Toronto Lab
> > >>>>>> E-mail: mrglavas@ca.ibm.com
> > >>>>>> E-mail: mrglavas@apache.org
> > >>>>>>
> > >>>>>> ---------------------------------------------------------------------
> > >>>>>>
> > >>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > >>>>>> For additional commands, e-mail: general-help@incubator.apache.org
> > >>>>>>
> > >>>>>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> > >>> For additional commands, e-mail: general-help@xml.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
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> > > For additional commands, e-mail: general-help@xml.apache.org
> > >
> >
>
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by Davanum Srinivas <da...@gmail.com>.
Neeraj,
Spotted a few typos:
XPathFactory factory = XpathFactory.newInstnace();
XPathFactory factory = XpathFactory.newInstance(object_model_uri);
Should be:
XPathFactory factory = XPathFactory.newInstance();
XPathFactory factory = XPathFactory.newInstance(object_model_uri);
Right?
-- dims
On 4/11/05, Neeraj Bajaj <Ne...@sun.com> wrote:
> Hello All,
>
> Sometimes back i wrote an article on JAXP 1.3 which explains the new
> concepts and important features introduced in JAXP 1.3
> Especially the new
>
> - Schema Validation Framework
> - Object model neutral XPath APIs
> - XML Schema Datatypes etc.
>
> Advantages of New Schema Validation Framework and how the new API works
> has been explained with code snippets and diagram.
> New XPath APIs have also been explained. Article is available at
> https://jaxp.dev.java.net/article/jaxp-1_3-article.html
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
> > Hello All,
> >
> > xml-commons has been upgraded to JAXP 1.3 APIs.
> > If anyone could try and confirm that would be great.
> >
> > - Neeraj
> >
> > Neeraj Bajaj wrote:
> >
> >> I tagged xml-commons module yesterday with tag name
> >> '*before-jaxp13-upgradation*'.
> >>
> >> I plan to do the following but i will wait till tomorrow so as to
> >> give chance to the community
> >> to correct me if i am doing something wrong.
> >>
> >> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
> >> xml-commons/java/external/src directory
> >> with JAXP 1.3 API sources.
> >>
> >> Currently in xml-commons there are sources like org.w3c.dom.views.*
> >> which are not part of JAXP 1.3
> >> I won't remove those sources. they will be as it is.
> >>
> >> * Make changes in xml-commons/java/external/build.xml file so as to
> >> upgrade
> >> JAXP 1.1 --> JAXP 1.3
> >> DOM2 --> DOM3
> >> SAX2 --> (SAX) 2.0.2 (sax2r3)
> >>
> >> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
> >> available as xml-apis.jar.
> >>
> >> Anything else i should take care ?
> >>
> >> - Neeraj
> >>
> >>
> >> Neeraj Bajaj wrote:
> >>
> >>> Geir, I have uploaded sources at the same location
> >>> (xml-commons/contrib/jaxp13)
> >>> with Apache 2.0 license on every source file.
> >>>
> >>> - Neeraj
> >>>
> >>> Neeraj Bajaj wrote:
> >>>
> >>>> Ok, So i will add it and upload again.
> >>>>
> >>>> - Neeraj
> >>>>
> >>>> Geir Magnusson Jr. wrote:
> >>>>
> >>>>>
> >>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
> >>>>>
> >>>>>> Hi Neeraj,
> >>>>>>
> >>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
> >>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the
> >>>>>> Apache
> >>>>>> license. Will this still be the case for JAXP 1.3?
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> yes - these files must be available under the apache license v2.
> >>>>> And the license grantor should be the one that adds it.
> >>>>>
> >>>>> Sorry Neeraj :)
> >>>>>
> >>>>> geir
> >>>>>
> >>>>>>
> >>>>>> Thanks.
> >>>>>>
> >>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
> >>>>>>
> >>>>>>> Ok I just finished uploading JAXP 1.3 sources in
> >>>>>>> "*xml-commons/contrib/jaxp13"* directory.
> >>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
> >>>>>>> xalan-src.zip which
> >>>>>>> corresponds to jaxp-api,
> >>>>>>> xerces & xalan sources respectively.
> >>>>>>>
> >>>>>>> - Neeraj
> >>>>>>>
> >>>>>>> Neeraj Bajaj wrote:
> >>>>>>>
> >>>>>>>> That really sounds good to me.. so i would try to finish it today.
> >>>>>>>> I will send mail to the community when i am done.
> >>>>>>>>
> >>>>>>>> Thanks dims for the suggestion.
> >>>>>>>>
> >>>>>>>> - Neeraj
> >>>>>>>>
> >>>>>>>> Davanum Srinivas wrote:
> >>>>>>>>
> >>>>>>>>> Neeraj,
> >>>>>>>>>
> >>>>>>>>> my 2 cents...upload the whole thing say in
> >>>>>>>>> xml-commons/contrib/jaxp13
> >>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
> >>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
> >>>>>>>>> tagging the current code in the main trunk there) and it's
> >>>>>>>>> upto the
> >>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they
> >>>>>>>>> fit.
> >>>>>>>>>
> >>>>>>>>> thanks,
> >>>>>>>>> dims
> >>>>>>>>>
> >>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Thanks Michael for your response.
> >>>>>>>>>>
> >>>>>>>>>> I was just wondering what would be idle time to wait before i
> >>>>>>>>>> start
> >>>>>>>>>> work
> >>>>>>>>>> on this ?
> >>>>>>>>>> Does anyone has an opinion, Is there any other list where i
> >>>>>>>>>> should
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>> send
> >>>>>>
> >>>>>>>>>> this mail
> >>>>>>>>>> before making changes ?
> >>>>>>>>>>
> >>>>>>>>>> - Neeraj
> >>>>>>>>>>
> >>>>>>>>>> Michael Glavassevich wrote:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> Hi Neeraj,
> >>>>>>>>>>>
> >>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk,
> >>>>>>>>>>> tagging it
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>> and
> >>>>>>
> >>>>>>>>>>> making a branch for the old JAXP sources on the current
> >>>>>>>>>>> main trunk.
> >>>>>>>>>>>
> >>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
> >>>>>>>>>>> other
> >>>>>>>>>>> updates
> >>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
> >>>>>>>>>>> branch we've
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>
> >>>>>>>>>>> used
> >>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and
> >>>>>>>>>>> Xalan. I
> >>>>>>>>>>> assume a
> >>>>>>>>>>> similar branch will exist for 1.3.
> >>>>>>>>>>>
> >>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
> >>>>>>>>>>> 03:40:57
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>> AM:
> >>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>
> >>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
> >>>>>>>>>>>> attached as
> >>>>>>>>>>>> zip but
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> mail bounced back with the following message
> >>>>>>>>>>>>
> >>>>>>>>>>>> <error>
> >>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
> >>>>>>>>>>>> <ge...@xml.apache.org>
> >>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
> >>>>>>>>>>>> </error>
> >>>>>>>>>>>>
> >>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
> >>>>>>>>>>>> Apache
> >>>>>>>>>>>> server somewhere ?
> >>>>>>>>>>>> Can anyone guide me what is the procedure for such code
> >>>>>>>>>>>> grants ?
> >>>>>>>>>>>>
> >>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
> >>>>>>>>>>>> community
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> to help put it in a
> >>>>>>>>>>>> a branch and make it work there. As i think due to large
> >>>>>>>>>>>> number of
> >>>>>>>>>>>> changes it would be a considerable
> >>>>>>>>>>>> amount of work. This will also help the committers &
> >>>>>>>>>>>> community to
> >>>>>>>>>>>> have a
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> look at the code before
> >>>>>>>>>>>> it is merged into the main stream work.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I think i have commit access at xml-commons so i can commit
> >>>>>>>>>>>> the
> >>>>>>>>>>>> sources
> >>>>>>>>>>>> in xml-commons branch
> >>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
> >>>>>>>>>>>> What is
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> the
> >>>>>>
> >>>>>>>>>>>> opinion of community ? I can
> >>>>>>>>>>>> start this as soon as i get a consensus from the community. My
> >>>>>>>>>>>> preference is to put the sources on
> >>>>>>>>>>>> xml-commons main trunk.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Please let me know how should i proceed.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>
> >>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>
> >>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>>>>>>>>>>> implementation to Apache XML.*
> >>>>>>>>>>>> JAXP 1.3 (JSR 206
> >>>>>>>>>>>> <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of
> >>>>>>>>>>>> new
> >>>>>>>>>>>> functionalities.
> >>>>>>>>>>>>
> >>>>>>>>>>>> * New Schema Validation Framework
> >>>>>>>>>>>> * New Object Model neutral XPath APIs
> >>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
> >>>>>>>>>>>> * Reuse parser instance
> >>>>>>>>>>>> * Security enhancements
> >>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
> >>>>>>>>>>>> Save, SAX
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> 2, XML 1.1 and XInclude)
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
> >>>>>>>>>>>>
> >>>>>>>>>>>> Due to large size of code base i will be sending different
> >>>>>>>>>>>> mails
> >>>>>>>>>>>> for the
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> source code of Xerces & Xalan.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I have attached the original mail where i proposed the
> >>>>>>>>>>>> process of
> >>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
> >>>>>>>>>>>> integrating this donation into the main stream work of
> >>>>>>>>>>>> Xerces &
> >>>>>>>>>>>> Xalan.
> >>>>>>>>>>>> There was a general consensus to my proposal
> >>>>>>>>>>>> and we can discuss more about the technicalities of merging
> >>>>>>>>>>>> with
> >>>>>>>>>>>> in the
> >>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
> >>>>>>>>>>>> community.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
> >>>>>>>>>>>>
> >>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Neeraj Bajaj wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Geir Magnusson Jr. wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
> >>>>>>>>>>>>>>> up the
> >>>>>>>>>>>>>>> ball
> >>>>>>>>>>>>>>> on this one.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
> >>>>>>>>>>>>>>> presume that
> >>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
> >>>>>>>>>>>>>>> xalan-dev, and
> >>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
> >>>>>>>>>>>>>> achieved.
> >>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
> >>>>>>>>>>>>>> process
> >>>>>>>>>>>>>> hold things up.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> To unsubscribe, e-mail:
> >>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>> ----------------------------------------------------------------------
> >>>>>>> --
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Subject:
> >>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
> >>>>>>>>>>>> From:
> >>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
> >>>>>>>>>>>> Date:
> >>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
> >>>>>>>>>>>>
> >>>>>>>>>>>> To:
> >>>>>>>>>>>> general@xml.apache.org
> >>>>>>>>>>>> CC:
> >>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> <Je...@Sun.COM>,
> >>>>>>
> >>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
> >>>>>>>>>>>> final. JAXP
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
> >>>>>>>>>>>> It introduces new Schema independent validation framework
> >>>>>>>>>>>> which
> >>>>>>>>>>>> decouples the validation as a process independent from
> >>>>>>>>>>>> parsing.
> >>>>>>>>>>>> It allows to compile Schema to an immutable memory
> >>>>>>>>>>>> representation
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> of
> >>>>>>
> >>>>>>>>>>>> Grammar which can validate different instances of XML document
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> thus
> >>>>>>
> >>>>>>>>>>>> greatly improving the performance of XML processing. XPath
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> language
> >>>>>>
> >>>>>>>>>>>> provides a simple, concise syntax for accessing individual
> >>>>>>>>>>>> parts
> >>>>>>>>>>>> of an
> >>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
> >>>>>>>>>>>> access to
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>
> >>>>>>>>>>>> the
> >>>>>>>>>>>> XPath evaluation environment and expression results
> >>>>>>>>>>>> independent
> >>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
> >>>>>>>>>>>> Datatypes to
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
> >>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
> >>>>>>>>>>>> 1.3 also
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>
> >>>>>>>>>>>> adds
> >>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> allowing
> >>>>>>
> >>>>>>>>>>>> application to reuse the same instance to process multiple XML
> >>>>>>>>>>>> documents. This also helps in increasing XML processing
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> performance.
> >>>>>>
> >>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
> >>>>>>>>>>>> DOM L3
> >>>>>>>>>>>> L/S, XML
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> 1.1, XInclude.
> >>>>>>>>>>>>
> >>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
> >>>>>>>>>>>> (API s +
> >>>>>>>>>>>> Reference Implementation) to Apache. *
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
> >>>>>>>>>>>>
> >>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> (Reference
> >>>>>>
> >>>>>>>>>>>> Implementation). RI has been done using
> >>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
> >>>>>>>>>>>> of newly
> >>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
> >>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
> >>>>>>>>>>>> Transformer
> >>>>>>>>>>>> Reset changes, Secured XML Processing changes.
> >>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
> >>>>>>>>>>>> XInclude
> >>>>>>>>>>>> already exist on Apache Xerces. So in the next
> >>>>>>>>>>>> section I have also proposed the way to merge rest of the
> >>>>>>>>>>>> JAXP 1.3
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> RI
> >>>>>>
> >>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
> >>>>>>>>>>>> suggested where implementation component should reside
> >>>>>>>>>>>> i.e. Xerces
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> or
> >>>>>>
> >>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
> >>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
> >>>>>>>>>>>> Xerces &
> >>>>>>>>>>>> Xalan is very welcome.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 APIs: *
> >>>>>>>>>>>>
> >>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
> >>>>>>>>>>>> set of
> >>>>>>>>>>>> APIs
> >>>>>>>>>>>> are used by many different projects.
> >>>>>>>>>>>> With JSR 206 declared as final and many new standards
> >>>>>>>>>>>> emerging, we
> >>>>>>>>>>>> should update xml-commons to JAXP 1.3
> >>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to
> >>>>>>>>>>>> xml-commons main
> >>>>>>>>>>>> trunk
> >>>>>>>>>>>> and apply a tag.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
> >>>>>>>>>>>> part of
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Xerces)*
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
> >>>>>>>>>>>>
> >>>>>>>>>>>> javax.xml.datatype
> >>>>>>>>>>>> javax.xml.validation
> >>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
> >>>>>>>>>>>>
> >>>>>>>>>>>> which should reside at Xerces.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
> >>>>>>>>>>>> changes
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> into
> >>>>>>
> >>>>>>>>>>>> that branch. This will help
> >>>>>>>>>>>> other Xerces active committers to have a chance to look at it
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> before
> >>>>>>
> >>>>>>>>>>>> these changes being finally
> >>>>>>>>>>>> committed to main trunk. This process would require merging
> >>>>>>>>>>>> changes to
> >>>>>>>>>>>> the branch and then committing
> >>>>>>>>>>>> changes to main trunk, i seek help of active Xerces
> >>>>>>>>>>>> committers.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
> >>>>>>>>>>>> part of
> >>>>>>>>>>>> Xalan)*
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
> >>>>>>>>>>>> XPath
> >>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
> >>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> changes
> >>>>>>
> >>>>>>>>>>>> done in "javax.xml.transform" package
> >>>>>>>>>>>> for ex. now application can use the same Transformer
> >>>>>>>>>>>> instance by
> >>>>>>>>>>>> invoking reset().
> >>>>>>>>>>>>
> >>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we
> >>>>>>>>>>>> create a
> >>>>>>>>>>>> branch
> >>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
> >>>>>>>>>>>> put there. This will help other Xalan active committers to
> >>>>>>>>>>>> have a
> >>>>>>>>>>>> chance
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> to look at it before these changes being finally
> >>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan
> >>>>>>>>>>>> committers
> >>>>>>>>>>>> for this
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> process.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> As always, all feedbacks are more than welcome.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks,
> >>>>>>>>>>>> Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
> >>>>>>>>>>>> [2]
> >>>>>>>>>>>> http://java.sun.com/j2se/1.5.
> >>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
> >>>>>>>>>>>> [3]
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> http://java.sun.com/j2se/1.5.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
> >>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> [4]
> >>>>>>>>>>>>
> >>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>>>>>
> >>>>>>>>>>>> summary.html
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>>>>>>> To unsubscribe, e-mail:
> >>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Michael Glavassevich
> >>>>>>>>>>> XML Parser Development
> >>>>>>>>>>> IBM Toronto Lab
> >>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
> >>>>>>>>>>> E-mail: mrglavas@apache.org
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
> >>>>>>>>
> >>>>>>
> >>>>>> Michael Glavassevich
> >>>>>> XML Parser Development
> >>>>>> IBM Toronto Lab
> >>>>>> E-mail: mrglavas@ca.ibm.com
> >>>>>> E-mail: mrglavas@apache.org
> >>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>>>>> For additional commands, e-mail: general-help@incubator.apache.org
> >>>>>>
> >>>>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> >>> For additional commands, e-mail: general-help@xml.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
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> > For additional commands, e-mail: general-help@xml.apache.org
> >
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by Davanum Srinivas <da...@gmail.com>.
Neeraj,
Spotted a few typos:
XPathFactory factory = XpathFactory.newInstnace();
XPathFactory factory = XpathFactory.newInstance(object_model_uri);
Should be:
XPathFactory factory = XPathFactory.newInstance();
XPathFactory factory = XPathFactory.newInstance(object_model_uri);
Right?
-- dims
On 4/11/05, Neeraj Bajaj <Ne...@sun.com> wrote:
> Hello All,
>
> Sometimes back i wrote an article on JAXP 1.3 which explains the new
> concepts and important features introduced in JAXP 1.3
> Especially the new
>
> - Schema Validation Framework
> - Object model neutral XPath APIs
> - XML Schema Datatypes etc.
>
> Advantages of New Schema Validation Framework and how the new API works
> has been explained with code snippets and diagram.
> New XPath APIs have also been explained. Article is available at
> https://jaxp.dev.java.net/article/jaxp-1_3-article.html
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
> > Hello All,
> >
> > xml-commons has been upgraded to JAXP 1.3 APIs.
> > If anyone could try and confirm that would be great.
> >
> > - Neeraj
> >
> > Neeraj Bajaj wrote:
> >
> >> I tagged xml-commons module yesterday with tag name
> >> '*before-jaxp13-upgradation*'.
> >>
> >> I plan to do the following but i will wait till tomorrow so as to
> >> give chance to the community
> >> to correct me if i am doing something wrong.
> >>
> >> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
> >> xml-commons/java/external/src directory
> >> with JAXP 1.3 API sources.
> >>
> >> Currently in xml-commons there are sources like org.w3c.dom.views.*
> >> which are not part of JAXP 1.3
> >> I won't remove those sources. they will be as it is.
> >>
> >> * Make changes in xml-commons/java/external/build.xml file so as to
> >> upgrade
> >> JAXP 1.1 --> JAXP 1.3
> >> DOM2 --> DOM3
> >> SAX2 --> (SAX) 2.0.2 (sax2r3)
> >>
> >> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
> >> available as xml-apis.jar.
> >>
> >> Anything else i should take care ?
> >>
> >> - Neeraj
> >>
> >>
> >> Neeraj Bajaj wrote:
> >>
> >>> Geir, I have uploaded sources at the same location
> >>> (xml-commons/contrib/jaxp13)
> >>> with Apache 2.0 license on every source file.
> >>>
> >>> - Neeraj
> >>>
> >>> Neeraj Bajaj wrote:
> >>>
> >>>> Ok, So i will add it and upload again.
> >>>>
> >>>> - Neeraj
> >>>>
> >>>> Geir Magnusson Jr. wrote:
> >>>>
> >>>>>
> >>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
> >>>>>
> >>>>>> Hi Neeraj,
> >>>>>>
> >>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
> >>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the
> >>>>>> Apache
> >>>>>> license. Will this still be the case for JAXP 1.3?
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> yes - these files must be available under the apache license v2.
> >>>>> And the license grantor should be the one that adds it.
> >>>>>
> >>>>> Sorry Neeraj :)
> >>>>>
> >>>>> geir
> >>>>>
> >>>>>>
> >>>>>> Thanks.
> >>>>>>
> >>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
> >>>>>>
> >>>>>>> Ok I just finished uploading JAXP 1.3 sources in
> >>>>>>> "*xml-commons/contrib/jaxp13"* directory.
> >>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
> >>>>>>> xalan-src.zip which
> >>>>>>> corresponds to jaxp-api,
> >>>>>>> xerces & xalan sources respectively.
> >>>>>>>
> >>>>>>> - Neeraj
> >>>>>>>
> >>>>>>> Neeraj Bajaj wrote:
> >>>>>>>
> >>>>>>>> That really sounds good to me.. so i would try to finish it today.
> >>>>>>>> I will send mail to the community when i am done.
> >>>>>>>>
> >>>>>>>> Thanks dims for the suggestion.
> >>>>>>>>
> >>>>>>>> - Neeraj
> >>>>>>>>
> >>>>>>>> Davanum Srinivas wrote:
> >>>>>>>>
> >>>>>>>>> Neeraj,
> >>>>>>>>>
> >>>>>>>>> my 2 cents...upload the whole thing say in
> >>>>>>>>> xml-commons/contrib/jaxp13
> >>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
> >>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
> >>>>>>>>> tagging the current code in the main trunk there) and it's
> >>>>>>>>> upto the
> >>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they
> >>>>>>>>> fit.
> >>>>>>>>>
> >>>>>>>>> thanks,
> >>>>>>>>> dims
> >>>>>>>>>
> >>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Thanks Michael for your response.
> >>>>>>>>>>
> >>>>>>>>>> I was just wondering what would be idle time to wait before i
> >>>>>>>>>> start
> >>>>>>>>>> work
> >>>>>>>>>> on this ?
> >>>>>>>>>> Does anyone has an opinion, Is there any other list where i
> >>>>>>>>>> should
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>> send
> >>>>>>
> >>>>>>>>>> this mail
> >>>>>>>>>> before making changes ?
> >>>>>>>>>>
> >>>>>>>>>> - Neeraj
> >>>>>>>>>>
> >>>>>>>>>> Michael Glavassevich wrote:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> Hi Neeraj,
> >>>>>>>>>>>
> >>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk,
> >>>>>>>>>>> tagging it
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>> and
> >>>>>>
> >>>>>>>>>>> making a branch for the old JAXP sources on the current
> >>>>>>>>>>> main trunk.
> >>>>>>>>>>>
> >>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
> >>>>>>>>>>> other
> >>>>>>>>>>> updates
> >>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
> >>>>>>>>>>> branch we've
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>
> >>>>>>>>>>> used
> >>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and
> >>>>>>>>>>> Xalan. I
> >>>>>>>>>>> assume a
> >>>>>>>>>>> similar branch will exist for 1.3.
> >>>>>>>>>>>
> >>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
> >>>>>>>>>>> 03:40:57
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>> AM:
> >>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>
> >>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
> >>>>>>>>>>>> attached as
> >>>>>>>>>>>> zip but
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> mail bounced back with the following message
> >>>>>>>>>>>>
> >>>>>>>>>>>> <error>
> >>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
> >>>>>>>>>>>> <ge...@xml.apache.org>
> >>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
> >>>>>>>>>>>> </error>
> >>>>>>>>>>>>
> >>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
> >>>>>>>>>>>> Apache
> >>>>>>>>>>>> server somewhere ?
> >>>>>>>>>>>> Can anyone guide me what is the procedure for such code
> >>>>>>>>>>>> grants ?
> >>>>>>>>>>>>
> >>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
> >>>>>>>>>>>> community
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> to help put it in a
> >>>>>>>>>>>> a branch and make it work there. As i think due to large
> >>>>>>>>>>>> number of
> >>>>>>>>>>>> changes it would be a considerable
> >>>>>>>>>>>> amount of work. This will also help the committers &
> >>>>>>>>>>>> community to
> >>>>>>>>>>>> have a
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> look at the code before
> >>>>>>>>>>>> it is merged into the main stream work.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I think i have commit access at xml-commons so i can commit
> >>>>>>>>>>>> the
> >>>>>>>>>>>> sources
> >>>>>>>>>>>> in xml-commons branch
> >>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
> >>>>>>>>>>>> What is
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> the
> >>>>>>
> >>>>>>>>>>>> opinion of community ? I can
> >>>>>>>>>>>> start this as soon as i get a consensus from the community. My
> >>>>>>>>>>>> preference is to put the sources on
> >>>>>>>>>>>> xml-commons main trunk.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Please let me know how should i proceed.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>
> >>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>
> >>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>>>>>>>>>>> implementation to Apache XML.*
> >>>>>>>>>>>> JAXP 1.3 (JSR 206
> >>>>>>>>>>>> <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of
> >>>>>>>>>>>> new
> >>>>>>>>>>>> functionalities.
> >>>>>>>>>>>>
> >>>>>>>>>>>> * New Schema Validation Framework
> >>>>>>>>>>>> * New Object Model neutral XPath APIs
> >>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
> >>>>>>>>>>>> * Reuse parser instance
> >>>>>>>>>>>> * Security enhancements
> >>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
> >>>>>>>>>>>> Save, SAX
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> 2, XML 1.1 and XInclude)
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
> >>>>>>>>>>>>
> >>>>>>>>>>>> Due to large size of code base i will be sending different
> >>>>>>>>>>>> mails
> >>>>>>>>>>>> for the
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> source code of Xerces & Xalan.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I have attached the original mail where i proposed the
> >>>>>>>>>>>> process of
> >>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
> >>>>>>>>>>>> integrating this donation into the main stream work of
> >>>>>>>>>>>> Xerces &
> >>>>>>>>>>>> Xalan.
> >>>>>>>>>>>> There was a general consensus to my proposal
> >>>>>>>>>>>> and we can discuss more about the technicalities of merging
> >>>>>>>>>>>> with
> >>>>>>>>>>>> in the
> >>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
> >>>>>>>>>>>> community.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
> >>>>>>>>>>>>
> >>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Neeraj Bajaj wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Geir Magnusson Jr. wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
> >>>>>>>>>>>>>>> up the
> >>>>>>>>>>>>>>> ball
> >>>>>>>>>>>>>>> on this one.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
> >>>>>>>>>>>>>>> presume that
> >>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
> >>>>>>>>>>>>>>> xalan-dev, and
> >>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
> >>>>>>>>>>>>>> achieved.
> >>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
> >>>>>>>>>>>>>> process
> >>>>>>>>>>>>>> hold things up.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> To unsubscribe, e-mail:
> >>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>> ----------------------------------------------------------------------
> >>>>>>> --
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Subject:
> >>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
> >>>>>>>>>>>> From:
> >>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
> >>>>>>>>>>>> Date:
> >>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
> >>>>>>>>>>>>
> >>>>>>>>>>>> To:
> >>>>>>>>>>>> general@xml.apache.org
> >>>>>>>>>>>> CC:
> >>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> <Je...@Sun.COM>,
> >>>>>>
> >>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
> >>>>>>>>>>>> final. JAXP
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
> >>>>>>>>>>>> It introduces new Schema independent validation framework
> >>>>>>>>>>>> which
> >>>>>>>>>>>> decouples the validation as a process independent from
> >>>>>>>>>>>> parsing.
> >>>>>>>>>>>> It allows to compile Schema to an immutable memory
> >>>>>>>>>>>> representation
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> of
> >>>>>>
> >>>>>>>>>>>> Grammar which can validate different instances of XML document
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> thus
> >>>>>>
> >>>>>>>>>>>> greatly improving the performance of XML processing. XPath
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> language
> >>>>>>
> >>>>>>>>>>>> provides a simple, concise syntax for accessing individual
> >>>>>>>>>>>> parts
> >>>>>>>>>>>> of an
> >>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
> >>>>>>>>>>>> access to
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>
> >>>>>>>>>>>> the
> >>>>>>>>>>>> XPath evaluation environment and expression results
> >>>>>>>>>>>> independent
> >>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
> >>>>>>>>>>>> Datatypes to
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
> >>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
> >>>>>>>>>>>> 1.3 also
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>
> >>>>>>>>>>>> adds
> >>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> allowing
> >>>>>>
> >>>>>>>>>>>> application to reuse the same instance to process multiple XML
> >>>>>>>>>>>> documents. This also helps in increasing XML processing
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> performance.
> >>>>>>
> >>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
> >>>>>>>>>>>> DOM L3
> >>>>>>>>>>>> L/S, XML
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> 1.1, XInclude.
> >>>>>>>>>>>>
> >>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
> >>>>>>>>>>>> (API s +
> >>>>>>>>>>>> Reference Implementation) to Apache. *
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
> >>>>>>>>>>>>
> >>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> (Reference
> >>>>>>
> >>>>>>>>>>>> Implementation). RI has been done using
> >>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
> >>>>>>>>>>>> of newly
> >>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
> >>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
> >>>>>>>>>>>> Transformer
> >>>>>>>>>>>> Reset changes, Secured XML Processing changes.
> >>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
> >>>>>>>>>>>> XInclude
> >>>>>>>>>>>> already exist on Apache Xerces. So in the next
> >>>>>>>>>>>> section I have also proposed the way to merge rest of the
> >>>>>>>>>>>> JAXP 1.3
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> RI
> >>>>>>
> >>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
> >>>>>>>>>>>> suggested where implementation component should reside
> >>>>>>>>>>>> i.e. Xerces
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> or
> >>>>>>
> >>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
> >>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
> >>>>>>>>>>>> Xerces &
> >>>>>>>>>>>> Xalan is very welcome.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 APIs: *
> >>>>>>>>>>>>
> >>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
> >>>>>>>>>>>> set of
> >>>>>>>>>>>> APIs
> >>>>>>>>>>>> are used by many different projects.
> >>>>>>>>>>>> With JSR 206 declared as final and many new standards
> >>>>>>>>>>>> emerging, we
> >>>>>>>>>>>> should update xml-commons to JAXP 1.3
> >>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to
> >>>>>>>>>>>> xml-commons main
> >>>>>>>>>>>> trunk
> >>>>>>>>>>>> and apply a tag.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
> >>>>>>>>>>>> part of
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Xerces)*
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
> >>>>>>>>>>>>
> >>>>>>>>>>>> javax.xml.datatype
> >>>>>>>>>>>> javax.xml.validation
> >>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
> >>>>>>>>>>>>
> >>>>>>>>>>>> which should reside at Xerces.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
> >>>>>>>>>>>> changes
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> into
> >>>>>>
> >>>>>>>>>>>> that branch. This will help
> >>>>>>>>>>>> other Xerces active committers to have a chance to look at it
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> before
> >>>>>>
> >>>>>>>>>>>> these changes being finally
> >>>>>>>>>>>> committed to main trunk. This process would require merging
> >>>>>>>>>>>> changes to
> >>>>>>>>>>>> the branch and then committing
> >>>>>>>>>>>> changes to main trunk, i seek help of active Xerces
> >>>>>>>>>>>> committers.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
> >>>>>>>>>>>> part of
> >>>>>>>>>>>> Xalan)*
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
> >>>>>>>>>>>> XPath
> >>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
> >>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> changes
> >>>>>>
> >>>>>>>>>>>> done in "javax.xml.transform" package
> >>>>>>>>>>>> for ex. now application can use the same Transformer
> >>>>>>>>>>>> instance by
> >>>>>>>>>>>> invoking reset().
> >>>>>>>>>>>>
> >>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we
> >>>>>>>>>>>> create a
> >>>>>>>>>>>> branch
> >>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
> >>>>>>>>>>>> put there. This will help other Xalan active committers to
> >>>>>>>>>>>> have a
> >>>>>>>>>>>> chance
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> to look at it before these changes being finally
> >>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan
> >>>>>>>>>>>> committers
> >>>>>>>>>>>> for this
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> process.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> As always, all feedbacks are more than welcome.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks,
> >>>>>>>>>>>> Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
> >>>>>>>>>>>> [2]
> >>>>>>>>>>>> http://java.sun.com/j2se/1.5.
> >>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
> >>>>>>>>>>>> [3]
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> http://java.sun.com/j2se/1.5.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
> >>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> [4]
> >>>>>>>>>>>>
> >>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>>>>>
> >>>>>>>>>>>> summary.html
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>>>>>>> To unsubscribe, e-mail:
> >>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Michael Glavassevich
> >>>>>>>>>>> XML Parser Development
> >>>>>>>>>>> IBM Toronto Lab
> >>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
> >>>>>>>>>>> E-mail: mrglavas@apache.org
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
> >>>>>>>>
> >>>>>>
> >>>>>> Michael Glavassevich
> >>>>>> XML Parser Development
> >>>>>> IBM Toronto Lab
> >>>>>> E-mail: mrglavas@ca.ibm.com
> >>>>>> E-mail: mrglavas@apache.org
> >>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>>>>> For additional commands, e-mail: general-help@incubator.apache.org
> >>>>>>
> >>>>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> >>> For additional commands, e-mail: general-help@xml.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
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> > For additional commands, e-mail: general-help@xml.apache.org
> >
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by Davanum Srinivas <da...@gmail.com>.
Neeraj,
Spotted a few typos:
XPathFactory factory = XpathFactory.newInstnace();
XPathFactory factory = XpathFactory.newInstance(object_model_uri);
Should be:
XPathFactory factory = XPathFactory.newInstance();
XPathFactory factory = XPathFactory.newInstance(object_model_uri);
Right?
-- dims
On 4/11/05, Neeraj Bajaj <Ne...@sun.com> wrote:
> Hello All,
>
> Sometimes back i wrote an article on JAXP 1.3 which explains the new
> concepts and important features introduced in JAXP 1.3
> Especially the new
>
> - Schema Validation Framework
> - Object model neutral XPath APIs
> - XML Schema Datatypes etc.
>
> Advantages of New Schema Validation Framework and how the new API works
> has been explained with code snippets and diagram.
> New XPath APIs have also been explained. Article is available at
> https://jaxp.dev.java.net/article/jaxp-1_3-article.html
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
> > Hello All,
> >
> > xml-commons has been upgraded to JAXP 1.3 APIs.
> > If anyone could try and confirm that would be great.
> >
> > - Neeraj
> >
> > Neeraj Bajaj wrote:
> >
> >> I tagged xml-commons module yesterday with tag name
> >> '*before-jaxp13-upgradation*'.
> >>
> >> I plan to do the following but i will wait till tomorrow so as to
> >> give chance to the community
> >> to correct me if i am doing something wrong.
> >>
> >> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
> >> xml-commons/java/external/src directory
> >> with JAXP 1.3 API sources.
> >>
> >> Currently in xml-commons there are sources like org.w3c.dom.views.*
> >> which are not part of JAXP 1.3
> >> I won't remove those sources. they will be as it is.
> >>
> >> * Make changes in xml-commons/java/external/build.xml file so as to
> >> upgrade
> >> JAXP 1.1 --> JAXP 1.3
> >> DOM2 --> DOM3
> >> SAX2 --> (SAX) 2.0.2 (sax2r3)
> >>
> >> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
> >> available as xml-apis.jar.
> >>
> >> Anything else i should take care ?
> >>
> >> - Neeraj
> >>
> >>
> >> Neeraj Bajaj wrote:
> >>
> >>> Geir, I have uploaded sources at the same location
> >>> (xml-commons/contrib/jaxp13)
> >>> with Apache 2.0 license on every source file.
> >>>
> >>> - Neeraj
> >>>
> >>> Neeraj Bajaj wrote:
> >>>
> >>>> Ok, So i will add it and upload again.
> >>>>
> >>>> - Neeraj
> >>>>
> >>>> Geir Magnusson Jr. wrote:
> >>>>
> >>>>>
> >>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
> >>>>>
> >>>>>> Hi Neeraj,
> >>>>>>
> >>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
> >>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the
> >>>>>> Apache
> >>>>>> license. Will this still be the case for JAXP 1.3?
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> yes - these files must be available under the apache license v2.
> >>>>> And the license grantor should be the one that adds it.
> >>>>>
> >>>>> Sorry Neeraj :)
> >>>>>
> >>>>> geir
> >>>>>
> >>>>>>
> >>>>>> Thanks.
> >>>>>>
> >>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
> >>>>>>
> >>>>>>> Ok I just finished uploading JAXP 1.3 sources in
> >>>>>>> "*xml-commons/contrib/jaxp13"* directory.
> >>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
> >>>>>>> xalan-src.zip which
> >>>>>>> corresponds to jaxp-api,
> >>>>>>> xerces & xalan sources respectively.
> >>>>>>>
> >>>>>>> - Neeraj
> >>>>>>>
> >>>>>>> Neeraj Bajaj wrote:
> >>>>>>>
> >>>>>>>> That really sounds good to me.. so i would try to finish it today.
> >>>>>>>> I will send mail to the community when i am done.
> >>>>>>>>
> >>>>>>>> Thanks dims for the suggestion.
> >>>>>>>>
> >>>>>>>> - Neeraj
> >>>>>>>>
> >>>>>>>> Davanum Srinivas wrote:
> >>>>>>>>
> >>>>>>>>> Neeraj,
> >>>>>>>>>
> >>>>>>>>> my 2 cents...upload the whole thing say in
> >>>>>>>>> xml-commons/contrib/jaxp13
> >>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
> >>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
> >>>>>>>>> tagging the current code in the main trunk there) and it's
> >>>>>>>>> upto the
> >>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they
> >>>>>>>>> fit.
> >>>>>>>>>
> >>>>>>>>> thanks,
> >>>>>>>>> dims
> >>>>>>>>>
> >>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Thanks Michael for your response.
> >>>>>>>>>>
> >>>>>>>>>> I was just wondering what would be idle time to wait before i
> >>>>>>>>>> start
> >>>>>>>>>> work
> >>>>>>>>>> on this ?
> >>>>>>>>>> Does anyone has an opinion, Is there any other list where i
> >>>>>>>>>> should
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>> send
> >>>>>>
> >>>>>>>>>> this mail
> >>>>>>>>>> before making changes ?
> >>>>>>>>>>
> >>>>>>>>>> - Neeraj
> >>>>>>>>>>
> >>>>>>>>>> Michael Glavassevich wrote:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> Hi Neeraj,
> >>>>>>>>>>>
> >>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk,
> >>>>>>>>>>> tagging it
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>> and
> >>>>>>
> >>>>>>>>>>> making a branch for the old JAXP sources on the current
> >>>>>>>>>>> main trunk.
> >>>>>>>>>>>
> >>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
> >>>>>>>>>>> other
> >>>>>>>>>>> updates
> >>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
> >>>>>>>>>>> branch we've
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>
> >>>>>>>>>>> used
> >>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and
> >>>>>>>>>>> Xalan. I
> >>>>>>>>>>> assume a
> >>>>>>>>>>> similar branch will exist for 1.3.
> >>>>>>>>>>>
> >>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
> >>>>>>>>>>> 03:40:57
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>> AM:
> >>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>
> >>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
> >>>>>>>>>>>> attached as
> >>>>>>>>>>>> zip but
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> mail bounced back with the following message
> >>>>>>>>>>>>
> >>>>>>>>>>>> <error>
> >>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
> >>>>>>>>>>>> <ge...@xml.apache.org>
> >>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
> >>>>>>>>>>>> </error>
> >>>>>>>>>>>>
> >>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
> >>>>>>>>>>>> Apache
> >>>>>>>>>>>> server somewhere ?
> >>>>>>>>>>>> Can anyone guide me what is the procedure for such code
> >>>>>>>>>>>> grants ?
> >>>>>>>>>>>>
> >>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
> >>>>>>>>>>>> community
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> to help put it in a
> >>>>>>>>>>>> a branch and make it work there. As i think due to large
> >>>>>>>>>>>> number of
> >>>>>>>>>>>> changes it would be a considerable
> >>>>>>>>>>>> amount of work. This will also help the committers &
> >>>>>>>>>>>> community to
> >>>>>>>>>>>> have a
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> look at the code before
> >>>>>>>>>>>> it is merged into the main stream work.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I think i have commit access at xml-commons so i can commit
> >>>>>>>>>>>> the
> >>>>>>>>>>>> sources
> >>>>>>>>>>>> in xml-commons branch
> >>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
> >>>>>>>>>>>> What is
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> the
> >>>>>>
> >>>>>>>>>>>> opinion of community ? I can
> >>>>>>>>>>>> start this as soon as i get a consensus from the community. My
> >>>>>>>>>>>> preference is to put the sources on
> >>>>>>>>>>>> xml-commons main trunk.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Please let me know how should i proceed.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>
> >>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>
> >>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>>>>>>>>>>> implementation to Apache XML.*
> >>>>>>>>>>>> JAXP 1.3 (JSR 206
> >>>>>>>>>>>> <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of
> >>>>>>>>>>>> new
> >>>>>>>>>>>> functionalities.
> >>>>>>>>>>>>
> >>>>>>>>>>>> * New Schema Validation Framework
> >>>>>>>>>>>> * New Object Model neutral XPath APIs
> >>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
> >>>>>>>>>>>> * Reuse parser instance
> >>>>>>>>>>>> * Security enhancements
> >>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
> >>>>>>>>>>>> Save, SAX
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> 2, XML 1.1 and XInclude)
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
> >>>>>>>>>>>>
> >>>>>>>>>>>> Due to large size of code base i will be sending different
> >>>>>>>>>>>> mails
> >>>>>>>>>>>> for the
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> source code of Xerces & Xalan.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I have attached the original mail where i proposed the
> >>>>>>>>>>>> process of
> >>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
> >>>>>>>>>>>> integrating this donation into the main stream work of
> >>>>>>>>>>>> Xerces &
> >>>>>>>>>>>> Xalan.
> >>>>>>>>>>>> There was a general consensus to my proposal
> >>>>>>>>>>>> and we can discuss more about the technicalities of merging
> >>>>>>>>>>>> with
> >>>>>>>>>>>> in the
> >>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
> >>>>>>>>>>>> community.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
> >>>>>>>>>>>>
> >>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Neeraj Bajaj wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Geir Magnusson Jr. wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
> >>>>>>>>>>>>>>> up the
> >>>>>>>>>>>>>>> ball
> >>>>>>>>>>>>>>> on this one.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
> >>>>>>>>>>>>>>> presume that
> >>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
> >>>>>>>>>>>>>>> xalan-dev, and
> >>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
> >>>>>>>>>>>>>> achieved.
> >>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
> >>>>>>>>>>>>>> process
> >>>>>>>>>>>>>> hold things up.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> To unsubscribe, e-mail:
> >>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>> ----------------------------------------------------------------------
> >>>>>>> --
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Subject:
> >>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
> >>>>>>>>>>>> From:
> >>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
> >>>>>>>>>>>> Date:
> >>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
> >>>>>>>>>>>>
> >>>>>>>>>>>> To:
> >>>>>>>>>>>> general@xml.apache.org
> >>>>>>>>>>>> CC:
> >>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> <Je...@Sun.COM>,
> >>>>>>
> >>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
> >>>>>>>>>>>> final. JAXP
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
> >>>>>>>>>>>> It introduces new Schema independent validation framework
> >>>>>>>>>>>> which
> >>>>>>>>>>>> decouples the validation as a process independent from
> >>>>>>>>>>>> parsing.
> >>>>>>>>>>>> It allows to compile Schema to an immutable memory
> >>>>>>>>>>>> representation
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> of
> >>>>>>
> >>>>>>>>>>>> Grammar which can validate different instances of XML document
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> thus
> >>>>>>
> >>>>>>>>>>>> greatly improving the performance of XML processing. XPath
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> language
> >>>>>>
> >>>>>>>>>>>> provides a simple, concise syntax for accessing individual
> >>>>>>>>>>>> parts
> >>>>>>>>>>>> of an
> >>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
> >>>>>>>>>>>> access to
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>
> >>>>>>>>>>>> the
> >>>>>>>>>>>> XPath evaluation environment and expression results
> >>>>>>>>>>>> independent
> >>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
> >>>>>>>>>>>> Datatypes to
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
> >>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
> >>>>>>>>>>>> 1.3 also
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>
> >>>>>>>>>>>> adds
> >>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> allowing
> >>>>>>
> >>>>>>>>>>>> application to reuse the same instance to process multiple XML
> >>>>>>>>>>>> documents. This also helps in increasing XML processing
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> performance.
> >>>>>>
> >>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
> >>>>>>>>>>>> DOM L3
> >>>>>>>>>>>> L/S, XML
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> 1.1, XInclude.
> >>>>>>>>>>>>
> >>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
> >>>>>>>>>>>> (API s +
> >>>>>>>>>>>> Reference Implementation) to Apache. *
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
> >>>>>>>>>>>>
> >>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> (Reference
> >>>>>>
> >>>>>>>>>>>> Implementation). RI has been done using
> >>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
> >>>>>>>>>>>> of newly
> >>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
> >>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
> >>>>>>>>>>>> Transformer
> >>>>>>>>>>>> Reset changes, Secured XML Processing changes.
> >>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
> >>>>>>>>>>>> XInclude
> >>>>>>>>>>>> already exist on Apache Xerces. So in the next
> >>>>>>>>>>>> section I have also proposed the way to merge rest of the
> >>>>>>>>>>>> JAXP 1.3
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> RI
> >>>>>>
> >>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
> >>>>>>>>>>>> suggested where implementation component should reside
> >>>>>>>>>>>> i.e. Xerces
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> or
> >>>>>>
> >>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
> >>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
> >>>>>>>>>>>> Xerces &
> >>>>>>>>>>>> Xalan is very welcome.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 APIs: *
> >>>>>>>>>>>>
> >>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
> >>>>>>>>>>>> set of
> >>>>>>>>>>>> APIs
> >>>>>>>>>>>> are used by many different projects.
> >>>>>>>>>>>> With JSR 206 declared as final and many new standards
> >>>>>>>>>>>> emerging, we
> >>>>>>>>>>>> should update xml-commons to JAXP 1.3
> >>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to
> >>>>>>>>>>>> xml-commons main
> >>>>>>>>>>>> trunk
> >>>>>>>>>>>> and apply a tag.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
> >>>>>>>>>>>> part of
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Xerces)*
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
> >>>>>>>>>>>>
> >>>>>>>>>>>> javax.xml.datatype
> >>>>>>>>>>>> javax.xml.validation
> >>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
> >>>>>>>>>>>>
> >>>>>>>>>>>> which should reside at Xerces.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
> >>>>>>>>>>>> changes
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> into
> >>>>>>
> >>>>>>>>>>>> that branch. This will help
> >>>>>>>>>>>> other Xerces active committers to have a chance to look at it
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> before
> >>>>>>
> >>>>>>>>>>>> these changes being finally
> >>>>>>>>>>>> committed to main trunk. This process would require merging
> >>>>>>>>>>>> changes to
> >>>>>>>>>>>> the branch and then committing
> >>>>>>>>>>>> changes to main trunk, i seek help of active Xerces
> >>>>>>>>>>>> committers.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
> >>>>>>>>>>>> part of
> >>>>>>>>>>>> Xalan)*
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
> >>>>>>>>>>>> XPath
> >>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
> >>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> changes
> >>>>>>
> >>>>>>>>>>>> done in "javax.xml.transform" package
> >>>>>>>>>>>> for ex. now application can use the same Transformer
> >>>>>>>>>>>> instance by
> >>>>>>>>>>>> invoking reset().
> >>>>>>>>>>>>
> >>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we
> >>>>>>>>>>>> create a
> >>>>>>>>>>>> branch
> >>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
> >>>>>>>>>>>> put there. This will help other Xalan active committers to
> >>>>>>>>>>>> have a
> >>>>>>>>>>>> chance
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> to look at it before these changes being finally
> >>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan
> >>>>>>>>>>>> committers
> >>>>>>>>>>>> for this
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> process.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> As always, all feedbacks are more than welcome.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks,
> >>>>>>>>>>>> Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
> >>>>>>>>>>>> [2]
> >>>>>>>>>>>> http://java.sun.com/j2se/1.5.
> >>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
> >>>>>>>>>>>> [3]
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> http://java.sun.com/j2se/1.5.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
> >>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> [4]
> >>>>>>>>>>>>
> >>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>>>>>
> >>>>>>>>>>>> summary.html
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>>>>>>> To unsubscribe, e-mail:
> >>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Michael Glavassevich
> >>>>>>>>>>> XML Parser Development
> >>>>>>>>>>> IBM Toronto Lab
> >>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
> >>>>>>>>>>> E-mail: mrglavas@apache.org
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
> >>>>>>>>
> >>>>>>
> >>>>>> Michael Glavassevich
> >>>>>> XML Parser Development
> >>>>>> IBM Toronto Lab
> >>>>>> E-mail: mrglavas@ca.ibm.com
> >>>>>> E-mail: mrglavas@apache.org
> >>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>>>>> For additional commands, e-mail: general-help@incubator.apache.org
> >>>>>>
> >>>>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> >>> For additional commands, e-mail: general-help@xml.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
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> > For additional commands, e-mail: general-help@xml.apache.org
> >
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by Davanum Srinivas <da...@gmail.com>.
Neeraj,
Spotted a few typos:
XPathFactory factory = XpathFactory.newInstnace();
XPathFactory factory = XpathFactory.newInstance(object_model_uri);
Should be:
XPathFactory factory = XPathFactory.newInstance();
XPathFactory factory = XPathFactory.newInstance(object_model_uri);
Right?
-- dims
On 4/11/05, Neeraj Bajaj <Ne...@sun.com> wrote:
> Hello All,
>
> Sometimes back i wrote an article on JAXP 1.3 which explains the new
> concepts and important features introduced in JAXP 1.3
> Especially the new
>
> - Schema Validation Framework
> - Object model neutral XPath APIs
> - XML Schema Datatypes etc.
>
> Advantages of New Schema Validation Framework and how the new API works
> has been explained with code snippets and diagram.
> New XPath APIs have also been explained. Article is available at
> https://jaxp.dev.java.net/article/jaxp-1_3-article.html
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
> > Hello All,
> >
> > xml-commons has been upgraded to JAXP 1.3 APIs.
> > If anyone could try and confirm that would be great.
> >
> > - Neeraj
> >
> > Neeraj Bajaj wrote:
> >
> >> I tagged xml-commons module yesterday with tag name
> >> '*before-jaxp13-upgradation*'.
> >>
> >> I plan to do the following but i will wait till tomorrow so as to
> >> give chance to the community
> >> to correct me if i am doing something wrong.
> >>
> >> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
> >> xml-commons/java/external/src directory
> >> with JAXP 1.3 API sources.
> >>
> >> Currently in xml-commons there are sources like org.w3c.dom.views.*
> >> which are not part of JAXP 1.3
> >> I won't remove those sources. they will be as it is.
> >>
> >> * Make changes in xml-commons/java/external/build.xml file so as to
> >> upgrade
> >> JAXP 1.1 --> JAXP 1.3
> >> DOM2 --> DOM3
> >> SAX2 --> (SAX) 2.0.2 (sax2r3)
> >>
> >> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
> >> available as xml-apis.jar.
> >>
> >> Anything else i should take care ?
> >>
> >> - Neeraj
> >>
> >>
> >> Neeraj Bajaj wrote:
> >>
> >>> Geir, I have uploaded sources at the same location
> >>> (xml-commons/contrib/jaxp13)
> >>> with Apache 2.0 license on every source file.
> >>>
> >>> - Neeraj
> >>>
> >>> Neeraj Bajaj wrote:
> >>>
> >>>> Ok, So i will add it and upload again.
> >>>>
> >>>> - Neeraj
> >>>>
> >>>> Geir Magnusson Jr. wrote:
> >>>>
> >>>>>
> >>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
> >>>>>
> >>>>>> Hi Neeraj,
> >>>>>>
> >>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
> >>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the
> >>>>>> Apache
> >>>>>> license. Will this still be the case for JAXP 1.3?
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> yes - these files must be available under the apache license v2.
> >>>>> And the license grantor should be the one that adds it.
> >>>>>
> >>>>> Sorry Neeraj :)
> >>>>>
> >>>>> geir
> >>>>>
> >>>>>>
> >>>>>> Thanks.
> >>>>>>
> >>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
> >>>>>>
> >>>>>>> Ok I just finished uploading JAXP 1.3 sources in
> >>>>>>> "*xml-commons/contrib/jaxp13"* directory.
> >>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
> >>>>>>> xalan-src.zip which
> >>>>>>> corresponds to jaxp-api,
> >>>>>>> xerces & xalan sources respectively.
> >>>>>>>
> >>>>>>> - Neeraj
> >>>>>>>
> >>>>>>> Neeraj Bajaj wrote:
> >>>>>>>
> >>>>>>>> That really sounds good to me.. so i would try to finish it today.
> >>>>>>>> I will send mail to the community when i am done.
> >>>>>>>>
> >>>>>>>> Thanks dims for the suggestion.
> >>>>>>>>
> >>>>>>>> - Neeraj
> >>>>>>>>
> >>>>>>>> Davanum Srinivas wrote:
> >>>>>>>>
> >>>>>>>>> Neeraj,
> >>>>>>>>>
> >>>>>>>>> my 2 cents...upload the whole thing say in
> >>>>>>>>> xml-commons/contrib/jaxp13
> >>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
> >>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
> >>>>>>>>> tagging the current code in the main trunk there) and it's
> >>>>>>>>> upto the
> >>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they
> >>>>>>>>> fit.
> >>>>>>>>>
> >>>>>>>>> thanks,
> >>>>>>>>> dims
> >>>>>>>>>
> >>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Thanks Michael for your response.
> >>>>>>>>>>
> >>>>>>>>>> I was just wondering what would be idle time to wait before i
> >>>>>>>>>> start
> >>>>>>>>>> work
> >>>>>>>>>> on this ?
> >>>>>>>>>> Does anyone has an opinion, Is there any other list where i
> >>>>>>>>>> should
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>> send
> >>>>>>
> >>>>>>>>>> this mail
> >>>>>>>>>> before making changes ?
> >>>>>>>>>>
> >>>>>>>>>> - Neeraj
> >>>>>>>>>>
> >>>>>>>>>> Michael Glavassevich wrote:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> Hi Neeraj,
> >>>>>>>>>>>
> >>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk,
> >>>>>>>>>>> tagging it
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>> and
> >>>>>>
> >>>>>>>>>>> making a branch for the old JAXP sources on the current
> >>>>>>>>>>> main trunk.
> >>>>>>>>>>>
> >>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
> >>>>>>>>>>> other
> >>>>>>>>>>> updates
> >>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
> >>>>>>>>>>> branch we've
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>
> >>>>>>>>>>> used
> >>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and
> >>>>>>>>>>> Xalan. I
> >>>>>>>>>>> assume a
> >>>>>>>>>>> similar branch will exist for 1.3.
> >>>>>>>>>>>
> >>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
> >>>>>>>>>>> 03:40:57
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>> AM:
> >>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>
> >>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
> >>>>>>>>>>>> attached as
> >>>>>>>>>>>> zip but
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> mail bounced back with the following message
> >>>>>>>>>>>>
> >>>>>>>>>>>> <error>
> >>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
> >>>>>>>>>>>> <ge...@xml.apache.org>
> >>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
> >>>>>>>>>>>> </error>
> >>>>>>>>>>>>
> >>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
> >>>>>>>>>>>> Apache
> >>>>>>>>>>>> server somewhere ?
> >>>>>>>>>>>> Can anyone guide me what is the procedure for such code
> >>>>>>>>>>>> grants ?
> >>>>>>>>>>>>
> >>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
> >>>>>>>>>>>> community
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> to help put it in a
> >>>>>>>>>>>> a branch and make it work there. As i think due to large
> >>>>>>>>>>>> number of
> >>>>>>>>>>>> changes it would be a considerable
> >>>>>>>>>>>> amount of work. This will also help the committers &
> >>>>>>>>>>>> community to
> >>>>>>>>>>>> have a
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> look at the code before
> >>>>>>>>>>>> it is merged into the main stream work.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I think i have commit access at xml-commons so i can commit
> >>>>>>>>>>>> the
> >>>>>>>>>>>> sources
> >>>>>>>>>>>> in xml-commons branch
> >>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
> >>>>>>>>>>>> What is
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> the
> >>>>>>
> >>>>>>>>>>>> opinion of community ? I can
> >>>>>>>>>>>> start this as soon as i get a consensus from the community. My
> >>>>>>>>>>>> preference is to put the sources on
> >>>>>>>>>>>> xml-commons main trunk.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Please let me know how should i proceed.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>
> >>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>
> >>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>>>>>>>>>>> implementation to Apache XML.*
> >>>>>>>>>>>> JAXP 1.3 (JSR 206
> >>>>>>>>>>>> <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of
> >>>>>>>>>>>> new
> >>>>>>>>>>>> functionalities.
> >>>>>>>>>>>>
> >>>>>>>>>>>> * New Schema Validation Framework
> >>>>>>>>>>>> * New Object Model neutral XPath APIs
> >>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
> >>>>>>>>>>>> * Reuse parser instance
> >>>>>>>>>>>> * Security enhancements
> >>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
> >>>>>>>>>>>> Save, SAX
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> 2, XML 1.1 and XInclude)
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
> >>>>>>>>>>>>
> >>>>>>>>>>>> Due to large size of code base i will be sending different
> >>>>>>>>>>>> mails
> >>>>>>>>>>>> for the
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> source code of Xerces & Xalan.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I have attached the original mail where i proposed the
> >>>>>>>>>>>> process of
> >>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
> >>>>>>>>>>>> integrating this donation into the main stream work of
> >>>>>>>>>>>> Xerces &
> >>>>>>>>>>>> Xalan.
> >>>>>>>>>>>> There was a general consensus to my proposal
> >>>>>>>>>>>> and we can discuss more about the technicalities of merging
> >>>>>>>>>>>> with
> >>>>>>>>>>>> in the
> >>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
> >>>>>>>>>>>> community.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
> >>>>>>>>>>>>
> >>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Neeraj Bajaj wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Geir Magnusson Jr. wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
> >>>>>>>>>>>>>>> up the
> >>>>>>>>>>>>>>> ball
> >>>>>>>>>>>>>>> on this one.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
> >>>>>>>>>>>>>>> presume that
> >>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
> >>>>>>>>>>>>>>> xalan-dev, and
> >>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
> >>>>>>>>>>>>>> achieved.
> >>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
> >>>>>>>>>>>>>> process
> >>>>>>>>>>>>>> hold things up.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> - Neeraj
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> To unsubscribe, e-mail:
> >>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>> ----------------------------------------------------------------------
> >>>>>>> --
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Subject:
> >>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
> >>>>>>>>>>>> From:
> >>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
> >>>>>>>>>>>> Date:
> >>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
> >>>>>>>>>>>>
> >>>>>>>>>>>> To:
> >>>>>>>>>>>> general@xml.apache.org
> >>>>>>>>>>>> CC:
> >>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> <Je...@Sun.COM>,
> >>>>>>
> >>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hello All,
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
> >>>>>>>>>>>> final. JAXP
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
> >>>>>>>>>>>> It introduces new Schema independent validation framework
> >>>>>>>>>>>> which
> >>>>>>>>>>>> decouples the validation as a process independent from
> >>>>>>>>>>>> parsing.
> >>>>>>>>>>>> It allows to compile Schema to an immutable memory
> >>>>>>>>>>>> representation
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> of
> >>>>>>
> >>>>>>>>>>>> Grammar which can validate different instances of XML document
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> thus
> >>>>>>
> >>>>>>>>>>>> greatly improving the performance of XML processing. XPath
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> language
> >>>>>>
> >>>>>>>>>>>> provides a simple, concise syntax for accessing individual
> >>>>>>>>>>>> parts
> >>>>>>>>>>>> of an
> >>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
> >>>>>>>>>>>> access to
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>
> >>>>>>>>>>>> the
> >>>>>>>>>>>> XPath evaluation environment and expression results
> >>>>>>>>>>>> independent
> >>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
> >>>>>>>>>>>> Datatypes to
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
> >>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
> >>>>>>>>>>>> 1.3 also
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>
> >>>>>>>>>>>> adds
> >>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> allowing
> >>>>>>
> >>>>>>>>>>>> application to reuse the same instance to process multiple XML
> >>>>>>>>>>>> documents. This also helps in increasing XML processing
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> performance.
> >>>>>>
> >>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
> >>>>>>>>>>>> DOM L3
> >>>>>>>>>>>> L/S, XML
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> 1.1, XInclude.
> >>>>>>>>>>>>
> >>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
> >>>>>>>>>>>> (API s +
> >>>>>>>>>>>> Reference Implementation) to Apache. *
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
> >>>>>>>>>>>>
> >>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> (Reference
> >>>>>>
> >>>>>>>>>>>> Implementation). RI has been done using
> >>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
> >>>>>>>>>>>> of newly
> >>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
> >>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
> >>>>>>>>>>>> Transformer
> >>>>>>>>>>>> Reset changes, Secured XML Processing changes.
> >>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
> >>>>>>>>>>>> XInclude
> >>>>>>>>>>>> already exist on Apache Xerces. So in the next
> >>>>>>>>>>>> section I have also proposed the way to merge rest of the
> >>>>>>>>>>>> JAXP 1.3
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> RI
> >>>>>>
> >>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
> >>>>>>>>>>>> suggested where implementation component should reside
> >>>>>>>>>>>> i.e. Xerces
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> or
> >>>>>>
> >>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
> >>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
> >>>>>>>>>>>> Xerces &
> >>>>>>>>>>>> Xalan is very welcome.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 APIs: *
> >>>>>>>>>>>>
> >>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
> >>>>>>>>>>>> set of
> >>>>>>>>>>>> APIs
> >>>>>>>>>>>> are used by many different projects.
> >>>>>>>>>>>> With JSR 206 declared as final and many new standards
> >>>>>>>>>>>> emerging, we
> >>>>>>>>>>>> should update xml-commons to JAXP 1.3
> >>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to
> >>>>>>>>>>>> xml-commons main
> >>>>>>>>>>>> trunk
> >>>>>>>>>>>> and apply a tag.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
> >>>>>>>>>>>> part of
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Xerces)*
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
> >>>>>>>>>>>>
> >>>>>>>>>>>> javax.xml.datatype
> >>>>>>>>>>>> javax.xml.validation
> >>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
> >>>>>>>>>>>>
> >>>>>>>>>>>> which should reside at Xerces.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
> >>>>>>>>>>>> changes
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> into
> >>>>>>
> >>>>>>>>>>>> that branch. This will help
> >>>>>>>>>>>> other Xerces active committers to have a chance to look at it
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> before
> >>>>>>
> >>>>>>>>>>>> these changes being finally
> >>>>>>>>>>>> committed to main trunk. This process would require merging
> >>>>>>>>>>>> changes to
> >>>>>>>>>>>> the branch and then committing
> >>>>>>>>>>>> changes to main trunk, i seek help of active Xerces
> >>>>>>>>>>>> committers.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
> >>>>>>>>>>>> part of
> >>>>>>>>>>>> Xalan)*
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
> >>>>>>>>>>>> XPath
> >>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
> >>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> changes
> >>>>>>
> >>>>>>>>>>>> done in "javax.xml.transform" package
> >>>>>>>>>>>> for ex. now application can use the same Transformer
> >>>>>>>>>>>> instance by
> >>>>>>>>>>>> invoking reset().
> >>>>>>>>>>>>
> >>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we
> >>>>>>>>>>>> create a
> >>>>>>>>>>>> branch
> >>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
> >>>>>>>>>>>> put there. This will help other Xalan active committers to
> >>>>>>>>>>>> have a
> >>>>>>>>>>>> chance
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> to look at it before these changes being finally
> >>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan
> >>>>>>>>>>>> committers
> >>>>>>>>>>>> for this
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> process.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> As always, all feedbacks are more than welcome.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks,
> >>>>>>>>>>>> Neeraj
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
> >>>>>>>>>>>> [2]
> >>>>>>>>>>>> http://java.sun.com/j2se/1.5.
> >>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
> >>>>>>>>>>>> [3]
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> http://java.sun.com/j2se/1.5.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
> >>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> [4]
> >>>>>>>>>>>>
> >>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>>>>>
> >>>>>>>>>>>> summary.html
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>>>>>>> To unsubscribe, e-mail:
> >>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>>> For additional commands, e-mail:
> >>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Michael Glavassevich
> >>>>>>>>>>> XML Parser Development
> >>>>>>>>>>> IBM Toronto Lab
> >>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
> >>>>>>>>>>> E-mail: mrglavas@apache.org
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
> >>>>>>>>
> >>>>>>
> >>>>>> Michael Glavassevich
> >>>>>> XML Parser Development
> >>>>>> IBM Toronto Lab
> >>>>>> E-mail: mrglavas@ca.ibm.com
> >>>>>> E-mail: mrglavas@apache.org
> >>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>>
> >>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>>>>> For additional commands, e-mail: general-help@incubator.apache.org
> >>>>>>
> >>>>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> >>> For additional commands, e-mail: general-help@xml.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
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> > For additional commands, e-mail: general-help@xml.apache.org
> >
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3 complete
[Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
Sometimes back i wrote an article on JAXP 1.3 which explains the new
concepts and important features introduced in JAXP 1.3
Especially the new
- Schema Validation Framework
- Object model neutral XPath APIs
- XML Schema Datatypes etc.
Advantages of New Schema Validation Framework and how the new API works
has been explained with code snippets and diagram.
New XPath APIs have also been explained. Article is available at
https://jaxp.dev.java.net/article/jaxp-1_3-article.html
- Neeraj
Neeraj Bajaj wrote:
> Hello All,
>
> xml-commons has been upgraded to JAXP 1.3 APIs.
> If anyone could try and confirm that would be great.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
>> I tagged xml-commons module yesterday with tag name
>> '*before-jaxp13-upgradation*'.
>>
>> I plan to do the following but i will wait till tomorrow so as to
>> give chance to the community
>> to correct me if i am doing something wrong.
>>
>> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
>> xml-commons/java/external/src directory
>> with JAXP 1.3 API sources.
>>
>> Currently in xml-commons there are sources like org.w3c.dom.views.*
>> which are not part of JAXP 1.3
>> I won't remove those sources. they will be as it is.
>>
>> * Make changes in xml-commons/java/external/build.xml file so as to
>> upgrade
>> JAXP 1.1 --> JAXP 1.3
>> DOM2 --> DOM3
>> SAX2 --> (SAX) 2.0.2 (sax2r3)
>>
>> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
>> available as xml-apis.jar.
>>
>> Anything else i should take care ?
>>
>> - Neeraj
>>
>>
>> Neeraj Bajaj wrote:
>>
>>> Geir, I have uploaded sources at the same location
>>> (xml-commons/contrib/jaxp13)
>>> with Apache 2.0 license on every source file.
>>>
>>> - Neeraj
>>>
>>> Neeraj Bajaj wrote:
>>>
>>>> Ok, So i will add it and upload again.
>>>>
>>>> - Neeraj
>>>>
>>>> Geir Magnusson Jr. wrote:
>>>>
>>>>>
>>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>>>
>>>>>> Hi Neeraj,
>>>>>>
>>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the
>>>>>> Apache
>>>>>> license. Will this still be the case for JAXP 1.3?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> yes - these files must be available under the apache license v2.
>>>>> And the license grantor should be the one that adds it.
>>>>>
>>>>> Sorry Neeraj :)
>>>>>
>>>>> geir
>>>>>
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>>>
>>>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
>>>>>>> xalan-src.zip which
>>>>>>> corresponds to jaxp-api,
>>>>>>> xerces & xalan sources respectively.
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Neeraj Bajaj wrote:
>>>>>>>
>>>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>>>> I will send mail to the community when i am done.
>>>>>>>>
>>>>>>>> Thanks dims for the suggestion.
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>> Davanum Srinivas wrote:
>>>>>>>>
>>>>>>>>> Neeraj,
>>>>>>>>>
>>>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>>>> xml-commons/contrib/jaxp13
>>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>>>> tagging the current code in the main trunk there) and it's
>>>>>>>>> upto the
>>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they
>>>>>>>>> fit.
>>>>>>>>>
>>>>>>>>> thanks,
>>>>>>>>> dims
>>>>>>>>>
>>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Thanks Michael for your response.
>>>>>>>>>>
>>>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>>>> start
>>>>>>>>>> work
>>>>>>>>>> on this ?
>>>>>>>>>> Does anyone has an opinion, Is there any other list where i
>>>>>>>>>> should
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>> send
>>>>>>
>>>>>>>>>> this mail
>>>>>>>>>> before making changes ?
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hi Neeraj,
>>>>>>>>>>>
>>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk,
>>>>>>>>>>> tagging it
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>> and
>>>>>>
>>>>>>>>>>> making a branch for the old JAXP sources on the current
>>>>>>>>>>> main trunk.
>>>>>>>>>>>
>>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
>>>>>>>>>>> other
>>>>>>>>>>> updates
>>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
>>>>>>>>>>> branch we've
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>>>>>>>>> used
>>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and
>>>>>>>>>>> Xalan. I
>>>>>>>>>>> assume a
>>>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>>>
>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
>>>>>>>>>>> 03:40:57
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>> AM:
>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
>>>>>>>>>>>> attached as
>>>>>>>>>>>> zip but
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>>>
>>>>>>>>>>>> <error>
>>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>>>> </error>
>>>>>>>>>>>>
>>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>>>> Apache
>>>>>>>>>>>> server somewhere ?
>>>>>>>>>>>> Can anyone guide me what is the procedure for such code
>>>>>>>>>>>> grants ?
>>>>>>>>>>>>
>>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>>>> community
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> to help put it in a
>>>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>>>> number of
>>>>>>>>>>>> changes it would be a considerable
>>>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>>>> community to
>>>>>>>>>>>> have a
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> look at the code before
>>>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>>>
>>>>>>>>>>>> I think i have commit access at xml-commons so i can commit
>>>>>>>>>>>> the
>>>>>>>>>>>> sources
>>>>>>>>>>>> in xml-commons branch
>>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>>>> What is
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> the
>>>>>>
>>>>>>>>>>>> opinion of community ? I can
>>>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>>>> preference is to put the sources on
>>>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>>>
>>>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>>>> JAXP 1.3 (JSR 206
>>>>>>>>>>>> <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of
>>>>>>>>>>>> new
>>>>>>>>>>>> functionalities.
>>>>>>>>>>>>
>>>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>>>> * Reuse parser instance
>>>>>>>>>>>> * Security enhancements
>>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>>>> Save, SAX
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>>>
>>>>>>>>>>>> Due to large size of code base i will be sending different
>>>>>>>>>>>> mails
>>>>>>>>>>>> for the
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>>>
>>>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>>>> process of
>>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>>>> integrating this donation into the main stream work of
>>>>>>>>>>>> Xerces &
>>>>>>>>>>>> Xalan.
>>>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>>>> and we can discuss more about the technicalities of merging
>>>>>>>>>>>> with
>>>>>>>>>>>> in the
>>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>>>> community.
>>>>>>>>>>>>
>>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
>>>>>>>>>>>>>>> up the
>>>>>>>>>>>>>>> ball
>>>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>>>> presume that
>>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>>>> achieved.
>>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>>>> process
>>>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>>>
>>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>> ----------------------------------------------------------------------
>>>>>>> --
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Subject:
>>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>>>> From:
>>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>>>> Date:
>>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>>>
>>>>>>>>>>>> To:
>>>>>>>>>>>> general@xml.apache.org
>>>>>>>>>>>> CC:
>>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> <Je...@Sun.COM>,
>>>>>>
>>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>>>> final. JAXP
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>>>> It introduces new Schema independent validation framework
>>>>>>>>>>>> which
>>>>>>>>>>>> decouples the validation as a process independent from
>>>>>>>>>>>> parsing.
>>>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>>>> representation
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> of
>>>>>>
>>>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> thus
>>>>>>
>>>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> language
>>>>>>
>>>>>>>>>>>> provides a simple, concise syntax for accessing individual
>>>>>>>>>>>> parts
>>>>>>>>>>>> of an
>>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>>>> access to
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>
>>>>>>>>>>>> the
>>>>>>>>>>>> XPath evaluation environment and expression results
>>>>>>>>>>>> independent
>>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>>>> Datatypes to
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>>>> 1.3 also
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>
>>>>>>>>>>>> adds
>>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> allowing
>>>>>>
>>>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> performance.
>>>>>>
>>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
>>>>>>>>>>>> DOM L3
>>>>>>>>>>>> L/S, XML
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>>>
>>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
>>>>>>>>>>>> (API s +
>>>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> (Reference
>>>>>>
>>>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
>>>>>>>>>>>> of newly
>>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>>>> Transformer
>>>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>>>> XInclude
>>>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>>>> JAXP 1.3
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> RI
>>>>>>
>>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>>>> suggested where implementation component should reside
>>>>>>>>>>>> i.e. Xerces
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> or
>>>>>>
>>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>>>> Xerces &
>>>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>>>> set of
>>>>>>>>>>>> APIs
>>>>>>>>>>>> are used by many different projects.
>>>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>>>> emerging, we
>>>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to
>>>>>>>>>>>> xml-commons main
>>>>>>>>>>>> trunk
>>>>>>>>>>>> and apply a tag.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>> part of
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Xerces)*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>>>
>>>>>>>>>>>> javax.xml.datatype
>>>>>>>>>>>> javax.xml.validation
>>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>>>
>>>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>>>
>>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
>>>>>>>>>>>> changes
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> into
>>>>>>
>>>>>>>>>>>> that branch. This will help
>>>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> before
>>>>>>
>>>>>>>>>>>> these changes being finally
>>>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>>>> changes to
>>>>>>>>>>>> the branch and then committing
>>>>>>>>>>>> changes to main trunk, i seek help of active Xerces
>>>>>>>>>>>> committers.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>> part of
>>>>>>>>>>>> Xalan)*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
>>>>>>>>>>>> XPath
>>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> changes
>>>>>>
>>>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>>>> for ex. now application can use the same Transformer
>>>>>>>>>>>> instance by
>>>>>>>>>>>> invoking reset().
>>>>>>>>>>>>
>>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we
>>>>>>>>>>>> create a
>>>>>>>>>>>> branch
>>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>>>> have a
>>>>>>>>>>>> chance
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan
>>>>>>>>>>>> committers
>>>>>>>>>>>> for this
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> process.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>>>> [2]
>>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>>>> [3]
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> [4]
>>>>>>>>>>>>
>>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>>
>>>>>>>>>>>> summary.html
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Michael Glavassevich
>>>>>>>>>>> XML Parser Development
>>>>>>>>>>> IBM Toronto Lab
>>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>>>
>>>>>>
>>>>>> Michael Glavassevich
>>>>>> XML Parser Development
>>>>>> IBM Toronto Lab
>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>> E-mail: mrglavas@apache.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.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
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3 complete
[Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
Sometimes back i wrote an article on JAXP 1.3 which explains the new
concepts and important features introduced in JAXP 1.3
Especially the new
- Schema Validation Framework
- Object model neutral XPath APIs
- XML Schema Datatypes etc.
Advantages of New Schema Validation Framework and how the new API works
has been explained with code snippets and diagram.
New XPath APIs have also been explained. Article is available at
https://jaxp.dev.java.net/article/jaxp-1_3-article.html
- Neeraj
Neeraj Bajaj wrote:
> Hello All,
>
> xml-commons has been upgraded to JAXP 1.3 APIs.
> If anyone could try and confirm that would be great.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
>> I tagged xml-commons module yesterday with tag name
>> '*before-jaxp13-upgradation*'.
>>
>> I plan to do the following but i will wait till tomorrow so as to
>> give chance to the community
>> to correct me if i am doing something wrong.
>>
>> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
>> xml-commons/java/external/src directory
>> with JAXP 1.3 API sources.
>>
>> Currently in xml-commons there are sources like org.w3c.dom.views.*
>> which are not part of JAXP 1.3
>> I won't remove those sources. they will be as it is.
>>
>> * Make changes in xml-commons/java/external/build.xml file so as to
>> upgrade
>> JAXP 1.1 --> JAXP 1.3
>> DOM2 --> DOM3
>> SAX2 --> (SAX) 2.0.2 (sax2r3)
>>
>> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
>> available as xml-apis.jar.
>>
>> Anything else i should take care ?
>>
>> - Neeraj
>>
>>
>> Neeraj Bajaj wrote:
>>
>>> Geir, I have uploaded sources at the same location
>>> (xml-commons/contrib/jaxp13)
>>> with Apache 2.0 license on every source file.
>>>
>>> - Neeraj
>>>
>>> Neeraj Bajaj wrote:
>>>
>>>> Ok, So i will add it and upload again.
>>>>
>>>> - Neeraj
>>>>
>>>> Geir Magnusson Jr. wrote:
>>>>
>>>>>
>>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>>>
>>>>>> Hi Neeraj,
>>>>>>
>>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the
>>>>>> Apache
>>>>>> license. Will this still be the case for JAXP 1.3?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> yes - these files must be available under the apache license v2.
>>>>> And the license grantor should be the one that adds it.
>>>>>
>>>>> Sorry Neeraj :)
>>>>>
>>>>> geir
>>>>>
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>>>
>>>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
>>>>>>> xalan-src.zip which
>>>>>>> corresponds to jaxp-api,
>>>>>>> xerces & xalan sources respectively.
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Neeraj Bajaj wrote:
>>>>>>>
>>>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>>>> I will send mail to the community when i am done.
>>>>>>>>
>>>>>>>> Thanks dims for the suggestion.
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>> Davanum Srinivas wrote:
>>>>>>>>
>>>>>>>>> Neeraj,
>>>>>>>>>
>>>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>>>> xml-commons/contrib/jaxp13
>>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>>>> tagging the current code in the main trunk there) and it's
>>>>>>>>> upto the
>>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they
>>>>>>>>> fit.
>>>>>>>>>
>>>>>>>>> thanks,
>>>>>>>>> dims
>>>>>>>>>
>>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Thanks Michael for your response.
>>>>>>>>>>
>>>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>>>> start
>>>>>>>>>> work
>>>>>>>>>> on this ?
>>>>>>>>>> Does anyone has an opinion, Is there any other list where i
>>>>>>>>>> should
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>> send
>>>>>>
>>>>>>>>>> this mail
>>>>>>>>>> before making changes ?
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hi Neeraj,
>>>>>>>>>>>
>>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk,
>>>>>>>>>>> tagging it
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>> and
>>>>>>
>>>>>>>>>>> making a branch for the old JAXP sources on the current
>>>>>>>>>>> main trunk.
>>>>>>>>>>>
>>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
>>>>>>>>>>> other
>>>>>>>>>>> updates
>>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
>>>>>>>>>>> branch we've
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>>>>>>>>> used
>>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and
>>>>>>>>>>> Xalan. I
>>>>>>>>>>> assume a
>>>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>>>
>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
>>>>>>>>>>> 03:40:57
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>> AM:
>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
>>>>>>>>>>>> attached as
>>>>>>>>>>>> zip but
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>>>
>>>>>>>>>>>> <error>
>>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>>>> </error>
>>>>>>>>>>>>
>>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>>>> Apache
>>>>>>>>>>>> server somewhere ?
>>>>>>>>>>>> Can anyone guide me what is the procedure for such code
>>>>>>>>>>>> grants ?
>>>>>>>>>>>>
>>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>>>> community
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> to help put it in a
>>>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>>>> number of
>>>>>>>>>>>> changes it would be a considerable
>>>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>>>> community to
>>>>>>>>>>>> have a
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> look at the code before
>>>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>>>
>>>>>>>>>>>> I think i have commit access at xml-commons so i can commit
>>>>>>>>>>>> the
>>>>>>>>>>>> sources
>>>>>>>>>>>> in xml-commons branch
>>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>>>> What is
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> the
>>>>>>
>>>>>>>>>>>> opinion of community ? I can
>>>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>>>> preference is to put the sources on
>>>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>>>
>>>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>>>> JAXP 1.3 (JSR 206
>>>>>>>>>>>> <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of
>>>>>>>>>>>> new
>>>>>>>>>>>> functionalities.
>>>>>>>>>>>>
>>>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>>>> * Reuse parser instance
>>>>>>>>>>>> * Security enhancements
>>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>>>> Save, SAX
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>>>
>>>>>>>>>>>> Due to large size of code base i will be sending different
>>>>>>>>>>>> mails
>>>>>>>>>>>> for the
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>>>
>>>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>>>> process of
>>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>>>> integrating this donation into the main stream work of
>>>>>>>>>>>> Xerces &
>>>>>>>>>>>> Xalan.
>>>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>>>> and we can discuss more about the technicalities of merging
>>>>>>>>>>>> with
>>>>>>>>>>>> in the
>>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>>>> community.
>>>>>>>>>>>>
>>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
>>>>>>>>>>>>>>> up the
>>>>>>>>>>>>>>> ball
>>>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>>>> presume that
>>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>>>> achieved.
>>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>>>> process
>>>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>>>
>>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>> ----------------------------------------------------------------------
>>>>>>> --
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Subject:
>>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>>>> From:
>>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>>>> Date:
>>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>>>
>>>>>>>>>>>> To:
>>>>>>>>>>>> general@xml.apache.org
>>>>>>>>>>>> CC:
>>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> <Je...@Sun.COM>,
>>>>>>
>>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>>>> final. JAXP
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>>>> It introduces new Schema independent validation framework
>>>>>>>>>>>> which
>>>>>>>>>>>> decouples the validation as a process independent from
>>>>>>>>>>>> parsing.
>>>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>>>> representation
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> of
>>>>>>
>>>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> thus
>>>>>>
>>>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> language
>>>>>>
>>>>>>>>>>>> provides a simple, concise syntax for accessing individual
>>>>>>>>>>>> parts
>>>>>>>>>>>> of an
>>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>>>> access to
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>
>>>>>>>>>>>> the
>>>>>>>>>>>> XPath evaluation environment and expression results
>>>>>>>>>>>> independent
>>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>>>> Datatypes to
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>>>> 1.3 also
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>
>>>>>>>>>>>> adds
>>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> allowing
>>>>>>
>>>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> performance.
>>>>>>
>>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
>>>>>>>>>>>> DOM L3
>>>>>>>>>>>> L/S, XML
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>>>
>>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
>>>>>>>>>>>> (API s +
>>>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> (Reference
>>>>>>
>>>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
>>>>>>>>>>>> of newly
>>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>>>> Transformer
>>>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>>>> XInclude
>>>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>>>> JAXP 1.3
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> RI
>>>>>>
>>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>>>> suggested where implementation component should reside
>>>>>>>>>>>> i.e. Xerces
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> or
>>>>>>
>>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>>>> Xerces &
>>>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>>>> set of
>>>>>>>>>>>> APIs
>>>>>>>>>>>> are used by many different projects.
>>>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>>>> emerging, we
>>>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to
>>>>>>>>>>>> xml-commons main
>>>>>>>>>>>> trunk
>>>>>>>>>>>> and apply a tag.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>> part of
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Xerces)*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>>>
>>>>>>>>>>>> javax.xml.datatype
>>>>>>>>>>>> javax.xml.validation
>>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>>>
>>>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>>>
>>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
>>>>>>>>>>>> changes
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> into
>>>>>>
>>>>>>>>>>>> that branch. This will help
>>>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> before
>>>>>>
>>>>>>>>>>>> these changes being finally
>>>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>>>> changes to
>>>>>>>>>>>> the branch and then committing
>>>>>>>>>>>> changes to main trunk, i seek help of active Xerces
>>>>>>>>>>>> committers.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>> part of
>>>>>>>>>>>> Xalan)*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
>>>>>>>>>>>> XPath
>>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> changes
>>>>>>
>>>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>>>> for ex. now application can use the same Transformer
>>>>>>>>>>>> instance by
>>>>>>>>>>>> invoking reset().
>>>>>>>>>>>>
>>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we
>>>>>>>>>>>> create a
>>>>>>>>>>>> branch
>>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>>>> have a
>>>>>>>>>>>> chance
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan
>>>>>>>>>>>> committers
>>>>>>>>>>>> for this
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> process.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>>>> [2]
>>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>>>> [3]
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> [4]
>>>>>>>>>>>>
>>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>>
>>>>>>>>>>>> summary.html
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Michael Glavassevich
>>>>>>>>>>> XML Parser Development
>>>>>>>>>>> IBM Toronto Lab
>>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>>>
>>>>>>
>>>>>> Michael Glavassevich
>>>>>> XML Parser Development
>>>>>> IBM Toronto Lab
>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>> E-mail: mrglavas@apache.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.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
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3 complete
[Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
Sometimes back i wrote an article on JAXP 1.3 which explains the new
concepts and important features introduced in JAXP 1.3
Especially the new
- Schema Validation Framework
- Object model neutral XPath APIs
- XML Schema Datatypes etc.
Advantages of New Schema Validation Framework and how the new API works
has been explained with code snippets and diagram.
New XPath APIs have also been explained. Article is available at
https://jaxp.dev.java.net/article/jaxp-1_3-article.html
- Neeraj
Neeraj Bajaj wrote:
> Hello All,
>
> xml-commons has been upgraded to JAXP 1.3 APIs.
> If anyone could try and confirm that would be great.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
>> I tagged xml-commons module yesterday with tag name
>> '*before-jaxp13-upgradation*'.
>>
>> I plan to do the following but i will wait till tomorrow so as to
>> give chance to the community
>> to correct me if i am doing something wrong.
>>
>> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
>> xml-commons/java/external/src directory
>> with JAXP 1.3 API sources.
>>
>> Currently in xml-commons there are sources like org.w3c.dom.views.*
>> which are not part of JAXP 1.3
>> I won't remove those sources. they will be as it is.
>>
>> * Make changes in xml-commons/java/external/build.xml file so as to
>> upgrade
>> JAXP 1.1 --> JAXP 1.3
>> DOM2 --> DOM3
>> SAX2 --> (SAX) 2.0.2 (sax2r3)
>>
>> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
>> available as xml-apis.jar.
>>
>> Anything else i should take care ?
>>
>> - Neeraj
>>
>>
>> Neeraj Bajaj wrote:
>>
>>> Geir, I have uploaded sources at the same location
>>> (xml-commons/contrib/jaxp13)
>>> with Apache 2.0 license on every source file.
>>>
>>> - Neeraj
>>>
>>> Neeraj Bajaj wrote:
>>>
>>>> Ok, So i will add it and upload again.
>>>>
>>>> - Neeraj
>>>>
>>>> Geir Magnusson Jr. wrote:
>>>>
>>>>>
>>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>>>
>>>>>> Hi Neeraj,
>>>>>>
>>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the
>>>>>> Apache
>>>>>> license. Will this still be the case for JAXP 1.3?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> yes - these files must be available under the apache license v2.
>>>>> And the license grantor should be the one that adds it.
>>>>>
>>>>> Sorry Neeraj :)
>>>>>
>>>>> geir
>>>>>
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>>>
>>>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
>>>>>>> xalan-src.zip which
>>>>>>> corresponds to jaxp-api,
>>>>>>> xerces & xalan sources respectively.
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Neeraj Bajaj wrote:
>>>>>>>
>>>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>>>> I will send mail to the community when i am done.
>>>>>>>>
>>>>>>>> Thanks dims for the suggestion.
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>> Davanum Srinivas wrote:
>>>>>>>>
>>>>>>>>> Neeraj,
>>>>>>>>>
>>>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>>>> xml-commons/contrib/jaxp13
>>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>>>> tagging the current code in the main trunk there) and it's
>>>>>>>>> upto the
>>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they
>>>>>>>>> fit.
>>>>>>>>>
>>>>>>>>> thanks,
>>>>>>>>> dims
>>>>>>>>>
>>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Thanks Michael for your response.
>>>>>>>>>>
>>>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>>>> start
>>>>>>>>>> work
>>>>>>>>>> on this ?
>>>>>>>>>> Does anyone has an opinion, Is there any other list where i
>>>>>>>>>> should
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>> send
>>>>>>
>>>>>>>>>> this mail
>>>>>>>>>> before making changes ?
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hi Neeraj,
>>>>>>>>>>>
>>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk,
>>>>>>>>>>> tagging it
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>> and
>>>>>>
>>>>>>>>>>> making a branch for the old JAXP sources on the current
>>>>>>>>>>> main trunk.
>>>>>>>>>>>
>>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
>>>>>>>>>>> other
>>>>>>>>>>> updates
>>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
>>>>>>>>>>> branch we've
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>>>>>>>>> used
>>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and
>>>>>>>>>>> Xalan. I
>>>>>>>>>>> assume a
>>>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>>>
>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
>>>>>>>>>>> 03:40:57
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>> AM:
>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
>>>>>>>>>>>> attached as
>>>>>>>>>>>> zip but
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>>>
>>>>>>>>>>>> <error>
>>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>>>> </error>
>>>>>>>>>>>>
>>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>>>> Apache
>>>>>>>>>>>> server somewhere ?
>>>>>>>>>>>> Can anyone guide me what is the procedure for such code
>>>>>>>>>>>> grants ?
>>>>>>>>>>>>
>>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>>>> community
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> to help put it in a
>>>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>>>> number of
>>>>>>>>>>>> changes it would be a considerable
>>>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>>>> community to
>>>>>>>>>>>> have a
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> look at the code before
>>>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>>>
>>>>>>>>>>>> I think i have commit access at xml-commons so i can commit
>>>>>>>>>>>> the
>>>>>>>>>>>> sources
>>>>>>>>>>>> in xml-commons branch
>>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>>>> What is
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> the
>>>>>>
>>>>>>>>>>>> opinion of community ? I can
>>>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>>>> preference is to put the sources on
>>>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>>>
>>>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>>>> JAXP 1.3 (JSR 206
>>>>>>>>>>>> <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of
>>>>>>>>>>>> new
>>>>>>>>>>>> functionalities.
>>>>>>>>>>>>
>>>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>>>> * Reuse parser instance
>>>>>>>>>>>> * Security enhancements
>>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>>>> Save, SAX
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>>>
>>>>>>>>>>>> Due to large size of code base i will be sending different
>>>>>>>>>>>> mails
>>>>>>>>>>>> for the
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>>>
>>>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>>>> process of
>>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>>>> integrating this donation into the main stream work of
>>>>>>>>>>>> Xerces &
>>>>>>>>>>>> Xalan.
>>>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>>>> and we can discuss more about the technicalities of merging
>>>>>>>>>>>> with
>>>>>>>>>>>> in the
>>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>>>> community.
>>>>>>>>>>>>
>>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
>>>>>>>>>>>>>>> up the
>>>>>>>>>>>>>>> ball
>>>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>>>> presume that
>>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>>>> achieved.
>>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>>>> process
>>>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>>>
>>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>> ----------------------------------------------------------------------
>>>>>>> --
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Subject:
>>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>>>> From:
>>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>>>> Date:
>>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>>>
>>>>>>>>>>>> To:
>>>>>>>>>>>> general@xml.apache.org
>>>>>>>>>>>> CC:
>>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> <Je...@Sun.COM>,
>>>>>>
>>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>>>> final. JAXP
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>>>> It introduces new Schema independent validation framework
>>>>>>>>>>>> which
>>>>>>>>>>>> decouples the validation as a process independent from
>>>>>>>>>>>> parsing.
>>>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>>>> representation
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> of
>>>>>>
>>>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> thus
>>>>>>
>>>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> language
>>>>>>
>>>>>>>>>>>> provides a simple, concise syntax for accessing individual
>>>>>>>>>>>> parts
>>>>>>>>>>>> of an
>>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>>>> access to
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>
>>>>>>>>>>>> the
>>>>>>>>>>>> XPath evaluation environment and expression results
>>>>>>>>>>>> independent
>>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>>>> Datatypes to
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>>>> 1.3 also
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>
>>>>>>>>>>>> adds
>>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> allowing
>>>>>>
>>>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> performance.
>>>>>>
>>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
>>>>>>>>>>>> DOM L3
>>>>>>>>>>>> L/S, XML
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>>>
>>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
>>>>>>>>>>>> (API s +
>>>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> (Reference
>>>>>>
>>>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
>>>>>>>>>>>> of newly
>>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>>>> Transformer
>>>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>>>> XInclude
>>>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>>>> JAXP 1.3
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> RI
>>>>>>
>>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>>>> suggested where implementation component should reside
>>>>>>>>>>>> i.e. Xerces
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> or
>>>>>>
>>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>>>> Xerces &
>>>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>>>> set of
>>>>>>>>>>>> APIs
>>>>>>>>>>>> are used by many different projects.
>>>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>>>> emerging, we
>>>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to
>>>>>>>>>>>> xml-commons main
>>>>>>>>>>>> trunk
>>>>>>>>>>>> and apply a tag.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>> part of
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Xerces)*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>>>
>>>>>>>>>>>> javax.xml.datatype
>>>>>>>>>>>> javax.xml.validation
>>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>>>
>>>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>>>
>>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
>>>>>>>>>>>> changes
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> into
>>>>>>
>>>>>>>>>>>> that branch. This will help
>>>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> before
>>>>>>
>>>>>>>>>>>> these changes being finally
>>>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>>>> changes to
>>>>>>>>>>>> the branch and then committing
>>>>>>>>>>>> changes to main trunk, i seek help of active Xerces
>>>>>>>>>>>> committers.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>> part of
>>>>>>>>>>>> Xalan)*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
>>>>>>>>>>>> XPath
>>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> changes
>>>>>>
>>>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>>>> for ex. now application can use the same Transformer
>>>>>>>>>>>> instance by
>>>>>>>>>>>> invoking reset().
>>>>>>>>>>>>
>>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we
>>>>>>>>>>>> create a
>>>>>>>>>>>> branch
>>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>>>> have a
>>>>>>>>>>>> chance
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan
>>>>>>>>>>>> committers
>>>>>>>>>>>> for this
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> process.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>>>> [2]
>>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>>>> [3]
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> [4]
>>>>>>>>>>>>
>>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>>
>>>>>>>>>>>> summary.html
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Michael Glavassevich
>>>>>>>>>>> XML Parser Development
>>>>>>>>>>> IBM Toronto Lab
>>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>>>
>>>>>>
>>>>>> Michael Glavassevich
>>>>>> XML Parser Development
>>>>>> IBM Toronto Lab
>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>> E-mail: mrglavas@apache.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.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
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3 complete
[Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
Sometimes back i wrote an article on JAXP 1.3 which explains the new
concepts and important features introduced in JAXP 1.3
Especially the new
- Schema Validation Framework
- Object model neutral XPath APIs
- XML Schema Datatypes etc.
Advantages of New Schema Validation Framework and how the new API works
has been explained with code snippets and diagram.
New XPath APIs have also been explained. Article is available at
https://jaxp.dev.java.net/article/jaxp-1_3-article.html
- Neeraj
Neeraj Bajaj wrote:
> Hello All,
>
> xml-commons has been upgraded to JAXP 1.3 APIs.
> If anyone could try and confirm that would be great.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
>> I tagged xml-commons module yesterday with tag name
>> '*before-jaxp13-upgradation*'.
>>
>> I plan to do the following but i will wait till tomorrow so as to
>> give chance to the community
>> to correct me if i am doing something wrong.
>>
>> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
>> xml-commons/java/external/src directory
>> with JAXP 1.3 API sources.
>>
>> Currently in xml-commons there are sources like org.w3c.dom.views.*
>> which are not part of JAXP 1.3
>> I won't remove those sources. they will be as it is.
>>
>> * Make changes in xml-commons/java/external/build.xml file so as to
>> upgrade
>> JAXP 1.1 --> JAXP 1.3
>> DOM2 --> DOM3
>> SAX2 --> (SAX) 2.0.2 (sax2r3)
>>
>> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
>> available as xml-apis.jar.
>>
>> Anything else i should take care ?
>>
>> - Neeraj
>>
>>
>> Neeraj Bajaj wrote:
>>
>>> Geir, I have uploaded sources at the same location
>>> (xml-commons/contrib/jaxp13)
>>> with Apache 2.0 license on every source file.
>>>
>>> - Neeraj
>>>
>>> Neeraj Bajaj wrote:
>>>
>>>> Ok, So i will add it and upload again.
>>>>
>>>> - Neeraj
>>>>
>>>> Geir Magnusson Jr. wrote:
>>>>
>>>>>
>>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>>>
>>>>>> Hi Neeraj,
>>>>>>
>>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the
>>>>>> Apache
>>>>>> license. Will this still be the case for JAXP 1.3?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> yes - these files must be available under the apache license v2.
>>>>> And the license grantor should be the one that adds it.
>>>>>
>>>>> Sorry Neeraj :)
>>>>>
>>>>> geir
>>>>>
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>>>
>>>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
>>>>>>> xalan-src.zip which
>>>>>>> corresponds to jaxp-api,
>>>>>>> xerces & xalan sources respectively.
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Neeraj Bajaj wrote:
>>>>>>>
>>>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>>>> I will send mail to the community when i am done.
>>>>>>>>
>>>>>>>> Thanks dims for the suggestion.
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>> Davanum Srinivas wrote:
>>>>>>>>
>>>>>>>>> Neeraj,
>>>>>>>>>
>>>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>>>> xml-commons/contrib/jaxp13
>>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>>>> tagging the current code in the main trunk there) and it's
>>>>>>>>> upto the
>>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they
>>>>>>>>> fit.
>>>>>>>>>
>>>>>>>>> thanks,
>>>>>>>>> dims
>>>>>>>>>
>>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Thanks Michael for your response.
>>>>>>>>>>
>>>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>>>> start
>>>>>>>>>> work
>>>>>>>>>> on this ?
>>>>>>>>>> Does anyone has an opinion, Is there any other list where i
>>>>>>>>>> should
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>> send
>>>>>>
>>>>>>>>>> this mail
>>>>>>>>>> before making changes ?
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hi Neeraj,
>>>>>>>>>>>
>>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk,
>>>>>>>>>>> tagging it
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>> and
>>>>>>
>>>>>>>>>>> making a branch for the old JAXP sources on the current
>>>>>>>>>>> main trunk.
>>>>>>>>>>>
>>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
>>>>>>>>>>> other
>>>>>>>>>>> updates
>>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
>>>>>>>>>>> branch we've
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>>>>>>>>> used
>>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and
>>>>>>>>>>> Xalan. I
>>>>>>>>>>> assume a
>>>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>>>
>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
>>>>>>>>>>> 03:40:57
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>> AM:
>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
>>>>>>>>>>>> attached as
>>>>>>>>>>>> zip but
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>>>
>>>>>>>>>>>> <error>
>>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>>>> </error>
>>>>>>>>>>>>
>>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>>>> Apache
>>>>>>>>>>>> server somewhere ?
>>>>>>>>>>>> Can anyone guide me what is the procedure for such code
>>>>>>>>>>>> grants ?
>>>>>>>>>>>>
>>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>>>> community
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> to help put it in a
>>>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>>>> number of
>>>>>>>>>>>> changes it would be a considerable
>>>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>>>> community to
>>>>>>>>>>>> have a
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> look at the code before
>>>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>>>
>>>>>>>>>>>> I think i have commit access at xml-commons so i can commit
>>>>>>>>>>>> the
>>>>>>>>>>>> sources
>>>>>>>>>>>> in xml-commons branch
>>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>>>> What is
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> the
>>>>>>
>>>>>>>>>>>> opinion of community ? I can
>>>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>>>> preference is to put the sources on
>>>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>>>
>>>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>>>> JAXP 1.3 (JSR 206
>>>>>>>>>>>> <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of
>>>>>>>>>>>> new
>>>>>>>>>>>> functionalities.
>>>>>>>>>>>>
>>>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>>>> * Reuse parser instance
>>>>>>>>>>>> * Security enhancements
>>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>>>> Save, SAX
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>>>
>>>>>>>>>>>> Due to large size of code base i will be sending different
>>>>>>>>>>>> mails
>>>>>>>>>>>> for the
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>>>
>>>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>>>> process of
>>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>>>> integrating this donation into the main stream work of
>>>>>>>>>>>> Xerces &
>>>>>>>>>>>> Xalan.
>>>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>>>> and we can discuss more about the technicalities of merging
>>>>>>>>>>>> with
>>>>>>>>>>>> in the
>>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>>>> community.
>>>>>>>>>>>>
>>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
>>>>>>>>>>>>>>> up the
>>>>>>>>>>>>>>> ball
>>>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>>>> presume that
>>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>>>> achieved.
>>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>>>> process
>>>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>>>
>>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>> ----------------------------------------------------------------------
>>>>>>> --
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Subject:
>>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>>>> From:
>>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>>>> Date:
>>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>>>
>>>>>>>>>>>> To:
>>>>>>>>>>>> general@xml.apache.org
>>>>>>>>>>>> CC:
>>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> <Je...@Sun.COM>,
>>>>>>
>>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>>>> final. JAXP
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>>>> It introduces new Schema independent validation framework
>>>>>>>>>>>> which
>>>>>>>>>>>> decouples the validation as a process independent from
>>>>>>>>>>>> parsing.
>>>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>>>> representation
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> of
>>>>>>
>>>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> thus
>>>>>>
>>>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> language
>>>>>>
>>>>>>>>>>>> provides a simple, concise syntax for accessing individual
>>>>>>>>>>>> parts
>>>>>>>>>>>> of an
>>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>>>> access to
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>
>>>>>>>>>>>> the
>>>>>>>>>>>> XPath evaluation environment and expression results
>>>>>>>>>>>> independent
>>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>>>> Datatypes to
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>>>> 1.3 also
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>
>>>>>>>>>>>> adds
>>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> allowing
>>>>>>
>>>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> performance.
>>>>>>
>>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
>>>>>>>>>>>> DOM L3
>>>>>>>>>>>> L/S, XML
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>>>
>>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
>>>>>>>>>>>> (API s +
>>>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> (Reference
>>>>>>
>>>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
>>>>>>>>>>>> of newly
>>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>>>> Transformer
>>>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>>>> XInclude
>>>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>>>> JAXP 1.3
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> RI
>>>>>>
>>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>>>> suggested where implementation component should reside
>>>>>>>>>>>> i.e. Xerces
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> or
>>>>>>
>>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>>>> Xerces &
>>>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>>>> set of
>>>>>>>>>>>> APIs
>>>>>>>>>>>> are used by many different projects.
>>>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>>>> emerging, we
>>>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to
>>>>>>>>>>>> xml-commons main
>>>>>>>>>>>> trunk
>>>>>>>>>>>> and apply a tag.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>> part of
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Xerces)*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>>>
>>>>>>>>>>>> javax.xml.datatype
>>>>>>>>>>>> javax.xml.validation
>>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>>>
>>>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>>>
>>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
>>>>>>>>>>>> changes
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> into
>>>>>>
>>>>>>>>>>>> that branch. This will help
>>>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> before
>>>>>>
>>>>>>>>>>>> these changes being finally
>>>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>>>> changes to
>>>>>>>>>>>> the branch and then committing
>>>>>>>>>>>> changes to main trunk, i seek help of active Xerces
>>>>>>>>>>>> committers.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>> part of
>>>>>>>>>>>> Xalan)*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
>>>>>>>>>>>> XPath
>>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> changes
>>>>>>
>>>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>>>> for ex. now application can use the same Transformer
>>>>>>>>>>>> instance by
>>>>>>>>>>>> invoking reset().
>>>>>>>>>>>>
>>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we
>>>>>>>>>>>> create a
>>>>>>>>>>>> branch
>>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>>>> have a
>>>>>>>>>>>> chance
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan
>>>>>>>>>>>> committers
>>>>>>>>>>>> for this
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> process.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>>>> [2]
>>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>>>> [3]
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> [4]
>>>>>>>>>>>>
>>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>>
>>>>>>>>>>>> summary.html
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Michael Glavassevich
>>>>>>>>>>> XML Parser Development
>>>>>>>>>>> IBM Toronto Lab
>>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>>>
>>>>>>
>>>>>> Michael Glavassevich
>>>>>> XML Parser Development
>>>>>> IBM Toronto Lab
>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>> E-mail: mrglavas@apache.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.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
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Article on JAXP 1.3 [Re: xml-commons upgradation to JAXP 1.3 complete
[Re: Donation of JAXP 1.3 Sources to Apache]]
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
Sometimes back i wrote an article on JAXP 1.3 which explains the new
concepts and important features introduced in JAXP 1.3
Especially the new
- Schema Validation Framework
- Object model neutral XPath APIs
- XML Schema Datatypes etc.
Advantages of New Schema Validation Framework and how the new API works
has been explained with code snippets and diagram.
New XPath APIs have also been explained. Article is available at
https://jaxp.dev.java.net/article/jaxp-1_3-article.html
- Neeraj
Neeraj Bajaj wrote:
> Hello All,
>
> xml-commons has been upgraded to JAXP 1.3 APIs.
> If anyone could try and confirm that would be great.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
>> I tagged xml-commons module yesterday with tag name
>> '*before-jaxp13-upgradation*'.
>>
>> I plan to do the following but i will wait till tomorrow so as to
>> give chance to the community
>> to correct me if i am doing something wrong.
>>
>> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
>> xml-commons/java/external/src directory
>> with JAXP 1.3 API sources.
>>
>> Currently in xml-commons there are sources like org.w3c.dom.views.*
>> which are not part of JAXP 1.3
>> I won't remove those sources. they will be as it is.
>>
>> * Make changes in xml-commons/java/external/build.xml file so as to
>> upgrade
>> JAXP 1.1 --> JAXP 1.3
>> DOM2 --> DOM3
>> SAX2 --> (SAX) 2.0.2 (sax2r3)
>>
>> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
>> available as xml-apis.jar.
>>
>> Anything else i should take care ?
>>
>> - Neeraj
>>
>>
>> Neeraj Bajaj wrote:
>>
>>> Geir, I have uploaded sources at the same location
>>> (xml-commons/contrib/jaxp13)
>>> with Apache 2.0 license on every source file.
>>>
>>> - Neeraj
>>>
>>> Neeraj Bajaj wrote:
>>>
>>>> Ok, So i will add it and upload again.
>>>>
>>>> - Neeraj
>>>>
>>>> Geir Magnusson Jr. wrote:
>>>>
>>>>>
>>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>>>
>>>>>> Hi Neeraj,
>>>>>>
>>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the
>>>>>> Apache
>>>>>> license. Will this still be the case for JAXP 1.3?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> yes - these files must be available under the apache license v2.
>>>>> And the license grantor should be the one that adds it.
>>>>>
>>>>> Sorry Neeraj :)
>>>>>
>>>>> geir
>>>>>
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>>>
>>>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
>>>>>>> xalan-src.zip which
>>>>>>> corresponds to jaxp-api,
>>>>>>> xerces & xalan sources respectively.
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Neeraj Bajaj wrote:
>>>>>>>
>>>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>>>> I will send mail to the community when i am done.
>>>>>>>>
>>>>>>>> Thanks dims for the suggestion.
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>> Davanum Srinivas wrote:
>>>>>>>>
>>>>>>>>> Neeraj,
>>>>>>>>>
>>>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>>>> xml-commons/contrib/jaxp13
>>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>>>> tagging the current code in the main trunk there) and it's
>>>>>>>>> upto the
>>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they
>>>>>>>>> fit.
>>>>>>>>>
>>>>>>>>> thanks,
>>>>>>>>> dims
>>>>>>>>>
>>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Thanks Michael for your response.
>>>>>>>>>>
>>>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>>>> start
>>>>>>>>>> work
>>>>>>>>>> on this ?
>>>>>>>>>> Does anyone has an opinion, Is there any other list where i
>>>>>>>>>> should
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>> send
>>>>>>
>>>>>>>>>> this mail
>>>>>>>>>> before making changes ?
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hi Neeraj,
>>>>>>>>>>>
>>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk,
>>>>>>>>>>> tagging it
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>> and
>>>>>>
>>>>>>>>>>> making a branch for the old JAXP sources on the current
>>>>>>>>>>> main trunk.
>>>>>>>>>>>
>>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
>>>>>>>>>>> other
>>>>>>>>>>> updates
>>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
>>>>>>>>>>> branch we've
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>
>>>>>>>>>>> used
>>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and
>>>>>>>>>>> Xalan. I
>>>>>>>>>>> assume a
>>>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>>>
>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005
>>>>>>>>>>> 03:40:57
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>> AM:
>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
>>>>>>>>>>>> attached as
>>>>>>>>>>>> zip but
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>>>
>>>>>>>>>>>> <error>
>>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>>>> </error>
>>>>>>>>>>>>
>>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>>>> Apache
>>>>>>>>>>>> server somewhere ?
>>>>>>>>>>>> Can anyone guide me what is the procedure for such code
>>>>>>>>>>>> grants ?
>>>>>>>>>>>>
>>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>>>> community
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> to help put it in a
>>>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>>>> number of
>>>>>>>>>>>> changes it would be a considerable
>>>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>>>> community to
>>>>>>>>>>>> have a
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> look at the code before
>>>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>>>
>>>>>>>>>>>> I think i have commit access at xml-commons so i can commit
>>>>>>>>>>>> the
>>>>>>>>>>>> sources
>>>>>>>>>>>> in xml-commons branch
>>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>>>> What is
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> the
>>>>>>
>>>>>>>>>>>> opinion of community ? I can
>>>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>>>> preference is to put the sources on
>>>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>>>
>>>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>>>> JAXP 1.3 (JSR 206
>>>>>>>>>>>> <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of
>>>>>>>>>>>> new
>>>>>>>>>>>> functionalities.
>>>>>>>>>>>>
>>>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>>>> * Reuse parser instance
>>>>>>>>>>>> * Security enhancements
>>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>>>> Save, SAX
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>>>
>>>>>>>>>>>> Due to large size of code base i will be sending different
>>>>>>>>>>>> mails
>>>>>>>>>>>> for the
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>>>
>>>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>>>> process of
>>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>>>> integrating this donation into the main stream work of
>>>>>>>>>>>> Xerces &
>>>>>>>>>>>> Xalan.
>>>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>>>> and we can discuss more about the technicalities of merging
>>>>>>>>>>>> with
>>>>>>>>>>>> in the
>>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>>>> community.
>>>>>>>>>>>>
>>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
>>>>>>>>>>>>>>> up the
>>>>>>>>>>>>>>> ball
>>>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>>>> presume that
>>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>>>> achieved.
>>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>>>> process
>>>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>>>
>>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>> ----------------------------------------------------------------------
>>>>>>> --
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Subject:
>>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>>>> From:
>>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>>>> Date:
>>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>>>
>>>>>>>>>>>> To:
>>>>>>>>>>>> general@xml.apache.org
>>>>>>>>>>>> CC:
>>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> <Je...@Sun.COM>,
>>>>>>
>>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>>>> final. JAXP
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>>>> It introduces new Schema independent validation framework
>>>>>>>>>>>> which
>>>>>>>>>>>> decouples the validation as a process independent from
>>>>>>>>>>>> parsing.
>>>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>>>> representation
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> of
>>>>>>
>>>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> thus
>>>>>>
>>>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> language
>>>>>>
>>>>>>>>>>>> provides a simple, concise syntax for accessing individual
>>>>>>>>>>>> parts
>>>>>>>>>>>> of an
>>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>>>> access to
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>
>>>>>>>>>>>> the
>>>>>>>>>>>> XPath evaluation environment and expression results
>>>>>>>>>>>> independent
>>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>>>> Datatypes to
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>>>> 1.3 also
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>
>>>>>>>>>>>> adds
>>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> allowing
>>>>>>
>>>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> performance.
>>>>>>
>>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core
>>>>>>>>>>>> DOM L3
>>>>>>>>>>>> L/S, XML
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>>>
>>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
>>>>>>>>>>>> (API s +
>>>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> (Reference
>>>>>>
>>>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
>>>>>>>>>>>> of newly
>>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>>>> Transformer
>>>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>>>> XInclude
>>>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>>>> JAXP 1.3
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> RI
>>>>>>
>>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>>>> suggested where implementation component should reside
>>>>>>>>>>>> i.e. Xerces
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> or
>>>>>>
>>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>>>> Xerces &
>>>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>>>> set of
>>>>>>>>>>>> APIs
>>>>>>>>>>>> are used by many different projects.
>>>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>>>> emerging, we
>>>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to
>>>>>>>>>>>> xml-commons main
>>>>>>>>>>>> trunk
>>>>>>>>>>>> and apply a tag.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>> part of
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Xerces)*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>>>
>>>>>>>>>>>> javax.xml.datatype
>>>>>>>>>>>> javax.xml.validation
>>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>>>
>>>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>>>
>>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
>>>>>>>>>>>> changes
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> into
>>>>>>
>>>>>>>>>>>> that branch. This will help
>>>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> before
>>>>>>
>>>>>>>>>>>> these changes being finally
>>>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>>>> changes to
>>>>>>>>>>>> the branch and then committing
>>>>>>>>>>>> changes to main trunk, i seek help of active Xerces
>>>>>>>>>>>> committers.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>>> part of
>>>>>>>>>>>> Xalan)*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
>>>>>>>>>>>> XPath
>>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> changes
>>>>>>
>>>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>>>> for ex. now application can use the same Transformer
>>>>>>>>>>>> instance by
>>>>>>>>>>>> invoking reset().
>>>>>>>>>>>>
>>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we
>>>>>>>>>>>> create a
>>>>>>>>>>>> branch
>>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>>>> have a
>>>>>>>>>>>> chance
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan
>>>>>>>>>>>> committers
>>>>>>>>>>>> for this
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> process.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>>>> [2]
>>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>>>> [3]
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> [4]
>>>>>>>>>>>>
>>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>>
>>>>>>>>>>>> summary.html
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Michael Glavassevich
>>>>>>>>>>> XML Parser Development
>>>>>>>>>>> IBM Toronto Lab
>>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>>>
>>>>>>
>>>>>> Michael Glavassevich
>>>>>> XML Parser Development
>>>>>> IBM Toronto Lab
>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>> E-mail: mrglavas@apache.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.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
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.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
xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3
Sources to Apache]
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
xml-commons has been upgraded to JAXP 1.3 APIs.
If anyone could try and confirm that would be great.
- Neeraj
Neeraj Bajaj wrote:
> I tagged xml-commons module yesterday with tag name
> '*before-jaxp13-upgradation*'.
>
> I plan to do the following but i will wait till tomorrow so as to give
> chance to the community
> to correct me if i am doing something wrong.
>
> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
> xml-commons/java/external/src directory
> with JAXP 1.3 API sources.
>
> Currently in xml-commons there are sources like org.w3c.dom.views.*
> which are not part of JAXP 1.3
> I won't remove those sources. they will be as it is.
>
> * Make changes in xml-commons/java/external/build.xml file so as to
> upgrade
> JAXP 1.1 --> JAXP 1.3
> DOM2 --> DOM3
> SAX2 --> (SAX) 2.0.2 (sax2r3)
>
> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
> available as xml-apis.jar.
>
> Anything else i should take care ?
>
> - Neeraj
>
>
> Neeraj Bajaj wrote:
>
>> Geir, I have uploaded sources at the same location
>> (xml-commons/contrib/jaxp13)
>> with Apache 2.0 license on every source file.
>>
>> - Neeraj
>>
>> Neeraj Bajaj wrote:
>>
>>> Ok, So i will add it and upload again.
>>>
>>> - Neeraj
>>>
>>> Geir Magnusson Jr. wrote:
>>>
>>>>
>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>>
>>>>> Hi Neeraj,
>>>>>
>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>>>> license. Will this still be the case for JAXP 1.3?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> yes - these files must be available under the apache license v2.
>>>> And the license grantor should be the one that adds it.
>>>>
>>>> Sorry Neeraj :)
>>>>
>>>> geir
>>>>
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>>
>>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
>>>>>> xalan-src.zip which
>>>>>> corresponds to jaxp-api,
>>>>>> xerces & xalan sources respectively.
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Neeraj Bajaj wrote:
>>>>>>
>>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>>> I will send mail to the community when i am done.
>>>>>>>
>>>>>>> Thanks dims for the suggestion.
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Davanum Srinivas wrote:
>>>>>>>
>>>>>>>> Neeraj,
>>>>>>>>
>>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>>> xml-commons/contrib/jaxp13
>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>>> tagging the current code in the main trunk there) and it's upto
>>>>>>>> the
>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>> dims
>>>>>>>>
>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Thanks Michael for your response.
>>>>>>>>>
>>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>>> start
>>>>>>>>> work
>>>>>>>>> on this ?
>>>>>>>>> Does anyone has an opinion, Is there any other list where i
>>>>>>>>> should
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> send
>>>>>
>>>>>>>>> this mail
>>>>>>>>> before making changes ?
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hi Neeraj,
>>>>>>>>>>
>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>> and
>>>>>
>>>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>>>> trunk.
>>>>>>>>>>
>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
>>>>>>>>>> other
>>>>>>>>>> updates
>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
>>>>>>>>>> branch we've
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>>> used
>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>>>> assume a
>>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>>
>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>> AM:
>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
>>>>>>>>>>> attached as
>>>>>>>>>>> zip but
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>>
>>>>>>>>>>> <error>
>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>>> </error>
>>>>>>>>>>>
>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>>> Apache
>>>>>>>>>>> server somewhere ?
>>>>>>>>>>> Can anyone guide me what is the procedure for such code
>>>>>>>>>>> grants ?
>>>>>>>>>>>
>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>>> community
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> to help put it in a
>>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>>> number of
>>>>>>>>>>> changes it would be a considerable
>>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>>> community to
>>>>>>>>>>> have a
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> look at the code before
>>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>>
>>>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>>>> sources
>>>>>>>>>>> in xml-commons branch
>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>>> What is
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> the
>>>>>
>>>>>>>>>>> opinion of community ? I can
>>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>>> preference is to put the sources on
>>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>>
>>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>>>> functionalities.
>>>>>>>>>>>
>>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>>> * Reuse parser instance
>>>>>>>>>>> * Security enhancements
>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>>> Save, SAX
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>>
>>>>>>>>>>> Due to large size of code base i will be sending different
>>>>>>>>>>> mails
>>>>>>>>>>> for the
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>>
>>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>>> process of
>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>>>> Xalan.
>>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>>> and we can discuss more about the technicalities of merging
>>>>>>>>>>> with
>>>>>>>>>>> in the
>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>>> community.
>>>>>>>>>>>
>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
>>>>>>>>>>>>>> up the
>>>>>>>>>>>>>> ball
>>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>>> presume that
>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>>> achieved.
>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>>> process
>>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> ----------------------------------------------------------------------
>>>>>> --
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Subject:
>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>>> From:
>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>>> Date:
>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>>
>>>>>>>>>>> To:
>>>>>>>>>>> general@xml.apache.org
>>>>>>>>>>> CC:
>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> <Je...@Sun.COM>,
>>>>>
>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>>> final. JAXP
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>>> representation
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> of
>>>>>
>>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> thus
>>>>>
>>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> language
>>>>>
>>>>>>>>>>> provides a simple, concise syntax for accessing individual
>>>>>>>>>>> parts
>>>>>>>>>>> of an
>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>>> access to
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>>> the
>>>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>>> Datatypes to
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>>> 1.3 also
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>>> adds
>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> allowing
>>>>>
>>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> performance.
>>>>>
>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>>>> L/S, XML
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>>
>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
>>>>>>>>>>> (API s +
>>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> (Reference
>>>>>
>>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
>>>>>>>>>>> of newly
>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>>> Transformer
>>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>>> XInclude
>>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>>> JAXP 1.3
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> RI
>>>>>
>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>>>> Xerces
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> or
>>>>>
>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>>> Xerces &
>>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>>
>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>>> set of
>>>>>>>>>>> APIs
>>>>>>>>>>> are used by many different projects.
>>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>>> emerging, we
>>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons
>>>>>>>>>>> main
>>>>>>>>>>> trunk
>>>>>>>>>>> and apply a tag.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>> part of
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Xerces)*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>>
>>>>>>>>>>> javax.xml.datatype
>>>>>>>>>>> javax.xml.validation
>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>>
>>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>>
>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
>>>>>>>>>>> changes
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> into
>>>>>
>>>>>>>>>>> that branch. This will help
>>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> before
>>>>>
>>>>>>>>>>> these changes being finally
>>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>>> changes to
>>>>>>>>>>> the branch and then committing
>>>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>> part of
>>>>>>>>>>> Xalan)*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
>>>>>>>>>>> XPath
>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> changes
>>>>>
>>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>>> for ex. now application can use the same Transformer
>>>>>>>>>>> instance by
>>>>>>>>>>> invoking reset().
>>>>>>>>>>>
>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>>>> branch
>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>>> have a
>>>>>>>>>>> chance
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>>>> for this
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> process.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>>> [2]
>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>>> [3]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> [4]
>>>>>>>>>>>
>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>
>>>>>>>>>>> summary.html
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Michael Glavassevich
>>>>>>>>>> XML Parser Development
>>>>>>>>>> IBM Toronto Lab
>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>>
>>>>>
>>>>> Michael Glavassevich
>>>>> XML Parser Development
>>>>> IBM Toronto Lab
>>>>> E-mail: mrglavas@ca.ibm.com
>>>>> E-mail: mrglavas@apache.org
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.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
>
xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3
Sources to Apache]
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
xml-commons has been upgraded to JAXP 1.3 APIs.
If anyone could try and confirm that would be great.
- Neeraj
Neeraj Bajaj wrote:
> I tagged xml-commons module yesterday with tag name
> '*before-jaxp13-upgradation*'.
>
> I plan to do the following but i will wait till tomorrow so as to give
> chance to the community
> to correct me if i am doing something wrong.
>
> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
> xml-commons/java/external/src directory
> with JAXP 1.3 API sources.
>
> Currently in xml-commons there are sources like org.w3c.dom.views.*
> which are not part of JAXP 1.3
> I won't remove those sources. they will be as it is.
>
> * Make changes in xml-commons/java/external/build.xml file so as to
> upgrade
> JAXP 1.1 --> JAXP 1.3
> DOM2 --> DOM3
> SAX2 --> (SAX) 2.0.2 (sax2r3)
>
> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
> available as xml-apis.jar.
>
> Anything else i should take care ?
>
> - Neeraj
>
>
> Neeraj Bajaj wrote:
>
>> Geir, I have uploaded sources at the same location
>> (xml-commons/contrib/jaxp13)
>> with Apache 2.0 license on every source file.
>>
>> - Neeraj
>>
>> Neeraj Bajaj wrote:
>>
>>> Ok, So i will add it and upload again.
>>>
>>> - Neeraj
>>>
>>> Geir Magnusson Jr. wrote:
>>>
>>>>
>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>>
>>>>> Hi Neeraj,
>>>>>
>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>>>> license. Will this still be the case for JAXP 1.3?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> yes - these files must be available under the apache license v2.
>>>> And the license grantor should be the one that adds it.
>>>>
>>>> Sorry Neeraj :)
>>>>
>>>> geir
>>>>
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>>
>>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
>>>>>> xalan-src.zip which
>>>>>> corresponds to jaxp-api,
>>>>>> xerces & xalan sources respectively.
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Neeraj Bajaj wrote:
>>>>>>
>>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>>> I will send mail to the community when i am done.
>>>>>>>
>>>>>>> Thanks dims for the suggestion.
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Davanum Srinivas wrote:
>>>>>>>
>>>>>>>> Neeraj,
>>>>>>>>
>>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>>> xml-commons/contrib/jaxp13
>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>>> tagging the current code in the main trunk there) and it's upto
>>>>>>>> the
>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>> dims
>>>>>>>>
>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Thanks Michael for your response.
>>>>>>>>>
>>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>>> start
>>>>>>>>> work
>>>>>>>>> on this ?
>>>>>>>>> Does anyone has an opinion, Is there any other list where i
>>>>>>>>> should
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> send
>>>>>
>>>>>>>>> this mail
>>>>>>>>> before making changes ?
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hi Neeraj,
>>>>>>>>>>
>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>> and
>>>>>
>>>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>>>> trunk.
>>>>>>>>>>
>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
>>>>>>>>>> other
>>>>>>>>>> updates
>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
>>>>>>>>>> branch we've
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>>> used
>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>>>> assume a
>>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>>
>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>> AM:
>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
>>>>>>>>>>> attached as
>>>>>>>>>>> zip but
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>>
>>>>>>>>>>> <error>
>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>>> </error>
>>>>>>>>>>>
>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>>> Apache
>>>>>>>>>>> server somewhere ?
>>>>>>>>>>> Can anyone guide me what is the procedure for such code
>>>>>>>>>>> grants ?
>>>>>>>>>>>
>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>>> community
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> to help put it in a
>>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>>> number of
>>>>>>>>>>> changes it would be a considerable
>>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>>> community to
>>>>>>>>>>> have a
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> look at the code before
>>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>>
>>>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>>>> sources
>>>>>>>>>>> in xml-commons branch
>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>>> What is
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> the
>>>>>
>>>>>>>>>>> opinion of community ? I can
>>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>>> preference is to put the sources on
>>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>>
>>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>>>> functionalities.
>>>>>>>>>>>
>>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>>> * Reuse parser instance
>>>>>>>>>>> * Security enhancements
>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>>> Save, SAX
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>>
>>>>>>>>>>> Due to large size of code base i will be sending different
>>>>>>>>>>> mails
>>>>>>>>>>> for the
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>>
>>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>>> process of
>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>>>> Xalan.
>>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>>> and we can discuss more about the technicalities of merging
>>>>>>>>>>> with
>>>>>>>>>>> in the
>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>>> community.
>>>>>>>>>>>
>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
>>>>>>>>>>>>>> up the
>>>>>>>>>>>>>> ball
>>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>>> presume that
>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>>> achieved.
>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>>> process
>>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> ----------------------------------------------------------------------
>>>>>> --
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Subject:
>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>>> From:
>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>>> Date:
>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>>
>>>>>>>>>>> To:
>>>>>>>>>>> general@xml.apache.org
>>>>>>>>>>> CC:
>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> <Je...@Sun.COM>,
>>>>>
>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>>> final. JAXP
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>>> representation
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> of
>>>>>
>>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> thus
>>>>>
>>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> language
>>>>>
>>>>>>>>>>> provides a simple, concise syntax for accessing individual
>>>>>>>>>>> parts
>>>>>>>>>>> of an
>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>>> access to
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>>> the
>>>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>>> Datatypes to
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>>> 1.3 also
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>>> adds
>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> allowing
>>>>>
>>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> performance.
>>>>>
>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>>>> L/S, XML
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>>
>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
>>>>>>>>>>> (API s +
>>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> (Reference
>>>>>
>>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
>>>>>>>>>>> of newly
>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>>> Transformer
>>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>>> XInclude
>>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>>> JAXP 1.3
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> RI
>>>>>
>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>>>> Xerces
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> or
>>>>>
>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>>> Xerces &
>>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>>
>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>>> set of
>>>>>>>>>>> APIs
>>>>>>>>>>> are used by many different projects.
>>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>>> emerging, we
>>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons
>>>>>>>>>>> main
>>>>>>>>>>> trunk
>>>>>>>>>>> and apply a tag.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>> part of
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Xerces)*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>>
>>>>>>>>>>> javax.xml.datatype
>>>>>>>>>>> javax.xml.validation
>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>>
>>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>>
>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
>>>>>>>>>>> changes
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> into
>>>>>
>>>>>>>>>>> that branch. This will help
>>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> before
>>>>>
>>>>>>>>>>> these changes being finally
>>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>>> changes to
>>>>>>>>>>> the branch and then committing
>>>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>> part of
>>>>>>>>>>> Xalan)*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
>>>>>>>>>>> XPath
>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> changes
>>>>>
>>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>>> for ex. now application can use the same Transformer
>>>>>>>>>>> instance by
>>>>>>>>>>> invoking reset().
>>>>>>>>>>>
>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>>>> branch
>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>>> have a
>>>>>>>>>>> chance
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>>>> for this
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> process.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>>> [2]
>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>>> [3]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> [4]
>>>>>>>>>>>
>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>
>>>>>>>>>>> summary.html
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Michael Glavassevich
>>>>>>>>>> XML Parser Development
>>>>>>>>>> IBM Toronto Lab
>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>>
>>>>>
>>>>> Michael Glavassevich
>>>>> XML Parser Development
>>>>> IBM Toronto Lab
>>>>> E-mail: mrglavas@ca.ibm.com
>>>>> E-mail: mrglavas@apache.org
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3
Sources to Apache]
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
xml-commons has been upgraded to JAXP 1.3 APIs.
If anyone could try and confirm that would be great.
- Neeraj
Neeraj Bajaj wrote:
> I tagged xml-commons module yesterday with tag name
> '*before-jaxp13-upgradation*'.
>
> I plan to do the following but i will wait till tomorrow so as to give
> chance to the community
> to correct me if i am doing something wrong.
>
> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
> xml-commons/java/external/src directory
> with JAXP 1.3 API sources.
>
> Currently in xml-commons there are sources like org.w3c.dom.views.*
> which are not part of JAXP 1.3
> I won't remove those sources. they will be as it is.
>
> * Make changes in xml-commons/java/external/build.xml file so as to
> upgrade
> JAXP 1.1 --> JAXP 1.3
> DOM2 --> DOM3
> SAX2 --> (SAX) 2.0.2 (sax2r3)
>
> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
> available as xml-apis.jar.
>
> Anything else i should take care ?
>
> - Neeraj
>
>
> Neeraj Bajaj wrote:
>
>> Geir, I have uploaded sources at the same location
>> (xml-commons/contrib/jaxp13)
>> with Apache 2.0 license on every source file.
>>
>> - Neeraj
>>
>> Neeraj Bajaj wrote:
>>
>>> Ok, So i will add it and upload again.
>>>
>>> - Neeraj
>>>
>>> Geir Magnusson Jr. wrote:
>>>
>>>>
>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>>
>>>>> Hi Neeraj,
>>>>>
>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>>>> license. Will this still be the case for JAXP 1.3?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> yes - these files must be available under the apache license v2.
>>>> And the license grantor should be the one that adds it.
>>>>
>>>> Sorry Neeraj :)
>>>>
>>>> geir
>>>>
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>>
>>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
>>>>>> xalan-src.zip which
>>>>>> corresponds to jaxp-api,
>>>>>> xerces & xalan sources respectively.
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Neeraj Bajaj wrote:
>>>>>>
>>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>>> I will send mail to the community when i am done.
>>>>>>>
>>>>>>> Thanks dims for the suggestion.
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Davanum Srinivas wrote:
>>>>>>>
>>>>>>>> Neeraj,
>>>>>>>>
>>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>>> xml-commons/contrib/jaxp13
>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>>> tagging the current code in the main trunk there) and it's upto
>>>>>>>> the
>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>> dims
>>>>>>>>
>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Thanks Michael for your response.
>>>>>>>>>
>>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>>> start
>>>>>>>>> work
>>>>>>>>> on this ?
>>>>>>>>> Does anyone has an opinion, Is there any other list where i
>>>>>>>>> should
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> send
>>>>>
>>>>>>>>> this mail
>>>>>>>>> before making changes ?
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hi Neeraj,
>>>>>>>>>>
>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>> and
>>>>>
>>>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>>>> trunk.
>>>>>>>>>>
>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
>>>>>>>>>> other
>>>>>>>>>> updates
>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
>>>>>>>>>> branch we've
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>>> used
>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>>>> assume a
>>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>>
>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>> AM:
>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
>>>>>>>>>>> attached as
>>>>>>>>>>> zip but
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>>
>>>>>>>>>>> <error>
>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>>> </error>
>>>>>>>>>>>
>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>>> Apache
>>>>>>>>>>> server somewhere ?
>>>>>>>>>>> Can anyone guide me what is the procedure for such code
>>>>>>>>>>> grants ?
>>>>>>>>>>>
>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>>> community
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> to help put it in a
>>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>>> number of
>>>>>>>>>>> changes it would be a considerable
>>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>>> community to
>>>>>>>>>>> have a
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> look at the code before
>>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>>
>>>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>>>> sources
>>>>>>>>>>> in xml-commons branch
>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>>> What is
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> the
>>>>>
>>>>>>>>>>> opinion of community ? I can
>>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>>> preference is to put the sources on
>>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>>
>>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>>>> functionalities.
>>>>>>>>>>>
>>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>>> * Reuse parser instance
>>>>>>>>>>> * Security enhancements
>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>>> Save, SAX
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>>
>>>>>>>>>>> Due to large size of code base i will be sending different
>>>>>>>>>>> mails
>>>>>>>>>>> for the
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>>
>>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>>> process of
>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>>>> Xalan.
>>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>>> and we can discuss more about the technicalities of merging
>>>>>>>>>>> with
>>>>>>>>>>> in the
>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>>> community.
>>>>>>>>>>>
>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
>>>>>>>>>>>>>> up the
>>>>>>>>>>>>>> ball
>>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>>> presume that
>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>>> achieved.
>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>>> process
>>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> ----------------------------------------------------------------------
>>>>>> --
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Subject:
>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>>> From:
>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>>> Date:
>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>>
>>>>>>>>>>> To:
>>>>>>>>>>> general@xml.apache.org
>>>>>>>>>>> CC:
>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> <Je...@Sun.COM>,
>>>>>
>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>>> final. JAXP
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>>> representation
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> of
>>>>>
>>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> thus
>>>>>
>>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> language
>>>>>
>>>>>>>>>>> provides a simple, concise syntax for accessing individual
>>>>>>>>>>> parts
>>>>>>>>>>> of an
>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>>> access to
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>>> the
>>>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>>> Datatypes to
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>>> 1.3 also
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>>> adds
>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> allowing
>>>>>
>>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> performance.
>>>>>
>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>>>> L/S, XML
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>>
>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
>>>>>>>>>>> (API s +
>>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> (Reference
>>>>>
>>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
>>>>>>>>>>> of newly
>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>>> Transformer
>>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>>> XInclude
>>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>>> JAXP 1.3
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> RI
>>>>>
>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>>>> Xerces
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> or
>>>>>
>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>>> Xerces &
>>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>>
>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>>> set of
>>>>>>>>>>> APIs
>>>>>>>>>>> are used by many different projects.
>>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>>> emerging, we
>>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons
>>>>>>>>>>> main
>>>>>>>>>>> trunk
>>>>>>>>>>> and apply a tag.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>> part of
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Xerces)*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>>
>>>>>>>>>>> javax.xml.datatype
>>>>>>>>>>> javax.xml.validation
>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>>
>>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>>
>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
>>>>>>>>>>> changes
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> into
>>>>>
>>>>>>>>>>> that branch. This will help
>>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> before
>>>>>
>>>>>>>>>>> these changes being finally
>>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>>> changes to
>>>>>>>>>>> the branch and then committing
>>>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>> part of
>>>>>>>>>>> Xalan)*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
>>>>>>>>>>> XPath
>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> changes
>>>>>
>>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>>> for ex. now application can use the same Transformer
>>>>>>>>>>> instance by
>>>>>>>>>>> invoking reset().
>>>>>>>>>>>
>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>>>> branch
>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>>> have a
>>>>>>>>>>> chance
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>>>> for this
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> process.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>>> [2]
>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>>> [3]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> [4]
>>>>>>>>>>>
>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>
>>>>>>>>>>> summary.html
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Michael Glavassevich
>>>>>>>>>> XML Parser Development
>>>>>>>>>> IBM Toronto Lab
>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>>
>>>>>
>>>>> Michael Glavassevich
>>>>> XML Parser Development
>>>>> IBM Toronto Lab
>>>>> E-mail: mrglavas@ca.ibm.com
>>>>> E-mail: mrglavas@apache.org
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3
Sources to Apache]
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
xml-commons has been upgraded to JAXP 1.3 APIs.
If anyone could try and confirm that would be great.
- Neeraj
Neeraj Bajaj wrote:
> I tagged xml-commons module yesterday with tag name
> '*before-jaxp13-upgradation*'.
>
> I plan to do the following but i will wait till tomorrow so as to give
> chance to the community
> to correct me if i am doing something wrong.
>
> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
> xml-commons/java/external/src directory
> with JAXP 1.3 API sources.
>
> Currently in xml-commons there are sources like org.w3c.dom.views.*
> which are not part of JAXP 1.3
> I won't remove those sources. they will be as it is.
>
> * Make changes in xml-commons/java/external/build.xml file so as to
> upgrade
> JAXP 1.1 --> JAXP 1.3
> DOM2 --> DOM3
> SAX2 --> (SAX) 2.0.2 (sax2r3)
>
> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
> available as xml-apis.jar.
>
> Anything else i should take care ?
>
> - Neeraj
>
>
> Neeraj Bajaj wrote:
>
>> Geir, I have uploaded sources at the same location
>> (xml-commons/contrib/jaxp13)
>> with Apache 2.0 license on every source file.
>>
>> - Neeraj
>>
>> Neeraj Bajaj wrote:
>>
>>> Ok, So i will add it and upload again.
>>>
>>> - Neeraj
>>>
>>> Geir Magnusson Jr. wrote:
>>>
>>>>
>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>>
>>>>> Hi Neeraj,
>>>>>
>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>>>> license. Will this still be the case for JAXP 1.3?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> yes - these files must be available under the apache license v2.
>>>> And the license grantor should be the one that adds it.
>>>>
>>>> Sorry Neeraj :)
>>>>
>>>> geir
>>>>
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>>
>>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
>>>>>> xalan-src.zip which
>>>>>> corresponds to jaxp-api,
>>>>>> xerces & xalan sources respectively.
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Neeraj Bajaj wrote:
>>>>>>
>>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>>> I will send mail to the community when i am done.
>>>>>>>
>>>>>>> Thanks dims for the suggestion.
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Davanum Srinivas wrote:
>>>>>>>
>>>>>>>> Neeraj,
>>>>>>>>
>>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>>> xml-commons/contrib/jaxp13
>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>>> tagging the current code in the main trunk there) and it's upto
>>>>>>>> the
>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>> dims
>>>>>>>>
>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Thanks Michael for your response.
>>>>>>>>>
>>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>>> start
>>>>>>>>> work
>>>>>>>>> on this ?
>>>>>>>>> Does anyone has an opinion, Is there any other list where i
>>>>>>>>> should
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> send
>>>>>
>>>>>>>>> this mail
>>>>>>>>> before making changes ?
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hi Neeraj,
>>>>>>>>>>
>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>> and
>>>>>
>>>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>>>> trunk.
>>>>>>>>>>
>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
>>>>>>>>>> other
>>>>>>>>>> updates
>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
>>>>>>>>>> branch we've
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>>> used
>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>>>> assume a
>>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>>
>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>> AM:
>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
>>>>>>>>>>> attached as
>>>>>>>>>>> zip but
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>>
>>>>>>>>>>> <error>
>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>>> </error>
>>>>>>>>>>>
>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>>> Apache
>>>>>>>>>>> server somewhere ?
>>>>>>>>>>> Can anyone guide me what is the procedure for such code
>>>>>>>>>>> grants ?
>>>>>>>>>>>
>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>>> community
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> to help put it in a
>>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>>> number of
>>>>>>>>>>> changes it would be a considerable
>>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>>> community to
>>>>>>>>>>> have a
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> look at the code before
>>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>>
>>>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>>>> sources
>>>>>>>>>>> in xml-commons branch
>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>>> What is
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> the
>>>>>
>>>>>>>>>>> opinion of community ? I can
>>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>>> preference is to put the sources on
>>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>>
>>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>>>> functionalities.
>>>>>>>>>>>
>>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>>> * Reuse parser instance
>>>>>>>>>>> * Security enhancements
>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>>> Save, SAX
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>>
>>>>>>>>>>> Due to large size of code base i will be sending different
>>>>>>>>>>> mails
>>>>>>>>>>> for the
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>>
>>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>>> process of
>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>>>> Xalan.
>>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>>> and we can discuss more about the technicalities of merging
>>>>>>>>>>> with
>>>>>>>>>>> in the
>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>>> community.
>>>>>>>>>>>
>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
>>>>>>>>>>>>>> up the
>>>>>>>>>>>>>> ball
>>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>>> presume that
>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>>> achieved.
>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>>> process
>>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> ----------------------------------------------------------------------
>>>>>> --
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Subject:
>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>>> From:
>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>>> Date:
>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>>
>>>>>>>>>>> To:
>>>>>>>>>>> general@xml.apache.org
>>>>>>>>>>> CC:
>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> <Je...@Sun.COM>,
>>>>>
>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>>> final. JAXP
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>>> representation
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> of
>>>>>
>>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> thus
>>>>>
>>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> language
>>>>>
>>>>>>>>>>> provides a simple, concise syntax for accessing individual
>>>>>>>>>>> parts
>>>>>>>>>>> of an
>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>>> access to
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>>> the
>>>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>>> Datatypes to
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>>> 1.3 also
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>>> adds
>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> allowing
>>>>>
>>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> performance.
>>>>>
>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>>>> L/S, XML
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>>
>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
>>>>>>>>>>> (API s +
>>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> (Reference
>>>>>
>>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
>>>>>>>>>>> of newly
>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>>> Transformer
>>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>>> XInclude
>>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>>> JAXP 1.3
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> RI
>>>>>
>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>>>> Xerces
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> or
>>>>>
>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>>> Xerces &
>>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>>
>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>>> set of
>>>>>>>>>>> APIs
>>>>>>>>>>> are used by many different projects.
>>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>>> emerging, we
>>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons
>>>>>>>>>>> main
>>>>>>>>>>> trunk
>>>>>>>>>>> and apply a tag.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>> part of
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Xerces)*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>>
>>>>>>>>>>> javax.xml.datatype
>>>>>>>>>>> javax.xml.validation
>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>>
>>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>>
>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
>>>>>>>>>>> changes
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> into
>>>>>
>>>>>>>>>>> that branch. This will help
>>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> before
>>>>>
>>>>>>>>>>> these changes being finally
>>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>>> changes to
>>>>>>>>>>> the branch and then committing
>>>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>> part of
>>>>>>>>>>> Xalan)*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
>>>>>>>>>>> XPath
>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> changes
>>>>>
>>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>>> for ex. now application can use the same Transformer
>>>>>>>>>>> instance by
>>>>>>>>>>> invoking reset().
>>>>>>>>>>>
>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>>>> branch
>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>>> have a
>>>>>>>>>>> chance
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>>>> for this
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> process.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>>> [2]
>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>>> [3]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> [4]
>>>>>>>>>>>
>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>
>>>>>>>>>>> summary.html
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Michael Glavassevich
>>>>>>>>>> XML Parser Development
>>>>>>>>>> IBM Toronto Lab
>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>>
>>>>>
>>>>> Michael Glavassevich
>>>>> XML Parser Development
>>>>> IBM Toronto Lab
>>>>> E-mail: mrglavas@ca.ibm.com
>>>>> E-mail: mrglavas@apache.org
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
xml-commons upgradation to JAXP 1.3 complete [Re: Donation of JAXP 1.3
Sources to Apache]
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
xml-commons has been upgraded to JAXP 1.3 APIs.
If anyone could try and confirm that would be great.
- Neeraj
Neeraj Bajaj wrote:
> I tagged xml-commons module yesterday with tag name
> '*before-jaxp13-upgradation*'.
>
> I plan to do the following but i will wait till tomorrow so as to give
> chance to the community
> to correct me if i am doing something wrong.
>
> * update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
> xml-commons/java/external/src directory
> with JAXP 1.3 API sources.
>
> Currently in xml-commons there are sources like org.w3c.dom.views.*
> which are not part of JAXP 1.3
> I won't remove those sources. they will be as it is.
>
> * Make changes in xml-commons/java/external/build.xml file so as to
> upgrade
> JAXP 1.1 --> JAXP 1.3
> DOM2 --> DOM3
> SAX2 --> (SAX) 2.0.2 (sax2r3)
>
> * Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
> available as xml-apis.jar.
>
> Anything else i should take care ?
>
> - Neeraj
>
>
> Neeraj Bajaj wrote:
>
>> Geir, I have uploaded sources at the same location
>> (xml-commons/contrib/jaxp13)
>> with Apache 2.0 license on every source file.
>>
>> - Neeraj
>>
>> Neeraj Bajaj wrote:
>>
>>> Ok, So i will add it and upload again.
>>>
>>> - Neeraj
>>>
>>> Geir Magnusson Jr. wrote:
>>>
>>>>
>>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>>
>>>>> Hi Neeraj,
>>>>>
>>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>>>> license. Will this still be the case for JAXP 1.3?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> yes - these files must be available under the apache license v2.
>>>> And the license grantor should be the one that adds it.
>>>>
>>>> Sorry Neeraj :)
>>>>
>>>> geir
>>>>
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>>
>>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip,
>>>>>> xalan-src.zip which
>>>>>> corresponds to jaxp-api,
>>>>>> xerces & xalan sources respectively.
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Neeraj Bajaj wrote:
>>>>>>
>>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>>> I will send mail to the community when i am done.
>>>>>>>
>>>>>>> Thanks dims for the suggestion.
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Davanum Srinivas wrote:
>>>>>>>
>>>>>>>> Neeraj,
>>>>>>>>
>>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>>> xml-commons/contrib/jaxp13
>>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>>> tagging the current code in the main trunk there) and it's upto
>>>>>>>> the
>>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>> dims
>>>>>>>>
>>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Thanks Michael for your response.
>>>>>>>>>
>>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>>> start
>>>>>>>>> work
>>>>>>>>> on this ?
>>>>>>>>> Does anyone has an opinion, Is there any other list where i
>>>>>>>>> should
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> send
>>>>>
>>>>>>>>> this mail
>>>>>>>>> before making changes ?
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hi Neeraj,
>>>>>>>>>>
>>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>> and
>>>>>
>>>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>>>> trunk.
>>>>>>>>>>
>>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and
>>>>>>>>>> other
>>>>>>>>>> updates
>>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the
>>>>>>>>>> branch we've
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>>>>>> used
>>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>>>> assume a
>>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>>
>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>> AM:
>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code
>>>>>>>>>>> attached as
>>>>>>>>>>> zip but
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>>
>>>>>>>>>>> <error>
>>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>>> </error>
>>>>>>>>>>>
>>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>>> Apache
>>>>>>>>>>> server somewhere ?
>>>>>>>>>>> Can anyone guide me what is the procedure for such code
>>>>>>>>>>> grants ?
>>>>>>>>>>>
>>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>>> community
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> to help put it in a
>>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>>> number of
>>>>>>>>>>> changes it would be a considerable
>>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>>> community to
>>>>>>>>>>> have a
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> look at the code before
>>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>>
>>>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>>>> sources
>>>>>>>>>>> in xml-commons branch
>>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>>> What is
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> the
>>>>>
>>>>>>>>>>> opinion of community ? I can
>>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>>> preference is to put the sources on
>>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>>
>>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>>>> functionalities.
>>>>>>>>>>>
>>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>>> * Reuse parser instance
>>>>>>>>>>> * Security enhancements
>>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>>> Save, SAX
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>>
>>>>>>>>>>> Due to large size of code base i will be sending different
>>>>>>>>>>> mails
>>>>>>>>>>> for the
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>>
>>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>>> process of
>>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>>>> Xalan.
>>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>>> and we can discuss more about the technicalities of merging
>>>>>>>>>>> with
>>>>>>>>>>> in the
>>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>>> community.
>>>>>>>>>>>
>>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking
>>>>>>>>>>>>>> up the
>>>>>>>>>>>>>> ball
>>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>>> presume that
>>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>>> achieved.
>>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>>> process
>>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>>
>>>>>>>>>>>> - Neeraj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> ----------------------------------------------------------------------
>>>>>> --
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Subject:
>>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>>> From:
>>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>>> Date:
>>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>>
>>>>>>>>>>> To:
>>>>>>>>>>> general@xml.apache.org
>>>>>>>>>>> CC:
>>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> <Je...@Sun.COM>,
>>>>>
>>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hello All,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>>> final. JAXP
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>>> representation
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> of
>>>>>
>>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> thus
>>>>>
>>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> language
>>>>>
>>>>>>>>>>> provides a simple, concise syntax for accessing individual
>>>>>>>>>>> parts
>>>>>>>>>>> of an
>>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>>> access to
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>>> the
>>>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>>> Datatypes to
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>>> 1.3 also
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>>>>>>>>> adds
>>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> allowing
>>>>>
>>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> performance.
>>>>>
>>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>>>> L/S, XML
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>>
>>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources
>>>>>>>>>>> (API s +
>>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> (Reference
>>>>>
>>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation
>>>>>>>>>>> of newly
>>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>>> Transformer
>>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>>> XInclude
>>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>>> JAXP 1.3
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> RI
>>>>>
>>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>>>> Xerces
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> or
>>>>>
>>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>>> Xerces &
>>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>>
>>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>>> set of
>>>>>>>>>>> APIs
>>>>>>>>>>> are used by many different projects.
>>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>>> emerging, we
>>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons
>>>>>>>>>>> main
>>>>>>>>>>> trunk
>>>>>>>>>>> and apply a tag.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>> part of
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Xerces)*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>>
>>>>>>>>>>> javax.xml.datatype
>>>>>>>>>>> javax.xml.validation
>>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>>
>>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>>
>>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI
>>>>>>>>>>> changes
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> into
>>>>>
>>>>>>>>>>> that branch. This will help
>>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> before
>>>>>
>>>>>>>>>>> these changes being finally
>>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>>> changes to
>>>>>>>>>>> the branch and then committing
>>>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be
>>>>>>>>>>> part of
>>>>>>>>>>> Xalan)*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed
>>>>>>>>>>> XPath
>>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> changes
>>>>>
>>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>>> for ex. now application can use the same Transformer
>>>>>>>>>>> instance by
>>>>>>>>>>> invoking reset().
>>>>>>>>>>>
>>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>>>> branch
>>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>>> have a
>>>>>>>>>>> chance
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>>>> for this
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> process.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>>> [2]
>>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>>> [3]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> [4]
>>>>>>>>>>>
>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>
>>>>>>>>>>> summary.html
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Michael Glavassevich
>>>>>>>>>> XML Parser Development
>>>>>>>>>> IBM Toronto Lab
>>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>
>>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>>
>>>>>
>>>>> Michael Glavassevich
>>>>> XML Parser Development
>>>>> IBM Toronto Lab
>>>>> E-mail: mrglavas@ca.ibm.com
>>>>> E-mail: mrglavas@apache.org
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
I tagged xml-commons module yesterday with tag name
'*before-jaxp13-upgradation*'.
I plan to do the following but i will wait till tomorrow so as to give
chance to the community
to correct me if i am doing something wrong.
* update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
xml-commons/java/external/src directory
with JAXP 1.3 API sources.
Currently in xml-commons there are sources like org.w3c.dom.views.*
which are not part of JAXP 1.3
I won't remove those sources. they will be as it is.
* Make changes in xml-commons/java/external/build.xml file so as to upgrade
JAXP 1.1 --> JAXP 1.3
DOM2 --> DOM3
SAX2 --> (SAX) 2.0.2 (sax2r3)
* Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
available as xml-apis.jar.
Anything else i should take care ?
- Neeraj
Neeraj Bajaj wrote:
> Geir, I have uploaded sources at the same location
> (xml-commons/contrib/jaxp13)
> with Apache 2.0 license on every source file.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
>> Ok, So i will add it and upload again.
>>
>> - Neeraj
>>
>> Geir Magnusson Jr. wrote:
>>
>>>
>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>
>>>> Hi Neeraj,
>>>>
>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>>> license. Will this still be the case for JAXP 1.3?
>>>
>>>
>>>
>>>
>>> yes - these files must be available under the apache license v2.
>>> And the license grantor should be the one that adds it.
>>>
>>> Sorry Neeraj :)
>>>
>>> geir
>>>
>>>>
>>>> Thanks.
>>>>
>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>
>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>>>> which
>>>>> corresponds to jaxp-api,
>>>>> xerces & xalan sources respectively.
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Neeraj Bajaj wrote:
>>>>>
>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>> I will send mail to the community when i am done.
>>>>>>
>>>>>> Thanks dims for the suggestion.
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Davanum Srinivas wrote:
>>>>>>
>>>>>>> Neeraj,
>>>>>>>
>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>> xml-commons/contrib/jaxp13
>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>>
>>>>>>> thanks,
>>>>>>> dims
>>>>>>>
>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Thanks Michael for your response.
>>>>>>>>
>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>> start
>>>>>>>> work
>>>>>>>> on this ?
>>>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>>>
>>>>>>>
>>>>>>>
>>>> send
>>>>
>>>>>>>> this mail
>>>>>>>> before making changes ?
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi Neeraj,
>>>>>>>>>
>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>> and
>>>>
>>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>>> trunk.
>>>>>>>>>
>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>>>> updates
>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>>>> we've
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>>>>>>>> used
>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>>> assume a
>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>
>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>> AM:
>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>>>> zip but
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>
>>>>>>>>>> <error>
>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>> </error>
>>>>>>>>>>
>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>> Apache
>>>>>>>>>> server somewhere ?
>>>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>>>
>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>> community
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> to help put it in a
>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>> number of
>>>>>>>>>> changes it would be a considerable
>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>> community to
>>>>>>>>>> have a
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> look at the code before
>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>
>>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>>> sources
>>>>>>>>>> in xml-commons branch
>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>> What is
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> the
>>>>
>>>>>>>>>> opinion of community ? I can
>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>> preference is to put the sources on
>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>
>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>>> functionalities.
>>>>>>>>>>
>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>> * Reuse parser instance
>>>>>>>>>> * Security enhancements
>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>> Save, SAX
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>
>>>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>>>> for the
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>
>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>> process of
>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>>> Xalan.
>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>>>> in the
>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>> community.
>>>>>>>>>>
>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up
>>>>>>>>>>>>> the
>>>>>>>>>>>>> ball
>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>> presume that
>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>> achieved.
>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>> process
>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> --
>>>>
>>>>
>>>>
>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Subject:
>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>> From:
>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>> Date:
>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>
>>>>>>>>>> To:
>>>>>>>>>> general@xml.apache.org
>>>>>>>>>> CC:
>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> <Je...@Sun.COM>,
>>>>
>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>> final. JAXP
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>> representation
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> of
>>>>
>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> thus
>>>>
>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> language
>>>>
>>>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>>>> of an
>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>> access to
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>>>>>>> the
>>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>> Datatypes to
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>> 1.3 also
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>>>>>>> adds
>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> allowing
>>>>
>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> performance.
>>>>
>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>>> L/S, XML
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>
>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API
>>>>>>>>>> s +
>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>
>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> (Reference
>>>>
>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>>>> newly
>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>> Transformer
>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>> XInclude
>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>> JAXP 1.3
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> RI
>>>>
>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>>> Xerces
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> or
>>>>
>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>> Xerces &
>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>
>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>> set of
>>>>>>>>>> APIs
>>>>>>>>>> are used by many different projects.
>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>> emerging, we
>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons
>>>>>>>>>> main
>>>>>>>>>> trunk
>>>>>>>>>> and apply a tag.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Xerces)*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>
>>>>>>>>>> javax.xml.datatype
>>>>>>>>>> javax.xml.validation
>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>
>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>
>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> into
>>>>
>>>>>>>>>> that branch. This will help
>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> before
>>>>
>>>>>>>>>> these changes being finally
>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>> changes to
>>>>>>>>>> the branch and then committing
>>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>> Xalan)*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> changes
>>>>
>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>>>> invoking reset().
>>>>>>>>>>
>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>>> branch
>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>> have a
>>>>>>>>>> chance
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>>> for this
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> process.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>> [2]
>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>> [3]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> [4]
>>>>>>>>>>
>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>
>>>>>>>>>> summary.html
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Michael Glavassevich
>>>>>>>>> XML Parser Development
>>>>>>>>> IBM Toronto Lab
>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>
>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>
>>>>
>>>> Michael Glavassevich
>>>> XML Parser Development
>>>> IBM Toronto Lab
>>>> E-mail: mrglavas@ca.ibm.com
>>>> E-mail: mrglavas@apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
I tagged xml-commons module yesterday with tag name
'*before-jaxp13-upgradation*'.
I plan to do the following but i will wait till tomorrow so as to give
chance to the community
to correct me if i am doing something wrong.
* update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
xml-commons/java/external/src directory
with JAXP 1.3 API sources.
Currently in xml-commons there are sources like org.w3c.dom.views.*
which are not part of JAXP 1.3
I won't remove those sources. they will be as it is.
* Make changes in xml-commons/java/external/build.xml file so as to upgrade
JAXP 1.1 --> JAXP 1.3
DOM2 --> DOM3
SAX2 --> (SAX) 2.0.2 (sax2r3)
* Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
available as xml-apis.jar.
Anything else i should take care ?
- Neeraj
Neeraj Bajaj wrote:
> Geir, I have uploaded sources at the same location
> (xml-commons/contrib/jaxp13)
> with Apache 2.0 license on every source file.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
>> Ok, So i will add it and upload again.
>>
>> - Neeraj
>>
>> Geir Magnusson Jr. wrote:
>>
>>>
>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>
>>>> Hi Neeraj,
>>>>
>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>>> license. Will this still be the case for JAXP 1.3?
>>>
>>>
>>>
>>>
>>> yes - these files must be available under the apache license v2.
>>> And the license grantor should be the one that adds it.
>>>
>>> Sorry Neeraj :)
>>>
>>> geir
>>>
>>>>
>>>> Thanks.
>>>>
>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>
>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>>>> which
>>>>> corresponds to jaxp-api,
>>>>> xerces & xalan sources respectively.
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Neeraj Bajaj wrote:
>>>>>
>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>> I will send mail to the community when i am done.
>>>>>>
>>>>>> Thanks dims for the suggestion.
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Davanum Srinivas wrote:
>>>>>>
>>>>>>> Neeraj,
>>>>>>>
>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>> xml-commons/contrib/jaxp13
>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>>
>>>>>>> thanks,
>>>>>>> dims
>>>>>>>
>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Thanks Michael for your response.
>>>>>>>>
>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>> start
>>>>>>>> work
>>>>>>>> on this ?
>>>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>>>
>>>>>>>
>>>>>>>
>>>> send
>>>>
>>>>>>>> this mail
>>>>>>>> before making changes ?
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi Neeraj,
>>>>>>>>>
>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>> and
>>>>
>>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>>> trunk.
>>>>>>>>>
>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>>>> updates
>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>>>> we've
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>>>>>>>> used
>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>>> assume a
>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>
>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>> AM:
>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>>>> zip but
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>
>>>>>>>>>> <error>
>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>> </error>
>>>>>>>>>>
>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>> Apache
>>>>>>>>>> server somewhere ?
>>>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>>>
>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>> community
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> to help put it in a
>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>> number of
>>>>>>>>>> changes it would be a considerable
>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>> community to
>>>>>>>>>> have a
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> look at the code before
>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>
>>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>>> sources
>>>>>>>>>> in xml-commons branch
>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>> What is
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> the
>>>>
>>>>>>>>>> opinion of community ? I can
>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>> preference is to put the sources on
>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>
>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>>> functionalities.
>>>>>>>>>>
>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>> * Reuse parser instance
>>>>>>>>>> * Security enhancements
>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>> Save, SAX
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>
>>>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>>>> for the
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>
>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>> process of
>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>>> Xalan.
>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>>>> in the
>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>> community.
>>>>>>>>>>
>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up
>>>>>>>>>>>>> the
>>>>>>>>>>>>> ball
>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>> presume that
>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>> achieved.
>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>> process
>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> --
>>>>
>>>>
>>>>
>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Subject:
>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>> From:
>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>> Date:
>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>
>>>>>>>>>> To:
>>>>>>>>>> general@xml.apache.org
>>>>>>>>>> CC:
>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> <Je...@Sun.COM>,
>>>>
>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>> final. JAXP
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>> representation
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> of
>>>>
>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> thus
>>>>
>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> language
>>>>
>>>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>>>> of an
>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>> access to
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>>>>>>> the
>>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>> Datatypes to
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>> 1.3 also
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>>>>>>> adds
>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> allowing
>>>>
>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> performance.
>>>>
>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>>> L/S, XML
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>
>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API
>>>>>>>>>> s +
>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>
>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> (Reference
>>>>
>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>>>> newly
>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>> Transformer
>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>> XInclude
>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>> JAXP 1.3
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> RI
>>>>
>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>>> Xerces
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> or
>>>>
>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>> Xerces &
>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>
>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>> set of
>>>>>>>>>> APIs
>>>>>>>>>> are used by many different projects.
>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>> emerging, we
>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons
>>>>>>>>>> main
>>>>>>>>>> trunk
>>>>>>>>>> and apply a tag.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Xerces)*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>
>>>>>>>>>> javax.xml.datatype
>>>>>>>>>> javax.xml.validation
>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>
>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>
>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> into
>>>>
>>>>>>>>>> that branch. This will help
>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> before
>>>>
>>>>>>>>>> these changes being finally
>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>> changes to
>>>>>>>>>> the branch and then committing
>>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>> Xalan)*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> changes
>>>>
>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>>>> invoking reset().
>>>>>>>>>>
>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>>> branch
>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>> have a
>>>>>>>>>> chance
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>>> for this
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> process.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>> [2]
>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>> [3]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> [4]
>>>>>>>>>>
>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>
>>>>>>>>>> summary.html
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Michael Glavassevich
>>>>>>>>> XML Parser Development
>>>>>>>>> IBM Toronto Lab
>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>
>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>
>>>>
>>>> Michael Glavassevich
>>>> XML Parser Development
>>>> IBM Toronto Lab
>>>> E-mail: mrglavas@ca.ibm.com
>>>> E-mail: mrglavas@apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
I tagged xml-commons module yesterday with tag name
'*before-jaxp13-upgradation*'.
I plan to do the following but i will wait till tomorrow so as to give
chance to the community
to correct me if i am doing something wrong.
* update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
xml-commons/java/external/src directory
with JAXP 1.3 API sources.
Currently in xml-commons there are sources like org.w3c.dom.views.*
which are not part of JAXP 1.3
I won't remove those sources. they will be as it is.
* Make changes in xml-commons/java/external/build.xml file so as to upgrade
JAXP 1.1 --> JAXP 1.3
DOM2 --> DOM3
SAX2 --> (SAX) 2.0.2 (sax2r3)
* Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
available as xml-apis.jar.
Anything else i should take care ?
- Neeraj
Neeraj Bajaj wrote:
> Geir, I have uploaded sources at the same location
> (xml-commons/contrib/jaxp13)
> with Apache 2.0 license on every source file.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
>> Ok, So i will add it and upload again.
>>
>> - Neeraj
>>
>> Geir Magnusson Jr. wrote:
>>
>>>
>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>
>>>> Hi Neeraj,
>>>>
>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>>> license. Will this still be the case for JAXP 1.3?
>>>
>>>
>>>
>>>
>>> yes - these files must be available under the apache license v2.
>>> And the license grantor should be the one that adds it.
>>>
>>> Sorry Neeraj :)
>>>
>>> geir
>>>
>>>>
>>>> Thanks.
>>>>
>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>
>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>>>> which
>>>>> corresponds to jaxp-api,
>>>>> xerces & xalan sources respectively.
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Neeraj Bajaj wrote:
>>>>>
>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>> I will send mail to the community when i am done.
>>>>>>
>>>>>> Thanks dims for the suggestion.
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Davanum Srinivas wrote:
>>>>>>
>>>>>>> Neeraj,
>>>>>>>
>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>> xml-commons/contrib/jaxp13
>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>>
>>>>>>> thanks,
>>>>>>> dims
>>>>>>>
>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Thanks Michael for your response.
>>>>>>>>
>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>> start
>>>>>>>> work
>>>>>>>> on this ?
>>>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>>>
>>>>>>>
>>>>>>>
>>>> send
>>>>
>>>>>>>> this mail
>>>>>>>> before making changes ?
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi Neeraj,
>>>>>>>>>
>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>> and
>>>>
>>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>>> trunk.
>>>>>>>>>
>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>>>> updates
>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>>>> we've
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>>>>>>>> used
>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>>> assume a
>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>
>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>> AM:
>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>>>> zip but
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>
>>>>>>>>>> <error>
>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>> </error>
>>>>>>>>>>
>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>> Apache
>>>>>>>>>> server somewhere ?
>>>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>>>
>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>> community
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> to help put it in a
>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>> number of
>>>>>>>>>> changes it would be a considerable
>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>> community to
>>>>>>>>>> have a
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> look at the code before
>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>
>>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>>> sources
>>>>>>>>>> in xml-commons branch
>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>> What is
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> the
>>>>
>>>>>>>>>> opinion of community ? I can
>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>> preference is to put the sources on
>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>
>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>>> functionalities.
>>>>>>>>>>
>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>> * Reuse parser instance
>>>>>>>>>> * Security enhancements
>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>> Save, SAX
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>
>>>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>>>> for the
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>
>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>> process of
>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>>> Xalan.
>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>>>> in the
>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>> community.
>>>>>>>>>>
>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up
>>>>>>>>>>>>> the
>>>>>>>>>>>>> ball
>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>> presume that
>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>> achieved.
>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>> process
>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> --
>>>>
>>>>
>>>>
>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Subject:
>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>> From:
>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>> Date:
>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>
>>>>>>>>>> To:
>>>>>>>>>> general@xml.apache.org
>>>>>>>>>> CC:
>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> <Je...@Sun.COM>,
>>>>
>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>> final. JAXP
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>> representation
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> of
>>>>
>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> thus
>>>>
>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> language
>>>>
>>>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>>>> of an
>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>> access to
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>>>>>>> the
>>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>> Datatypes to
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>> 1.3 also
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>>>>>>> adds
>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> allowing
>>>>
>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> performance.
>>>>
>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>>> L/S, XML
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>
>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API
>>>>>>>>>> s +
>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>
>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> (Reference
>>>>
>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>>>> newly
>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>> Transformer
>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>> XInclude
>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>> JAXP 1.3
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> RI
>>>>
>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>>> Xerces
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> or
>>>>
>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>> Xerces &
>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>
>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>> set of
>>>>>>>>>> APIs
>>>>>>>>>> are used by many different projects.
>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>> emerging, we
>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons
>>>>>>>>>> main
>>>>>>>>>> trunk
>>>>>>>>>> and apply a tag.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Xerces)*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>
>>>>>>>>>> javax.xml.datatype
>>>>>>>>>> javax.xml.validation
>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>
>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>
>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> into
>>>>
>>>>>>>>>> that branch. This will help
>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> before
>>>>
>>>>>>>>>> these changes being finally
>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>> changes to
>>>>>>>>>> the branch and then committing
>>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>> Xalan)*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> changes
>>>>
>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>>>> invoking reset().
>>>>>>>>>>
>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>>> branch
>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>> have a
>>>>>>>>>> chance
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>>> for this
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> process.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>> [2]
>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>> [3]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> [4]
>>>>>>>>>>
>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>
>>>>>>>>>> summary.html
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Michael Glavassevich
>>>>>>>>> XML Parser Development
>>>>>>>>> IBM Toronto Lab
>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>
>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>
>>>>
>>>> Michael Glavassevich
>>>> XML Parser Development
>>>> IBM Toronto Lab
>>>> E-mail: mrglavas@ca.ibm.com
>>>> E-mail: mrglavas@apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
I tagged xml-commons module yesterday with tag name
'*before-jaxp13-upgradation*'.
I plan to do the following but i will wait till tomorrow so as to give
chance to the community
to correct me if i am doing something wrong.
* update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
xml-commons/java/external/src directory
with JAXP 1.3 API sources.
Currently in xml-commons there are sources like org.w3c.dom.views.*
which are not part of JAXP 1.3
I won't remove those sources. they will be as it is.
* Make changes in xml-commons/java/external/build.xml file so as to upgrade
JAXP 1.1 --> JAXP 1.3
DOM2 --> DOM3
SAX2 --> (SAX) 2.0.2 (sax2r3)
* Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
available as xml-apis.jar.
Anything else i should take care ?
- Neeraj
Neeraj Bajaj wrote:
> Geir, I have uploaded sources at the same location
> (xml-commons/contrib/jaxp13)
> with Apache 2.0 license on every source file.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
>> Ok, So i will add it and upload again.
>>
>> - Neeraj
>>
>> Geir Magnusson Jr. wrote:
>>
>>>
>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>
>>>> Hi Neeraj,
>>>>
>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>>> license. Will this still be the case for JAXP 1.3?
>>>
>>>
>>>
>>>
>>> yes - these files must be available under the apache license v2.
>>> And the license grantor should be the one that adds it.
>>>
>>> Sorry Neeraj :)
>>>
>>> geir
>>>
>>>>
>>>> Thanks.
>>>>
>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>
>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>>>> which
>>>>> corresponds to jaxp-api,
>>>>> xerces & xalan sources respectively.
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Neeraj Bajaj wrote:
>>>>>
>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>> I will send mail to the community when i am done.
>>>>>>
>>>>>> Thanks dims for the suggestion.
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Davanum Srinivas wrote:
>>>>>>
>>>>>>> Neeraj,
>>>>>>>
>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>> xml-commons/contrib/jaxp13
>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>>
>>>>>>> thanks,
>>>>>>> dims
>>>>>>>
>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Thanks Michael for your response.
>>>>>>>>
>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>> start
>>>>>>>> work
>>>>>>>> on this ?
>>>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>>>
>>>>>>>
>>>>>>>
>>>> send
>>>>
>>>>>>>> this mail
>>>>>>>> before making changes ?
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi Neeraj,
>>>>>>>>>
>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>> and
>>>>
>>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>>> trunk.
>>>>>>>>>
>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>>>> updates
>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>>>> we've
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>>>>>>>> used
>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>>> assume a
>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>
>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>> AM:
>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>>>> zip but
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>
>>>>>>>>>> <error>
>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>> </error>
>>>>>>>>>>
>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>> Apache
>>>>>>>>>> server somewhere ?
>>>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>>>
>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>> community
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> to help put it in a
>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>> number of
>>>>>>>>>> changes it would be a considerable
>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>> community to
>>>>>>>>>> have a
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> look at the code before
>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>
>>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>>> sources
>>>>>>>>>> in xml-commons branch
>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>> What is
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> the
>>>>
>>>>>>>>>> opinion of community ? I can
>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>> preference is to put the sources on
>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>
>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>>> functionalities.
>>>>>>>>>>
>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>> * Reuse parser instance
>>>>>>>>>> * Security enhancements
>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>> Save, SAX
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>
>>>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>>>> for the
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>
>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>> process of
>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>>> Xalan.
>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>>>> in the
>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>> community.
>>>>>>>>>>
>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up
>>>>>>>>>>>>> the
>>>>>>>>>>>>> ball
>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>> presume that
>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>> achieved.
>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>> process
>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> --
>>>>
>>>>
>>>>
>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Subject:
>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>> From:
>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>> Date:
>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>
>>>>>>>>>> To:
>>>>>>>>>> general@xml.apache.org
>>>>>>>>>> CC:
>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> <Je...@Sun.COM>,
>>>>
>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>> final. JAXP
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>> representation
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> of
>>>>
>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> thus
>>>>
>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> language
>>>>
>>>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>>>> of an
>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>> access to
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>>>>>>> the
>>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>> Datatypes to
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>> 1.3 also
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>>>>>>> adds
>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> allowing
>>>>
>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> performance.
>>>>
>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>>> L/S, XML
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>
>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API
>>>>>>>>>> s +
>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>
>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> (Reference
>>>>
>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>>>> newly
>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>> Transformer
>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>> XInclude
>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>> JAXP 1.3
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> RI
>>>>
>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>>> Xerces
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> or
>>>>
>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>> Xerces &
>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>
>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>> set of
>>>>>>>>>> APIs
>>>>>>>>>> are used by many different projects.
>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>> emerging, we
>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons
>>>>>>>>>> main
>>>>>>>>>> trunk
>>>>>>>>>> and apply a tag.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Xerces)*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>
>>>>>>>>>> javax.xml.datatype
>>>>>>>>>> javax.xml.validation
>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>
>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>
>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> into
>>>>
>>>>>>>>>> that branch. This will help
>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> before
>>>>
>>>>>>>>>> these changes being finally
>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>> changes to
>>>>>>>>>> the branch and then committing
>>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>> Xalan)*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> changes
>>>>
>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>>>> invoking reset().
>>>>>>>>>>
>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>>> branch
>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>> have a
>>>>>>>>>> chance
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>>> for this
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> process.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>> [2]
>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>> [3]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> [4]
>>>>>>>>>>
>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>
>>>>>>>>>> summary.html
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Michael Glavassevich
>>>>>>>>> XML Parser Development
>>>>>>>>> IBM Toronto Lab
>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>
>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>
>>>>
>>>> Michael Glavassevich
>>>> XML Parser Development
>>>> IBM Toronto Lab
>>>> E-mail: mrglavas@ca.ibm.com
>>>> E-mail: mrglavas@apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
I tagged xml-commons module yesterday with tag name
'*before-jaxp13-upgradation*'.
I plan to do the following but i will wait till tomorrow so as to give
chance to the community
to correct me if i am doing something wrong.
* update javax.xml.*, org.xml.sax*, org.w3c.dom.* sources under
xml-commons/java/external/src directory
with JAXP 1.3 API sources.
Currently in xml-commons there are sources like org.w3c.dom.views.*
which are not part of JAXP 1.3
I won't remove those sources. they will be as it is.
* Make changes in xml-commons/java/external/build.xml file so as to upgrade
JAXP 1.1 --> JAXP 1.3
DOM2 --> DOM3
SAX2 --> (SAX) 2.0.2 (sax2r3)
* Make updated javax.xml.* , org.xml.sax.* , org.w3c.dom.* sources
available as xml-apis.jar.
Anything else i should take care ?
- Neeraj
Neeraj Bajaj wrote:
> Geir, I have uploaded sources at the same location
> (xml-commons/contrib/jaxp13)
> with Apache 2.0 license on every source file.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
>> Ok, So i will add it and upload again.
>>
>> - Neeraj
>>
>> Geir Magnusson Jr. wrote:
>>
>>>
>>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>>
>>>> Hi Neeraj,
>>>>
>>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>>> license. Will this still be the case for JAXP 1.3?
>>>
>>>
>>>
>>>
>>> yes - these files must be available under the apache license v2.
>>> And the license grantor should be the one that adds it.
>>>
>>> Sorry Neeraj :)
>>>
>>> geir
>>>
>>>>
>>>> Thanks.
>>>>
>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>>
>>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>>>> which
>>>>> corresponds to jaxp-api,
>>>>> xerces & xalan sources respectively.
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Neeraj Bajaj wrote:
>>>>>
>>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>>> I will send mail to the community when i am done.
>>>>>>
>>>>>> Thanks dims for the suggestion.
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Davanum Srinivas wrote:
>>>>>>
>>>>>>> Neeraj,
>>>>>>>
>>>>>>> my 2 cents...upload the whole thing say in
>>>>>>> xml-commons/contrib/jaxp13
>>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>>
>>>>>>> thanks,
>>>>>>> dims
>>>>>>>
>>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Thanks Michael for your response.
>>>>>>>>
>>>>>>>> I was just wondering what would be idle time to wait before i
>>>>>>>> start
>>>>>>>> work
>>>>>>>> on this ?
>>>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>>>
>>>>>>>
>>>>>>>
>>>> send
>>>>
>>>>>>>> this mail
>>>>>>>> before making changes ?
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>> Michael Glavassevich wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi Neeraj,
>>>>>>>>>
>>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>> and
>>>>
>>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>>> trunk.
>>>>>>>>>
>>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>>>> updates
>>>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>>>> we've
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>>>>>>>> used
>>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>>> assume a
>>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>>
>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>> AM:
>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>>>> zip but
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> mail bounced back with the following message
>>>>>>>>>>
>>>>>>>>>> <error>
>>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>>> </error>
>>>>>>>>>>
>>>>>>>>>> What should i do now ? Is there a way to upload sources on
>>>>>>>>>> Apache
>>>>>>>>>> server somewhere ?
>>>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>>>
>>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>>> community
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> to help put it in a
>>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>>> number of
>>>>>>>>>> changes it would be a considerable
>>>>>>>>>> amount of work. This will also help the committers &
>>>>>>>>>> community to
>>>>>>>>>> have a
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> look at the code before
>>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>>
>>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>>> sources
>>>>>>>>>> in xml-commons branch
>>>>>>>>>> or main trunk (and create branch for old jaxp sources ).
>>>>>>>>>> What is
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> the
>>>>
>>>>>>>>>> opinion of community ? I can
>>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>>> preference is to put the sources on
>>>>>>>>>> xml-commons main trunk.
>>>>>>>>>>
>>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>>> implementation to Apache XML.*
>>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>>> functionalities.
>>>>>>>>>>
>>>>>>>>>> * New Schema Validation Framework
>>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>>> * Reuse parser instance
>>>>>>>>>> * Security enhancements
>>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>>> Save, SAX
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>>
>>>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>>>> for the
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>>
>>>>>>>>>> I have attached the original mail where i proposed the
>>>>>>>>>> process of
>>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>>> Xalan.
>>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>>>> in the
>>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>>> community.
>>>>>>>>>>
>>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up
>>>>>>>>>>>>> the
>>>>>>>>>>>>> ball
>>>>>>>>>>>>> on this one.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I
>>>>>>>>>>>>> presume that
>>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>>> achieved.
>>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>>> process
>>>>>>>>>>>> hold things up.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>>
>>>>>>>>>>> - Neeraj
>>>>>>>>>>>
>>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> --
>>>>
>>>>
>>>>
>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Subject:
>>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>>> From:
>>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>>> Date:
>>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>>
>>>>>>>>>> To:
>>>>>>>>>> general@xml.apache.org
>>>>>>>>>> CC:
>>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> <Je...@Sun.COM>,
>>>>
>>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello All,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>>> final. JAXP
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>>> It allows to compile Schema to an immutable memory
>>>>>>>>>> representation
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> of
>>>>
>>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> thus
>>>>
>>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> language
>>>>
>>>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>>>> of an
>>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>>> access to
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>>>>>>> the
>>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>>> Datatypes to
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP
>>>>>>>>>> 1.3 also
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>>>>>>> adds
>>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> allowing
>>>>
>>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> performance.
>>>>
>>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>>> L/S, XML
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> 1.1, XInclude.
>>>>>>>>>>
>>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API
>>>>>>>>>> s +
>>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>>
>>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> (Reference
>>>>
>>>>>>>>>> Implementation). RI has been done using
>>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>>>> newly
>>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>>> Transformer
>>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>>> XInclude
>>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>>> JAXP 1.3
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> RI
>>>>
>>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>>> Xerces
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> or
>>>>
>>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>>> Xerces &
>>>>>>>>>> Xalan is very welcome.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>>
>>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these
>>>>>>>>>> set of
>>>>>>>>>> APIs
>>>>>>>>>> are used by many different projects.
>>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>>> emerging, we
>>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons
>>>>>>>>>> main
>>>>>>>>>> trunk
>>>>>>>>>> and apply a tag.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Xerces)*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>>
>>>>>>>>>> javax.xml.datatype
>>>>>>>>>> javax.xml.validation
>>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>>
>>>>>>>>>> which should reside at Xerces.
>>>>>>>>>>
>>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> into
>>>>
>>>>>>>>>> that branch. This will help
>>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> before
>>>>
>>>>>>>>>> these changes being finally
>>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>>> changes to
>>>>>>>>>> the branch and then committing
>>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>> Xalan)*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> changes
>>>>
>>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>>>> invoking reset().
>>>>>>>>>>
>>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>>> branch
>>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>>> put there. This will help other Xalan active committers to
>>>>>>>>>> have a
>>>>>>>>>> chance
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> to look at it before these changes being finally
>>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>>> for this
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> process.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>>> [2]
>>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>>> [3]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> [4]
>>>>>>>>>>
>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>
>>>>>>>>>> summary.html
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Michael Glavassevich
>>>>>>>>> XML Parser Development
>>>>>>>>> IBM Toronto Lab
>>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>>
>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>>
>>>>
>>>> Michael Glavassevich
>>>> XML Parser Development
>>>> IBM Toronto Lab
>>>> E-mail: mrglavas@ca.ibm.com
>>>> E-mail: mrglavas@apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir, I have uploaded sources at the same location
(xml-commons/contrib/jaxp13)
with Apache 2.0 license on every source file.
- Neeraj
Neeraj Bajaj wrote:
> Ok, So i will add it and upload again.
>
> - Neeraj
>
> Geir Magnusson Jr. wrote:
>
>>
>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>
>>> Hi Neeraj,
>>>
>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>> license. Will this still be the case for JAXP 1.3?
>>
>>
>>
>> yes - these files must be available under the apache license v2.
>> And the license grantor should be the one that adds it.
>>
>> Sorry Neeraj :)
>>
>> geir
>>
>>>
>>> Thanks.
>>>
>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>
>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>>> which
>>>> corresponds to jaxp-api,
>>>> xerces & xalan sources respectively.
>>>>
>>>> - Neeraj
>>>>
>>>> Neeraj Bajaj wrote:
>>>>
>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>> I will send mail to the community when i am done.
>>>>>
>>>>> Thanks dims for the suggestion.
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Davanum Srinivas wrote:
>>>>>
>>>>>> Neeraj,
>>>>>>
>>>>>> my 2 cents...upload the whole thing say in
>>>>>> xml-commons/contrib/jaxp13
>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>
>>>>>> thanks,
>>>>>> dims
>>>>>>
>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>
>>>>>>
>>>>>>> Thanks Michael for your response.
>>>>>>>
>>>>>>> I was just wondering what would be idle time to wait before i start
>>>>>>> work
>>>>>>> on this ?
>>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>>
>>>>>>
>>> send
>>>
>>>>>>> this mail
>>>>>>> before making changes ?
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Michael Glavassevich wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hi Neeraj,
>>>>>>>>
>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>
>>>>>>>
>>> and
>>>
>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>> trunk.
>>>>>>>>
>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>>> updates
>>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>>> we've
>>>>>>>
>>>>>>>
>>>
>>>>>>>> used
>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>> assume a
>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>
>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>
>>>>>>>
>>> AM:
>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>>> zip but
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> mail bounced back with the following message
>>>>>>>>>
>>>>>>>>> <error>
>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>> </error>
>>>>>>>>>
>>>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>>>> server somewhere ?
>>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>>
>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>> community
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> to help put it in a
>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>> number of
>>>>>>>>> changes it would be a considerable
>>>>>>>>> amount of work. This will also help the committers & community to
>>>>>>>>> have a
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> look at the code before
>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>
>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>> sources
>>>>>>>>> in xml-commons branch
>>>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
>>>>>>>>
>>>>>>>>
>>> the
>>>
>>>>>>>>> opinion of community ? I can
>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>> preference is to put the sources on
>>>>>>>>> xml-commons main trunk.
>>>>>>>>>
>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>> implementation to Apache XML.*
>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>> functionalities.
>>>>>>>>>
>>>>>>>>> * New Schema Validation Framework
>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>> * Reuse parser instance
>>>>>>>>> * Security enhancements
>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>> Save, SAX
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>
>>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>>> for the
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>
>>>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>> Xalan.
>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>>> in the
>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>> community.
>>>>>>>>>
>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>>>> ball
>>>>>>>>>>>> on this one.
>>>>>>>>>>>>
>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>>>> that
>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>> achieved.
>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>> process
>>>>>>>>>>> hold things up.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> ----------------------------------------------------------------------
>>>> --
>>>
>>>
>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Subject:
>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>> From:
>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>> Date:
>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>
>>>>>>>>> To:
>>>>>>>>> general@xml.apache.org
>>>>>>>>> CC:
>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>
>>>>>>>>
>>> <Je...@Sun.COM>,
>>>
>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>> final. JAXP
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>> It allows to compile Schema to an immutable memory representation
>>>>>>>>
>>>>>>>>
>>> of
>>>
>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>
>>>>>>>>
>>> thus
>>>
>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>
>>>>>>>>
>>> language
>>>
>>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>>> of an
>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>> access to
>>>>>>>>
>>>>>>>>
>>>
>>>>>>>>> the
>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>> Datatypes to
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>>>> also
>>>>>>>>
>>>>>>>>
>>>
>>>>>>>>> adds
>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>
>>>>>>>>
>>> allowing
>>>
>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>
>>>>>>>>
>>> performance.
>>>
>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>> L/S, XML
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 1.1, XInclude.
>>>>>>>>>
>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>
>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>
>>>>>>>>
>>> (Reference
>>>
>>>>>>>>> Implementation). RI has been done using
>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>>> newly
>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>> Transformer
>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>> XInclude
>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>> JAXP 1.3
>>>>>>>>
>>>>>>>>
>>> RI
>>>
>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>> Xerces
>>>>>>>>
>>>>>>>>
>>> or
>>>
>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>> Xerces &
>>>>>>>>> Xalan is very welcome.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>
>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>>>> APIs
>>>>>>>>> are used by many different projects.
>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>> emerging, we
>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>>>> trunk
>>>>>>>>> and apply a tag.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Xerces)*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>
>>>>>>>>> javax.xml.datatype
>>>>>>>>> javax.xml.validation
>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>
>>>>>>>>> which should reside at Xerces.
>>>>>>>>>
>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>>
>>>>>>>>
>>> into
>>>
>>>>>>>>> that branch. This will help
>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>
>>>>>>>>
>>> before
>>>
>>>>>>>>> these changes being finally
>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>> changes to
>>>>>>>>> the branch and then committing
>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>> Xalan)*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>
>>>>>>>>
>>> changes
>>>
>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>>> invoking reset().
>>>>>>>>>
>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>> branch
>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>>>> chance
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> to look at it before these changes being finally
>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>> for this
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> process.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>> [2]
>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>> [3]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>
>>>>>>>
>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> [4]
>>>>>>>>>
>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>
>>>>>>>>> summary.html
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Michael Glavassevich
>>>>>>>> XML Parser Development
>>>>>>>> IBM Toronto Lab
>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>
>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>
>>>
>>> Michael Glavassevich
>>> XML Parser Development
>>> IBM Toronto Lab
>>> E-mail: mrglavas@ca.ibm.com
>>> E-mail: mrglavas@apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir, I have uploaded sources at the same location
(xml-commons/contrib/jaxp13)
with Apache 2.0 license on every source file.
- Neeraj
Neeraj Bajaj wrote:
> Ok, So i will add it and upload again.
>
> - Neeraj
>
> Geir Magnusson Jr. wrote:
>
>>
>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>
>>> Hi Neeraj,
>>>
>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>> license. Will this still be the case for JAXP 1.3?
>>
>>
>>
>> yes - these files must be available under the apache license v2.
>> And the license grantor should be the one that adds it.
>>
>> Sorry Neeraj :)
>>
>> geir
>>
>>>
>>> Thanks.
>>>
>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>
>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>>> which
>>>> corresponds to jaxp-api,
>>>> xerces & xalan sources respectively.
>>>>
>>>> - Neeraj
>>>>
>>>> Neeraj Bajaj wrote:
>>>>
>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>> I will send mail to the community when i am done.
>>>>>
>>>>> Thanks dims for the suggestion.
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Davanum Srinivas wrote:
>>>>>
>>>>>> Neeraj,
>>>>>>
>>>>>> my 2 cents...upload the whole thing say in
>>>>>> xml-commons/contrib/jaxp13
>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>
>>>>>> thanks,
>>>>>> dims
>>>>>>
>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>
>>>>>>
>>>>>>> Thanks Michael for your response.
>>>>>>>
>>>>>>> I was just wondering what would be idle time to wait before i start
>>>>>>> work
>>>>>>> on this ?
>>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>>
>>>>>>
>>> send
>>>
>>>>>>> this mail
>>>>>>> before making changes ?
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Michael Glavassevich wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hi Neeraj,
>>>>>>>>
>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>
>>>>>>>
>>> and
>>>
>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>> trunk.
>>>>>>>>
>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>>> updates
>>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>>> we've
>>>>>>>
>>>>>>>
>>>
>>>>>>>> used
>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>> assume a
>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>
>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>
>>>>>>>
>>> AM:
>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>>> zip but
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> mail bounced back with the following message
>>>>>>>>>
>>>>>>>>> <error>
>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>> </error>
>>>>>>>>>
>>>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>>>> server somewhere ?
>>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>>
>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>> community
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> to help put it in a
>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>> number of
>>>>>>>>> changes it would be a considerable
>>>>>>>>> amount of work. This will also help the committers & community to
>>>>>>>>> have a
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> look at the code before
>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>
>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>> sources
>>>>>>>>> in xml-commons branch
>>>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
>>>>>>>>
>>>>>>>>
>>> the
>>>
>>>>>>>>> opinion of community ? I can
>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>> preference is to put the sources on
>>>>>>>>> xml-commons main trunk.
>>>>>>>>>
>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>> implementation to Apache XML.*
>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>> functionalities.
>>>>>>>>>
>>>>>>>>> * New Schema Validation Framework
>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>> * Reuse parser instance
>>>>>>>>> * Security enhancements
>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>> Save, SAX
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>
>>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>>> for the
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>
>>>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>> Xalan.
>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>>> in the
>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>> community.
>>>>>>>>>
>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>>>> ball
>>>>>>>>>>>> on this one.
>>>>>>>>>>>>
>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>>>> that
>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>> achieved.
>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>> process
>>>>>>>>>>> hold things up.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> ----------------------------------------------------------------------
>>>> --
>>>
>>>
>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Subject:
>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>> From:
>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>> Date:
>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>
>>>>>>>>> To:
>>>>>>>>> general@xml.apache.org
>>>>>>>>> CC:
>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>
>>>>>>>>
>>> <Je...@Sun.COM>,
>>>
>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>> final. JAXP
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>> It allows to compile Schema to an immutable memory representation
>>>>>>>>
>>>>>>>>
>>> of
>>>
>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>
>>>>>>>>
>>> thus
>>>
>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>
>>>>>>>>
>>> language
>>>
>>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>>> of an
>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>> access to
>>>>>>>>
>>>>>>>>
>>>
>>>>>>>>> the
>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>> Datatypes to
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>>>> also
>>>>>>>>
>>>>>>>>
>>>
>>>>>>>>> adds
>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>
>>>>>>>>
>>> allowing
>>>
>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>
>>>>>>>>
>>> performance.
>>>
>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>> L/S, XML
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 1.1, XInclude.
>>>>>>>>>
>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>
>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>
>>>>>>>>
>>> (Reference
>>>
>>>>>>>>> Implementation). RI has been done using
>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>>> newly
>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>> Transformer
>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>> XInclude
>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>> JAXP 1.3
>>>>>>>>
>>>>>>>>
>>> RI
>>>
>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>> Xerces
>>>>>>>>
>>>>>>>>
>>> or
>>>
>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>> Xerces &
>>>>>>>>> Xalan is very welcome.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>
>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>>>> APIs
>>>>>>>>> are used by many different projects.
>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>> emerging, we
>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>>>> trunk
>>>>>>>>> and apply a tag.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Xerces)*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>
>>>>>>>>> javax.xml.datatype
>>>>>>>>> javax.xml.validation
>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>
>>>>>>>>> which should reside at Xerces.
>>>>>>>>>
>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>>
>>>>>>>>
>>> into
>>>
>>>>>>>>> that branch. This will help
>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>
>>>>>>>>
>>> before
>>>
>>>>>>>>> these changes being finally
>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>> changes to
>>>>>>>>> the branch and then committing
>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>> Xalan)*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>
>>>>>>>>
>>> changes
>>>
>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>>> invoking reset().
>>>>>>>>>
>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>> branch
>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>>>> chance
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> to look at it before these changes being finally
>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>> for this
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> process.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>> [2]
>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>> [3]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>
>>>>>>>
>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> [4]
>>>>>>>>>
>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>
>>>>>>>>> summary.html
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Michael Glavassevich
>>>>>>>> XML Parser Development
>>>>>>>> IBM Toronto Lab
>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>
>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>
>>>
>>> Michael Glavassevich
>>> XML Parser Development
>>> IBM Toronto Lab
>>> E-mail: mrglavas@ca.ibm.com
>>> E-mail: mrglavas@apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir, I have uploaded sources at the same location
(xml-commons/contrib/jaxp13)
with Apache 2.0 license on every source file.
- Neeraj
Neeraj Bajaj wrote:
> Ok, So i will add it and upload again.
>
> - Neeraj
>
> Geir Magnusson Jr. wrote:
>
>>
>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>
>>> Hi Neeraj,
>>>
>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>> license. Will this still be the case for JAXP 1.3?
>>
>>
>>
>> yes - these files must be available under the apache license v2.
>> And the license grantor should be the one that adds it.
>>
>> Sorry Neeraj :)
>>
>> geir
>>
>>>
>>> Thanks.
>>>
>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>
>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>>> which
>>>> corresponds to jaxp-api,
>>>> xerces & xalan sources respectively.
>>>>
>>>> - Neeraj
>>>>
>>>> Neeraj Bajaj wrote:
>>>>
>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>> I will send mail to the community when i am done.
>>>>>
>>>>> Thanks dims for the suggestion.
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Davanum Srinivas wrote:
>>>>>
>>>>>> Neeraj,
>>>>>>
>>>>>> my 2 cents...upload the whole thing say in
>>>>>> xml-commons/contrib/jaxp13
>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>
>>>>>> thanks,
>>>>>> dims
>>>>>>
>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>
>>>>>>
>>>>>>> Thanks Michael for your response.
>>>>>>>
>>>>>>> I was just wondering what would be idle time to wait before i start
>>>>>>> work
>>>>>>> on this ?
>>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>>
>>>>>>
>>> send
>>>
>>>>>>> this mail
>>>>>>> before making changes ?
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Michael Glavassevich wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hi Neeraj,
>>>>>>>>
>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>
>>>>>>>
>>> and
>>>
>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>> trunk.
>>>>>>>>
>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>>> updates
>>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>>> we've
>>>>>>>
>>>>>>>
>>>
>>>>>>>> used
>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>> assume a
>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>
>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>
>>>>>>>
>>> AM:
>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>>> zip but
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> mail bounced back with the following message
>>>>>>>>>
>>>>>>>>> <error>
>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>> </error>
>>>>>>>>>
>>>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>>>> server somewhere ?
>>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>>
>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>> community
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> to help put it in a
>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>> number of
>>>>>>>>> changes it would be a considerable
>>>>>>>>> amount of work. This will also help the committers & community to
>>>>>>>>> have a
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> look at the code before
>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>
>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>> sources
>>>>>>>>> in xml-commons branch
>>>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
>>>>>>>>
>>>>>>>>
>>> the
>>>
>>>>>>>>> opinion of community ? I can
>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>> preference is to put the sources on
>>>>>>>>> xml-commons main trunk.
>>>>>>>>>
>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>> implementation to Apache XML.*
>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>> functionalities.
>>>>>>>>>
>>>>>>>>> * New Schema Validation Framework
>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>> * Reuse parser instance
>>>>>>>>> * Security enhancements
>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>> Save, SAX
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>
>>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>>> for the
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>
>>>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>> Xalan.
>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>>> in the
>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>> community.
>>>>>>>>>
>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>>>> ball
>>>>>>>>>>>> on this one.
>>>>>>>>>>>>
>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>>>> that
>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>> achieved.
>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>> process
>>>>>>>>>>> hold things up.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> ----------------------------------------------------------------------
>>>> --
>>>
>>>
>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Subject:
>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>> From:
>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>> Date:
>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>
>>>>>>>>> To:
>>>>>>>>> general@xml.apache.org
>>>>>>>>> CC:
>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>
>>>>>>>>
>>> <Je...@Sun.COM>,
>>>
>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>> final. JAXP
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>> It allows to compile Schema to an immutable memory representation
>>>>>>>>
>>>>>>>>
>>> of
>>>
>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>
>>>>>>>>
>>> thus
>>>
>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>
>>>>>>>>
>>> language
>>>
>>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>>> of an
>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>> access to
>>>>>>>>
>>>>>>>>
>>>
>>>>>>>>> the
>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>> Datatypes to
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>>>> also
>>>>>>>>
>>>>>>>>
>>>
>>>>>>>>> adds
>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>
>>>>>>>>
>>> allowing
>>>
>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>
>>>>>>>>
>>> performance.
>>>
>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>> L/S, XML
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 1.1, XInclude.
>>>>>>>>>
>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>
>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>
>>>>>>>>
>>> (Reference
>>>
>>>>>>>>> Implementation). RI has been done using
>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>>> newly
>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>> Transformer
>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>> XInclude
>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>> JAXP 1.3
>>>>>>>>
>>>>>>>>
>>> RI
>>>
>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>> Xerces
>>>>>>>>
>>>>>>>>
>>> or
>>>
>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>> Xerces &
>>>>>>>>> Xalan is very welcome.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>
>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>>>> APIs
>>>>>>>>> are used by many different projects.
>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>> emerging, we
>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>>>> trunk
>>>>>>>>> and apply a tag.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Xerces)*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>
>>>>>>>>> javax.xml.datatype
>>>>>>>>> javax.xml.validation
>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>
>>>>>>>>> which should reside at Xerces.
>>>>>>>>>
>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>>
>>>>>>>>
>>> into
>>>
>>>>>>>>> that branch. This will help
>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>
>>>>>>>>
>>> before
>>>
>>>>>>>>> these changes being finally
>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>> changes to
>>>>>>>>> the branch and then committing
>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>> Xalan)*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>
>>>>>>>>
>>> changes
>>>
>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>>> invoking reset().
>>>>>>>>>
>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>> branch
>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>>>> chance
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> to look at it before these changes being finally
>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>> for this
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> process.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>> [2]
>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>> [3]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>
>>>>>>>
>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> [4]
>>>>>>>>>
>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>
>>>>>>>>> summary.html
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Michael Glavassevich
>>>>>>>> XML Parser Development
>>>>>>>> IBM Toronto Lab
>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>
>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>
>>>
>>> Michael Glavassevich
>>> XML Parser Development
>>> IBM Toronto Lab
>>> E-mail: mrglavas@ca.ibm.com
>>> E-mail: mrglavas@apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir, I have uploaded sources at the same location
(xml-commons/contrib/jaxp13)
with Apache 2.0 license on every source file.
- Neeraj
Neeraj Bajaj wrote:
> Ok, So i will add it and upload again.
>
> - Neeraj
>
> Geir Magnusson Jr. wrote:
>
>>
>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>
>>> Hi Neeraj,
>>>
>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>> license. Will this still be the case for JAXP 1.3?
>>
>>
>>
>> yes - these files must be available under the apache license v2.
>> And the license grantor should be the one that adds it.
>>
>> Sorry Neeraj :)
>>
>> geir
>>
>>>
>>> Thanks.
>>>
>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>
>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>>> which
>>>> corresponds to jaxp-api,
>>>> xerces & xalan sources respectively.
>>>>
>>>> - Neeraj
>>>>
>>>> Neeraj Bajaj wrote:
>>>>
>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>> I will send mail to the community when i am done.
>>>>>
>>>>> Thanks dims for the suggestion.
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Davanum Srinivas wrote:
>>>>>
>>>>>> Neeraj,
>>>>>>
>>>>>> my 2 cents...upload the whole thing say in
>>>>>> xml-commons/contrib/jaxp13
>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>
>>>>>> thanks,
>>>>>> dims
>>>>>>
>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>
>>>>>>
>>>>>>> Thanks Michael for your response.
>>>>>>>
>>>>>>> I was just wondering what would be idle time to wait before i start
>>>>>>> work
>>>>>>> on this ?
>>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>>
>>>>>>
>>> send
>>>
>>>>>>> this mail
>>>>>>> before making changes ?
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Michael Glavassevich wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hi Neeraj,
>>>>>>>>
>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>
>>>>>>>
>>> and
>>>
>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>> trunk.
>>>>>>>>
>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>>> updates
>>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>>> we've
>>>>>>>
>>>>>>>
>>>
>>>>>>>> used
>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>> assume a
>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>
>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>
>>>>>>>
>>> AM:
>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>>> zip but
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> mail bounced back with the following message
>>>>>>>>>
>>>>>>>>> <error>
>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>> </error>
>>>>>>>>>
>>>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>>>> server somewhere ?
>>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>>
>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>> community
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> to help put it in a
>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>> number of
>>>>>>>>> changes it would be a considerable
>>>>>>>>> amount of work. This will also help the committers & community to
>>>>>>>>> have a
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> look at the code before
>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>
>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>> sources
>>>>>>>>> in xml-commons branch
>>>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
>>>>>>>>
>>>>>>>>
>>> the
>>>
>>>>>>>>> opinion of community ? I can
>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>> preference is to put the sources on
>>>>>>>>> xml-commons main trunk.
>>>>>>>>>
>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>> implementation to Apache XML.*
>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>> functionalities.
>>>>>>>>>
>>>>>>>>> * New Schema Validation Framework
>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>> * Reuse parser instance
>>>>>>>>> * Security enhancements
>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>> Save, SAX
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>
>>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>>> for the
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>
>>>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>> Xalan.
>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>>> in the
>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>> community.
>>>>>>>>>
>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>>>> ball
>>>>>>>>>>>> on this one.
>>>>>>>>>>>>
>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>>>> that
>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>> achieved.
>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>> process
>>>>>>>>>>> hold things up.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> ----------------------------------------------------------------------
>>>> --
>>>
>>>
>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Subject:
>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>> From:
>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>> Date:
>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>
>>>>>>>>> To:
>>>>>>>>> general@xml.apache.org
>>>>>>>>> CC:
>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>
>>>>>>>>
>>> <Je...@Sun.COM>,
>>>
>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>> final. JAXP
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>> It allows to compile Schema to an immutable memory representation
>>>>>>>>
>>>>>>>>
>>> of
>>>
>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>
>>>>>>>>
>>> thus
>>>
>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>
>>>>>>>>
>>> language
>>>
>>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>>> of an
>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>> access to
>>>>>>>>
>>>>>>>>
>>>
>>>>>>>>> the
>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>> Datatypes to
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>>>> also
>>>>>>>>
>>>>>>>>
>>>
>>>>>>>>> adds
>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>
>>>>>>>>
>>> allowing
>>>
>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>
>>>>>>>>
>>> performance.
>>>
>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>> L/S, XML
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 1.1, XInclude.
>>>>>>>>>
>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>
>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>
>>>>>>>>
>>> (Reference
>>>
>>>>>>>>> Implementation). RI has been done using
>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>>> newly
>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>> Transformer
>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>> XInclude
>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>> JAXP 1.3
>>>>>>>>
>>>>>>>>
>>> RI
>>>
>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>> Xerces
>>>>>>>>
>>>>>>>>
>>> or
>>>
>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>> Xerces &
>>>>>>>>> Xalan is very welcome.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>
>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>>>> APIs
>>>>>>>>> are used by many different projects.
>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>> emerging, we
>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>>>> trunk
>>>>>>>>> and apply a tag.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Xerces)*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>
>>>>>>>>> javax.xml.datatype
>>>>>>>>> javax.xml.validation
>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>
>>>>>>>>> which should reside at Xerces.
>>>>>>>>>
>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>>
>>>>>>>>
>>> into
>>>
>>>>>>>>> that branch. This will help
>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>
>>>>>>>>
>>> before
>>>
>>>>>>>>> these changes being finally
>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>> changes to
>>>>>>>>> the branch and then committing
>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>> Xalan)*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>
>>>>>>>>
>>> changes
>>>
>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>>> invoking reset().
>>>>>>>>>
>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>> branch
>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>>>> chance
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> to look at it before these changes being finally
>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>> for this
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> process.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>> [2]
>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>> [3]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>
>>>>>>>
>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> [4]
>>>>>>>>>
>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>
>>>>>>>>> summary.html
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Michael Glavassevich
>>>>>>>> XML Parser Development
>>>>>>>> IBM Toronto Lab
>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>
>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>
>>>
>>> Michael Glavassevich
>>> XML Parser Development
>>> IBM Toronto Lab
>>> E-mail: mrglavas@ca.ibm.com
>>> E-mail: mrglavas@apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir, I have uploaded sources at the same location
(xml-commons/contrib/jaxp13)
with Apache 2.0 license on every source file.
- Neeraj
Neeraj Bajaj wrote:
> Ok, So i will add it and upload again.
>
> - Neeraj
>
> Geir Magnusson Jr. wrote:
>
>>
>> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>>
>>> Hi Neeraj,
>>>
>>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>>> license. Will this still be the case for JAXP 1.3?
>>
>>
>>
>> yes - these files must be available under the apache license v2.
>> And the license grantor should be the one that adds it.
>>
>> Sorry Neeraj :)
>>
>> geir
>>
>>>
>>> Thanks.
>>>
>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>>
>>>> Ok I just finished uploading JAXP 1.3 sources in
>>>> "*xml-commons/contrib/jaxp13"* directory.
>>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>>> which
>>>> corresponds to jaxp-api,
>>>> xerces & xalan sources respectively.
>>>>
>>>> - Neeraj
>>>>
>>>> Neeraj Bajaj wrote:
>>>>
>>>>> That really sounds good to me.. so i would try to finish it today.
>>>>> I will send mail to the community when i am done.
>>>>>
>>>>> Thanks dims for the suggestion.
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Davanum Srinivas wrote:
>>>>>
>>>>>> Neeraj,
>>>>>>
>>>>>> my 2 cents...upload the whole thing say in
>>>>>> xml-commons/contrib/jaxp13
>>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>>
>>>>>> thanks,
>>>>>> dims
>>>>>>
>>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>>
>>>>>>
>>>>>>> Thanks Michael for your response.
>>>>>>>
>>>>>>> I was just wondering what would be idle time to wait before i start
>>>>>>> work
>>>>>>> on this ?
>>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>>
>>>>>>
>>> send
>>>
>>>>>>> this mail
>>>>>>> before making changes ?
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>> Michael Glavassevich wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hi Neeraj,
>>>>>>>>
>>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>>
>>>>>>>
>>> and
>>>
>>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>>> trunk.
>>>>>>>>
>>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>>> updates
>>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>>> we've
>>>>>>>
>>>>>>>
>>>
>>>>>>>> used
>>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>>> assume a
>>>>>>>> similar branch will exist for 1.3.
>>>>>>>>
>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>>
>>>>>>>
>>> AM:
>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>>> zip but
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> mail bounced back with the following message
>>>>>>>>>
>>>>>>>>> <error>
>>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>>> <ge...@xml.apache.org>
>>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>>> </error>
>>>>>>>>>
>>>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>>>> server somewhere ?
>>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>>
>>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>>> community
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> to help put it in a
>>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>>> number of
>>>>>>>>> changes it would be a considerable
>>>>>>>>> amount of work. This will also help the committers & community to
>>>>>>>>> have a
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> look at the code before
>>>>>>>>> it is merged into the main stream work.
>>>>>>>>>
>>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>>> sources
>>>>>>>>> in xml-commons branch
>>>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
>>>>>>>>
>>>>>>>>
>>> the
>>>
>>>>>>>>> opinion of community ? I can
>>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>>> preference is to put the sources on
>>>>>>>>> xml-commons main trunk.
>>>>>>>>>
>>>>>>>>> Please let me know how should i proceed.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>>> implementation to Apache XML.*
>>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>>> functionalities.
>>>>>>>>>
>>>>>>>>> * New Schema Validation Framework
>>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>>> * Reuse parser instance
>>>>>>>>> * Security enhancements
>>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>>> Save, SAX
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>>
>>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>>> for the
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>>
>>>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>>> Xalan.
>>>>>>>>> There was a general consensus to my proposal
>>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>>> in the
>>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>>> community.
>>>>>>>>>
>>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>>>> ball
>>>>>>>>>>>> on this one.
>>>>>>>>>>>>
>>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>>>> that
>>>>>>>>>>>> Neeraj will get some consensus from xml-commons,
>>>>>>>>>>>> xalan-dev, and
>>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>>> achieved.
>>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>>> process
>>>>>>>>>>> hold things up.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>>
>>>>>>>>>> - Neeraj
>>>>>>>>>>
>>>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> ----------------------------------------------------------------------
>>>> --
>>>
>>>
>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Subject:
>>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>>> From:
>>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>>> Date:
>>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>>
>>>>>>>>> To:
>>>>>>>>> general@xml.apache.org
>>>>>>>>> CC:
>>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>>
>>>>>>>>
>>> <Je...@Sun.COM>,
>>>
>>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello All,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>>> final. JAXP
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>>> It allows to compile Schema to an immutable memory representation
>>>>>>>>
>>>>>>>>
>>> of
>>>
>>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>>
>>>>>>>>
>>> thus
>>>
>>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>>
>>>>>>>>
>>> language
>>>
>>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>>> of an
>>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>>> access to
>>>>>>>>
>>>>>>>>
>>>
>>>>>>>>> the
>>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>>> Datatypes to
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>>>> also
>>>>>>>>
>>>>>>>>
>>>
>>>>>>>>> adds
>>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>>
>>>>>>>>
>>> allowing
>>>
>>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>>
>>>>>>>>
>>> performance.
>>>
>>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>>> L/S, XML
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 1.1, XInclude.
>>>>>>>>>
>>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>>
>>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>>
>>>>>>>>
>>> (Reference
>>>
>>>>>>>>> Implementation). RI has been done using
>>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>>> newly
>>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>>> Transformer
>>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>>> XInclude
>>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>>> section I have also proposed the way to merge rest of the
>>>>>>>>> JAXP 1.3
>>>>>>>>
>>>>>>>>
>>> RI
>>>
>>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>>> Xerces
>>>>>>>>
>>>>>>>>
>>> or
>>>
>>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>>> Xerces &
>>>>>>>>> Xalan is very welcome.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>>
>>>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>>>> APIs
>>>>>>>>> are used by many different projects.
>>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>>> emerging, we
>>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>>>> trunk
>>>>>>>>> and apply a tag.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Xerces)*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>>
>>>>>>>>> javax.xml.datatype
>>>>>>>>> javax.xml.validation
>>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>>
>>>>>>>>> which should reside at Xerces.
>>>>>>>>>
>>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>>
>>>>>>>>
>>> into
>>>
>>>>>>>>> that branch. This will help
>>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>>
>>>>>>>>
>>> before
>>>
>>>>>>>>> these changes being finally
>>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>>> changes to
>>>>>>>>> the branch and then committing
>>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>> Xalan)*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>>
>>>>>>>>
>>> changes
>>>
>>>>>>>>> done in "javax.xml.transform" package
>>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>>> invoking reset().
>>>>>>>>>
>>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>>> branch
>>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>>>> chance
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> to look at it before these changes being finally
>>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>>> for this
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> process.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Neeraj
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>>> [2]
>>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>>> [3]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>
>>>>>>>
>>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> [4]
>>>>>>>>>
>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>
>>>>>>>>> summary.html
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Michael Glavassevich
>>>>>>>> XML Parser Development
>>>>>>>> IBM Toronto Lab
>>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>>
>>>>>>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>>
>>>
>>> Michael Glavassevich
>>> XML Parser Development
>>> IBM Toronto Lab
>>> E-mail: mrglavas@ca.ibm.com
>>> E-mail: mrglavas@apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ok, So i will add it and upload again.
- Neeraj
Geir Magnusson Jr. wrote:
>
> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>
>> Hi Neeraj,
>>
>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>> license. Will this still be the case for JAXP 1.3?
>
>
> yes - these files must be available under the apache license v2. And
> the license grantor should be the one that adds it.
>
> Sorry Neeraj :)
>
> geir
>
>>
>> Thanks.
>>
>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>
>>> Ok I just finished uploading JAXP 1.3 sources in
>>> "*xml-commons/contrib/jaxp13"* directory.
>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>> which
>>> corresponds to jaxp-api,
>>> xerces & xalan sources respectively.
>>>
>>> - Neeraj
>>>
>>> Neeraj Bajaj wrote:
>>>
>>>> That really sounds good to me.. so i would try to finish it today.
>>>> I will send mail to the community when i am done.
>>>>
>>>> Thanks dims for the suggestion.
>>>>
>>>> - Neeraj
>>>>
>>>> Davanum Srinivas wrote:
>>>>
>>>>> Neeraj,
>>>>>
>>>>> my 2 cents...upload the whole thing say in
>>>>> xml-commons/contrib/jaxp13
>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>
>>>>> thanks,
>>>>> dims
>>>>>
>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>
>>>>>
>>>>>> Thanks Michael for your response.
>>>>>>
>>>>>> I was just wondering what would be idle time to wait before i start
>>>>>> work
>>>>>> on this ?
>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>
>> send
>>
>>>>>> this mail
>>>>>> before making changes ?
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Michael Glavassevich wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hi Neeraj,
>>>>>>>
>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>
>> and
>>
>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>> trunk.
>>>>>>>
>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>> updates
>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>> we've
>>>>>>
>>
>>>>>>> used
>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>> assume a
>>>>>>> similar branch will exist for 1.3.
>>>>>>>
>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>
>> AM:
>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>> zip but
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> mail bounced back with the following message
>>>>>>>>
>>>>>>>> <error>
>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>> <ge...@xml.apache.org>
>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>> </error>
>>>>>>>>
>>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>>> server somewhere ?
>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>
>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>> community
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> to help put it in a
>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>> number of
>>>>>>>> changes it would be a considerable
>>>>>>>> amount of work. This will also help the committers & community to
>>>>>>>> have a
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> look at the code before
>>>>>>>> it is merged into the main stream work.
>>>>>>>>
>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>> sources
>>>>>>>> in xml-commons branch
>>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
>>>>>>>
>> the
>>
>>>>>>>> opinion of community ? I can
>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>> preference is to put the sources on
>>>>>>>> xml-commons main trunk.
>>>>>>>>
>>>>>>>> Please let me know how should i proceed.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>> implementation to Apache XML.*
>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>> functionalities.
>>>>>>>>
>>>>>>>> * New Schema Validation Framework
>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>> * Reuse parser instance
>>>>>>>> * Security enhancements
>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>> Save, SAX
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>
>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>
>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>> for the
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>
>>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>> Xalan.
>>>>>>>> There was a general consensus to my proposal
>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>> in the
>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>> community.
>>>>>>>>
>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>>> ball
>>>>>>>>>>> on this one.
>>>>>>>>>>>
>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>>> that
>>>>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev,
>>>>>>>>>>> and
>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>> achieved.
>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>> process
>>>>>>>>>> hold things up.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>> ----------------------------------------------------------------------
>>> --
>>
>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Subject:
>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>> From:
>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>> Date:
>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>
>>>>>>>> To:
>>>>>>>> general@xml.apache.org
>>>>>>>> CC:
>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>
>> <Je...@Sun.COM>,
>>
>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>>
>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>> final. JAXP
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>> It allows to compile Schema to an immutable memory representation
>>>>>>>
>> of
>>
>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>
>> thus
>>
>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>
>> language
>>
>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>> of an
>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>> access to
>>>>>>>
>>
>>>>>>>> the
>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>> Datatypes to
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>>> also
>>>>>>>
>>
>>>>>>>> adds
>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>
>> allowing
>>
>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>
>> performance.
>>
>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>> L/S, XML
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 1.1, XInclude.
>>>>>>>>
>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>
>>>>>>>>
>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>
>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>
>> (Reference
>>
>>>>>>>> Implementation). RI has been done using
>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>> newly
>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>> Transformer
>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>> XInclude
>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>> section I have also proposed the way to merge rest of the JAXP
>>>>>>>> 1.3
>>>>>>>
>> RI
>>
>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>> Xerces
>>>>>>>
>> or
>>
>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>> Xerces &
>>>>>>>> Xalan is very welcome.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>
>>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>>> APIs
>>>>>>>> are used by many different projects.
>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>> emerging, we
>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>>> trunk
>>>>>>>> and apply a tag.
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Xerces)*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>
>>>>>>>> javax.xml.datatype
>>>>>>>> javax.xml.validation
>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>
>>>>>>>> which should reside at Xerces.
>>>>>>>>
>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>
>> into
>>
>>>>>>>> that branch. This will help
>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>
>> before
>>
>>>>>>>> these changes being finally
>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>> changes to
>>>>>>>> the branch and then committing
>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>> Xalan)*
>>>>>>>>
>>>>>>>>
>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>
>> changes
>>
>>>>>>>> done in "javax.xml.transform" package
>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>> invoking reset().
>>>>>>>>
>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>> branch
>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>>> chance
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> to look at it before these changes being finally
>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>> for this
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> process.
>>>>>>>>
>>>>>>>>
>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>> [2]
>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>> [3]
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>
>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> [4]
>>>>>>>>
>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>
>>>>>>>> summary.html
>>>>>>>>
>>>>>>>>
>>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Michael Glavassevich
>>>>>>> XML Parser Development
>>>>>>> IBM Toronto Lab
>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>
>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>
>> Michael Glavassevich
>> XML Parser Development
>> IBM Toronto Lab
>> E-mail: mrglavas@ca.ibm.com
>> E-mail: mrglavas@apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ok, So i will add it and upload again.
- Neeraj
Geir Magnusson Jr. wrote:
>
> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>
>> Hi Neeraj,
>>
>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>> license. Will this still be the case for JAXP 1.3?
>
>
> yes - these files must be available under the apache license v2. And
> the license grantor should be the one that adds it.
>
> Sorry Neeraj :)
>
> geir
>
>>
>> Thanks.
>>
>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>
>>> Ok I just finished uploading JAXP 1.3 sources in
>>> "*xml-commons/contrib/jaxp13"* directory.
>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>> which
>>> corresponds to jaxp-api,
>>> xerces & xalan sources respectively.
>>>
>>> - Neeraj
>>>
>>> Neeraj Bajaj wrote:
>>>
>>>> That really sounds good to me.. so i would try to finish it today.
>>>> I will send mail to the community when i am done.
>>>>
>>>> Thanks dims for the suggestion.
>>>>
>>>> - Neeraj
>>>>
>>>> Davanum Srinivas wrote:
>>>>
>>>>> Neeraj,
>>>>>
>>>>> my 2 cents...upload the whole thing say in
>>>>> xml-commons/contrib/jaxp13
>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>
>>>>> thanks,
>>>>> dims
>>>>>
>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>
>>>>>
>>>>>> Thanks Michael for your response.
>>>>>>
>>>>>> I was just wondering what would be idle time to wait before i start
>>>>>> work
>>>>>> on this ?
>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>
>> send
>>
>>>>>> this mail
>>>>>> before making changes ?
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Michael Glavassevich wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hi Neeraj,
>>>>>>>
>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>
>> and
>>
>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>> trunk.
>>>>>>>
>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>> updates
>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>> we've
>>>>>>
>>
>>>>>>> used
>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>> assume a
>>>>>>> similar branch will exist for 1.3.
>>>>>>>
>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>
>> AM:
>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>> zip but
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> mail bounced back with the following message
>>>>>>>>
>>>>>>>> <error>
>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>> <ge...@xml.apache.org>
>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>> </error>
>>>>>>>>
>>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>>> server somewhere ?
>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>
>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>> community
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> to help put it in a
>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>> number of
>>>>>>>> changes it would be a considerable
>>>>>>>> amount of work. This will also help the committers & community to
>>>>>>>> have a
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> look at the code before
>>>>>>>> it is merged into the main stream work.
>>>>>>>>
>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>> sources
>>>>>>>> in xml-commons branch
>>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
>>>>>>>
>> the
>>
>>>>>>>> opinion of community ? I can
>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>> preference is to put the sources on
>>>>>>>> xml-commons main trunk.
>>>>>>>>
>>>>>>>> Please let me know how should i proceed.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>> implementation to Apache XML.*
>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>> functionalities.
>>>>>>>>
>>>>>>>> * New Schema Validation Framework
>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>> * Reuse parser instance
>>>>>>>> * Security enhancements
>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>> Save, SAX
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>
>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>
>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>> for the
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>
>>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>> Xalan.
>>>>>>>> There was a general consensus to my proposal
>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>> in the
>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>> community.
>>>>>>>>
>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>>> ball
>>>>>>>>>>> on this one.
>>>>>>>>>>>
>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>>> that
>>>>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev,
>>>>>>>>>>> and
>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>> achieved.
>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>> process
>>>>>>>>>> hold things up.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>> ----------------------------------------------------------------------
>>> --
>>
>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Subject:
>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>> From:
>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>> Date:
>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>
>>>>>>>> To:
>>>>>>>> general@xml.apache.org
>>>>>>>> CC:
>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>
>> <Je...@Sun.COM>,
>>
>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>>
>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>> final. JAXP
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>> It allows to compile Schema to an immutable memory representation
>>>>>>>
>> of
>>
>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>
>> thus
>>
>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>
>> language
>>
>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>> of an
>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>> access to
>>>>>>>
>>
>>>>>>>> the
>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>> Datatypes to
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>>> also
>>>>>>>
>>
>>>>>>>> adds
>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>
>> allowing
>>
>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>
>> performance.
>>
>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>> L/S, XML
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 1.1, XInclude.
>>>>>>>>
>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>
>>>>>>>>
>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>
>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>
>> (Reference
>>
>>>>>>>> Implementation). RI has been done using
>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>> newly
>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>> Transformer
>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>> XInclude
>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>> section I have also proposed the way to merge rest of the JAXP
>>>>>>>> 1.3
>>>>>>>
>> RI
>>
>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>> Xerces
>>>>>>>
>> or
>>
>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>> Xerces &
>>>>>>>> Xalan is very welcome.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>
>>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>>> APIs
>>>>>>>> are used by many different projects.
>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>> emerging, we
>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>>> trunk
>>>>>>>> and apply a tag.
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Xerces)*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>
>>>>>>>> javax.xml.datatype
>>>>>>>> javax.xml.validation
>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>
>>>>>>>> which should reside at Xerces.
>>>>>>>>
>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>
>> into
>>
>>>>>>>> that branch. This will help
>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>
>> before
>>
>>>>>>>> these changes being finally
>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>> changes to
>>>>>>>> the branch and then committing
>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>> Xalan)*
>>>>>>>>
>>>>>>>>
>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>
>> changes
>>
>>>>>>>> done in "javax.xml.transform" package
>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>> invoking reset().
>>>>>>>>
>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>> branch
>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>>> chance
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> to look at it before these changes being finally
>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>> for this
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> process.
>>>>>>>>
>>>>>>>>
>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>> [2]
>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>> [3]
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>
>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> [4]
>>>>>>>>
>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>
>>>>>>>> summary.html
>>>>>>>>
>>>>>>>>
>>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Michael Glavassevich
>>>>>>> XML Parser Development
>>>>>>> IBM Toronto Lab
>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>
>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>
>> Michael Glavassevich
>> XML Parser Development
>> IBM Toronto Lab
>> E-mail: mrglavas@ca.ibm.com
>> E-mail: mrglavas@apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ok, So i will add it and upload again.
- Neeraj
Geir Magnusson Jr. wrote:
>
> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>
>> Hi Neeraj,
>>
>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>> license. Will this still be the case for JAXP 1.3?
>
>
> yes - these files must be available under the apache license v2. And
> the license grantor should be the one that adds it.
>
> Sorry Neeraj :)
>
> geir
>
>>
>> Thanks.
>>
>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>
>>> Ok I just finished uploading JAXP 1.3 sources in
>>> "*xml-commons/contrib/jaxp13"* directory.
>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>> which
>>> corresponds to jaxp-api,
>>> xerces & xalan sources respectively.
>>>
>>> - Neeraj
>>>
>>> Neeraj Bajaj wrote:
>>>
>>>> That really sounds good to me.. so i would try to finish it today.
>>>> I will send mail to the community when i am done.
>>>>
>>>> Thanks dims for the suggestion.
>>>>
>>>> - Neeraj
>>>>
>>>> Davanum Srinivas wrote:
>>>>
>>>>> Neeraj,
>>>>>
>>>>> my 2 cents...upload the whole thing say in
>>>>> xml-commons/contrib/jaxp13
>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>
>>>>> thanks,
>>>>> dims
>>>>>
>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>
>>>>>
>>>>>> Thanks Michael for your response.
>>>>>>
>>>>>> I was just wondering what would be idle time to wait before i start
>>>>>> work
>>>>>> on this ?
>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>
>> send
>>
>>>>>> this mail
>>>>>> before making changes ?
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Michael Glavassevich wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hi Neeraj,
>>>>>>>
>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>
>> and
>>
>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>> trunk.
>>>>>>>
>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>> updates
>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>> we've
>>>>>>
>>
>>>>>>> used
>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>> assume a
>>>>>>> similar branch will exist for 1.3.
>>>>>>>
>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>
>> AM:
>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>> zip but
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> mail bounced back with the following message
>>>>>>>>
>>>>>>>> <error>
>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>> <ge...@xml.apache.org>
>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>> </error>
>>>>>>>>
>>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>>> server somewhere ?
>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>
>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>> community
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> to help put it in a
>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>> number of
>>>>>>>> changes it would be a considerable
>>>>>>>> amount of work. This will also help the committers & community to
>>>>>>>> have a
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> look at the code before
>>>>>>>> it is merged into the main stream work.
>>>>>>>>
>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>> sources
>>>>>>>> in xml-commons branch
>>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
>>>>>>>
>> the
>>
>>>>>>>> opinion of community ? I can
>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>> preference is to put the sources on
>>>>>>>> xml-commons main trunk.
>>>>>>>>
>>>>>>>> Please let me know how should i proceed.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>> implementation to Apache XML.*
>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>> functionalities.
>>>>>>>>
>>>>>>>> * New Schema Validation Framework
>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>> * Reuse parser instance
>>>>>>>> * Security enhancements
>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>> Save, SAX
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>
>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>
>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>> for the
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>
>>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>> Xalan.
>>>>>>>> There was a general consensus to my proposal
>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>> in the
>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>> community.
>>>>>>>>
>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>>> ball
>>>>>>>>>>> on this one.
>>>>>>>>>>>
>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>>> that
>>>>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev,
>>>>>>>>>>> and
>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>> achieved.
>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>> process
>>>>>>>>>> hold things up.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>> ----------------------------------------------------------------------
>>> --
>>
>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Subject:
>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>> From:
>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>> Date:
>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>
>>>>>>>> To:
>>>>>>>> general@xml.apache.org
>>>>>>>> CC:
>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>
>> <Je...@Sun.COM>,
>>
>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>>
>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>> final. JAXP
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>> It allows to compile Schema to an immutable memory representation
>>>>>>>
>> of
>>
>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>
>> thus
>>
>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>
>> language
>>
>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>> of an
>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>> access to
>>>>>>>
>>
>>>>>>>> the
>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>> Datatypes to
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>>> also
>>>>>>>
>>
>>>>>>>> adds
>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>
>> allowing
>>
>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>
>> performance.
>>
>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>> L/S, XML
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 1.1, XInclude.
>>>>>>>>
>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>
>>>>>>>>
>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>
>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>
>> (Reference
>>
>>>>>>>> Implementation). RI has been done using
>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>> newly
>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>> Transformer
>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>> XInclude
>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>> section I have also proposed the way to merge rest of the JAXP
>>>>>>>> 1.3
>>>>>>>
>> RI
>>
>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>> Xerces
>>>>>>>
>> or
>>
>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>> Xerces &
>>>>>>>> Xalan is very welcome.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>
>>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>>> APIs
>>>>>>>> are used by many different projects.
>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>> emerging, we
>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>>> trunk
>>>>>>>> and apply a tag.
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Xerces)*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>
>>>>>>>> javax.xml.datatype
>>>>>>>> javax.xml.validation
>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>
>>>>>>>> which should reside at Xerces.
>>>>>>>>
>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>
>> into
>>
>>>>>>>> that branch. This will help
>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>
>> before
>>
>>>>>>>> these changes being finally
>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>> changes to
>>>>>>>> the branch and then committing
>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>> Xalan)*
>>>>>>>>
>>>>>>>>
>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>
>> changes
>>
>>>>>>>> done in "javax.xml.transform" package
>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>> invoking reset().
>>>>>>>>
>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>> branch
>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>>> chance
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> to look at it before these changes being finally
>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>> for this
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> process.
>>>>>>>>
>>>>>>>>
>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>> [2]
>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>> [3]
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>
>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> [4]
>>>>>>>>
>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>
>>>>>>>> summary.html
>>>>>>>>
>>>>>>>>
>>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Michael Glavassevich
>>>>>>> XML Parser Development
>>>>>>> IBM Toronto Lab
>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>
>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>
>> Michael Glavassevich
>> XML Parser Development
>> IBM Toronto Lab
>> E-mail: mrglavas@ca.ibm.com
>> E-mail: mrglavas@apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ok, So i will add it and upload again.
- Neeraj
Geir Magnusson Jr. wrote:
>
> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>
>> Hi Neeraj,
>>
>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>> license. Will this still be the case for JAXP 1.3?
>
>
> yes - these files must be available under the apache license v2. And
> the license grantor should be the one that adds it.
>
> Sorry Neeraj :)
>
> geir
>
>>
>> Thanks.
>>
>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>
>>> Ok I just finished uploading JAXP 1.3 sources in
>>> "*xml-commons/contrib/jaxp13"* directory.
>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>> which
>>> corresponds to jaxp-api,
>>> xerces & xalan sources respectively.
>>>
>>> - Neeraj
>>>
>>> Neeraj Bajaj wrote:
>>>
>>>> That really sounds good to me.. so i would try to finish it today.
>>>> I will send mail to the community when i am done.
>>>>
>>>> Thanks dims for the suggestion.
>>>>
>>>> - Neeraj
>>>>
>>>> Davanum Srinivas wrote:
>>>>
>>>>> Neeraj,
>>>>>
>>>>> my 2 cents...upload the whole thing say in
>>>>> xml-commons/contrib/jaxp13
>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>
>>>>> thanks,
>>>>> dims
>>>>>
>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>
>>>>>
>>>>>> Thanks Michael for your response.
>>>>>>
>>>>>> I was just wondering what would be idle time to wait before i start
>>>>>> work
>>>>>> on this ?
>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>
>> send
>>
>>>>>> this mail
>>>>>> before making changes ?
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Michael Glavassevich wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hi Neeraj,
>>>>>>>
>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>
>> and
>>
>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>> trunk.
>>>>>>>
>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>> updates
>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>> we've
>>>>>>
>>
>>>>>>> used
>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>> assume a
>>>>>>> similar branch will exist for 1.3.
>>>>>>>
>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>
>> AM:
>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>> zip but
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> mail bounced back with the following message
>>>>>>>>
>>>>>>>> <error>
>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>> <ge...@xml.apache.org>
>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>> </error>
>>>>>>>>
>>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>>> server somewhere ?
>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>
>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>> community
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> to help put it in a
>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>> number of
>>>>>>>> changes it would be a considerable
>>>>>>>> amount of work. This will also help the committers & community to
>>>>>>>> have a
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> look at the code before
>>>>>>>> it is merged into the main stream work.
>>>>>>>>
>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>> sources
>>>>>>>> in xml-commons branch
>>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
>>>>>>>
>> the
>>
>>>>>>>> opinion of community ? I can
>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>> preference is to put the sources on
>>>>>>>> xml-commons main trunk.
>>>>>>>>
>>>>>>>> Please let me know how should i proceed.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>> implementation to Apache XML.*
>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>> functionalities.
>>>>>>>>
>>>>>>>> * New Schema Validation Framework
>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>> * Reuse parser instance
>>>>>>>> * Security enhancements
>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>> Save, SAX
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>
>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>
>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>> for the
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>
>>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>> Xalan.
>>>>>>>> There was a general consensus to my proposal
>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>> in the
>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>> community.
>>>>>>>>
>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>>> ball
>>>>>>>>>>> on this one.
>>>>>>>>>>>
>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>>> that
>>>>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev,
>>>>>>>>>>> and
>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>> achieved.
>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>> process
>>>>>>>>>> hold things up.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>> ----------------------------------------------------------------------
>>> --
>>
>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Subject:
>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>> From:
>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>> Date:
>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>
>>>>>>>> To:
>>>>>>>> general@xml.apache.org
>>>>>>>> CC:
>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>
>> <Je...@Sun.COM>,
>>
>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>>
>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>> final. JAXP
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>> It allows to compile Schema to an immutable memory representation
>>>>>>>
>> of
>>
>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>
>> thus
>>
>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>
>> language
>>
>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>> of an
>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>> access to
>>>>>>>
>>
>>>>>>>> the
>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>> Datatypes to
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>>> also
>>>>>>>
>>
>>>>>>>> adds
>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>
>> allowing
>>
>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>
>> performance.
>>
>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>> L/S, XML
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 1.1, XInclude.
>>>>>>>>
>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>
>>>>>>>>
>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>
>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>
>> (Reference
>>
>>>>>>>> Implementation). RI has been done using
>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>> newly
>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>> Transformer
>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>> XInclude
>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>> section I have also proposed the way to merge rest of the JAXP
>>>>>>>> 1.3
>>>>>>>
>> RI
>>
>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>> Xerces
>>>>>>>
>> or
>>
>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>> Xerces &
>>>>>>>> Xalan is very welcome.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>
>>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>>> APIs
>>>>>>>> are used by many different projects.
>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>> emerging, we
>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>>> trunk
>>>>>>>> and apply a tag.
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Xerces)*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>
>>>>>>>> javax.xml.datatype
>>>>>>>> javax.xml.validation
>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>
>>>>>>>> which should reside at Xerces.
>>>>>>>>
>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>
>> into
>>
>>>>>>>> that branch. This will help
>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>
>> before
>>
>>>>>>>> these changes being finally
>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>> changes to
>>>>>>>> the branch and then committing
>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>> Xalan)*
>>>>>>>>
>>>>>>>>
>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>
>> changes
>>
>>>>>>>> done in "javax.xml.transform" package
>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>> invoking reset().
>>>>>>>>
>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>> branch
>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>>> chance
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> to look at it before these changes being finally
>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>> for this
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> process.
>>>>>>>>
>>>>>>>>
>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>> [2]
>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>> [3]
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>
>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> [4]
>>>>>>>>
>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>
>>>>>>>> summary.html
>>>>>>>>
>>>>>>>>
>>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Michael Glavassevich
>>>>>>> XML Parser Development
>>>>>>> IBM Toronto Lab
>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>
>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>
>> Michael Glavassevich
>> XML Parser Development
>> IBM Toronto Lab
>> E-mail: mrglavas@ca.ibm.com
>> E-mail: mrglavas@apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ok, So i will add it and upload again.
- Neeraj
Geir Magnusson Jr. wrote:
>
> On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
>
>> Hi Neeraj,
>>
>> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
>> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
>> license. Will this still be the case for JAXP 1.3?
>
>
> yes - these files must be available under the apache license v2. And
> the license grantor should be the one that adds it.
>
> Sorry Neeraj :)
>
> geir
>
>>
>> Thanks.
>>
>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>>
>>> Ok I just finished uploading JAXP 1.3 sources in
>>> "*xml-commons/contrib/jaxp13"* directory.
>>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>>> which
>>> corresponds to jaxp-api,
>>> xerces & xalan sources respectively.
>>>
>>> - Neeraj
>>>
>>> Neeraj Bajaj wrote:
>>>
>>>> That really sounds good to me.. so i would try to finish it today.
>>>> I will send mail to the community when i am done.
>>>>
>>>> Thanks dims for the suggestion.
>>>>
>>>> - Neeraj
>>>>
>>>> Davanum Srinivas wrote:
>>>>
>>>>> Neeraj,
>>>>>
>>>>> my 2 cents...upload the whole thing say in
>>>>> xml-commons/contrib/jaxp13
>>>>> cvs so everyone can take a look (and then pick on the bits they
>>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>>> tagging the current code in the main trunk there) and it's upto the
>>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>>
>>>>> thanks,
>>>>> dims
>>>>>
>>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>>
>>>>>
>>>>>> Thanks Michael for your response.
>>>>>>
>>>>>> I was just wondering what would be idle time to wait before i start
>>>>>> work
>>>>>> on this ?
>>>>>> Does anyone has an opinion, Is there any other list where i should
>>>>>
>> send
>>
>>>>>> this mail
>>>>>> before making changes ?
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> Michael Glavassevich wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hi Neeraj,
>>>>>>>
>>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
>>>>>>
>> and
>>
>>>>>>> making a branch for the old JAXP sources on the current main
>>>>>>> trunk.
>>>>>>>
>>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>>> updates
>>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>>> we've
>>>>>>
>>
>>>>>>> used
>>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>>> assume a
>>>>>>> similar branch will exist for 1.3.
>>>>>>>
>>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
>>>>>>
>> AM:
>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>>> zip but
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> mail bounced back with the following message
>>>>>>>>
>>>>>>>> <error>
>>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>>> <ge...@xml.apache.org>
>>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>>> </error>
>>>>>>>>
>>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>>> server somewhere ?
>>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>>
>>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>>> community
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> to help put it in a
>>>>>>>> a branch and make it work there. As i think due to large
>>>>>>>> number of
>>>>>>>> changes it would be a considerable
>>>>>>>> amount of work. This will also help the committers & community to
>>>>>>>> have a
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> look at the code before
>>>>>>>> it is merged into the main stream work.
>>>>>>>>
>>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>>> sources
>>>>>>>> in xml-commons branch
>>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
>>>>>>>
>> the
>>
>>>>>>>> opinion of community ? I can
>>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>>> preference is to put the sources on
>>>>>>>> xml-commons main trunk.
>>>>>>>>
>>>>>>>> Please let me know how should i proceed.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>>> implementation to Apache XML.*
>>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>>> functionalities.
>>>>>>>>
>>>>>>>> * New Schema Validation Framework
>>>>>>>> * New Object Model neutral XPath APIs
>>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>>> * Reuse parser instance
>>>>>>>> * Security enhancements
>>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>>> Save, SAX
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>>
>>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>>
>>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>>> for the
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> source code of Xerces & Xalan.
>>>>>>>>
>>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>>> Xalan.
>>>>>>>> There was a general consensus to my proposal
>>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>>> in the
>>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>>> community.
>>>>>>>>
>>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Neeraj Bajaj wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>>> ball
>>>>>>>>>>> on this one.
>>>>>>>>>>>
>>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>>> that
>>>>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev,
>>>>>>>>>>> and
>>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>>> achieved.
>>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>>> process
>>>>>>>>>> hold things up.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>>
>>>>>>>>> - Neeraj
>>>>>>>>>
>>>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>> ----------------------------------------------------------------------
>>> --
>>
>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Subject:
>>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>>> From:
>>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>>> Date:
>>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>>
>>>>>>>> To:
>>>>>>>> general@xml.apache.org
>>>>>>>> CC:
>>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
>>>>>>>
>> <Je...@Sun.COM>,
>>
>>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello All,
>>>>>>>>
>>>>>>>>
>>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>>> final. JAXP
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>>> It introduces new Schema independent validation framework which
>>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>>> It allows to compile Schema to an immutable memory representation
>>>>>>>
>> of
>>
>>>>>>>> Grammar which can validate different instances of XML document
>>>>>>>
>> thus
>>
>>>>>>>> greatly improving the performance of XML processing. XPath
>>>>>>>
>> language
>>
>>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>>> of an
>>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides
>>>>>>>> access to
>>>>>>>
>>
>>>>>>>> the
>>>>>>>> XPath evaluation environment and expression results independent
>>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>>> Datatypes to
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>>> also
>>>>>>>
>>
>>>>>>>> adds
>>>>>>>> the ability to reset XML Parser and Transformer instance ,
>>>>>>>
>> allowing
>>
>>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>>> documents. This also helps in increasing XML processing
>>>>>>>
>> performance.
>>
>>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>>> L/S, XML
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 1.1, XInclude.
>>>>>>>>
>>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>>> Reference Implementation) to Apache. *
>>>>>>>>
>>>>>>>>
>>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>>
>>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
>>>>>>>
>> (Reference
>>
>>>>>>>> Implementation). RI has been done using
>>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>>> newly
>>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>>> Transformer
>>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>>> XInclude
>>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>>> section I have also proposed the way to merge rest of the JAXP
>>>>>>>> 1.3
>>>>>>>
>> RI
>>
>>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>>> suggested where implementation component should reside i.e.
>>>>>>>> Xerces
>>>>>>>
>> or
>>
>>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>>> Xerces &
>>>>>>>> Xalan is very welcome.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>>
>>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>>> APIs
>>>>>>>> are used by many different projects.
>>>>>>>> With JSR 206 declared as final and many new standards
>>>>>>>> emerging, we
>>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>>> trunk
>>>>>>>> and apply a tag.
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Xerces)*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>>
>>>>>>>> javax.xml.datatype
>>>>>>>> javax.xml.validation
>>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>>
>>>>>>>> which should reside at Xerces.
>>>>>>>>
>>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
>>>>>>>
>> into
>>
>>>>>>>> that branch. This will help
>>>>>>>> other Xerces active committers to have a chance to look at it
>>>>>>>
>> before
>>
>>>>>>>> these changes being finally
>>>>>>>> committed to main trunk. This process would require merging
>>>>>>>> changes to
>>>>>>>> the branch and then committing
>>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>>
>>>>>>>>
>>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>> Xalan)*
>>>>>>>>
>>>>>>>>
>>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
>>>>>>>
>> changes
>>
>>>>>>>> done in "javax.xml.transform" package
>>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>>> invoking reset().
>>>>>>>>
>>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>>> branch
>>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>>> chance
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> to look at it before these changes being finally
>>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>>> for this
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> process.
>>>>>>>>
>>>>>>>>
>>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Neeraj
>>>>>>>>
>>>>>>>>
>>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>>> [2]
>>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>>> [3]
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>
>>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> [4]
>>>>>>>>
>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>
>>>>>>>> summary.html
>>>>>>>>
>>>>>>>>
>>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Michael Glavassevich
>>>>>>> XML Parser Development
>>>>>>> IBM Toronto Lab
>>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>>> E-mail: mrglavas@apache.org
>>>>>>>
>>>>>>>
>> ---------------------------------------------------------------------
>>
>>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>
>> Michael Glavassevich
>> XML Parser Development
>> IBM Toronto Lab
>> E-mail: mrglavas@ca.ibm.com
>> E-mail: mrglavas@apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
> Hi Neeraj,
>
> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
> license. Will this still be the case for JAXP 1.3?
yes - these files must be available under the apache license v2. And
the license grantor should be the one that adds it.
Sorry Neeraj :)
geir
>
> Thanks.
>
> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>
>> Ok I just finished uploading JAXP 1.3 sources in
>> "*xml-commons/contrib/jaxp13"* directory.
>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>> which
>> corresponds to jaxp-api,
>> xerces & xalan sources respectively.
>>
>> - Neeraj
>>
>> Neeraj Bajaj wrote:
>>
>>> That really sounds good to me.. so i would try to finish it today.
>>> I will send mail to the community when i am done.
>>>
>>> Thanks dims for the suggestion.
>>>
>>> - Neeraj
>>>
>>> Davanum Srinivas wrote:
>>>
>>>> Neeraj,
>>>>
>>>> my 2 cents...upload the whole thing say in
>>>> xml-commons/contrib/jaxp13
>>>> cvs so everyone can take a look (and then pick on the bits they
>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>> tagging the current code in the main trunk there) and it's upto the
>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>
>>>> thanks,
>>>> dims
>>>>
>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>
>>>>
>>>>> Thanks Michael for your response.
>>>>>
>>>>> I was just wondering what would be idle time to wait before i start
>>>>> work
>>>>> on this ?
>>>>> Does anyone has an opinion, Is there any other list where i should
> send
>>>>> this mail
>>>>> before making changes ?
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Michael Glavassevich wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hi Neeraj,
>>>>>>
>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
> and
>>>>>> making a branch for the old JAXP sources on the current main
>>>>>> trunk.
>>>>>>
>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>> updates
>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>> we've
>
>>>>>> used
>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>> assume a
>>>>>> similar branch will exist for 1.3.
>>>>>>
>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
> AM:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hello All,
>>>>>>>
>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>> zip but
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> mail bounced back with the following message
>>>>>>>
>>>>>>> <error>
>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>> <ge...@xml.apache.org>
>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>> </error>
>>>>>>>
>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>> server somewhere ?
>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>
>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>> community
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> to help put it in a
>>>>>>> a branch and make it work there. As i think due to large number
>>>>>>> of
>>>>>>> changes it would be a considerable
>>>>>>> amount of work. This will also help the committers & community to
>>>>>>> have a
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> look at the code before
>>>>>>> it is merged into the main stream work.
>>>>>>>
>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>> sources
>>>>>>> in xml-commons branch
>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
> the
>>>>>>> opinion of community ? I can
>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>> preference is to put the sources on
>>>>>>> xml-commons main trunk.
>>>>>>>
>>>>>>> Please let me know how should i proceed.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>>
>>>>>>> Hello All,
>>>>>>>
>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>> implementation to Apache XML.*
>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>> functionalities.
>>>>>>>
>>>>>>> * New Schema Validation Framework
>>>>>>> * New Object Model neutral XPath APIs
>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>> * Reuse parser instance
>>>>>>> * Security enhancements
>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>> Save, SAX
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>
>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>
>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>> for the
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> source code of Xerces & Xalan.
>>>>>>>
>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>> Xalan.
>>>>>>> There was a general consensus to my proposal
>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>> in the
>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>> community.
>>>>>>>
>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Neeraj Bajaj wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>> ball
>>>>>>>>>> on this one.
>>>>>>>>>>
>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>> that
>>>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev,
>>>>>>>>>> and
>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>> achieved.
>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>> process
>>>>>>>>> hold things up.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail:
>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>> ----------------------------------------------------------------------
>> --
>
>>>>>>>
>>>>>>>
>>>>>>> Subject:
>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>> From:
>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>> Date:
>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>
>>>>>>> To:
>>>>>>> general@xml.apache.org
>>>>>>> CC:
>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
> <Je...@Sun.COM>,
>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>
>>>>>>>
>>>>>>> Hello All,
>>>>>>>
>>>>>>>
>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>> final. JAXP
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>> It introduces new Schema independent validation framework which
>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>> It allows to compile Schema to an immutable memory representation
> of
>>>>>>> Grammar which can validate different instances of XML document
> thus
>>>>>>> greatly improving the performance of XML processing. XPath
> language
>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>> of an
>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides access
>>>>>>> to
>
>>>>>>> the
>>>>>>> XPath evaluation environment and expression results independent
>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>> Datatypes to
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>> also
>
>>>>>>> adds
>>>>>>> the ability to reset XML Parser and Transformer instance ,
> allowing
>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>> documents. This also helps in increasing XML processing
> performance.
>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>> L/S, XML
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 1.1, XInclude.
>>>>>>>
>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>> Reference Implementation) to Apache. *
>>>>>>>
>>>>>>>
>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>
>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
> (Reference
>>>>>>> Implementation). RI has been done using
>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>> newly
>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>> Transformer
>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>> XInclude
>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>> section I have also proposed the way to merge rest of the JAXP
>>>>>>> 1.3
> RI
>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>> suggested where implementation component should reside i.e.
>>>>>>> Xerces
> or
>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>> Xerces &
>>>>>>> Xalan is very welcome.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>
>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>> APIs
>>>>>>> are used by many different projects.
>>>>>>> With JSR 206 declared as final and many new standards emerging,
>>>>>>> we
>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>> trunk
>>>>>>> and apply a tag.
>>>>>>>
>>>>>>>
>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Xerces)*
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>
>>>>>>> javax.xml.datatype
>>>>>>> javax.xml.validation
>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>
>>>>>>> which should reside at Xerces.
>>>>>>>
>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
> into
>>>>>>> that branch. This will help
>>>>>>> other Xerces active committers to have a chance to look at it
> before
>>>>>>> these changes being finally
>>>>>>> committed to main trunk. This process would require merging
>>>>>>> changes to
>>>>>>> the branch and then committing
>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>
>>>>>>>
>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>> Xalan)*
>>>>>>>
>>>>>>>
>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
> changes
>>>>>>> done in "javax.xml.transform" package
>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>> invoking reset().
>>>>>>>
>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>> branch
>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>> chance
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> to look at it before these changes being finally
>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>> for this
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> process.
>>>>>>>
>>>>>>>
>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Neeraj
>>>>>>>
>>>>>>>
>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>> [2]
>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>> [3]
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> http://java.sun.com/j2se/1.5.
>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> [4]
>>>>>>>
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>>> summary.html
>>>>>>>
>>>>>>>
>>>>>>>
> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Michael Glavassevich
>>>>>> XML Parser Development
>>>>>> IBM Toronto Lab
>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>> E-mail: mrglavas@apache.org
>>>>>>
>>>>>>
> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
> Hi Neeraj,
>
> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
> license. Will this still be the case for JAXP 1.3?
yes - these files must be available under the apache license v2. And
the license grantor should be the one that adds it.
Sorry Neeraj :)
geir
>
> Thanks.
>
> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>
>> Ok I just finished uploading JAXP 1.3 sources in
>> "*xml-commons/contrib/jaxp13"* directory.
>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>> which
>> corresponds to jaxp-api,
>> xerces & xalan sources respectively.
>>
>> - Neeraj
>>
>> Neeraj Bajaj wrote:
>>
>>> That really sounds good to me.. so i would try to finish it today.
>>> I will send mail to the community when i am done.
>>>
>>> Thanks dims for the suggestion.
>>>
>>> - Neeraj
>>>
>>> Davanum Srinivas wrote:
>>>
>>>> Neeraj,
>>>>
>>>> my 2 cents...upload the whole thing say in
>>>> xml-commons/contrib/jaxp13
>>>> cvs so everyone can take a look (and then pick on the bits they
>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>> tagging the current code in the main trunk there) and it's upto the
>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>
>>>> thanks,
>>>> dims
>>>>
>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>
>>>>
>>>>> Thanks Michael for your response.
>>>>>
>>>>> I was just wondering what would be idle time to wait before i start
>>>>> work
>>>>> on this ?
>>>>> Does anyone has an opinion, Is there any other list where i should
> send
>>>>> this mail
>>>>> before making changes ?
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Michael Glavassevich wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hi Neeraj,
>>>>>>
>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
> and
>>>>>> making a branch for the old JAXP sources on the current main
>>>>>> trunk.
>>>>>>
>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>> updates
>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>> we've
>
>>>>>> used
>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>> assume a
>>>>>> similar branch will exist for 1.3.
>>>>>>
>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
> AM:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hello All,
>>>>>>>
>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>> zip but
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> mail bounced back with the following message
>>>>>>>
>>>>>>> <error>
>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>> <ge...@xml.apache.org>
>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>> </error>
>>>>>>>
>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>> server somewhere ?
>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>
>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>> community
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> to help put it in a
>>>>>>> a branch and make it work there. As i think due to large number
>>>>>>> of
>>>>>>> changes it would be a considerable
>>>>>>> amount of work. This will also help the committers & community to
>>>>>>> have a
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> look at the code before
>>>>>>> it is merged into the main stream work.
>>>>>>>
>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>> sources
>>>>>>> in xml-commons branch
>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
> the
>>>>>>> opinion of community ? I can
>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>> preference is to put the sources on
>>>>>>> xml-commons main trunk.
>>>>>>>
>>>>>>> Please let me know how should i proceed.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>>
>>>>>>> Hello All,
>>>>>>>
>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>> implementation to Apache XML.*
>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>> functionalities.
>>>>>>>
>>>>>>> * New Schema Validation Framework
>>>>>>> * New Object Model neutral XPath APIs
>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>> * Reuse parser instance
>>>>>>> * Security enhancements
>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>> Save, SAX
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>
>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>
>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>> for the
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> source code of Xerces & Xalan.
>>>>>>>
>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>> Xalan.
>>>>>>> There was a general consensus to my proposal
>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>> in the
>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>> community.
>>>>>>>
>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Neeraj Bajaj wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>> ball
>>>>>>>>>> on this one.
>>>>>>>>>>
>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>> that
>>>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev,
>>>>>>>>>> and
>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>> achieved.
>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>> process
>>>>>>>>> hold things up.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail:
>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>> ----------------------------------------------------------------------
>> --
>
>>>>>>>
>>>>>>>
>>>>>>> Subject:
>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>> From:
>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>> Date:
>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>
>>>>>>> To:
>>>>>>> general@xml.apache.org
>>>>>>> CC:
>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
> <Je...@Sun.COM>,
>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>
>>>>>>>
>>>>>>> Hello All,
>>>>>>>
>>>>>>>
>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>> final. JAXP
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>> It introduces new Schema independent validation framework which
>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>> It allows to compile Schema to an immutable memory representation
> of
>>>>>>> Grammar which can validate different instances of XML document
> thus
>>>>>>> greatly improving the performance of XML processing. XPath
> language
>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>> of an
>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides access
>>>>>>> to
>
>>>>>>> the
>>>>>>> XPath evaluation environment and expression results independent
>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>> Datatypes to
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>> also
>
>>>>>>> adds
>>>>>>> the ability to reset XML Parser and Transformer instance ,
> allowing
>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>> documents. This also helps in increasing XML processing
> performance.
>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>> L/S, XML
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 1.1, XInclude.
>>>>>>>
>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>> Reference Implementation) to Apache. *
>>>>>>>
>>>>>>>
>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>
>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
> (Reference
>>>>>>> Implementation). RI has been done using
>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>> newly
>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>> Transformer
>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>> XInclude
>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>> section I have also proposed the way to merge rest of the JAXP
>>>>>>> 1.3
> RI
>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>> suggested where implementation component should reside i.e.
>>>>>>> Xerces
> or
>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>> Xerces &
>>>>>>> Xalan is very welcome.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>
>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>> APIs
>>>>>>> are used by many different projects.
>>>>>>> With JSR 206 declared as final and many new standards emerging,
>>>>>>> we
>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>> trunk
>>>>>>> and apply a tag.
>>>>>>>
>>>>>>>
>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Xerces)*
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>
>>>>>>> javax.xml.datatype
>>>>>>> javax.xml.validation
>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>
>>>>>>> which should reside at Xerces.
>>>>>>>
>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
> into
>>>>>>> that branch. This will help
>>>>>>> other Xerces active committers to have a chance to look at it
> before
>>>>>>> these changes being finally
>>>>>>> committed to main trunk. This process would require merging
>>>>>>> changes to
>>>>>>> the branch and then committing
>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>
>>>>>>>
>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>> Xalan)*
>>>>>>>
>>>>>>>
>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
> changes
>>>>>>> done in "javax.xml.transform" package
>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>> invoking reset().
>>>>>>>
>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>> branch
>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>> chance
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> to look at it before these changes being finally
>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>> for this
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> process.
>>>>>>>
>>>>>>>
>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Neeraj
>>>>>>>
>>>>>>>
>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>> [2]
>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>> [3]
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> http://java.sun.com/j2se/1.5.
>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> [4]
>>>>>>>
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>>> summary.html
>>>>>>>
>>>>>>>
>>>>>>>
> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Michael Glavassevich
>>>>>> XML Parser Development
>>>>>> IBM Toronto Lab
>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>> E-mail: mrglavas@apache.org
>>>>>>
>>>>>>
> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
> Hi Neeraj,
>
> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
> license. Will this still be the case for JAXP 1.3?
yes - these files must be available under the apache license v2. And
the license grantor should be the one that adds it.
Sorry Neeraj :)
geir
>
> Thanks.
>
> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>
>> Ok I just finished uploading JAXP 1.3 sources in
>> "*xml-commons/contrib/jaxp13"* directory.
>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>> which
>> corresponds to jaxp-api,
>> xerces & xalan sources respectively.
>>
>> - Neeraj
>>
>> Neeraj Bajaj wrote:
>>
>>> That really sounds good to me.. so i would try to finish it today.
>>> I will send mail to the community when i am done.
>>>
>>> Thanks dims for the suggestion.
>>>
>>> - Neeraj
>>>
>>> Davanum Srinivas wrote:
>>>
>>>> Neeraj,
>>>>
>>>> my 2 cents...upload the whole thing say in
>>>> xml-commons/contrib/jaxp13
>>>> cvs so everyone can take a look (and then pick on the bits they
>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>> tagging the current code in the main trunk there) and it's upto the
>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>
>>>> thanks,
>>>> dims
>>>>
>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>
>>>>
>>>>> Thanks Michael for your response.
>>>>>
>>>>> I was just wondering what would be idle time to wait before i start
>>>>> work
>>>>> on this ?
>>>>> Does anyone has an opinion, Is there any other list where i should
> send
>>>>> this mail
>>>>> before making changes ?
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Michael Glavassevich wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hi Neeraj,
>>>>>>
>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
> and
>>>>>> making a branch for the old JAXP sources on the current main
>>>>>> trunk.
>>>>>>
>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>> updates
>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>> we've
>
>>>>>> used
>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>> assume a
>>>>>> similar branch will exist for 1.3.
>>>>>>
>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
> AM:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hello All,
>>>>>>>
>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>> zip but
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> mail bounced back with the following message
>>>>>>>
>>>>>>> <error>
>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>> <ge...@xml.apache.org>
>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>> </error>
>>>>>>>
>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>> server somewhere ?
>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>
>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>> community
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> to help put it in a
>>>>>>> a branch and make it work there. As i think due to large number
>>>>>>> of
>>>>>>> changes it would be a considerable
>>>>>>> amount of work. This will also help the committers & community to
>>>>>>> have a
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> look at the code before
>>>>>>> it is merged into the main stream work.
>>>>>>>
>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>> sources
>>>>>>> in xml-commons branch
>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
> the
>>>>>>> opinion of community ? I can
>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>> preference is to put the sources on
>>>>>>> xml-commons main trunk.
>>>>>>>
>>>>>>> Please let me know how should i proceed.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>>
>>>>>>> Hello All,
>>>>>>>
>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>> implementation to Apache XML.*
>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>> functionalities.
>>>>>>>
>>>>>>> * New Schema Validation Framework
>>>>>>> * New Object Model neutral XPath APIs
>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>> * Reuse parser instance
>>>>>>> * Security enhancements
>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>> Save, SAX
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>
>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>
>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>> for the
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> source code of Xerces & Xalan.
>>>>>>>
>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>> Xalan.
>>>>>>> There was a general consensus to my proposal
>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>> in the
>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>> community.
>>>>>>>
>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Neeraj Bajaj wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>> ball
>>>>>>>>>> on this one.
>>>>>>>>>>
>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>> that
>>>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev,
>>>>>>>>>> and
>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>> achieved.
>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>> process
>>>>>>>>> hold things up.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail:
>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>> ----------------------------------------------------------------------
>> --
>
>>>>>>>
>>>>>>>
>>>>>>> Subject:
>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>> From:
>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>> Date:
>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>
>>>>>>> To:
>>>>>>> general@xml.apache.org
>>>>>>> CC:
>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
> <Je...@Sun.COM>,
>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>
>>>>>>>
>>>>>>> Hello All,
>>>>>>>
>>>>>>>
>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>> final. JAXP
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>> It introduces new Schema independent validation framework which
>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>> It allows to compile Schema to an immutable memory representation
> of
>>>>>>> Grammar which can validate different instances of XML document
> thus
>>>>>>> greatly improving the performance of XML processing. XPath
> language
>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>> of an
>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides access
>>>>>>> to
>
>>>>>>> the
>>>>>>> XPath evaluation environment and expression results independent
>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>> Datatypes to
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>> also
>
>>>>>>> adds
>>>>>>> the ability to reset XML Parser and Transformer instance ,
> allowing
>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>> documents. This also helps in increasing XML processing
> performance.
>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>> L/S, XML
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 1.1, XInclude.
>>>>>>>
>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>> Reference Implementation) to Apache. *
>>>>>>>
>>>>>>>
>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>
>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
> (Reference
>>>>>>> Implementation). RI has been done using
>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>> newly
>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>> Transformer
>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>> XInclude
>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>> section I have also proposed the way to merge rest of the JAXP
>>>>>>> 1.3
> RI
>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>> suggested where implementation component should reside i.e.
>>>>>>> Xerces
> or
>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>> Xerces &
>>>>>>> Xalan is very welcome.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>
>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>> APIs
>>>>>>> are used by many different projects.
>>>>>>> With JSR 206 declared as final and many new standards emerging,
>>>>>>> we
>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>> trunk
>>>>>>> and apply a tag.
>>>>>>>
>>>>>>>
>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Xerces)*
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>
>>>>>>> javax.xml.datatype
>>>>>>> javax.xml.validation
>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>
>>>>>>> which should reside at Xerces.
>>>>>>>
>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
> into
>>>>>>> that branch. This will help
>>>>>>> other Xerces active committers to have a chance to look at it
> before
>>>>>>> these changes being finally
>>>>>>> committed to main trunk. This process would require merging
>>>>>>> changes to
>>>>>>> the branch and then committing
>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>
>>>>>>>
>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>> Xalan)*
>>>>>>>
>>>>>>>
>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
> changes
>>>>>>> done in "javax.xml.transform" package
>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>> invoking reset().
>>>>>>>
>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>> branch
>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>> chance
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> to look at it before these changes being finally
>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>> for this
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> process.
>>>>>>>
>>>>>>>
>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Neeraj
>>>>>>>
>>>>>>>
>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>> [2]
>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>> [3]
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> http://java.sun.com/j2se/1.5.
>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> [4]
>>>>>>>
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>>> summary.html
>>>>>>>
>>>>>>>
>>>>>>>
> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Michael Glavassevich
>>>>>> XML Parser Development
>>>>>> IBM Toronto Lab
>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>> E-mail: mrglavas@apache.org
>>>>>>
>>>>>>
> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Apr 6, 2005, at 12:44 AM, Michael Glavassevich wrote:
> Hi Neeraj,
>
> I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
> license on them. The JAXP 1.2 sources in xml-commons carry the Apache
> license. Will this still be the case for JAXP 1.3?
yes - these files must be available under the apache license v2. And
the license grantor should be the one that adds it.
Sorry Neeraj :)
geir
>
> Thanks.
>
> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
>
>> Ok I just finished uploading JAXP 1.3 sources in
>> "*xml-commons/contrib/jaxp13"* directory.
>> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip
>> which
>> corresponds to jaxp-api,
>> xerces & xalan sources respectively.
>>
>> - Neeraj
>>
>> Neeraj Bajaj wrote:
>>
>>> That really sounds good to me.. so i would try to finish it today.
>>> I will send mail to the community when i am done.
>>>
>>> Thanks dims for the suggestion.
>>>
>>> - Neeraj
>>>
>>> Davanum Srinivas wrote:
>>>
>>>> Neeraj,
>>>>
>>>> my 2 cents...upload the whole thing say in
>>>> xml-commons/contrib/jaxp13
>>>> cvs so everyone can take a look (and then pick on the bits they
>>>> want/need)...yes, changes to xml-commons can be made ASAP (after
>>>> tagging the current code in the main trunk there) and it's upto the
>>>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>>>
>>>> thanks,
>>>> dims
>>>>
>>>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>>>
>>>>
>>>>> Thanks Michael for your response.
>>>>>
>>>>> I was just wondering what would be idle time to wait before i start
>>>>> work
>>>>> on this ?
>>>>> Does anyone has an opinion, Is there any other list where i should
> send
>>>>> this mail
>>>>> before making changes ?
>>>>>
>>>>> - Neeraj
>>>>>
>>>>> Michael Glavassevich wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hi Neeraj,
>>>>>>
>>>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
> and
>>>>>> making a branch for the old JAXP sources on the current main
>>>>>> trunk.
>>>>>>
>>>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>>>> updates
>>>>>> have been applied to the JAXP 1.2 sources. This is the branch
>>>>>> we've
>
>>>>>> used
>>>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>>>> assume a
>>>>>> similar branch will exist for 1.3.
>>>>>>
>>>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
> AM:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hello All,
>>>>>>>
>>>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>>>> zip but
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> mail bounced back with the following message
>>>>>>>
>>>>>>> <error>
>>>>>>> ----- The following addresses had permanent fatal errors -----
>>>>>>> <ge...@xml.apache.org>
>>>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>>>> </error>
>>>>>>>
>>>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>>>> server somewhere ?
>>>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>>>
>>>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>>>> community
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> to help put it in a
>>>>>>> a branch and make it work there. As i think due to large number
>>>>>>> of
>>>>>>> changes it would be a considerable
>>>>>>> amount of work. This will also help the committers & community to
>>>>>>> have a
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> look at the code before
>>>>>>> it is merged into the main stream work.
>>>>>>>
>>>>>>> I think i have commit access at xml-commons so i can commit the
>>>>>>> sources
>>>>>>> in xml-commons branch
>>>>>>> or main trunk (and create branch for old jaxp sources ). What is
> the
>>>>>>> opinion of community ? I can
>>>>>>> start this as soon as i get a consensus from the community. My
>>>>>>> preference is to put the sources on
>>>>>>> xml-commons main trunk.
>>>>>>>
>>>>>>> Please let me know how should i proceed.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>>
>>>>>>> Hello All,
>>>>>>>
>>>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>>>> implementation to Apache XML.*
>>>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>>>> functionalities.
>>>>>>>
>>>>>>> * New Schema Validation Framework
>>>>>>> * New Object Model neutral XPath APIs
>>>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>>>> * Reuse parser instance
>>>>>>> * Security enhancements
>>>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>>>> Save, SAX
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 2, XML 1.1 and XInclude)
>>>>>>>
>>>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>>>
>>>>>>> Due to large size of code base i will be sending different mails
>>>>>>> for the
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> source code of Xerces & Xalan.
>>>>>>>
>>>>>>> I have attached the original mail where i proposed the process of
>>>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>>>> integrating this donation into the main stream work of Xerces &
>>>>>>> Xalan.
>>>>>>> There was a general consensus to my proposal
>>>>>>> and we can discuss more about the technicalities of merging with
>>>>>>> in the
>>>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>>>> community.
>>>>>>>
>>>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>>>
>>>>>>> - Neeraj
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Neeraj Bajaj wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Geir Magnusson Jr. wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>>>> ball
>>>>>>>>>> on this one.
>>>>>>>>>>
>>>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume
>>>>>>>>>> that
>>>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev,
>>>>>>>>>> and
>>>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>>>> achieved.
>>>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>>>> process
>>>>>>>>> hold things up.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>>>
>>>>>>>> - Neeraj
>>>>>>>>
>>>>>>>>
> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>>> For additional commands, e-mail:
>>>>>>>> xerces-j-dev-help@xml.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>> ----------------------------------------------------------------------
>> --
>
>>>>>>>
>>>>>>>
>>>>>>> Subject:
>>>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>>>> From:
>>>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>>>> Date:
>>>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>>>
>>>>>>> To:
>>>>>>> general@xml.apache.org
>>>>>>> CC:
>>>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>>>> <Ed...@Sun.COM>, Jeff Suttor
> <Je...@Sun.COM>,
>>>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>>>
>>>>>>>
>>>>>>> Hello All,
>>>>>>>
>>>>>>>
>>>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>>>> final. JAXP
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>>>> It introduces new Schema independent validation framework which
>>>>>>> decouples the validation as a process independent from parsing.
>>>>>>> It allows to compile Schema to an immutable memory representation
> of
>>>>>>> Grammar which can validate different instances of XML document
> thus
>>>>>>> greatly improving the performance of XML processing. XPath
> language
>>>>>>> provides a simple, concise syntax for accessing individual parts
>>>>>>> of an
>>>>>>> XML document. JAXP 1.3 defines XPath APIs which provides access
>>>>>>> to
>
>>>>>>> the
>>>>>>> XPath evaluation environment and expression results independent
>>>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>>>> Datatypes to
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3
>>>>>>> also
>
>>>>>>> adds
>>>>>>> the ability to reset XML Parser and Transformer instance ,
> allowing
>>>>>>> application to reuse the same instance to process multiple XML
>>>>>>> documents. This also helps in increasing XML processing
> performance.
>>>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>>>> L/S, XML
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 1.1, XInclude.
>>>>>>>
>>>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>>>> Reference Implementation) to Apache. *
>>>>>>>
>>>>>>>
>>>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>>>
>>>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
> (Reference
>>>>>>> Implementation). RI has been done using
>>>>>>> Xerces/Xalan as code base. RI contains the implementation of
>>>>>>> newly
>>>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>>>> Transformer
>>>>>>> Reset changes, Secured XML Processing changes.
>>>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>>>> XInclude
>>>>>>> already exist on Apache Xerces. So in the next
>>>>>>> section I have also proposed the way to merge rest of the JAXP
>>>>>>> 1.3
> RI
>>>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>>>> suggested where implementation component should reside i.e.
>>>>>>> Xerces
> or
>>>>>>> Xalan. Any idea or feedback for the smoother and
>>>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>>>> Xerces &
>>>>>>> Xalan is very welcome.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *JAXP 1.3 APIs: *
>>>>>>>
>>>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>>>> APIs
>>>>>>> are used by many different projects.
>>>>>>> With JSR 206 declared as final and many new standards emerging,
>>>>>>> we
>>>>>>> should update xml-commons to JAXP 1.3
>>>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>>>> trunk
>>>>>>> and apply a tag.
>>>>>>>
>>>>>>>
>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Xerces)*
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>>>
>>>>>>> javax.xml.datatype
>>>>>>> javax.xml.validation
>>>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>>>
>>>>>>> which should reside at Xerces.
>>>>>>>
>>>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
> into
>>>>>>> that branch. This will help
>>>>>>> other Xerces active committers to have a chance to look at it
> before
>>>>>>> these changes being finally
>>>>>>> committed to main trunk. This process would require merging
>>>>>>> changes to
>>>>>>> the branch and then committing
>>>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>>>
>>>>>>>
>>>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>>> Xalan)*
>>>>>>>
>>>>>>>
>>>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
> changes
>>>>>>> done in "javax.xml.transform" package
>>>>>>> for ex. now application can use the same Transformer instance by
>>>>>>> invoking reset().
>>>>>>>
>>>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>>>> branch
>>>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>>>> put there. This will help other Xalan active committers to have a
>>>>>>> chance
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> to look at it before these changes being finally
>>>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>>>> for this
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> process.
>>>>>>>
>>>>>>>
>>>>>>> As always, all feedbacks are more than welcome.
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Neeraj
>>>>>>>
>>>>>>>
>>>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>>>> [2]
>>>>>>> http://java.sun.com/j2se/1.5.
>>>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>>>> [3]
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> http://java.sun.com/j2se/1.5.
>> 0/docs/api/javax/xml/xpath/package-summary.html
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> [4]
>>>>>>>
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>>>> summary.html
>>>>>>>
>>>>>>>
>>>>>>>
> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Michael Glavassevich
>>>>>> XML Parser Development
>>>>>> IBM Toronto Lab
>>>>>> E-mail: mrglavas@ca.ibm.com
>>>>>> E-mail: mrglavas@apache.org
>>>>>>
>>>>>>
> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Neeraj,
I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
license on them. The JAXP 1.2 sources in xml-commons carry the Apache
license. Will this still be the case for JAXP 1.3?
Thanks.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
> Ok I just finished uploading JAXP 1.3 sources in
> "*xml-commons/contrib/jaxp13"* directory.
> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip which
> corresponds to jaxp-api,
> xerces & xalan sources respectively.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
> > That really sounds good to me.. so i would try to finish it today.
> > I will send mail to the community when i am done.
> >
> > Thanks dims for the suggestion.
> >
> > - Neeraj
> >
> > Davanum Srinivas wrote:
> >
> >> Neeraj,
> >>
> >> my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
> >> cvs so everyone can take a look (and then pick on the bits they
> >> want/need)...yes, changes to xml-commons can be made ASAP (after
> >> tagging the current code in the main trunk there) and it's upto the
> >> xml xerces/xalan folks to start picking up stuff as/when they fit.
> >>
> >> thanks,
> >> dims
> >>
> >> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
> >>
> >>
> >>> Thanks Michael for your response.
> >>>
> >>> I was just wondering what would be idle time to wait before i start
> >>> work
> >>> on this ?
> >>> Does anyone has an opinion, Is there any other list where i should
send
> >>> this mail
> >>> before making changes ?
> >>>
> >>> - Neeraj
> >>>
> >>> Michael Glavassevich wrote:
> >>>
> >>>
> >>>
> >>>> Hi Neeraj,
> >>>>
> >>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
and
> >>>> making a branch for the old JAXP sources on the current main trunk.
> >>>>
> >>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
> >>>> updates
> >>>> have been applied to the JAXP 1.2 sources. This is the branch we've
> >>>> used
> >>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
> >>>> assume a
> >>>> similar branch will exist for 1.3.
> >>>>
> >>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
AM:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> Hello All,
> >>>>>
> >>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
> >>>>> zip but
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> mail bounced back with the following message
> >>>>>
> >>>>> <error>
> >>>>> ----- The following addresses had permanent fatal errors -----
> >>>>> <ge...@xml.apache.org>
> >>>>> (reason: 552 ZIP attachments are not accepted here.)
> >>>>> </error>
> >>>>>
> >>>>> What should i do now ? Is there a way to upload sources on Apache
> >>>>> server somewhere ?
> >>>>> Can anyone guide me what is the procedure for such code grants ?
> >>>>>
> >>>>> I am looking help from the active committers of Xerces & Xalan
> >>>>> community
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> to help put it in a
> >>>>> a branch and make it work there. As i think due to large number of
> >>>>> changes it would be a considerable
> >>>>> amount of work. This will also help the committers & community to
> >>>>> have a
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> look at the code before
> >>>>> it is merged into the main stream work.
> >>>>>
> >>>>> I think i have commit access at xml-commons so i can commit the
> >>>>> sources
> >>>>> in xml-commons branch
> >>>>> or main trunk (and create branch for old jaxp sources ). What is
the
> >>>>> opinion of community ? I can
> >>>>> start this as soon as i get a consensus from the community. My
> >>>>> preference is to put the sources on
> >>>>> xml-commons main trunk.
> >>>>>
> >>>>> Please let me know how should i proceed.
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> - Neeraj
> >>>>>
> >>>>>
> >>>>> Hello All,
> >>>>>
> >>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>>>> implementation to Apache XML.*
> >>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>>>> significant advancement over JAXP 1.2 and adds whole lot of new
> >>>>> functionalities.
> >>>>>
> >>>>> * New Schema Validation Framework
> >>>>> * New Object Model neutral XPath APIs
> >>>>> * New Java datatypes which maps to XML Schema Datatypes.
> >>>>> * Reuse parser instance
> >>>>> * Security enhancements
> >>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
> >>>>> Save, SAX
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 2, XML 1.1 and XInclude)
> >>>>>
> >>>>> *JAXP 1.3 APIs source code is attached with this mail. *
> >>>>>
> >>>>> Due to large size of code base i will be sending different mails
> >>>>> for the
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> source code of Xerces & Xalan.
> >>>>>
> >>>>> I have attached the original mail where i proposed the process of
> >>>>> upgrading xml-commons to JAXP 1.3 APIs and
> >>>>> integrating this donation into the main stream work of Xerces &
> >>>>> Xalan.
> >>>>> There was a general consensus to my proposal
> >>>>> and we can discuss more about the technicalities of merging with
> >>>>> in the
> >>>>> appropriate (Xml-commons, Xerces, Xalan)
> >>>>> community.
> >>>>>
> >>>>> Let's upgrade to JAXP 1.3 :-)
> >>>>>
> >>>>> - Neeraj
> >>>>>
> >>>>>
> >>>>>
> >>>>> Neeraj Bajaj wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Geir Magnusson Jr. wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
> >>>>>>>> ball
> >>>>>>>> on this one.
> >>>>>>>>
> >>>>>>>> Note: once the papers are in the Hallowed Halls, I presume that
> >>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>>>>>>> xerces-j-dev as to how to actually check this in?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>> There is no need to wait until Hall Hallowed-ness has been
> >>>>>>> achieved.
> >>>>>>> I have received them on behalf of the ASF, and don't let the
> >>>>>>> process
> >>>>>>> hold things up.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> Great... Thanks Geir. No more held up is good
> >>>>>>
> >>>>>> - Neeraj
> >>>>>>
> >>>>>>
---------------------------------------------------------------------
> >>>>>>
> >>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------------
> >>>>>
> >>>>>
> >>>>> Subject:
> >>>>> Donation of JAXP 1.3 Sources to Apache
> >>>>> From:
> >>>>> Neeraj Bajaj <Ne...@Sun.COM>
> >>>>> Date:
> >>>>> Tue, 12 Oct 2004 17:32:14 +0530
> >>>>>
> >>>>> To:
> >>>>> general@xml.apache.org
> >>>>> CC:
> >>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >>>>> <Ed...@Sun.COM>, Jeff Suttor
<Je...@Sun.COM>,
> >>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>>>>
> >>>>>
> >>>>> Hello All,
> >>>>>
> >>>>>
> >>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
> >>>>> final. JAXP
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 1.3 adds lots of new features in the area of XML processing.
> >>>>> It introduces new Schema independent validation framework which
> >>>>> decouples the validation as a process independent from parsing.
> >>>>> It allows to compile Schema to an immutable memory representation
of
> >>>>> Grammar which can validate different instances of XML document
thus
> >>>>> greatly improving the performance of XML processing. XPath
language
> >>>>> provides a simple, concise syntax for accessing individual parts
> >>>>> of an
> >>>>> XML document. JAXP 1.3 defines XPath APIs which provides access to
> >>>>> the
> >>>>> XPath evaluation environment and expression results independent
> >>>>> of the underlying data object model. JAXP 1.3 also adds new
> >>>>> Datatypes to
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> the Java platform which maps to some of the W3C XML Schema
> >>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also
> >>>>> adds
> >>>>> the ability to reset XML Parser and Transformer instance ,
allowing
> >>>>> application to reuse the same instance to process multiple XML
> >>>>> documents. This also helps in increasing XML processing
performance.
> >>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
> >>>>> L/S, XML
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 1.1, XInclude.
> >>>>>
> >>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> >>>>> Reference Implementation) to Apache. *
> >>>>>
> >>>>>
> >>>>> /Details of JAXP 1.3 sources to be donated:/
> >>>>>
> >>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
(Reference
> >>>>> Implementation). RI has been done using
> >>>>> Xerces/Xalan as code base. RI contains the implementation of newly
> >>>>> introduced Validation Framework [2], XPath APIs [3]
> >>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
> >>>>> Transformer
> >>>>> Reset changes, Secured XML Processing changes.
> >>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
> >>>>> XInclude
> >>>>> already exist on Apache Xerces. So in the next
> >>>>> section I have also proposed the way to merge rest of the JAXP 1.3
RI
> >>>>> changes into Apache Xerces & Xalan project. I have also
> >>>>> suggested where implementation component should reside i.e. Xerces
or
> >>>>> Xalan. Any idea or feedback for the smoother and
> >>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
> >>>>> Xerces &
> >>>>> Xalan is very welcome.
> >>>>>
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 APIs: *
> >>>>>
> >>>>> JAXP APIs has been at xml-commons for a long time as these set of
> >>>>> APIs
> >>>>> are used by many different projects.
> >>>>> With JSR 206 declared as final and many new standards emerging, we
> >>>>> should update xml-commons to JAXP 1.3
> >>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
> >>>>> trunk
> >>>>> and apply a tag.
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 RI: (Implementation components that should be part of
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> Xerces)*
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> JAXP 1.3 RI contains the implementation of following packages
> >>>>>
> >>>>> javax.xml.datatype
> >>>>> javax.xml.validation
> >>>>> javax.xml.parsers ( reset(), xinclude, etc.)
> >>>>>
> >>>>> which should reside at Xerces.
> >>>>>
> >>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
into
> >>>>> that branch. This will help
> >>>>> other Xerces active committers to have a chance to look at it
before
> >>>>> these changes being finally
> >>>>> committed to main trunk. This process would require merging
> >>>>> changes to
> >>>>> the branch and then committing
> >>>>> changes to main trunk, i seek help of active Xerces committers.
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 RI: (Implementation components that should be part of
> >>>>> Xalan)*
> >>>>>
> >>>>>
> >>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
> >>>>> (javax.xml.xpath.*) APIs which i think, should be part of
> >>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
changes
> >>>>> done in "javax.xml.transform" package
> >>>>> for ex. now application can use the same Transformer instance by
> >>>>> invoking reset().
> >>>>>
> >>>>> I propose the same for the Xalan/XSLTC project that we create a
> >>>>> branch
> >>>>> and JAXP 1.3 Reference Implementation changes are
> >>>>> put there. This will help other Xalan active committers to have a
> >>>>> chance
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> to look at it before these changes being finally
> >>>>> committed to main trunk. Again i seek help of Xalan committers
> >>>>> for this
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> process.
> >>>>>
> >>>>>
> >>>>> As always, all feedbacks are more than welcome.
> >>>>>
> >>>>>
> >>>>> Thanks,
> >>>>> Neeraj
> >>>>>
> >>>>>
> >>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
> >>>>> [2]
> >>>>> http://java.sun.com/j2se/1.5.
> >>>>> 0/docs/api/javax/xml/validation/package-summary.html
> >>>>> [3]
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> http://java.sun.com/j2se/1.5.
> 0/docs/api/javax/xml/xpath/package-summary.html
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> [4]
> >>>>>
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>>>> summary.html
> >>>>>
> >>>>>
> >>>>>
---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> Michael Glavassevich
> >>>> XML Parser Development
> >>>> IBM Toronto Lab
> >>>> E-mail: mrglavas@ca.ibm.com
> >>>> E-mail: mrglavas@apache.org
> >>>>
> >>>>
---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >>>> For additional commands, e-mail: xalan-dev-help@xml.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
> >
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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Neeraj,
I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
license on them. The JAXP 1.2 sources in xml-commons carry the Apache
license. Will this still be the case for JAXP 1.3?
Thanks.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
> Ok I just finished uploading JAXP 1.3 sources in
> "*xml-commons/contrib/jaxp13"* directory.
> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip which
> corresponds to jaxp-api,
> xerces & xalan sources respectively.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
> > That really sounds good to me.. so i would try to finish it today.
> > I will send mail to the community when i am done.
> >
> > Thanks dims for the suggestion.
> >
> > - Neeraj
> >
> > Davanum Srinivas wrote:
> >
> >> Neeraj,
> >>
> >> my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
> >> cvs so everyone can take a look (and then pick on the bits they
> >> want/need)...yes, changes to xml-commons can be made ASAP (after
> >> tagging the current code in the main trunk there) and it's upto the
> >> xml xerces/xalan folks to start picking up stuff as/when they fit.
> >>
> >> thanks,
> >> dims
> >>
> >> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
> >>
> >>
> >>> Thanks Michael for your response.
> >>>
> >>> I was just wondering what would be idle time to wait before i start
> >>> work
> >>> on this ?
> >>> Does anyone has an opinion, Is there any other list where i should
send
> >>> this mail
> >>> before making changes ?
> >>>
> >>> - Neeraj
> >>>
> >>> Michael Glavassevich wrote:
> >>>
> >>>
> >>>
> >>>> Hi Neeraj,
> >>>>
> >>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
and
> >>>> making a branch for the old JAXP sources on the current main trunk.
> >>>>
> >>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
> >>>> updates
> >>>> have been applied to the JAXP 1.2 sources. This is the branch we've
> >>>> used
> >>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
> >>>> assume a
> >>>> similar branch will exist for 1.3.
> >>>>
> >>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
AM:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> Hello All,
> >>>>>
> >>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
> >>>>> zip but
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> mail bounced back with the following message
> >>>>>
> >>>>> <error>
> >>>>> ----- The following addresses had permanent fatal errors -----
> >>>>> <ge...@xml.apache.org>
> >>>>> (reason: 552 ZIP attachments are not accepted here.)
> >>>>> </error>
> >>>>>
> >>>>> What should i do now ? Is there a way to upload sources on Apache
> >>>>> server somewhere ?
> >>>>> Can anyone guide me what is the procedure for such code grants ?
> >>>>>
> >>>>> I am looking help from the active committers of Xerces & Xalan
> >>>>> community
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> to help put it in a
> >>>>> a branch and make it work there. As i think due to large number of
> >>>>> changes it would be a considerable
> >>>>> amount of work. This will also help the committers & community to
> >>>>> have a
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> look at the code before
> >>>>> it is merged into the main stream work.
> >>>>>
> >>>>> I think i have commit access at xml-commons so i can commit the
> >>>>> sources
> >>>>> in xml-commons branch
> >>>>> or main trunk (and create branch for old jaxp sources ). What is
the
> >>>>> opinion of community ? I can
> >>>>> start this as soon as i get a consensus from the community. My
> >>>>> preference is to put the sources on
> >>>>> xml-commons main trunk.
> >>>>>
> >>>>> Please let me know how should i proceed.
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> - Neeraj
> >>>>>
> >>>>>
> >>>>> Hello All,
> >>>>>
> >>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>>>> implementation to Apache XML.*
> >>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>>>> significant advancement over JAXP 1.2 and adds whole lot of new
> >>>>> functionalities.
> >>>>>
> >>>>> * New Schema Validation Framework
> >>>>> * New Object Model neutral XPath APIs
> >>>>> * New Java datatypes which maps to XML Schema Datatypes.
> >>>>> * Reuse parser instance
> >>>>> * Security enhancements
> >>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
> >>>>> Save, SAX
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 2, XML 1.1 and XInclude)
> >>>>>
> >>>>> *JAXP 1.3 APIs source code is attached with this mail. *
> >>>>>
> >>>>> Due to large size of code base i will be sending different mails
> >>>>> for the
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> source code of Xerces & Xalan.
> >>>>>
> >>>>> I have attached the original mail where i proposed the process of
> >>>>> upgrading xml-commons to JAXP 1.3 APIs and
> >>>>> integrating this donation into the main stream work of Xerces &
> >>>>> Xalan.
> >>>>> There was a general consensus to my proposal
> >>>>> and we can discuss more about the technicalities of merging with
> >>>>> in the
> >>>>> appropriate (Xml-commons, Xerces, Xalan)
> >>>>> community.
> >>>>>
> >>>>> Let's upgrade to JAXP 1.3 :-)
> >>>>>
> >>>>> - Neeraj
> >>>>>
> >>>>>
> >>>>>
> >>>>> Neeraj Bajaj wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Geir Magnusson Jr. wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
> >>>>>>>> ball
> >>>>>>>> on this one.
> >>>>>>>>
> >>>>>>>> Note: once the papers are in the Hallowed Halls, I presume that
> >>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>>>>>>> xerces-j-dev as to how to actually check this in?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>> There is no need to wait until Hall Hallowed-ness has been
> >>>>>>> achieved.
> >>>>>>> I have received them on behalf of the ASF, and don't let the
> >>>>>>> process
> >>>>>>> hold things up.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> Great... Thanks Geir. No more held up is good
> >>>>>>
> >>>>>> - Neeraj
> >>>>>>
> >>>>>>
---------------------------------------------------------------------
> >>>>>>
> >>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------------
> >>>>>
> >>>>>
> >>>>> Subject:
> >>>>> Donation of JAXP 1.3 Sources to Apache
> >>>>> From:
> >>>>> Neeraj Bajaj <Ne...@Sun.COM>
> >>>>> Date:
> >>>>> Tue, 12 Oct 2004 17:32:14 +0530
> >>>>>
> >>>>> To:
> >>>>> general@xml.apache.org
> >>>>> CC:
> >>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >>>>> <Ed...@Sun.COM>, Jeff Suttor
<Je...@Sun.COM>,
> >>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>>>>
> >>>>>
> >>>>> Hello All,
> >>>>>
> >>>>>
> >>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
> >>>>> final. JAXP
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 1.3 adds lots of new features in the area of XML processing.
> >>>>> It introduces new Schema independent validation framework which
> >>>>> decouples the validation as a process independent from parsing.
> >>>>> It allows to compile Schema to an immutable memory representation
of
> >>>>> Grammar which can validate different instances of XML document
thus
> >>>>> greatly improving the performance of XML processing. XPath
language
> >>>>> provides a simple, concise syntax for accessing individual parts
> >>>>> of an
> >>>>> XML document. JAXP 1.3 defines XPath APIs which provides access to
> >>>>> the
> >>>>> XPath evaluation environment and expression results independent
> >>>>> of the underlying data object model. JAXP 1.3 also adds new
> >>>>> Datatypes to
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> the Java platform which maps to some of the W3C XML Schema
> >>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also
> >>>>> adds
> >>>>> the ability to reset XML Parser and Transformer instance ,
allowing
> >>>>> application to reuse the same instance to process multiple XML
> >>>>> documents. This also helps in increasing XML processing
performance.
> >>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
> >>>>> L/S, XML
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 1.1, XInclude.
> >>>>>
> >>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> >>>>> Reference Implementation) to Apache. *
> >>>>>
> >>>>>
> >>>>> /Details of JAXP 1.3 sources to be donated:/
> >>>>>
> >>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
(Reference
> >>>>> Implementation). RI has been done using
> >>>>> Xerces/Xalan as code base. RI contains the implementation of newly
> >>>>> introduced Validation Framework [2], XPath APIs [3]
> >>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
> >>>>> Transformer
> >>>>> Reset changes, Secured XML Processing changes.
> >>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
> >>>>> XInclude
> >>>>> already exist on Apache Xerces. So in the next
> >>>>> section I have also proposed the way to merge rest of the JAXP 1.3
RI
> >>>>> changes into Apache Xerces & Xalan project. I have also
> >>>>> suggested where implementation component should reside i.e. Xerces
or
> >>>>> Xalan. Any idea or feedback for the smoother and
> >>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
> >>>>> Xerces &
> >>>>> Xalan is very welcome.
> >>>>>
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 APIs: *
> >>>>>
> >>>>> JAXP APIs has been at xml-commons for a long time as these set of
> >>>>> APIs
> >>>>> are used by many different projects.
> >>>>> With JSR 206 declared as final and many new standards emerging, we
> >>>>> should update xml-commons to JAXP 1.3
> >>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
> >>>>> trunk
> >>>>> and apply a tag.
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 RI: (Implementation components that should be part of
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> Xerces)*
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> JAXP 1.3 RI contains the implementation of following packages
> >>>>>
> >>>>> javax.xml.datatype
> >>>>> javax.xml.validation
> >>>>> javax.xml.parsers ( reset(), xinclude, etc.)
> >>>>>
> >>>>> which should reside at Xerces.
> >>>>>
> >>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
into
> >>>>> that branch. This will help
> >>>>> other Xerces active committers to have a chance to look at it
before
> >>>>> these changes being finally
> >>>>> committed to main trunk. This process would require merging
> >>>>> changes to
> >>>>> the branch and then committing
> >>>>> changes to main trunk, i seek help of active Xerces committers.
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 RI: (Implementation components that should be part of
> >>>>> Xalan)*
> >>>>>
> >>>>>
> >>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
> >>>>> (javax.xml.xpath.*) APIs which i think, should be part of
> >>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
changes
> >>>>> done in "javax.xml.transform" package
> >>>>> for ex. now application can use the same Transformer instance by
> >>>>> invoking reset().
> >>>>>
> >>>>> I propose the same for the Xalan/XSLTC project that we create a
> >>>>> branch
> >>>>> and JAXP 1.3 Reference Implementation changes are
> >>>>> put there. This will help other Xalan active committers to have a
> >>>>> chance
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> to look at it before these changes being finally
> >>>>> committed to main trunk. Again i seek help of Xalan committers
> >>>>> for this
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> process.
> >>>>>
> >>>>>
> >>>>> As always, all feedbacks are more than welcome.
> >>>>>
> >>>>>
> >>>>> Thanks,
> >>>>> Neeraj
> >>>>>
> >>>>>
> >>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
> >>>>> [2]
> >>>>> http://java.sun.com/j2se/1.5.
> >>>>> 0/docs/api/javax/xml/validation/package-summary.html
> >>>>> [3]
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> http://java.sun.com/j2se/1.5.
> 0/docs/api/javax/xml/xpath/package-summary.html
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> [4]
> >>>>>
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>>>> summary.html
> >>>>>
> >>>>>
> >>>>>
---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> Michael Glavassevich
> >>>> XML Parser Development
> >>>> IBM Toronto Lab
> >>>> E-mail: mrglavas@ca.ibm.com
> >>>> E-mail: mrglavas@apache.org
> >>>>
> >>>>
---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >>>> For additional commands, e-mail: xalan-dev-help@xml.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
> >
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Neeraj,
I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
license on them. The JAXP 1.2 sources in xml-commons carry the Apache
license. Will this still be the case for JAXP 1.3?
Thanks.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
> Ok I just finished uploading JAXP 1.3 sources in
> "*xml-commons/contrib/jaxp13"* directory.
> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip which
> corresponds to jaxp-api,
> xerces & xalan sources respectively.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
> > That really sounds good to me.. so i would try to finish it today.
> > I will send mail to the community when i am done.
> >
> > Thanks dims for the suggestion.
> >
> > - Neeraj
> >
> > Davanum Srinivas wrote:
> >
> >> Neeraj,
> >>
> >> my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
> >> cvs so everyone can take a look (and then pick on the bits they
> >> want/need)...yes, changes to xml-commons can be made ASAP (after
> >> tagging the current code in the main trunk there) and it's upto the
> >> xml xerces/xalan folks to start picking up stuff as/when they fit.
> >>
> >> thanks,
> >> dims
> >>
> >> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
> >>
> >>
> >>> Thanks Michael for your response.
> >>>
> >>> I was just wondering what would be idle time to wait before i start
> >>> work
> >>> on this ?
> >>> Does anyone has an opinion, Is there any other list where i should
send
> >>> this mail
> >>> before making changes ?
> >>>
> >>> - Neeraj
> >>>
> >>> Michael Glavassevich wrote:
> >>>
> >>>
> >>>
> >>>> Hi Neeraj,
> >>>>
> >>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
and
> >>>> making a branch for the old JAXP sources on the current main trunk.
> >>>>
> >>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
> >>>> updates
> >>>> have been applied to the JAXP 1.2 sources. This is the branch we've
> >>>> used
> >>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
> >>>> assume a
> >>>> similar branch will exist for 1.3.
> >>>>
> >>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
AM:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> Hello All,
> >>>>>
> >>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
> >>>>> zip but
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> mail bounced back with the following message
> >>>>>
> >>>>> <error>
> >>>>> ----- The following addresses had permanent fatal errors -----
> >>>>> <ge...@xml.apache.org>
> >>>>> (reason: 552 ZIP attachments are not accepted here.)
> >>>>> </error>
> >>>>>
> >>>>> What should i do now ? Is there a way to upload sources on Apache
> >>>>> server somewhere ?
> >>>>> Can anyone guide me what is the procedure for such code grants ?
> >>>>>
> >>>>> I am looking help from the active committers of Xerces & Xalan
> >>>>> community
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> to help put it in a
> >>>>> a branch and make it work there. As i think due to large number of
> >>>>> changes it would be a considerable
> >>>>> amount of work. This will also help the committers & community to
> >>>>> have a
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> look at the code before
> >>>>> it is merged into the main stream work.
> >>>>>
> >>>>> I think i have commit access at xml-commons so i can commit the
> >>>>> sources
> >>>>> in xml-commons branch
> >>>>> or main trunk (and create branch for old jaxp sources ). What is
the
> >>>>> opinion of community ? I can
> >>>>> start this as soon as i get a consensus from the community. My
> >>>>> preference is to put the sources on
> >>>>> xml-commons main trunk.
> >>>>>
> >>>>> Please let me know how should i proceed.
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> - Neeraj
> >>>>>
> >>>>>
> >>>>> Hello All,
> >>>>>
> >>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>>>> implementation to Apache XML.*
> >>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>>>> significant advancement over JAXP 1.2 and adds whole lot of new
> >>>>> functionalities.
> >>>>>
> >>>>> * New Schema Validation Framework
> >>>>> * New Object Model neutral XPath APIs
> >>>>> * New Java datatypes which maps to XML Schema Datatypes.
> >>>>> * Reuse parser instance
> >>>>> * Security enhancements
> >>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
> >>>>> Save, SAX
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 2, XML 1.1 and XInclude)
> >>>>>
> >>>>> *JAXP 1.3 APIs source code is attached with this mail. *
> >>>>>
> >>>>> Due to large size of code base i will be sending different mails
> >>>>> for the
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> source code of Xerces & Xalan.
> >>>>>
> >>>>> I have attached the original mail where i proposed the process of
> >>>>> upgrading xml-commons to JAXP 1.3 APIs and
> >>>>> integrating this donation into the main stream work of Xerces &
> >>>>> Xalan.
> >>>>> There was a general consensus to my proposal
> >>>>> and we can discuss more about the technicalities of merging with
> >>>>> in the
> >>>>> appropriate (Xml-commons, Xerces, Xalan)
> >>>>> community.
> >>>>>
> >>>>> Let's upgrade to JAXP 1.3 :-)
> >>>>>
> >>>>> - Neeraj
> >>>>>
> >>>>>
> >>>>>
> >>>>> Neeraj Bajaj wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Geir Magnusson Jr. wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
> >>>>>>>> ball
> >>>>>>>> on this one.
> >>>>>>>>
> >>>>>>>> Note: once the papers are in the Hallowed Halls, I presume that
> >>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>>>>>>> xerces-j-dev as to how to actually check this in?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>> There is no need to wait until Hall Hallowed-ness has been
> >>>>>>> achieved.
> >>>>>>> I have received them on behalf of the ASF, and don't let the
> >>>>>>> process
> >>>>>>> hold things up.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> Great... Thanks Geir. No more held up is good
> >>>>>>
> >>>>>> - Neeraj
> >>>>>>
> >>>>>>
---------------------------------------------------------------------
> >>>>>>
> >>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------------
> >>>>>
> >>>>>
> >>>>> Subject:
> >>>>> Donation of JAXP 1.3 Sources to Apache
> >>>>> From:
> >>>>> Neeraj Bajaj <Ne...@Sun.COM>
> >>>>> Date:
> >>>>> Tue, 12 Oct 2004 17:32:14 +0530
> >>>>>
> >>>>> To:
> >>>>> general@xml.apache.org
> >>>>> CC:
> >>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >>>>> <Ed...@Sun.COM>, Jeff Suttor
<Je...@Sun.COM>,
> >>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>>>>
> >>>>>
> >>>>> Hello All,
> >>>>>
> >>>>>
> >>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
> >>>>> final. JAXP
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 1.3 adds lots of new features in the area of XML processing.
> >>>>> It introduces new Schema independent validation framework which
> >>>>> decouples the validation as a process independent from parsing.
> >>>>> It allows to compile Schema to an immutable memory representation
of
> >>>>> Grammar which can validate different instances of XML document
thus
> >>>>> greatly improving the performance of XML processing. XPath
language
> >>>>> provides a simple, concise syntax for accessing individual parts
> >>>>> of an
> >>>>> XML document. JAXP 1.3 defines XPath APIs which provides access to
> >>>>> the
> >>>>> XPath evaluation environment and expression results independent
> >>>>> of the underlying data object model. JAXP 1.3 also adds new
> >>>>> Datatypes to
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> the Java platform which maps to some of the W3C XML Schema
> >>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also
> >>>>> adds
> >>>>> the ability to reset XML Parser and Transformer instance ,
allowing
> >>>>> application to reuse the same instance to process multiple XML
> >>>>> documents. This also helps in increasing XML processing
performance.
> >>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
> >>>>> L/S, XML
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 1.1, XInclude.
> >>>>>
> >>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> >>>>> Reference Implementation) to Apache. *
> >>>>>
> >>>>>
> >>>>> /Details of JAXP 1.3 sources to be donated:/
> >>>>>
> >>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
(Reference
> >>>>> Implementation). RI has been done using
> >>>>> Xerces/Xalan as code base. RI contains the implementation of newly
> >>>>> introduced Validation Framework [2], XPath APIs [3]
> >>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
> >>>>> Transformer
> >>>>> Reset changes, Secured XML Processing changes.
> >>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
> >>>>> XInclude
> >>>>> already exist on Apache Xerces. So in the next
> >>>>> section I have also proposed the way to merge rest of the JAXP 1.3
RI
> >>>>> changes into Apache Xerces & Xalan project. I have also
> >>>>> suggested where implementation component should reside i.e. Xerces
or
> >>>>> Xalan. Any idea or feedback for the smoother and
> >>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
> >>>>> Xerces &
> >>>>> Xalan is very welcome.
> >>>>>
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 APIs: *
> >>>>>
> >>>>> JAXP APIs has been at xml-commons for a long time as these set of
> >>>>> APIs
> >>>>> are used by many different projects.
> >>>>> With JSR 206 declared as final and many new standards emerging, we
> >>>>> should update xml-commons to JAXP 1.3
> >>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
> >>>>> trunk
> >>>>> and apply a tag.
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 RI: (Implementation components that should be part of
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> Xerces)*
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> JAXP 1.3 RI contains the implementation of following packages
> >>>>>
> >>>>> javax.xml.datatype
> >>>>> javax.xml.validation
> >>>>> javax.xml.parsers ( reset(), xinclude, etc.)
> >>>>>
> >>>>> which should reside at Xerces.
> >>>>>
> >>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
into
> >>>>> that branch. This will help
> >>>>> other Xerces active committers to have a chance to look at it
before
> >>>>> these changes being finally
> >>>>> committed to main trunk. This process would require merging
> >>>>> changes to
> >>>>> the branch and then committing
> >>>>> changes to main trunk, i seek help of active Xerces committers.
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 RI: (Implementation components that should be part of
> >>>>> Xalan)*
> >>>>>
> >>>>>
> >>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
> >>>>> (javax.xml.xpath.*) APIs which i think, should be part of
> >>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
changes
> >>>>> done in "javax.xml.transform" package
> >>>>> for ex. now application can use the same Transformer instance by
> >>>>> invoking reset().
> >>>>>
> >>>>> I propose the same for the Xalan/XSLTC project that we create a
> >>>>> branch
> >>>>> and JAXP 1.3 Reference Implementation changes are
> >>>>> put there. This will help other Xalan active committers to have a
> >>>>> chance
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> to look at it before these changes being finally
> >>>>> committed to main trunk. Again i seek help of Xalan committers
> >>>>> for this
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> process.
> >>>>>
> >>>>>
> >>>>> As always, all feedbacks are more than welcome.
> >>>>>
> >>>>>
> >>>>> Thanks,
> >>>>> Neeraj
> >>>>>
> >>>>>
> >>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
> >>>>> [2]
> >>>>> http://java.sun.com/j2se/1.5.
> >>>>> 0/docs/api/javax/xml/validation/package-summary.html
> >>>>> [3]
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> http://java.sun.com/j2se/1.5.
> 0/docs/api/javax/xml/xpath/package-summary.html
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> [4]
> >>>>>
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>>>> summary.html
> >>>>>
> >>>>>
> >>>>>
---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> Michael Glavassevich
> >>>> XML Parser Development
> >>>> IBM Toronto Lab
> >>>> E-mail: mrglavas@ca.ibm.com
> >>>> E-mail: mrglavas@apache.org
> >>>>
> >>>>
---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >>>> For additional commands, e-mail: xalan-dev-help@xml.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
> >
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Neeraj,
I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
license on them. The JAXP 1.2 sources in xml-commons carry the Apache
license. Will this still be the case for JAXP 1.3?
Thanks.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
> Ok I just finished uploading JAXP 1.3 sources in
> "*xml-commons/contrib/jaxp13"* directory.
> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip which
> corresponds to jaxp-api,
> xerces & xalan sources respectively.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
> > That really sounds good to me.. so i would try to finish it today.
> > I will send mail to the community when i am done.
> >
> > Thanks dims for the suggestion.
> >
> > - Neeraj
> >
> > Davanum Srinivas wrote:
> >
> >> Neeraj,
> >>
> >> my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
> >> cvs so everyone can take a look (and then pick on the bits they
> >> want/need)...yes, changes to xml-commons can be made ASAP (after
> >> tagging the current code in the main trunk there) and it's upto the
> >> xml xerces/xalan folks to start picking up stuff as/when they fit.
> >>
> >> thanks,
> >> dims
> >>
> >> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
> >>
> >>
> >>> Thanks Michael for your response.
> >>>
> >>> I was just wondering what would be idle time to wait before i start
> >>> work
> >>> on this ?
> >>> Does anyone has an opinion, Is there any other list where i should
send
> >>> this mail
> >>> before making changes ?
> >>>
> >>> - Neeraj
> >>>
> >>> Michael Glavassevich wrote:
> >>>
> >>>
> >>>
> >>>> Hi Neeraj,
> >>>>
> >>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
and
> >>>> making a branch for the old JAXP sources on the current main trunk.
> >>>>
> >>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
> >>>> updates
> >>>> have been applied to the JAXP 1.2 sources. This is the branch we've
> >>>> used
> >>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
> >>>> assume a
> >>>> similar branch will exist for 1.3.
> >>>>
> >>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
AM:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> Hello All,
> >>>>>
> >>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
> >>>>> zip but
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> mail bounced back with the following message
> >>>>>
> >>>>> <error>
> >>>>> ----- The following addresses had permanent fatal errors -----
> >>>>> <ge...@xml.apache.org>
> >>>>> (reason: 552 ZIP attachments are not accepted here.)
> >>>>> </error>
> >>>>>
> >>>>> What should i do now ? Is there a way to upload sources on Apache
> >>>>> server somewhere ?
> >>>>> Can anyone guide me what is the procedure for such code grants ?
> >>>>>
> >>>>> I am looking help from the active committers of Xerces & Xalan
> >>>>> community
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> to help put it in a
> >>>>> a branch and make it work there. As i think due to large number of
> >>>>> changes it would be a considerable
> >>>>> amount of work. This will also help the committers & community to
> >>>>> have a
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> look at the code before
> >>>>> it is merged into the main stream work.
> >>>>>
> >>>>> I think i have commit access at xml-commons so i can commit the
> >>>>> sources
> >>>>> in xml-commons branch
> >>>>> or main trunk (and create branch for old jaxp sources ). What is
the
> >>>>> opinion of community ? I can
> >>>>> start this as soon as i get a consensus from the community. My
> >>>>> preference is to put the sources on
> >>>>> xml-commons main trunk.
> >>>>>
> >>>>> Please let me know how should i proceed.
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> - Neeraj
> >>>>>
> >>>>>
> >>>>> Hello All,
> >>>>>
> >>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>>>> implementation to Apache XML.*
> >>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>>>> significant advancement over JAXP 1.2 and adds whole lot of new
> >>>>> functionalities.
> >>>>>
> >>>>> * New Schema Validation Framework
> >>>>> * New Object Model neutral XPath APIs
> >>>>> * New Java datatypes which maps to XML Schema Datatypes.
> >>>>> * Reuse parser instance
> >>>>> * Security enhancements
> >>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
> >>>>> Save, SAX
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 2, XML 1.1 and XInclude)
> >>>>>
> >>>>> *JAXP 1.3 APIs source code is attached with this mail. *
> >>>>>
> >>>>> Due to large size of code base i will be sending different mails
> >>>>> for the
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> source code of Xerces & Xalan.
> >>>>>
> >>>>> I have attached the original mail where i proposed the process of
> >>>>> upgrading xml-commons to JAXP 1.3 APIs and
> >>>>> integrating this donation into the main stream work of Xerces &
> >>>>> Xalan.
> >>>>> There was a general consensus to my proposal
> >>>>> and we can discuss more about the technicalities of merging with
> >>>>> in the
> >>>>> appropriate (Xml-commons, Xerces, Xalan)
> >>>>> community.
> >>>>>
> >>>>> Let's upgrade to JAXP 1.3 :-)
> >>>>>
> >>>>> - Neeraj
> >>>>>
> >>>>>
> >>>>>
> >>>>> Neeraj Bajaj wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Geir Magnusson Jr. wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
> >>>>>>>> ball
> >>>>>>>> on this one.
> >>>>>>>>
> >>>>>>>> Note: once the papers are in the Hallowed Halls, I presume that
> >>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>>>>>>> xerces-j-dev as to how to actually check this in?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>> There is no need to wait until Hall Hallowed-ness has been
> >>>>>>> achieved.
> >>>>>>> I have received them on behalf of the ASF, and don't let the
> >>>>>>> process
> >>>>>>> hold things up.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> Great... Thanks Geir. No more held up is good
> >>>>>>
> >>>>>> - Neeraj
> >>>>>>
> >>>>>>
---------------------------------------------------------------------
> >>>>>>
> >>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------------
> >>>>>
> >>>>>
> >>>>> Subject:
> >>>>> Donation of JAXP 1.3 Sources to Apache
> >>>>> From:
> >>>>> Neeraj Bajaj <Ne...@Sun.COM>
> >>>>> Date:
> >>>>> Tue, 12 Oct 2004 17:32:14 +0530
> >>>>>
> >>>>> To:
> >>>>> general@xml.apache.org
> >>>>> CC:
> >>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >>>>> <Ed...@Sun.COM>, Jeff Suttor
<Je...@Sun.COM>,
> >>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>>>>
> >>>>>
> >>>>> Hello All,
> >>>>>
> >>>>>
> >>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
> >>>>> final. JAXP
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 1.3 adds lots of new features in the area of XML processing.
> >>>>> It introduces new Schema independent validation framework which
> >>>>> decouples the validation as a process independent from parsing.
> >>>>> It allows to compile Schema to an immutable memory representation
of
> >>>>> Grammar which can validate different instances of XML document
thus
> >>>>> greatly improving the performance of XML processing. XPath
language
> >>>>> provides a simple, concise syntax for accessing individual parts
> >>>>> of an
> >>>>> XML document. JAXP 1.3 defines XPath APIs which provides access to
> >>>>> the
> >>>>> XPath evaluation environment and expression results independent
> >>>>> of the underlying data object model. JAXP 1.3 also adds new
> >>>>> Datatypes to
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> the Java platform which maps to some of the W3C XML Schema
> >>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also
> >>>>> adds
> >>>>> the ability to reset XML Parser and Transformer instance ,
allowing
> >>>>> application to reuse the same instance to process multiple XML
> >>>>> documents. This also helps in increasing XML processing
performance.
> >>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
> >>>>> L/S, XML
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 1.1, XInclude.
> >>>>>
> >>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> >>>>> Reference Implementation) to Apache. *
> >>>>>
> >>>>>
> >>>>> /Details of JAXP 1.3 sources to be donated:/
> >>>>>
> >>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
(Reference
> >>>>> Implementation). RI has been done using
> >>>>> Xerces/Xalan as code base. RI contains the implementation of newly
> >>>>> introduced Validation Framework [2], XPath APIs [3]
> >>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
> >>>>> Transformer
> >>>>> Reset changes, Secured XML Processing changes.
> >>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
> >>>>> XInclude
> >>>>> already exist on Apache Xerces. So in the next
> >>>>> section I have also proposed the way to merge rest of the JAXP 1.3
RI
> >>>>> changes into Apache Xerces & Xalan project. I have also
> >>>>> suggested where implementation component should reside i.e. Xerces
or
> >>>>> Xalan. Any idea or feedback for the smoother and
> >>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
> >>>>> Xerces &
> >>>>> Xalan is very welcome.
> >>>>>
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 APIs: *
> >>>>>
> >>>>> JAXP APIs has been at xml-commons for a long time as these set of
> >>>>> APIs
> >>>>> are used by many different projects.
> >>>>> With JSR 206 declared as final and many new standards emerging, we
> >>>>> should update xml-commons to JAXP 1.3
> >>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
> >>>>> trunk
> >>>>> and apply a tag.
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 RI: (Implementation components that should be part of
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> Xerces)*
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> JAXP 1.3 RI contains the implementation of following packages
> >>>>>
> >>>>> javax.xml.datatype
> >>>>> javax.xml.validation
> >>>>> javax.xml.parsers ( reset(), xinclude, etc.)
> >>>>>
> >>>>> which should reside at Xerces.
> >>>>>
> >>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
into
> >>>>> that branch. This will help
> >>>>> other Xerces active committers to have a chance to look at it
before
> >>>>> these changes being finally
> >>>>> committed to main trunk. This process would require merging
> >>>>> changes to
> >>>>> the branch and then committing
> >>>>> changes to main trunk, i seek help of active Xerces committers.
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 RI: (Implementation components that should be part of
> >>>>> Xalan)*
> >>>>>
> >>>>>
> >>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
> >>>>> (javax.xml.xpath.*) APIs which i think, should be part of
> >>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
changes
> >>>>> done in "javax.xml.transform" package
> >>>>> for ex. now application can use the same Transformer instance by
> >>>>> invoking reset().
> >>>>>
> >>>>> I propose the same for the Xalan/XSLTC project that we create a
> >>>>> branch
> >>>>> and JAXP 1.3 Reference Implementation changes are
> >>>>> put there. This will help other Xalan active committers to have a
> >>>>> chance
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> to look at it before these changes being finally
> >>>>> committed to main trunk. Again i seek help of Xalan committers
> >>>>> for this
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> process.
> >>>>>
> >>>>>
> >>>>> As always, all feedbacks are more than welcome.
> >>>>>
> >>>>>
> >>>>> Thanks,
> >>>>> Neeraj
> >>>>>
> >>>>>
> >>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
> >>>>> [2]
> >>>>> http://java.sun.com/j2se/1.5.
> >>>>> 0/docs/api/javax/xml/validation/package-summary.html
> >>>>> [3]
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> http://java.sun.com/j2se/1.5.
> 0/docs/api/javax/xml/xpath/package-summary.html
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> [4]
> >>>>>
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>>>> summary.html
> >>>>>
> >>>>>
> >>>>>
---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> Michael Glavassevich
> >>>> XML Parser Development
> >>>> IBM Toronto Lab
> >>>> E-mail: mrglavas@ca.ibm.com
> >>>> E-mail: mrglavas@apache.org
> >>>>
> >>>>
---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >>>> For additional commands, e-mail: xalan-dev-help@xml.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
> >
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Neeraj,
I noticed that the JAXP 1.3 source files in jsr-206-src.zip have no
license on them. The JAXP 1.2 sources in xml-commons carry the Apache
license. Will this still be the case for JAXP 1.3?
Thanks.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/05/2005 06:48:30 AM:
> Ok I just finished uploading JAXP 1.3 sources in
> "*xml-commons/contrib/jaxp13"* directory.
> There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip which
> corresponds to jaxp-api,
> xerces & xalan sources respectively.
>
> - Neeraj
>
> Neeraj Bajaj wrote:
>
> > That really sounds good to me.. so i would try to finish it today.
> > I will send mail to the community when i am done.
> >
> > Thanks dims for the suggestion.
> >
> > - Neeraj
> >
> > Davanum Srinivas wrote:
> >
> >> Neeraj,
> >>
> >> my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
> >> cvs so everyone can take a look (and then pick on the bits they
> >> want/need)...yes, changes to xml-commons can be made ASAP (after
> >> tagging the current code in the main trunk there) and it's upto the
> >> xml xerces/xalan folks to start picking up stuff as/when they fit.
> >>
> >> thanks,
> >> dims
> >>
> >> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
> >>
> >>
> >>> Thanks Michael for your response.
> >>>
> >>> I was just wondering what would be idle time to wait before i start
> >>> work
> >>> on this ?
> >>> Does anyone has an opinion, Is there any other list where i should
send
> >>> this mail
> >>> before making changes ?
> >>>
> >>> - Neeraj
> >>>
> >>> Michael Glavassevich wrote:
> >>>
> >>>
> >>>
> >>>> Hi Neeraj,
> >>>>
> >>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it
and
> >>>> making a branch for the old JAXP sources on the current main trunk.
> >>>>
> >>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
> >>>> updates
> >>>> have been applied to the JAXP 1.2 sources. This is the branch we've
> >>>> used
> >>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
> >>>> assume a
> >>>> similar branch will exist for 1.3.
> >>>>
> >>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57
AM:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> Hello All,
> >>>>>
> >>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
> >>>>> zip but
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> mail bounced back with the following message
> >>>>>
> >>>>> <error>
> >>>>> ----- The following addresses had permanent fatal errors -----
> >>>>> <ge...@xml.apache.org>
> >>>>> (reason: 552 ZIP attachments are not accepted here.)
> >>>>> </error>
> >>>>>
> >>>>> What should i do now ? Is there a way to upload sources on Apache
> >>>>> server somewhere ?
> >>>>> Can anyone guide me what is the procedure for such code grants ?
> >>>>>
> >>>>> I am looking help from the active committers of Xerces & Xalan
> >>>>> community
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> to help put it in a
> >>>>> a branch and make it work there. As i think due to large number of
> >>>>> changes it would be a considerable
> >>>>> amount of work. This will also help the committers & community to
> >>>>> have a
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> look at the code before
> >>>>> it is merged into the main stream work.
> >>>>>
> >>>>> I think i have commit access at xml-commons so i can commit the
> >>>>> sources
> >>>>> in xml-commons branch
> >>>>> or main trunk (and create branch for old jaxp sources ). What is
the
> >>>>> opinion of community ? I can
> >>>>> start this as soon as i get a consensus from the community. My
> >>>>> preference is to put the sources on
> >>>>> xml-commons main trunk.
> >>>>>
> >>>>> Please let me know how should i proceed.
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> - Neeraj
> >>>>>
> >>>>>
> >>>>> Hello All,
> >>>>>
> >>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>>>> implementation to Apache XML.*
> >>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>>>> significant advancement over JAXP 1.2 and adds whole lot of new
> >>>>> functionalities.
> >>>>>
> >>>>> * New Schema Validation Framework
> >>>>> * New Object Model neutral XPath APIs
> >>>>> * New Java datatypes which maps to XML Schema Datatypes.
> >>>>> * Reuse parser instance
> >>>>> * Security enhancements
> >>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
> >>>>> Save, SAX
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 2, XML 1.1 and XInclude)
> >>>>>
> >>>>> *JAXP 1.3 APIs source code is attached with this mail. *
> >>>>>
> >>>>> Due to large size of code base i will be sending different mails
> >>>>> for the
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> source code of Xerces & Xalan.
> >>>>>
> >>>>> I have attached the original mail where i proposed the process of
> >>>>> upgrading xml-commons to JAXP 1.3 APIs and
> >>>>> integrating this donation into the main stream work of Xerces &
> >>>>> Xalan.
> >>>>> There was a general consensus to my proposal
> >>>>> and we can discuss more about the technicalities of merging with
> >>>>> in the
> >>>>> appropriate (Xml-commons, Xerces, Xalan)
> >>>>> community.
> >>>>>
> >>>>> Let's upgrade to JAXP 1.3 :-)
> >>>>>
> >>>>> - Neeraj
> >>>>>
> >>>>>
> >>>>>
> >>>>> Neeraj Bajaj wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Geir Magnusson Jr. wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
> >>>>>>>> ball
> >>>>>>>> on this one.
> >>>>>>>>
> >>>>>>>> Note: once the papers are in the Hallowed Halls, I presume that
> >>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>>>>>>> xerces-j-dev as to how to actually check this in?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>> There is no need to wait until Hall Hallowed-ness has been
> >>>>>>> achieved.
> >>>>>>> I have received them on behalf of the ASF, and don't let the
> >>>>>>> process
> >>>>>>> hold things up.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> Great... Thanks Geir. No more held up is good
> >>>>>>
> >>>>>> - Neeraj
> >>>>>>
> >>>>>>
---------------------------------------------------------------------
> >>>>>>
> >>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------------
> >>>>>
> >>>>>
> >>>>> Subject:
> >>>>> Donation of JAXP 1.3 Sources to Apache
> >>>>> From:
> >>>>> Neeraj Bajaj <Ne...@Sun.COM>
> >>>>> Date:
> >>>>> Tue, 12 Oct 2004 17:32:14 +0530
> >>>>>
> >>>>> To:
> >>>>> general@xml.apache.org
> >>>>> CC:
> >>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >>>>> <Ed...@Sun.COM>, Jeff Suttor
<Je...@Sun.COM>,
> >>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>>>>
> >>>>>
> >>>>> Hello All,
> >>>>>
> >>>>>
> >>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
> >>>>> final. JAXP
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 1.3 adds lots of new features in the area of XML processing.
> >>>>> It introduces new Schema independent validation framework which
> >>>>> decouples the validation as a process independent from parsing.
> >>>>> It allows to compile Schema to an immutable memory representation
of
> >>>>> Grammar which can validate different instances of XML document
thus
> >>>>> greatly improving the performance of XML processing. XPath
language
> >>>>> provides a simple, concise syntax for accessing individual parts
> >>>>> of an
> >>>>> XML document. JAXP 1.3 defines XPath APIs which provides access to
> >>>>> the
> >>>>> XPath evaluation environment and expression results independent
> >>>>> of the underlying data object model. JAXP 1.3 also adds new
> >>>>> Datatypes to
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> the Java platform which maps to some of the W3C XML Schema
> >>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also
> >>>>> adds
> >>>>> the ability to reset XML Parser and Transformer instance ,
allowing
> >>>>> application to reuse the same instance to process multiple XML
> >>>>> documents. This also helps in increasing XML processing
performance.
> >>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
> >>>>> L/S, XML
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 1.1, XInclude.
> >>>>>
> >>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> >>>>> Reference Implementation) to Apache. *
> >>>>>
> >>>>>
> >>>>> /Details of JAXP 1.3 sources to be donated:/
> >>>>>
> >>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI
(Reference
> >>>>> Implementation). RI has been done using
> >>>>> Xerces/Xalan as code base. RI contains the implementation of newly
> >>>>> introduced Validation Framework [2], XPath APIs [3]
> >>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
> >>>>> Transformer
> >>>>> Reset changes, Secured XML Processing changes.
> >>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
> >>>>> XInclude
> >>>>> already exist on Apache Xerces. So in the next
> >>>>> section I have also proposed the way to merge rest of the JAXP 1.3
RI
> >>>>> changes into Apache Xerces & Xalan project. I have also
> >>>>> suggested where implementation component should reside i.e. Xerces
or
> >>>>> Xalan. Any idea or feedback for the smoother and
> >>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
> >>>>> Xerces &
> >>>>> Xalan is very welcome.
> >>>>>
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 APIs: *
> >>>>>
> >>>>> JAXP APIs has been at xml-commons for a long time as these set of
> >>>>> APIs
> >>>>> are used by many different projects.
> >>>>> With JSR 206 declared as final and many new standards emerging, we
> >>>>> should update xml-commons to JAXP 1.3
> >>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
> >>>>> trunk
> >>>>> and apply a tag.
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 RI: (Implementation components that should be part of
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> Xerces)*
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> JAXP 1.3 RI contains the implementation of following packages
> >>>>>
> >>>>> javax.xml.datatype
> >>>>> javax.xml.validation
> >>>>> javax.xml.parsers ( reset(), xinclude, etc.)
> >>>>>
> >>>>> which should reside at Xerces.
> >>>>>
> >>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes
into
> >>>>> that branch. This will help
> >>>>> other Xerces active committers to have a chance to look at it
before
> >>>>> these changes being finally
> >>>>> committed to main trunk. This process would require merging
> >>>>> changes to
> >>>>> the branch and then committing
> >>>>> changes to main trunk, i seek help of active Xerces committers.
> >>>>>
> >>>>>
> >>>>> *JAXP 1.3 RI: (Implementation components that should be part of
> >>>>> Xalan)*
> >>>>>
> >>>>>
> >>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
> >>>>> (javax.xml.xpath.*) APIs which i think, should be part of
> >>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains
changes
> >>>>> done in "javax.xml.transform" package
> >>>>> for ex. now application can use the same Transformer instance by
> >>>>> invoking reset().
> >>>>>
> >>>>> I propose the same for the Xalan/XSLTC project that we create a
> >>>>> branch
> >>>>> and JAXP 1.3 Reference Implementation changes are
> >>>>> put there. This will help other Xalan active committers to have a
> >>>>> chance
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> to look at it before these changes being finally
> >>>>> committed to main trunk. Again i seek help of Xalan committers
> >>>>> for this
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> process.
> >>>>>
> >>>>>
> >>>>> As always, all feedbacks are more than welcome.
> >>>>>
> >>>>>
> >>>>> Thanks,
> >>>>> Neeraj
> >>>>>
> >>>>>
> >>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
> >>>>> [2]
> >>>>> http://java.sun.com/j2se/1.5.
> >>>>> 0/docs/api/javax/xml/validation/package-summary.html
> >>>>> [3]
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> http://java.sun.com/j2se/1.5.
> 0/docs/api/javax/xml/xpath/package-summary.html
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> [4]
> >>>>>
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>>>> summary.html
> >>>>>
> >>>>>
> >>>>>
---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> Michael Glavassevich
> >>>> XML Parser Development
> >>>> IBM Toronto Lab
> >>>> E-mail: mrglavas@ca.ibm.com
> >>>> E-mail: mrglavas@apache.org
> >>>>
> >>>>
---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >>>> For additional commands, e-mail: xalan-dev-help@xml.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
> >
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ok I just finished uploading JAXP 1.3 sources in
"*xml-commons/contrib/jaxp13"* directory.
There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip which
corresponds to jaxp-api,
xerces & xalan sources respectively.
- Neeraj
Neeraj Bajaj wrote:
> That really sounds good to me.. so i would try to finish it today.
> I will send mail to the community when i am done.
>
> Thanks dims for the suggestion.
>
> - Neeraj
>
> Davanum Srinivas wrote:
>
>> Neeraj,
>>
>> my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
>> cvs so everyone can take a look (and then pick on the bits they
>> want/need)...yes, changes to xml-commons can be made ASAP (after
>> tagging the current code in the main trunk there) and it's upto the
>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>
>> thanks,
>> dims
>>
>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>
>>
>>> Thanks Michael for your response.
>>>
>>> I was just wondering what would be idle time to wait before i start
>>> work
>>> on this ?
>>> Does anyone has an opinion, Is there any other list where i should send
>>> this mail
>>> before making changes ?
>>>
>>> - Neeraj
>>>
>>> Michael Glavassevich wrote:
>>>
>>>
>>>
>>>> Hi Neeraj,
>>>>
>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>>>> making a branch for the old JAXP sources on the current main trunk.
>>>>
>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>> updates
>>>> have been applied to the JAXP 1.2 sources. This is the branch we've
>>>> used
>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>> assume a
>>>> similar branch will exist for 1.3.
>>>>
>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Hello All,
>>>>>
>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>> zip but
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> mail bounced back with the following message
>>>>>
>>>>> <error>
>>>>> ----- The following addresses had permanent fatal errors -----
>>>>> <ge...@xml.apache.org>
>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>> </error>
>>>>>
>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>> server somewhere ?
>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>
>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>> community
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> to help put it in a
>>>>> a branch and make it work there. As i think due to large number of
>>>>> changes it would be a considerable
>>>>> amount of work. This will also help the committers & community to
>>>>> have a
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> look at the code before
>>>>> it is merged into the main stream work.
>>>>>
>>>>> I think i have commit access at xml-commons so i can commit the
>>>>> sources
>>>>> in xml-commons branch
>>>>> or main trunk (and create branch for old jaxp sources ). What is the
>>>>> opinion of community ? I can
>>>>> start this as soon as i get a consensus from the community. My
>>>>> preference is to put the sources on
>>>>> xml-commons main trunk.
>>>>>
>>>>> Please let me know how should i proceed.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> - Neeraj
>>>>>
>>>>>
>>>>> Hello All,
>>>>>
>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>> implementation to Apache XML.*
>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>> functionalities.
>>>>>
>>>>> * New Schema Validation Framework
>>>>> * New Object Model neutral XPath APIs
>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>> * Reuse parser instance
>>>>> * Security enhancements
>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>> Save, SAX
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 2, XML 1.1 and XInclude)
>>>>>
>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>
>>>>> Due to large size of code base i will be sending different mails
>>>>> for the
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> source code of Xerces & Xalan.
>>>>>
>>>>> I have attached the original mail where i proposed the process of
>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>> integrating this donation into the main stream work of Xerces &
>>>>> Xalan.
>>>>> There was a general consensus to my proposal
>>>>> and we can discuss more about the technicalities of merging with
>>>>> in the
>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>> community.
>>>>>
>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>
>>>>> - Neeraj
>>>>>
>>>>>
>>>>>
>>>>> Neeraj Bajaj wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Geir Magnusson Jr. wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>> ball
>>>>>>>> on this one.
>>>>>>>>
>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume that
>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>> achieved.
>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>> process
>>>>>>> hold things up.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> Subject:
>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>> From:
>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>> Date:
>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>
>>>>> To:
>>>>> general@xml.apache.org
>>>>> CC:
>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>> <Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>
>>>>>
>>>>> Hello All,
>>>>>
>>>>>
>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>> final. JAXP
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>> It introduces new Schema independent validation framework which
>>>>> decouples the validation as a process independent from parsing.
>>>>> It allows to compile Schema to an immutable memory representation of
>>>>> Grammar which can validate different instances of XML document thus
>>>>> greatly improving the performance of XML processing. XPath language
>>>>> provides a simple, concise syntax for accessing individual parts
>>>>> of an
>>>>> XML document. JAXP 1.3 defines XPath APIs which provides access to
>>>>> the
>>>>> XPath evaluation environment and expression results independent
>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>> Datatypes to
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also
>>>>> adds
>>>>> the ability to reset XML Parser and Transformer instance , allowing
>>>>> application to reuse the same instance to process multiple XML
>>>>> documents. This also helps in increasing XML processing performance.
>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>> L/S, XML
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 1.1, XInclude.
>>>>>
>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>> Reference Implementation) to Apache. *
>>>>>
>>>>>
>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>
>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>>>> Implementation). RI has been done using
>>>>> Xerces/Xalan as code base. RI contains the implementation of newly
>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>> Transformer
>>>>> Reset changes, Secured XML Processing changes.
>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>> XInclude
>>>>> already exist on Apache Xerces. So in the next
>>>>> section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>> suggested where implementation component should reside i.e. Xerces or
>>>>> Xalan. Any idea or feedback for the smoother and
>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>> Xerces &
>>>>> Xalan is very welcome.
>>>>>
>>>>>
>>>>>
>>>>> *JAXP 1.3 APIs: *
>>>>>
>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>> APIs
>>>>> are used by many different projects.
>>>>> With JSR 206 declared as final and many new standards emerging, we
>>>>> should update xml-commons to JAXP 1.3
>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>> trunk
>>>>> and apply a tag.
>>>>>
>>>>>
>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>
>>>>>
>>>>>
>>>>
>>>> Xerces)*
>>>>
>>>>
>>>>
>>>>
>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>
>>>>> javax.xml.datatype
>>>>> javax.xml.validation
>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>
>>>>> which should reside at Xerces.
>>>>>
>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>>>> that branch. This will help
>>>>> other Xerces active committers to have a chance to look at it before
>>>>> these changes being finally
>>>>> committed to main trunk. This process would require merging
>>>>> changes to
>>>>> the branch and then committing
>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>
>>>>>
>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>> Xalan)*
>>>>>
>>>>>
>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>>>> done in "javax.xml.transform" package
>>>>> for ex. now application can use the same Transformer instance by
>>>>> invoking reset().
>>>>>
>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>> branch
>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>> put there. This will help other Xalan active committers to have a
>>>>> chance
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> to look at it before these changes being finally
>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>> for this
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> process.
>>>>>
>>>>>
>>>>> As always, all feedbacks are more than welcome.
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Neeraj
>>>>>
>>>>>
>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>> [2]
>>>>> http://java.sun.com/j2se/1.5.
>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>> [3]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> [4]
>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>> summary.html
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> Michael Glavassevich
>>>> XML Parser Development
>>>> IBM Toronto Lab
>>>> E-mail: mrglavas@ca.ibm.com
>>>> E-mail: mrglavas@apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ok I just finished uploading JAXP 1.3 sources in
"*xml-commons/contrib/jaxp13"* directory.
There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip which
corresponds to jaxp-api,
xerces & xalan sources respectively.
- Neeraj
Neeraj Bajaj wrote:
> That really sounds good to me.. so i would try to finish it today.
> I will send mail to the community when i am done.
>
> Thanks dims for the suggestion.
>
> - Neeraj
>
> Davanum Srinivas wrote:
>
>> Neeraj,
>>
>> my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
>> cvs so everyone can take a look (and then pick on the bits they
>> want/need)...yes, changes to xml-commons can be made ASAP (after
>> tagging the current code in the main trunk there) and it's upto the
>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>
>> thanks,
>> dims
>>
>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>
>>
>>> Thanks Michael for your response.
>>>
>>> I was just wondering what would be idle time to wait before i start
>>> work
>>> on this ?
>>> Does anyone has an opinion, Is there any other list where i should send
>>> this mail
>>> before making changes ?
>>>
>>> - Neeraj
>>>
>>> Michael Glavassevich wrote:
>>>
>>>
>>>
>>>> Hi Neeraj,
>>>>
>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>>>> making a branch for the old JAXP sources on the current main trunk.
>>>>
>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>> updates
>>>> have been applied to the JAXP 1.2 sources. This is the branch we've
>>>> used
>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>> assume a
>>>> similar branch will exist for 1.3.
>>>>
>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Hello All,
>>>>>
>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>> zip but
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> mail bounced back with the following message
>>>>>
>>>>> <error>
>>>>> ----- The following addresses had permanent fatal errors -----
>>>>> <ge...@xml.apache.org>
>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>> </error>
>>>>>
>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>> server somewhere ?
>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>
>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>> community
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> to help put it in a
>>>>> a branch and make it work there. As i think due to large number of
>>>>> changes it would be a considerable
>>>>> amount of work. This will also help the committers & community to
>>>>> have a
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> look at the code before
>>>>> it is merged into the main stream work.
>>>>>
>>>>> I think i have commit access at xml-commons so i can commit the
>>>>> sources
>>>>> in xml-commons branch
>>>>> or main trunk (and create branch for old jaxp sources ). What is the
>>>>> opinion of community ? I can
>>>>> start this as soon as i get a consensus from the community. My
>>>>> preference is to put the sources on
>>>>> xml-commons main trunk.
>>>>>
>>>>> Please let me know how should i proceed.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> - Neeraj
>>>>>
>>>>>
>>>>> Hello All,
>>>>>
>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>> implementation to Apache XML.*
>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>> functionalities.
>>>>>
>>>>> * New Schema Validation Framework
>>>>> * New Object Model neutral XPath APIs
>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>> * Reuse parser instance
>>>>> * Security enhancements
>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>> Save, SAX
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 2, XML 1.1 and XInclude)
>>>>>
>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>
>>>>> Due to large size of code base i will be sending different mails
>>>>> for the
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> source code of Xerces & Xalan.
>>>>>
>>>>> I have attached the original mail where i proposed the process of
>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>> integrating this donation into the main stream work of Xerces &
>>>>> Xalan.
>>>>> There was a general consensus to my proposal
>>>>> and we can discuss more about the technicalities of merging with
>>>>> in the
>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>> community.
>>>>>
>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>
>>>>> - Neeraj
>>>>>
>>>>>
>>>>>
>>>>> Neeraj Bajaj wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Geir Magnusson Jr. wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>> ball
>>>>>>>> on this one.
>>>>>>>>
>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume that
>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>> achieved.
>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>> process
>>>>>>> hold things up.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> Subject:
>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>> From:
>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>> Date:
>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>
>>>>> To:
>>>>> general@xml.apache.org
>>>>> CC:
>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>> <Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>
>>>>>
>>>>> Hello All,
>>>>>
>>>>>
>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>> final. JAXP
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>> It introduces new Schema independent validation framework which
>>>>> decouples the validation as a process independent from parsing.
>>>>> It allows to compile Schema to an immutable memory representation of
>>>>> Grammar which can validate different instances of XML document thus
>>>>> greatly improving the performance of XML processing. XPath language
>>>>> provides a simple, concise syntax for accessing individual parts
>>>>> of an
>>>>> XML document. JAXP 1.3 defines XPath APIs which provides access to
>>>>> the
>>>>> XPath evaluation environment and expression results independent
>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>> Datatypes to
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also
>>>>> adds
>>>>> the ability to reset XML Parser and Transformer instance , allowing
>>>>> application to reuse the same instance to process multiple XML
>>>>> documents. This also helps in increasing XML processing performance.
>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>> L/S, XML
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 1.1, XInclude.
>>>>>
>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>> Reference Implementation) to Apache. *
>>>>>
>>>>>
>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>
>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>>>> Implementation). RI has been done using
>>>>> Xerces/Xalan as code base. RI contains the implementation of newly
>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>> Transformer
>>>>> Reset changes, Secured XML Processing changes.
>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>> XInclude
>>>>> already exist on Apache Xerces. So in the next
>>>>> section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>> suggested where implementation component should reside i.e. Xerces or
>>>>> Xalan. Any idea or feedback for the smoother and
>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>> Xerces &
>>>>> Xalan is very welcome.
>>>>>
>>>>>
>>>>>
>>>>> *JAXP 1.3 APIs: *
>>>>>
>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>> APIs
>>>>> are used by many different projects.
>>>>> With JSR 206 declared as final and many new standards emerging, we
>>>>> should update xml-commons to JAXP 1.3
>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>> trunk
>>>>> and apply a tag.
>>>>>
>>>>>
>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>
>>>>>
>>>>>
>>>>
>>>> Xerces)*
>>>>
>>>>
>>>>
>>>>
>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>
>>>>> javax.xml.datatype
>>>>> javax.xml.validation
>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>
>>>>> which should reside at Xerces.
>>>>>
>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>>>> that branch. This will help
>>>>> other Xerces active committers to have a chance to look at it before
>>>>> these changes being finally
>>>>> committed to main trunk. This process would require merging
>>>>> changes to
>>>>> the branch and then committing
>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>
>>>>>
>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>> Xalan)*
>>>>>
>>>>>
>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>>>> done in "javax.xml.transform" package
>>>>> for ex. now application can use the same Transformer instance by
>>>>> invoking reset().
>>>>>
>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>> branch
>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>> put there. This will help other Xalan active committers to have a
>>>>> chance
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> to look at it before these changes being finally
>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>> for this
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> process.
>>>>>
>>>>>
>>>>> As always, all feedbacks are more than welcome.
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Neeraj
>>>>>
>>>>>
>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>> [2]
>>>>> http://java.sun.com/j2se/1.5.
>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>> [3]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> [4]
>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>> summary.html
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> Michael Glavassevich
>>>> XML Parser Development
>>>> IBM Toronto Lab
>>>> E-mail: mrglavas@ca.ibm.com
>>>> E-mail: mrglavas@apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ok I just finished uploading JAXP 1.3 sources in
"*xml-commons/contrib/jaxp13"* directory.
There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip which
corresponds to jaxp-api,
xerces & xalan sources respectively.
- Neeraj
Neeraj Bajaj wrote:
> That really sounds good to me.. so i would try to finish it today.
> I will send mail to the community when i am done.
>
> Thanks dims for the suggestion.
>
> - Neeraj
>
> Davanum Srinivas wrote:
>
>> Neeraj,
>>
>> my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
>> cvs so everyone can take a look (and then pick on the bits they
>> want/need)...yes, changes to xml-commons can be made ASAP (after
>> tagging the current code in the main trunk there) and it's upto the
>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>
>> thanks,
>> dims
>>
>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>
>>
>>> Thanks Michael for your response.
>>>
>>> I was just wondering what would be idle time to wait before i start
>>> work
>>> on this ?
>>> Does anyone has an opinion, Is there any other list where i should send
>>> this mail
>>> before making changes ?
>>>
>>> - Neeraj
>>>
>>> Michael Glavassevich wrote:
>>>
>>>
>>>
>>>> Hi Neeraj,
>>>>
>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>>>> making a branch for the old JAXP sources on the current main trunk.
>>>>
>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>> updates
>>>> have been applied to the JAXP 1.2 sources. This is the branch we've
>>>> used
>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>> assume a
>>>> similar branch will exist for 1.3.
>>>>
>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Hello All,
>>>>>
>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>> zip but
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> mail bounced back with the following message
>>>>>
>>>>> <error>
>>>>> ----- The following addresses had permanent fatal errors -----
>>>>> <ge...@xml.apache.org>
>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>> </error>
>>>>>
>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>> server somewhere ?
>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>
>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>> community
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> to help put it in a
>>>>> a branch and make it work there. As i think due to large number of
>>>>> changes it would be a considerable
>>>>> amount of work. This will also help the committers & community to
>>>>> have a
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> look at the code before
>>>>> it is merged into the main stream work.
>>>>>
>>>>> I think i have commit access at xml-commons so i can commit the
>>>>> sources
>>>>> in xml-commons branch
>>>>> or main trunk (and create branch for old jaxp sources ). What is the
>>>>> opinion of community ? I can
>>>>> start this as soon as i get a consensus from the community. My
>>>>> preference is to put the sources on
>>>>> xml-commons main trunk.
>>>>>
>>>>> Please let me know how should i proceed.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> - Neeraj
>>>>>
>>>>>
>>>>> Hello All,
>>>>>
>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>> implementation to Apache XML.*
>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>> functionalities.
>>>>>
>>>>> * New Schema Validation Framework
>>>>> * New Object Model neutral XPath APIs
>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>> * Reuse parser instance
>>>>> * Security enhancements
>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>> Save, SAX
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 2, XML 1.1 and XInclude)
>>>>>
>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>
>>>>> Due to large size of code base i will be sending different mails
>>>>> for the
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> source code of Xerces & Xalan.
>>>>>
>>>>> I have attached the original mail where i proposed the process of
>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>> integrating this donation into the main stream work of Xerces &
>>>>> Xalan.
>>>>> There was a general consensus to my proposal
>>>>> and we can discuss more about the technicalities of merging with
>>>>> in the
>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>> community.
>>>>>
>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>
>>>>> - Neeraj
>>>>>
>>>>>
>>>>>
>>>>> Neeraj Bajaj wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Geir Magnusson Jr. wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>> ball
>>>>>>>> on this one.
>>>>>>>>
>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume that
>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>> achieved.
>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>> process
>>>>>>> hold things up.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> Subject:
>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>> From:
>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>> Date:
>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>
>>>>> To:
>>>>> general@xml.apache.org
>>>>> CC:
>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>> <Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>
>>>>>
>>>>> Hello All,
>>>>>
>>>>>
>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>> final. JAXP
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>> It introduces new Schema independent validation framework which
>>>>> decouples the validation as a process independent from parsing.
>>>>> It allows to compile Schema to an immutable memory representation of
>>>>> Grammar which can validate different instances of XML document thus
>>>>> greatly improving the performance of XML processing. XPath language
>>>>> provides a simple, concise syntax for accessing individual parts
>>>>> of an
>>>>> XML document. JAXP 1.3 defines XPath APIs which provides access to
>>>>> the
>>>>> XPath evaluation environment and expression results independent
>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>> Datatypes to
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also
>>>>> adds
>>>>> the ability to reset XML Parser and Transformer instance , allowing
>>>>> application to reuse the same instance to process multiple XML
>>>>> documents. This also helps in increasing XML processing performance.
>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>> L/S, XML
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 1.1, XInclude.
>>>>>
>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>> Reference Implementation) to Apache. *
>>>>>
>>>>>
>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>
>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>>>> Implementation). RI has been done using
>>>>> Xerces/Xalan as code base. RI contains the implementation of newly
>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>> Transformer
>>>>> Reset changes, Secured XML Processing changes.
>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>> XInclude
>>>>> already exist on Apache Xerces. So in the next
>>>>> section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>> suggested where implementation component should reside i.e. Xerces or
>>>>> Xalan. Any idea or feedback for the smoother and
>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>> Xerces &
>>>>> Xalan is very welcome.
>>>>>
>>>>>
>>>>>
>>>>> *JAXP 1.3 APIs: *
>>>>>
>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>> APIs
>>>>> are used by many different projects.
>>>>> With JSR 206 declared as final and many new standards emerging, we
>>>>> should update xml-commons to JAXP 1.3
>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>> trunk
>>>>> and apply a tag.
>>>>>
>>>>>
>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>
>>>>>
>>>>>
>>>>
>>>> Xerces)*
>>>>
>>>>
>>>>
>>>>
>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>
>>>>> javax.xml.datatype
>>>>> javax.xml.validation
>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>
>>>>> which should reside at Xerces.
>>>>>
>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>>>> that branch. This will help
>>>>> other Xerces active committers to have a chance to look at it before
>>>>> these changes being finally
>>>>> committed to main trunk. This process would require merging
>>>>> changes to
>>>>> the branch and then committing
>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>
>>>>>
>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>> Xalan)*
>>>>>
>>>>>
>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>>>> done in "javax.xml.transform" package
>>>>> for ex. now application can use the same Transformer instance by
>>>>> invoking reset().
>>>>>
>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>> branch
>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>> put there. This will help other Xalan active committers to have a
>>>>> chance
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> to look at it before these changes being finally
>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>> for this
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> process.
>>>>>
>>>>>
>>>>> As always, all feedbacks are more than welcome.
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Neeraj
>>>>>
>>>>>
>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>> [2]
>>>>> http://java.sun.com/j2se/1.5.
>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>> [3]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> [4]
>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>> summary.html
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> Michael Glavassevich
>>>> XML Parser Development
>>>> IBM Toronto Lab
>>>> E-mail: mrglavas@ca.ibm.com
>>>> E-mail: mrglavas@apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ok I just finished uploading JAXP 1.3 sources in
"*xml-commons/contrib/jaxp13"* directory.
There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip which
corresponds to jaxp-api,
xerces & xalan sources respectively.
- Neeraj
Neeraj Bajaj wrote:
> That really sounds good to me.. so i would try to finish it today.
> I will send mail to the community when i am done.
>
> Thanks dims for the suggestion.
>
> - Neeraj
>
> Davanum Srinivas wrote:
>
>> Neeraj,
>>
>> my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
>> cvs so everyone can take a look (and then pick on the bits they
>> want/need)...yes, changes to xml-commons can be made ASAP (after
>> tagging the current code in the main trunk there) and it's upto the
>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>
>> thanks,
>> dims
>>
>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>
>>
>>> Thanks Michael for your response.
>>>
>>> I was just wondering what would be idle time to wait before i start
>>> work
>>> on this ?
>>> Does anyone has an opinion, Is there any other list where i should send
>>> this mail
>>> before making changes ?
>>>
>>> - Neeraj
>>>
>>> Michael Glavassevich wrote:
>>>
>>>
>>>
>>>> Hi Neeraj,
>>>>
>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>>>> making a branch for the old JAXP sources on the current main trunk.
>>>>
>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>> updates
>>>> have been applied to the JAXP 1.2 sources. This is the branch we've
>>>> used
>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>> assume a
>>>> similar branch will exist for 1.3.
>>>>
>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Hello All,
>>>>>
>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>> zip but
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> mail bounced back with the following message
>>>>>
>>>>> <error>
>>>>> ----- The following addresses had permanent fatal errors -----
>>>>> <ge...@xml.apache.org>
>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>> </error>
>>>>>
>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>> server somewhere ?
>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>
>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>> community
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> to help put it in a
>>>>> a branch and make it work there. As i think due to large number of
>>>>> changes it would be a considerable
>>>>> amount of work. This will also help the committers & community to
>>>>> have a
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> look at the code before
>>>>> it is merged into the main stream work.
>>>>>
>>>>> I think i have commit access at xml-commons so i can commit the
>>>>> sources
>>>>> in xml-commons branch
>>>>> or main trunk (and create branch for old jaxp sources ). What is the
>>>>> opinion of community ? I can
>>>>> start this as soon as i get a consensus from the community. My
>>>>> preference is to put the sources on
>>>>> xml-commons main trunk.
>>>>>
>>>>> Please let me know how should i proceed.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> - Neeraj
>>>>>
>>>>>
>>>>> Hello All,
>>>>>
>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>> implementation to Apache XML.*
>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>> functionalities.
>>>>>
>>>>> * New Schema Validation Framework
>>>>> * New Object Model neutral XPath APIs
>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>> * Reuse parser instance
>>>>> * Security enhancements
>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>> Save, SAX
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 2, XML 1.1 and XInclude)
>>>>>
>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>
>>>>> Due to large size of code base i will be sending different mails
>>>>> for the
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> source code of Xerces & Xalan.
>>>>>
>>>>> I have attached the original mail where i proposed the process of
>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>> integrating this donation into the main stream work of Xerces &
>>>>> Xalan.
>>>>> There was a general consensus to my proposal
>>>>> and we can discuss more about the technicalities of merging with
>>>>> in the
>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>> community.
>>>>>
>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>
>>>>> - Neeraj
>>>>>
>>>>>
>>>>>
>>>>> Neeraj Bajaj wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Geir Magnusson Jr. wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>> ball
>>>>>>>> on this one.
>>>>>>>>
>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume that
>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>> achieved.
>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>> process
>>>>>>> hold things up.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> Subject:
>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>> From:
>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>> Date:
>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>
>>>>> To:
>>>>> general@xml.apache.org
>>>>> CC:
>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>> <Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>
>>>>>
>>>>> Hello All,
>>>>>
>>>>>
>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>> final. JAXP
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>> It introduces new Schema independent validation framework which
>>>>> decouples the validation as a process independent from parsing.
>>>>> It allows to compile Schema to an immutable memory representation of
>>>>> Grammar which can validate different instances of XML document thus
>>>>> greatly improving the performance of XML processing. XPath language
>>>>> provides a simple, concise syntax for accessing individual parts
>>>>> of an
>>>>> XML document. JAXP 1.3 defines XPath APIs which provides access to
>>>>> the
>>>>> XPath evaluation environment and expression results independent
>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>> Datatypes to
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also
>>>>> adds
>>>>> the ability to reset XML Parser and Transformer instance , allowing
>>>>> application to reuse the same instance to process multiple XML
>>>>> documents. This also helps in increasing XML processing performance.
>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>> L/S, XML
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 1.1, XInclude.
>>>>>
>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>> Reference Implementation) to Apache. *
>>>>>
>>>>>
>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>
>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>>>> Implementation). RI has been done using
>>>>> Xerces/Xalan as code base. RI contains the implementation of newly
>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>> Transformer
>>>>> Reset changes, Secured XML Processing changes.
>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>> XInclude
>>>>> already exist on Apache Xerces. So in the next
>>>>> section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>> suggested where implementation component should reside i.e. Xerces or
>>>>> Xalan. Any idea or feedback for the smoother and
>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>> Xerces &
>>>>> Xalan is very welcome.
>>>>>
>>>>>
>>>>>
>>>>> *JAXP 1.3 APIs: *
>>>>>
>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>> APIs
>>>>> are used by many different projects.
>>>>> With JSR 206 declared as final and many new standards emerging, we
>>>>> should update xml-commons to JAXP 1.3
>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>> trunk
>>>>> and apply a tag.
>>>>>
>>>>>
>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>
>>>>>
>>>>>
>>>>
>>>> Xerces)*
>>>>
>>>>
>>>>
>>>>
>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>
>>>>> javax.xml.datatype
>>>>> javax.xml.validation
>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>
>>>>> which should reside at Xerces.
>>>>>
>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>>>> that branch. This will help
>>>>> other Xerces active committers to have a chance to look at it before
>>>>> these changes being finally
>>>>> committed to main trunk. This process would require merging
>>>>> changes to
>>>>> the branch and then committing
>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>
>>>>>
>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>> Xalan)*
>>>>>
>>>>>
>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>>>> done in "javax.xml.transform" package
>>>>> for ex. now application can use the same Transformer instance by
>>>>> invoking reset().
>>>>>
>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>> branch
>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>> put there. This will help other Xalan active committers to have a
>>>>> chance
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> to look at it before these changes being finally
>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>> for this
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> process.
>>>>>
>>>>>
>>>>> As always, all feedbacks are more than welcome.
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Neeraj
>>>>>
>>>>>
>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>> [2]
>>>>> http://java.sun.com/j2se/1.5.
>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>> [3]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> [4]
>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>> summary.html
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> Michael Glavassevich
>>>> XML Parser Development
>>>> IBM Toronto Lab
>>>> E-mail: mrglavas@ca.ibm.com
>>>> E-mail: mrglavas@apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ok I just finished uploading JAXP 1.3 sources in
"*xml-commons/contrib/jaxp13"* directory.
There are 3 files, jsr-206-src.zip, xml-xerces.zip, xalan-src.zip which
corresponds to jaxp-api,
xerces & xalan sources respectively.
- Neeraj
Neeraj Bajaj wrote:
> That really sounds good to me.. so i would try to finish it today.
> I will send mail to the community when i am done.
>
> Thanks dims for the suggestion.
>
> - Neeraj
>
> Davanum Srinivas wrote:
>
>> Neeraj,
>>
>> my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
>> cvs so everyone can take a look (and then pick on the bits they
>> want/need)...yes, changes to xml-commons can be made ASAP (after
>> tagging the current code in the main trunk there) and it's upto the
>> xml xerces/xalan folks to start picking up stuff as/when they fit.
>>
>> thanks,
>> dims
>>
>> On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>>
>>
>>> Thanks Michael for your response.
>>>
>>> I was just wondering what would be idle time to wait before i start
>>> work
>>> on this ?
>>> Does anyone has an opinion, Is there any other list where i should send
>>> this mail
>>> before making changes ?
>>>
>>> - Neeraj
>>>
>>> Michael Glavassevich wrote:
>>>
>>>
>>>
>>>> Hi Neeraj,
>>>>
>>>> +1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>>>> making a branch for the old JAXP sources on the current main trunk.
>>>>
>>>> There exists a branch called tck-jaxp-1_2_0 where fixes and other
>>>> updates
>>>> have been applied to the JAXP 1.2 sources. This is the branch we've
>>>> used
>>>> for generating the xml-apis.jar shipped with Xerces and Xalan. I
>>>> assume a
>>>> similar branch will exist for 1.3.
>>>>
>>>> Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Hello All,
>>>>>
>>>>> I sent the mail below with JAXP 1.3 APIs source code attached as
>>>>> zip but
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> mail bounced back with the following message
>>>>>
>>>>> <error>
>>>>> ----- The following addresses had permanent fatal errors -----
>>>>> <ge...@xml.apache.org>
>>>>> (reason: 552 ZIP attachments are not accepted here.)
>>>>> </error>
>>>>>
>>>>> What should i do now ? Is there a way to upload sources on Apache
>>>>> server somewhere ?
>>>>> Can anyone guide me what is the procedure for such code grants ?
>>>>>
>>>>> I am looking help from the active committers of Xerces & Xalan
>>>>> community
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> to help put it in a
>>>>> a branch and make it work there. As i think due to large number of
>>>>> changes it would be a considerable
>>>>> amount of work. This will also help the committers & community to
>>>>> have a
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> look at the code before
>>>>> it is merged into the main stream work.
>>>>>
>>>>> I think i have commit access at xml-commons so i can commit the
>>>>> sources
>>>>> in xml-commons branch
>>>>> or main trunk (and create branch for old jaxp sources ). What is the
>>>>> opinion of community ? I can
>>>>> start this as soon as i get a consensus from the community. My
>>>>> preference is to put the sources on
>>>>> xml-commons main trunk.
>>>>>
>>>>> Please let me know how should i proceed.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> - Neeraj
>>>>>
>>>>>
>>>>> Hello All,
>>>>>
>>>>> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>> implementation to Apache XML.*
>>>>> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>> significant advancement over JAXP 1.2 and adds whole lot of new
>>>>> functionalities.
>>>>>
>>>>> * New Schema Validation Framework
>>>>> * New Object Model neutral XPath APIs
>>>>> * New Java datatypes which maps to XML Schema Datatypes.
>>>>> * Reuse parser instance
>>>>> * Security enhancements
>>>>> * Support for the latest standards (DOM L3 Core, DOM L3 Load &
>>>>> Save, SAX
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 2, XML 1.1 and XInclude)
>>>>>
>>>>> *JAXP 1.3 APIs source code is attached with this mail. *
>>>>>
>>>>> Due to large size of code base i will be sending different mails
>>>>> for the
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> source code of Xerces & Xalan.
>>>>>
>>>>> I have attached the original mail where i proposed the process of
>>>>> upgrading xml-commons to JAXP 1.3 APIs and
>>>>> integrating this donation into the main stream work of Xerces &
>>>>> Xalan.
>>>>> There was a general consensus to my proposal
>>>>> and we can discuss more about the technicalities of merging with
>>>>> in the
>>>>> appropriate (Xml-commons, Xerces, Xalan)
>>>>> community.
>>>>>
>>>>> Let's upgrade to JAXP 1.3 :-)
>>>>>
>>>>> - Neeraj
>>>>>
>>>>>
>>>>>
>>>>> Neeraj Bajaj wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Geir Magnusson Jr. wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Excellent news! Thank to Sun folk and Geir for picking up the
>>>>>>>> ball
>>>>>>>> on this one.
>>>>>>>>
>>>>>>>> Note: once the papers are in the Hallowed Halls, I presume that
>>>>>>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>>>> xerces-j-dev as to how to actually check this in?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> There is no need to wait until Hall Hallowed-ness has been
>>>>>>> achieved.
>>>>>>> I have received them on behalf of the ASF, and don't let the
>>>>>>> process
>>>>>>> hold things up.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Great... Thanks Geir. No more held up is good
>>>>>>
>>>>>> - Neeraj
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> Subject:
>>>>> Donation of JAXP 1.3 Sources to Apache
>>>>> From:
>>>>> Neeraj Bajaj <Ne...@Sun.COM>
>>>>> Date:
>>>>> Tue, 12 Oct 2004 17:32:14 +0530
>>>>>
>>>>> To:
>>>>> general@xml.apache.org
>>>>> CC:
>>>>> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>>> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>>> <Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>>>> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>>
>>>>>
>>>>> Hello All,
>>>>>
>>>>>
>>>>> As most of you already know JSR 206 [1] JAXP 1.3 has become
>>>>> final. JAXP
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 1.3 adds lots of new features in the area of XML processing.
>>>>> It introduces new Schema independent validation framework which
>>>>> decouples the validation as a process independent from parsing.
>>>>> It allows to compile Schema to an immutable memory representation of
>>>>> Grammar which can validate different instances of XML document thus
>>>>> greatly improving the performance of XML processing. XPath language
>>>>> provides a simple, concise syntax for accessing individual parts
>>>>> of an
>>>>> XML document. JAXP 1.3 defines XPath APIs which provides access to
>>>>> the
>>>>> XPath evaluation environment and expression results independent
>>>>> of the underlying data object model. JAXP 1.3 also adds new
>>>>> Datatypes to
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> the Java platform which maps to some of the W3C XML Schema
>>>>> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also
>>>>> adds
>>>>> the ability to reset XML Parser and Transformer instance , allowing
>>>>> application to reuse the same instance to process multiple XML
>>>>> documents. This also helps in increasing XML processing performance.
>>>>> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3
>>>>> L/S, XML
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 1.1, XInclude.
>>>>>
>>>>> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>> Reference Implementation) to Apache. *
>>>>>
>>>>>
>>>>> /Details of JAXP 1.3 sources to be donated:/
>>>>>
>>>>> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>>>> Implementation). RI has been done using
>>>>> Xerces/Xalan as code base. RI contains the implementation of newly
>>>>> introduced Validation Framework [2], XPath APIs [3]
>>>>> , Datatypes [4] implementation, SAXParser, DocumentBuilder,
>>>>> Transformer
>>>>> Reset changes, Secured XML Processing changes.
>>>>> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1,
>>>>> XInclude
>>>>> already exist on Apache Xerces. So in the next
>>>>> section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>>>> changes into Apache Xerces & Xalan project. I have also
>>>>> suggested where implementation component should reside i.e. Xerces or
>>>>> Xalan. Any idea or feedback for the smoother and
>>>>> expedited merger of JAXP 1.3 sources into Apache xml-commons,
>>>>> Xerces &
>>>>> Xalan is very welcome.
>>>>>
>>>>>
>>>>>
>>>>> *JAXP 1.3 APIs: *
>>>>>
>>>>> JAXP APIs has been at xml-commons for a long time as these set of
>>>>> APIs
>>>>> are used by many different projects.
>>>>> With JSR 206 declared as final and many new standards emerging, we
>>>>> should update xml-commons to JAXP 1.3
>>>>> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main
>>>>> trunk
>>>>> and apply a tag.
>>>>>
>>>>>
>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>>
>>>>>
>>>>>
>>>>
>>>> Xerces)*
>>>>
>>>>
>>>>
>>>>
>>>>> JAXP 1.3 RI contains the implementation of following packages
>>>>>
>>>>> javax.xml.datatype
>>>>> javax.xml.validation
>>>>> javax.xml.parsers ( reset(), xinclude, etc.)
>>>>>
>>>>> which should reside at Xerces.
>>>>>
>>>>> I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>>>> that branch. This will help
>>>>> other Xerces active committers to have a chance to look at it before
>>>>> these changes being finally
>>>>> committed to main trunk. This process would require merging
>>>>> changes to
>>>>> the branch and then committing
>>>>> changes to main trunk, i seek help of active Xerces committers.
>>>>>
>>>>>
>>>>> *JAXP 1.3 RI: (Implementation components that should be part of
>>>>> Xalan)*
>>>>>
>>>>>
>>>>> JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>> (javax.xml.xpath.*) APIs which i think, should be part of
>>>>> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>>>> done in "javax.xml.transform" package
>>>>> for ex. now application can use the same Transformer instance by
>>>>> invoking reset().
>>>>>
>>>>> I propose the same for the Xalan/XSLTC project that we create a
>>>>> branch
>>>>> and JAXP 1.3 Reference Implementation changes are
>>>>> put there. This will help other Xalan active committers to have a
>>>>> chance
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> to look at it before these changes being finally
>>>>> committed to main trunk. Again i seek help of Xalan committers
>>>>> for this
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> process.
>>>>>
>>>>>
>>>>> As always, all feedbacks are more than welcome.
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Neeraj
>>>>>
>>>>>
>>>>> [1] http://www.jcp.org/en/jsr/detail?id=206
>>>>> [2]
>>>>> http://java.sun.com/j2se/1.5.
>>>>> 0/docs/api/javax/xml/validation/package-summary.html
>>>>> [3]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> [4]
>>>>> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>> summary.html
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> Michael Glavassevich
>>>> XML Parser Development
>>>> IBM Toronto Lab
>>>> E-mail: mrglavas@ca.ibm.com
>>>> E-mail: mrglavas@apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
That really sounds good to me.. so i would try to finish it today.
I will send mail to the community when i am done.
Thanks dims for the suggestion.
- Neeraj
Davanum Srinivas wrote:
>Neeraj,
>
>my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
>cvs so everyone can take a look (and then pick on the bits they
>want/need)...yes, changes to xml-commons can be made ASAP (after
>tagging the current code in the main trunk there) and it's upto the
>xml xerces/xalan folks to start picking up stuff as/when they fit.
>
>thanks,
>dims
>
>On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>
>
>>Thanks Michael for your response.
>>
>>I was just wondering what would be idle time to wait before i start work
>>on this ?
>>Does anyone has an opinion, Is there any other list where i should send
>>this mail
>>before making changes ?
>>
>>- Neeraj
>>
>>Michael Glavassevich wrote:
>>
>>
>>
>>>Hi Neeraj,
>>>
>>>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>>>making a branch for the old JAXP sources on the current main trunk.
>>>
>>>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>>>have been applied to the JAXP 1.2 sources. This is the branch we've used
>>>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>>>similar branch will exist for 1.3.
>>>
>>>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>>>
>>>
>>>
>>>
>>>
>>>>Hello All,
>>>>
>>>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>mail bounced back with the following message
>>>>
>>>><error>
>>>>----- The following addresses had permanent fatal errors -----
>>>><ge...@xml.apache.org>
>>>>(reason: 552 ZIP attachments are not accepted here.)
>>>></error>
>>>>
>>>>What should i do now ? Is there a way to upload sources on Apache
>>>>server somewhere ?
>>>>Can anyone guide me what is the procedure for such code grants ?
>>>>
>>>>I am looking help from the active committers of Xerces & Xalan community
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>to help put it in a
>>>>a branch and make it work there. As i think due to large number of
>>>>changes it would be a considerable
>>>>amount of work. This will also help the committers & community to have a
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>look at the code before
>>>>it is merged into the main stream work.
>>>>
>>>>I think i have commit access at xml-commons so i can commit the sources
>>>>in xml-commons branch
>>>>or main trunk (and create branch for old jaxp sources ). What is the
>>>>opinion of community ? I can
>>>>start this as soon as i get a consensus from the community. My
>>>>preference is to put the sources on
>>>>xml-commons main trunk.
>>>>
>>>>Please let me know how should i proceed.
>>>>
>>>>Thanks,
>>>>
>>>>- Neeraj
>>>>
>>>>
>>>>Hello All,
>>>>
>>>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>implementation to Apache XML.*
>>>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>significant advancement over JAXP 1.2 and adds whole lot of new
>>>>functionalities.
>>>>
>>>>* New Schema Validation Framework
>>>>* New Object Model neutral XPath APIs
>>>>* New Java datatypes which maps to XML Schema Datatypes.
>>>>* Reuse parser instance
>>>>* Security enhancements
>>>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>2, XML 1.1 and XInclude)
>>>>
>>>>*JAXP 1.3 APIs source code is attached with this mail. *
>>>>
>>>>Due to large size of code base i will be sending different mails for the
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>source code of Xerces & Xalan.
>>>>
>>>>I have attached the original mail where i proposed the process of
>>>>upgrading xml-commons to JAXP 1.3 APIs and
>>>>integrating this donation into the main stream work of Xerces & Xalan.
>>>>There was a general consensus to my proposal
>>>>and we can discuss more about the technicalities of merging with in the
>>>>appropriate (Xml-commons, Xerces, Xalan)
>>>>community.
>>>>
>>>>Let's upgrade to JAXP 1.3 :-)
>>>>
>>>>- Neeraj
>>>>
>>>>
>>>>
>>>>Neeraj Bajaj wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Geir Magnusson Jr. wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>>>on this one.
>>>>>>>
>>>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>>>xerces-j-dev as to how to actually check this in?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>>>I have received them on behalf of the ASF, and don't let the process
>>>>>>hold things up.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>Great... Thanks Geir. No more held up is good
>>>>>
>>>>>- Neeraj
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>------------------------------------------------------------------------
>>>>
>>>>Subject:
>>>>Donation of JAXP 1.3 Sources to Apache
>>>>From:
>>>>Neeraj Bajaj <Ne...@Sun.COM>
>>>>Date:
>>>>Tue, 12 Oct 2004 17:32:14 +0530
>>>>
>>>>To:
>>>>general@xml.apache.org
>>>>CC:
>>>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>
>>>>
>>>>Hello All,
>>>>
>>>>
>>>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>1.3 adds lots of new features in the area of XML processing.
>>>>It introduces new Schema independent validation framework which
>>>>decouples the validation as a process independent from parsing.
>>>>It allows to compile Schema to an immutable memory representation of
>>>>Grammar which can validate different instances of XML document thus
>>>>greatly improving the performance of XML processing. XPath language
>>>>provides a simple, concise syntax for accessing individual parts of an
>>>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>>>XPath evaluation environment and expression results independent
>>>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>the Java platform which maps to some of the W3C XML Schema
>>>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>>>the ability to reset XML Parser and Transformer instance , allowing
>>>>application to reuse the same instance to process multiple XML
>>>>documents. This also helps in increasing XML processing performance.
>>>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>1.1, XInclude.
>>>>
>>>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>Reference Implementation) to Apache. *
>>>>
>>>>
>>>>/Details of JAXP 1.3 sources to be donated:/
>>>>
>>>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>>>Implementation). RI has been done using
>>>>Xerces/Xalan as code base. RI contains the implementation of newly
>>>>introduced Validation Framework [2], XPath APIs [3]
>>>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>>>Reset changes, Secured XML Processing changes.
>>>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>>>already exist on Apache Xerces. So in the next
>>>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>>>changes into Apache Xerces & Xalan project. I have also
>>>>suggested where implementation component should reside i.e. Xerces or
>>>>Xalan. Any idea or feedback for the smoother and
>>>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>>>Xalan is very welcome.
>>>>
>>>>
>>>>
>>>>*JAXP 1.3 APIs: *
>>>>
>>>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>>>are used by many different projects.
>>>>With JSR 206 declared as final and many new standards emerging, we
>>>>should update xml-commons to JAXP 1.3
>>>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>>>and apply a tag.
>>>>
>>>>
>>>>*JAXP 1.3 RI: (Implementation components that should be part of
>>>>
>>>>
>>>>
>>>>
>>>Xerces)*
>>>
>>>
>>>
>>>
>>>>JAXP 1.3 RI contains the implementation of following packages
>>>>
>>>>javax.xml.datatype
>>>>javax.xml.validation
>>>>javax.xml.parsers ( reset(), xinclude, etc.)
>>>>
>>>>which should reside at Xerces.
>>>>
>>>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>>>that branch. This will help
>>>>other Xerces active committers to have a chance to look at it before
>>>>these changes being finally
>>>>committed to main trunk. This process would require merging changes to
>>>>the branch and then committing
>>>>changes to main trunk, i seek help of active Xerces committers.
>>>>
>>>>
>>>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>>>
>>>>
>>>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>(javax.xml.xpath.*) APIs which i think, should be part of
>>>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>>>done in "javax.xml.transform" package
>>>>for ex. now application can use the same Transformer instance by
>>>>invoking reset().
>>>>
>>>>I propose the same for the Xalan/XSLTC project that we create a branch
>>>>and JAXP 1.3 Reference Implementation changes are
>>>>put there. This will help other Xalan active committers to have a chance
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>to look at it before these changes being finally
>>>>committed to main trunk. Again i seek help of Xalan committers for this
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>process.
>>>>
>>>>
>>>>As always, all feedbacks are more than welcome.
>>>>
>>>>
>>>>Thanks,
>>>>Neeraj
>>>>
>>>>
>>>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>>>[2]
>>>>http://java.sun.com/j2se/1.5.
>>>>0/docs/api/javax/xml/validation/package-summary.html
>>>>[3]
>>>>
>>>>
>>>>
>>>>
>>>>
>>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>>>
>>>
>>>
>>>
>>>>[4]
>>>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>summary.html
>>>>
>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>Michael Glavassevich
>>>XML Parser Development
>>>IBM Toronto Lab
>>>E-mail: mrglavas@ca.ibm.com
>>>E-mail: mrglavas@apache.org
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xalan-dev-help@xml.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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
That really sounds good to me.. so i would try to finish it today.
I will send mail to the community when i am done.
Thanks dims for the suggestion.
- Neeraj
Davanum Srinivas wrote:
>Neeraj,
>
>my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
>cvs so everyone can take a look (and then pick on the bits they
>want/need)...yes, changes to xml-commons can be made ASAP (after
>tagging the current code in the main trunk there) and it's upto the
>xml xerces/xalan folks to start picking up stuff as/when they fit.
>
>thanks,
>dims
>
>On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>
>
>>Thanks Michael for your response.
>>
>>I was just wondering what would be idle time to wait before i start work
>>on this ?
>>Does anyone has an opinion, Is there any other list where i should send
>>this mail
>>before making changes ?
>>
>>- Neeraj
>>
>>Michael Glavassevich wrote:
>>
>>
>>
>>>Hi Neeraj,
>>>
>>>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>>>making a branch for the old JAXP sources on the current main trunk.
>>>
>>>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>>>have been applied to the JAXP 1.2 sources. This is the branch we've used
>>>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>>>similar branch will exist for 1.3.
>>>
>>>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>>>
>>>
>>>
>>>
>>>
>>>>Hello All,
>>>>
>>>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>mail bounced back with the following message
>>>>
>>>><error>
>>>>----- The following addresses had permanent fatal errors -----
>>>><ge...@xml.apache.org>
>>>>(reason: 552 ZIP attachments are not accepted here.)
>>>></error>
>>>>
>>>>What should i do now ? Is there a way to upload sources on Apache
>>>>server somewhere ?
>>>>Can anyone guide me what is the procedure for such code grants ?
>>>>
>>>>I am looking help from the active committers of Xerces & Xalan community
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>to help put it in a
>>>>a branch and make it work there. As i think due to large number of
>>>>changes it would be a considerable
>>>>amount of work. This will also help the committers & community to have a
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>look at the code before
>>>>it is merged into the main stream work.
>>>>
>>>>I think i have commit access at xml-commons so i can commit the sources
>>>>in xml-commons branch
>>>>or main trunk (and create branch for old jaxp sources ). What is the
>>>>opinion of community ? I can
>>>>start this as soon as i get a consensus from the community. My
>>>>preference is to put the sources on
>>>>xml-commons main trunk.
>>>>
>>>>Please let me know how should i proceed.
>>>>
>>>>Thanks,
>>>>
>>>>- Neeraj
>>>>
>>>>
>>>>Hello All,
>>>>
>>>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>implementation to Apache XML.*
>>>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>significant advancement over JAXP 1.2 and adds whole lot of new
>>>>functionalities.
>>>>
>>>>* New Schema Validation Framework
>>>>* New Object Model neutral XPath APIs
>>>>* New Java datatypes which maps to XML Schema Datatypes.
>>>>* Reuse parser instance
>>>>* Security enhancements
>>>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>2, XML 1.1 and XInclude)
>>>>
>>>>*JAXP 1.3 APIs source code is attached with this mail. *
>>>>
>>>>Due to large size of code base i will be sending different mails for the
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>source code of Xerces & Xalan.
>>>>
>>>>I have attached the original mail where i proposed the process of
>>>>upgrading xml-commons to JAXP 1.3 APIs and
>>>>integrating this donation into the main stream work of Xerces & Xalan.
>>>>There was a general consensus to my proposal
>>>>and we can discuss more about the technicalities of merging with in the
>>>>appropriate (Xml-commons, Xerces, Xalan)
>>>>community.
>>>>
>>>>Let's upgrade to JAXP 1.3 :-)
>>>>
>>>>- Neeraj
>>>>
>>>>
>>>>
>>>>Neeraj Bajaj wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Geir Magnusson Jr. wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>>>on this one.
>>>>>>>
>>>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>>>xerces-j-dev as to how to actually check this in?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>>>I have received them on behalf of the ASF, and don't let the process
>>>>>>hold things up.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>Great... Thanks Geir. No more held up is good
>>>>>
>>>>>- Neeraj
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>------------------------------------------------------------------------
>>>>
>>>>Subject:
>>>>Donation of JAXP 1.3 Sources to Apache
>>>>From:
>>>>Neeraj Bajaj <Ne...@Sun.COM>
>>>>Date:
>>>>Tue, 12 Oct 2004 17:32:14 +0530
>>>>
>>>>To:
>>>>general@xml.apache.org
>>>>CC:
>>>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>
>>>>
>>>>Hello All,
>>>>
>>>>
>>>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>1.3 adds lots of new features in the area of XML processing.
>>>>It introduces new Schema independent validation framework which
>>>>decouples the validation as a process independent from parsing.
>>>>It allows to compile Schema to an immutable memory representation of
>>>>Grammar which can validate different instances of XML document thus
>>>>greatly improving the performance of XML processing. XPath language
>>>>provides a simple, concise syntax for accessing individual parts of an
>>>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>>>XPath evaluation environment and expression results independent
>>>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>the Java platform which maps to some of the W3C XML Schema
>>>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>>>the ability to reset XML Parser and Transformer instance , allowing
>>>>application to reuse the same instance to process multiple XML
>>>>documents. This also helps in increasing XML processing performance.
>>>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>1.1, XInclude.
>>>>
>>>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>Reference Implementation) to Apache. *
>>>>
>>>>
>>>>/Details of JAXP 1.3 sources to be donated:/
>>>>
>>>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>>>Implementation). RI has been done using
>>>>Xerces/Xalan as code base. RI contains the implementation of newly
>>>>introduced Validation Framework [2], XPath APIs [3]
>>>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>>>Reset changes, Secured XML Processing changes.
>>>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>>>already exist on Apache Xerces. So in the next
>>>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>>>changes into Apache Xerces & Xalan project. I have also
>>>>suggested where implementation component should reside i.e. Xerces or
>>>>Xalan. Any idea or feedback for the smoother and
>>>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>>>Xalan is very welcome.
>>>>
>>>>
>>>>
>>>>*JAXP 1.3 APIs: *
>>>>
>>>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>>>are used by many different projects.
>>>>With JSR 206 declared as final and many new standards emerging, we
>>>>should update xml-commons to JAXP 1.3
>>>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>>>and apply a tag.
>>>>
>>>>
>>>>*JAXP 1.3 RI: (Implementation components that should be part of
>>>>
>>>>
>>>>
>>>>
>>>Xerces)*
>>>
>>>
>>>
>>>
>>>>JAXP 1.3 RI contains the implementation of following packages
>>>>
>>>>javax.xml.datatype
>>>>javax.xml.validation
>>>>javax.xml.parsers ( reset(), xinclude, etc.)
>>>>
>>>>which should reside at Xerces.
>>>>
>>>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>>>that branch. This will help
>>>>other Xerces active committers to have a chance to look at it before
>>>>these changes being finally
>>>>committed to main trunk. This process would require merging changes to
>>>>the branch and then committing
>>>>changes to main trunk, i seek help of active Xerces committers.
>>>>
>>>>
>>>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>>>
>>>>
>>>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>(javax.xml.xpath.*) APIs which i think, should be part of
>>>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>>>done in "javax.xml.transform" package
>>>>for ex. now application can use the same Transformer instance by
>>>>invoking reset().
>>>>
>>>>I propose the same for the Xalan/XSLTC project that we create a branch
>>>>and JAXP 1.3 Reference Implementation changes are
>>>>put there. This will help other Xalan active committers to have a chance
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>to look at it before these changes being finally
>>>>committed to main trunk. Again i seek help of Xalan committers for this
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>process.
>>>>
>>>>
>>>>As always, all feedbacks are more than welcome.
>>>>
>>>>
>>>>Thanks,
>>>>Neeraj
>>>>
>>>>
>>>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>>>[2]
>>>>http://java.sun.com/j2se/1.5.
>>>>0/docs/api/javax/xml/validation/package-summary.html
>>>>[3]
>>>>
>>>>
>>>>
>>>>
>>>>
>>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>>>
>>>
>>>
>>>
>>>>[4]
>>>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>summary.html
>>>>
>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>Michael Glavassevich
>>>XML Parser Development
>>>IBM Toronto Lab
>>>E-mail: mrglavas@ca.ibm.com
>>>E-mail: mrglavas@apache.org
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xalan-dev-help@xml.apache.org
>>>
>>>
>>>
>>>
>>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
That really sounds good to me.. so i would try to finish it today.
I will send mail to the community when i am done.
Thanks dims for the suggestion.
- Neeraj
Davanum Srinivas wrote:
>Neeraj,
>
>my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
>cvs so everyone can take a look (and then pick on the bits they
>want/need)...yes, changes to xml-commons can be made ASAP (after
>tagging the current code in the main trunk there) and it's upto the
>xml xerces/xalan folks to start picking up stuff as/when they fit.
>
>thanks,
>dims
>
>On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>
>
>>Thanks Michael for your response.
>>
>>I was just wondering what would be idle time to wait before i start work
>>on this ?
>>Does anyone has an opinion, Is there any other list where i should send
>>this mail
>>before making changes ?
>>
>>- Neeraj
>>
>>Michael Glavassevich wrote:
>>
>>
>>
>>>Hi Neeraj,
>>>
>>>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>>>making a branch for the old JAXP sources on the current main trunk.
>>>
>>>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>>>have been applied to the JAXP 1.2 sources. This is the branch we've used
>>>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>>>similar branch will exist for 1.3.
>>>
>>>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>>>
>>>
>>>
>>>
>>>
>>>>Hello All,
>>>>
>>>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>mail bounced back with the following message
>>>>
>>>><error>
>>>>----- The following addresses had permanent fatal errors -----
>>>><ge...@xml.apache.org>
>>>>(reason: 552 ZIP attachments are not accepted here.)
>>>></error>
>>>>
>>>>What should i do now ? Is there a way to upload sources on Apache
>>>>server somewhere ?
>>>>Can anyone guide me what is the procedure for such code grants ?
>>>>
>>>>I am looking help from the active committers of Xerces & Xalan community
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>to help put it in a
>>>>a branch and make it work there. As i think due to large number of
>>>>changes it would be a considerable
>>>>amount of work. This will also help the committers & community to have a
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>look at the code before
>>>>it is merged into the main stream work.
>>>>
>>>>I think i have commit access at xml-commons so i can commit the sources
>>>>in xml-commons branch
>>>>or main trunk (and create branch for old jaxp sources ). What is the
>>>>opinion of community ? I can
>>>>start this as soon as i get a consensus from the community. My
>>>>preference is to put the sources on
>>>>xml-commons main trunk.
>>>>
>>>>Please let me know how should i proceed.
>>>>
>>>>Thanks,
>>>>
>>>>- Neeraj
>>>>
>>>>
>>>>Hello All,
>>>>
>>>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>implementation to Apache XML.*
>>>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>significant advancement over JAXP 1.2 and adds whole lot of new
>>>>functionalities.
>>>>
>>>>* New Schema Validation Framework
>>>>* New Object Model neutral XPath APIs
>>>>* New Java datatypes which maps to XML Schema Datatypes.
>>>>* Reuse parser instance
>>>>* Security enhancements
>>>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>2, XML 1.1 and XInclude)
>>>>
>>>>*JAXP 1.3 APIs source code is attached with this mail. *
>>>>
>>>>Due to large size of code base i will be sending different mails for the
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>source code of Xerces & Xalan.
>>>>
>>>>I have attached the original mail where i proposed the process of
>>>>upgrading xml-commons to JAXP 1.3 APIs and
>>>>integrating this donation into the main stream work of Xerces & Xalan.
>>>>There was a general consensus to my proposal
>>>>and we can discuss more about the technicalities of merging with in the
>>>>appropriate (Xml-commons, Xerces, Xalan)
>>>>community.
>>>>
>>>>Let's upgrade to JAXP 1.3 :-)
>>>>
>>>>- Neeraj
>>>>
>>>>
>>>>
>>>>Neeraj Bajaj wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Geir Magnusson Jr. wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>>>on this one.
>>>>>>>
>>>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>>>xerces-j-dev as to how to actually check this in?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>>>I have received them on behalf of the ASF, and don't let the process
>>>>>>hold things up.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>Great... Thanks Geir. No more held up is good
>>>>>
>>>>>- Neeraj
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>------------------------------------------------------------------------
>>>>
>>>>Subject:
>>>>Donation of JAXP 1.3 Sources to Apache
>>>>From:
>>>>Neeraj Bajaj <Ne...@Sun.COM>
>>>>Date:
>>>>Tue, 12 Oct 2004 17:32:14 +0530
>>>>
>>>>To:
>>>>general@xml.apache.org
>>>>CC:
>>>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>
>>>>
>>>>Hello All,
>>>>
>>>>
>>>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>1.3 adds lots of new features in the area of XML processing.
>>>>It introduces new Schema independent validation framework which
>>>>decouples the validation as a process independent from parsing.
>>>>It allows to compile Schema to an immutable memory representation of
>>>>Grammar which can validate different instances of XML document thus
>>>>greatly improving the performance of XML processing. XPath language
>>>>provides a simple, concise syntax for accessing individual parts of an
>>>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>>>XPath evaluation environment and expression results independent
>>>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>the Java platform which maps to some of the W3C XML Schema
>>>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>>>the ability to reset XML Parser and Transformer instance , allowing
>>>>application to reuse the same instance to process multiple XML
>>>>documents. This also helps in increasing XML processing performance.
>>>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>1.1, XInclude.
>>>>
>>>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>Reference Implementation) to Apache. *
>>>>
>>>>
>>>>/Details of JAXP 1.3 sources to be donated:/
>>>>
>>>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>>>Implementation). RI has been done using
>>>>Xerces/Xalan as code base. RI contains the implementation of newly
>>>>introduced Validation Framework [2], XPath APIs [3]
>>>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>>>Reset changes, Secured XML Processing changes.
>>>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>>>already exist on Apache Xerces. So in the next
>>>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>>>changes into Apache Xerces & Xalan project. I have also
>>>>suggested where implementation component should reside i.e. Xerces or
>>>>Xalan. Any idea or feedback for the smoother and
>>>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>>>Xalan is very welcome.
>>>>
>>>>
>>>>
>>>>*JAXP 1.3 APIs: *
>>>>
>>>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>>>are used by many different projects.
>>>>With JSR 206 declared as final and many new standards emerging, we
>>>>should update xml-commons to JAXP 1.3
>>>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>>>and apply a tag.
>>>>
>>>>
>>>>*JAXP 1.3 RI: (Implementation components that should be part of
>>>>
>>>>
>>>>
>>>>
>>>Xerces)*
>>>
>>>
>>>
>>>
>>>>JAXP 1.3 RI contains the implementation of following packages
>>>>
>>>>javax.xml.datatype
>>>>javax.xml.validation
>>>>javax.xml.parsers ( reset(), xinclude, etc.)
>>>>
>>>>which should reside at Xerces.
>>>>
>>>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>>>that branch. This will help
>>>>other Xerces active committers to have a chance to look at it before
>>>>these changes being finally
>>>>committed to main trunk. This process would require merging changes to
>>>>the branch and then committing
>>>>changes to main trunk, i seek help of active Xerces committers.
>>>>
>>>>
>>>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>>>
>>>>
>>>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>(javax.xml.xpath.*) APIs which i think, should be part of
>>>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>>>done in "javax.xml.transform" package
>>>>for ex. now application can use the same Transformer instance by
>>>>invoking reset().
>>>>
>>>>I propose the same for the Xalan/XSLTC project that we create a branch
>>>>and JAXP 1.3 Reference Implementation changes are
>>>>put there. This will help other Xalan active committers to have a chance
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>to look at it before these changes being finally
>>>>committed to main trunk. Again i seek help of Xalan committers for this
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>process.
>>>>
>>>>
>>>>As always, all feedbacks are more than welcome.
>>>>
>>>>
>>>>Thanks,
>>>>Neeraj
>>>>
>>>>
>>>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>>>[2]
>>>>http://java.sun.com/j2se/1.5.
>>>>0/docs/api/javax/xml/validation/package-summary.html
>>>>[3]
>>>>
>>>>
>>>>
>>>>
>>>>
>>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>>>
>>>
>>>
>>>
>>>>[4]
>>>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>summary.html
>>>>
>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>Michael Glavassevich
>>>XML Parser Development
>>>IBM Toronto Lab
>>>E-mail: mrglavas@ca.ibm.com
>>>E-mail: mrglavas@apache.org
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xalan-dev-help@xml.apache.org
>>>
>>>
>>>
>>>
>>>
>
>
>
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
That really sounds good to me.. so i would try to finish it today.
I will send mail to the community when i am done.
Thanks dims for the suggestion.
- Neeraj
Davanum Srinivas wrote:
>Neeraj,
>
>my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
>cvs so everyone can take a look (and then pick on the bits they
>want/need)...yes, changes to xml-commons can be made ASAP (after
>tagging the current code in the main trunk there) and it's upto the
>xml xerces/xalan folks to start picking up stuff as/when they fit.
>
>thanks,
>dims
>
>On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>
>
>>Thanks Michael for your response.
>>
>>I was just wondering what would be idle time to wait before i start work
>>on this ?
>>Does anyone has an opinion, Is there any other list where i should send
>>this mail
>>before making changes ?
>>
>>- Neeraj
>>
>>Michael Glavassevich wrote:
>>
>>
>>
>>>Hi Neeraj,
>>>
>>>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>>>making a branch for the old JAXP sources on the current main trunk.
>>>
>>>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>>>have been applied to the JAXP 1.2 sources. This is the branch we've used
>>>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>>>similar branch will exist for 1.3.
>>>
>>>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>>>
>>>
>>>
>>>
>>>
>>>>Hello All,
>>>>
>>>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>mail bounced back with the following message
>>>>
>>>><error>
>>>>----- The following addresses had permanent fatal errors -----
>>>><ge...@xml.apache.org>
>>>>(reason: 552 ZIP attachments are not accepted here.)
>>>></error>
>>>>
>>>>What should i do now ? Is there a way to upload sources on Apache
>>>>server somewhere ?
>>>>Can anyone guide me what is the procedure for such code grants ?
>>>>
>>>>I am looking help from the active committers of Xerces & Xalan community
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>to help put it in a
>>>>a branch and make it work there. As i think due to large number of
>>>>changes it would be a considerable
>>>>amount of work. This will also help the committers & community to have a
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>look at the code before
>>>>it is merged into the main stream work.
>>>>
>>>>I think i have commit access at xml-commons so i can commit the sources
>>>>in xml-commons branch
>>>>or main trunk (and create branch for old jaxp sources ). What is the
>>>>opinion of community ? I can
>>>>start this as soon as i get a consensus from the community. My
>>>>preference is to put the sources on
>>>>xml-commons main trunk.
>>>>
>>>>Please let me know how should i proceed.
>>>>
>>>>Thanks,
>>>>
>>>>- Neeraj
>>>>
>>>>
>>>>Hello All,
>>>>
>>>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>implementation to Apache XML.*
>>>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>significant advancement over JAXP 1.2 and adds whole lot of new
>>>>functionalities.
>>>>
>>>>* New Schema Validation Framework
>>>>* New Object Model neutral XPath APIs
>>>>* New Java datatypes which maps to XML Schema Datatypes.
>>>>* Reuse parser instance
>>>>* Security enhancements
>>>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>2, XML 1.1 and XInclude)
>>>>
>>>>*JAXP 1.3 APIs source code is attached with this mail. *
>>>>
>>>>Due to large size of code base i will be sending different mails for the
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>source code of Xerces & Xalan.
>>>>
>>>>I have attached the original mail where i proposed the process of
>>>>upgrading xml-commons to JAXP 1.3 APIs and
>>>>integrating this donation into the main stream work of Xerces & Xalan.
>>>>There was a general consensus to my proposal
>>>>and we can discuss more about the technicalities of merging with in the
>>>>appropriate (Xml-commons, Xerces, Xalan)
>>>>community.
>>>>
>>>>Let's upgrade to JAXP 1.3 :-)
>>>>
>>>>- Neeraj
>>>>
>>>>
>>>>
>>>>Neeraj Bajaj wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Geir Magnusson Jr. wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>>>on this one.
>>>>>>>
>>>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>>>xerces-j-dev as to how to actually check this in?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>>>I have received them on behalf of the ASF, and don't let the process
>>>>>>hold things up.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>Great... Thanks Geir. No more held up is good
>>>>>
>>>>>- Neeraj
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>------------------------------------------------------------------------
>>>>
>>>>Subject:
>>>>Donation of JAXP 1.3 Sources to Apache
>>>>From:
>>>>Neeraj Bajaj <Ne...@Sun.COM>
>>>>Date:
>>>>Tue, 12 Oct 2004 17:32:14 +0530
>>>>
>>>>To:
>>>>general@xml.apache.org
>>>>CC:
>>>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>
>>>>
>>>>Hello All,
>>>>
>>>>
>>>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>1.3 adds lots of new features in the area of XML processing.
>>>>It introduces new Schema independent validation framework which
>>>>decouples the validation as a process independent from parsing.
>>>>It allows to compile Schema to an immutable memory representation of
>>>>Grammar which can validate different instances of XML document thus
>>>>greatly improving the performance of XML processing. XPath language
>>>>provides a simple, concise syntax for accessing individual parts of an
>>>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>>>XPath evaluation environment and expression results independent
>>>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>the Java platform which maps to some of the W3C XML Schema
>>>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>>>the ability to reset XML Parser and Transformer instance , allowing
>>>>application to reuse the same instance to process multiple XML
>>>>documents. This also helps in increasing XML processing performance.
>>>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>1.1, XInclude.
>>>>
>>>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>Reference Implementation) to Apache. *
>>>>
>>>>
>>>>/Details of JAXP 1.3 sources to be donated:/
>>>>
>>>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>>>Implementation). RI has been done using
>>>>Xerces/Xalan as code base. RI contains the implementation of newly
>>>>introduced Validation Framework [2], XPath APIs [3]
>>>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>>>Reset changes, Secured XML Processing changes.
>>>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>>>already exist on Apache Xerces. So in the next
>>>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>>>changes into Apache Xerces & Xalan project. I have also
>>>>suggested where implementation component should reside i.e. Xerces or
>>>>Xalan. Any idea or feedback for the smoother and
>>>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>>>Xalan is very welcome.
>>>>
>>>>
>>>>
>>>>*JAXP 1.3 APIs: *
>>>>
>>>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>>>are used by many different projects.
>>>>With JSR 206 declared as final and many new standards emerging, we
>>>>should update xml-commons to JAXP 1.3
>>>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>>>and apply a tag.
>>>>
>>>>
>>>>*JAXP 1.3 RI: (Implementation components that should be part of
>>>>
>>>>
>>>>
>>>>
>>>Xerces)*
>>>
>>>
>>>
>>>
>>>>JAXP 1.3 RI contains the implementation of following packages
>>>>
>>>>javax.xml.datatype
>>>>javax.xml.validation
>>>>javax.xml.parsers ( reset(), xinclude, etc.)
>>>>
>>>>which should reside at Xerces.
>>>>
>>>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>>>that branch. This will help
>>>>other Xerces active committers to have a chance to look at it before
>>>>these changes being finally
>>>>committed to main trunk. This process would require merging changes to
>>>>the branch and then committing
>>>>changes to main trunk, i seek help of active Xerces committers.
>>>>
>>>>
>>>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>>>
>>>>
>>>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>(javax.xml.xpath.*) APIs which i think, should be part of
>>>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>>>done in "javax.xml.transform" package
>>>>for ex. now application can use the same Transformer instance by
>>>>invoking reset().
>>>>
>>>>I propose the same for the Xalan/XSLTC project that we create a branch
>>>>and JAXP 1.3 Reference Implementation changes are
>>>>put there. This will help other Xalan active committers to have a chance
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>to look at it before these changes being finally
>>>>committed to main trunk. Again i seek help of Xalan committers for this
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>process.
>>>>
>>>>
>>>>As always, all feedbacks are more than welcome.
>>>>
>>>>
>>>>Thanks,
>>>>Neeraj
>>>>
>>>>
>>>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>>>[2]
>>>>http://java.sun.com/j2se/1.5.
>>>>0/docs/api/javax/xml/validation/package-summary.html
>>>>[3]
>>>>
>>>>
>>>>
>>>>
>>>>
>>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>>>
>>>
>>>
>>>
>>>>[4]
>>>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>summary.html
>>>>
>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>Michael Glavassevich
>>>XML Parser Development
>>>IBM Toronto Lab
>>>E-mail: mrglavas@ca.ibm.com
>>>E-mail: mrglavas@apache.org
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xalan-dev-help@xml.apache.org
>>>
>>>
>>>
>>>
>>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
That really sounds good to me.. so i would try to finish it today.
I will send mail to the community when i am done.
Thanks dims for the suggestion.
- Neeraj
Davanum Srinivas wrote:
>Neeraj,
>
>my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
>cvs so everyone can take a look (and then pick on the bits they
>want/need)...yes, changes to xml-commons can be made ASAP (after
>tagging the current code in the main trunk there) and it's upto the
>xml xerces/xalan folks to start picking up stuff as/when they fit.
>
>thanks,
>dims
>
>On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
>
>
>>Thanks Michael for your response.
>>
>>I was just wondering what would be idle time to wait before i start work
>>on this ?
>>Does anyone has an opinion, Is there any other list where i should send
>>this mail
>>before making changes ?
>>
>>- Neeraj
>>
>>Michael Glavassevich wrote:
>>
>>
>>
>>>Hi Neeraj,
>>>
>>>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>>>making a branch for the old JAXP sources on the current main trunk.
>>>
>>>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>>>have been applied to the JAXP 1.2 sources. This is the branch we've used
>>>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>>>similar branch will exist for 1.3.
>>>
>>>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>>>
>>>
>>>
>>>
>>>
>>>>Hello All,
>>>>
>>>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>mail bounced back with the following message
>>>>
>>>><error>
>>>>----- The following addresses had permanent fatal errors -----
>>>><ge...@xml.apache.org>
>>>>(reason: 552 ZIP attachments are not accepted here.)
>>>></error>
>>>>
>>>>What should i do now ? Is there a way to upload sources on Apache
>>>>server somewhere ?
>>>>Can anyone guide me what is the procedure for such code grants ?
>>>>
>>>>I am looking help from the active committers of Xerces & Xalan community
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>to help put it in a
>>>>a branch and make it work there. As i think due to large number of
>>>>changes it would be a considerable
>>>>amount of work. This will also help the committers & community to have a
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>look at the code before
>>>>it is merged into the main stream work.
>>>>
>>>>I think i have commit access at xml-commons so i can commit the sources
>>>>in xml-commons branch
>>>>or main trunk (and create branch for old jaxp sources ). What is the
>>>>opinion of community ? I can
>>>>start this as soon as i get a consensus from the community. My
>>>>preference is to put the sources on
>>>>xml-commons main trunk.
>>>>
>>>>Please let me know how should i proceed.
>>>>
>>>>Thanks,
>>>>
>>>>- Neeraj
>>>>
>>>>
>>>>Hello All,
>>>>
>>>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>>>implementation to Apache XML.*
>>>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>>>significant advancement over JAXP 1.2 and adds whole lot of new
>>>>functionalities.
>>>>
>>>>* New Schema Validation Framework
>>>>* New Object Model neutral XPath APIs
>>>>* New Java datatypes which maps to XML Schema Datatypes.
>>>>* Reuse parser instance
>>>>* Security enhancements
>>>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>2, XML 1.1 and XInclude)
>>>>
>>>>*JAXP 1.3 APIs source code is attached with this mail. *
>>>>
>>>>Due to large size of code base i will be sending different mails for the
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>source code of Xerces & Xalan.
>>>>
>>>>I have attached the original mail where i proposed the process of
>>>>upgrading xml-commons to JAXP 1.3 APIs and
>>>>integrating this donation into the main stream work of Xerces & Xalan.
>>>>There was a general consensus to my proposal
>>>>and we can discuss more about the technicalities of merging with in the
>>>>appropriate (Xml-commons, Xerces, Xalan)
>>>>community.
>>>>
>>>>Let's upgrade to JAXP 1.3 :-)
>>>>
>>>>- Neeraj
>>>>
>>>>
>>>>
>>>>Neeraj Bajaj wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Geir Magnusson Jr. wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>>>on this one.
>>>>>>>
>>>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>>>xerces-j-dev as to how to actually check this in?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>>>I have received them on behalf of the ASF, and don't let the process
>>>>>>hold things up.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>Great... Thanks Geir. No more held up is good
>>>>>
>>>>>- Neeraj
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>------------------------------------------------------------------------
>>>>
>>>>Subject:
>>>>Donation of JAXP 1.3 Sources to Apache
>>>>From:
>>>>Neeraj Bajaj <Ne...@Sun.COM>
>>>>Date:
>>>>Tue, 12 Oct 2004 17:32:14 +0530
>>>>
>>>>To:
>>>>general@xml.apache.org
>>>>CC:
>>>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>>>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>>>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>>>
>>>>
>>>>Hello All,
>>>>
>>>>
>>>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>1.3 adds lots of new features in the area of XML processing.
>>>>It introduces new Schema independent validation framework which
>>>>decouples the validation as a process independent from parsing.
>>>>It allows to compile Schema to an immutable memory representation of
>>>>Grammar which can validate different instances of XML document thus
>>>>greatly improving the performance of XML processing. XPath language
>>>>provides a simple, concise syntax for accessing individual parts of an
>>>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>>>XPath evaluation environment and expression results independent
>>>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>the Java platform which maps to some of the W3C XML Schema
>>>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>>>the ability to reset XML Parser and Transformer instance , allowing
>>>>application to reuse the same instance to process multiple XML
>>>>documents. This also helps in increasing XML processing performance.
>>>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>1.1, XInclude.
>>>>
>>>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>>>Reference Implementation) to Apache. *
>>>>
>>>>
>>>>/Details of JAXP 1.3 sources to be donated:/
>>>>
>>>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>>>Implementation). RI has been done using
>>>>Xerces/Xalan as code base. RI contains the implementation of newly
>>>>introduced Validation Framework [2], XPath APIs [3]
>>>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>>>Reset changes, Secured XML Processing changes.
>>>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>>>already exist on Apache Xerces. So in the next
>>>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>>>changes into Apache Xerces & Xalan project. I have also
>>>>suggested where implementation component should reside i.e. Xerces or
>>>>Xalan. Any idea or feedback for the smoother and
>>>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>>>Xalan is very welcome.
>>>>
>>>>
>>>>
>>>>*JAXP 1.3 APIs: *
>>>>
>>>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>>>are used by many different projects.
>>>>With JSR 206 declared as final and many new standards emerging, we
>>>>should update xml-commons to JAXP 1.3
>>>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>>>and apply a tag.
>>>>
>>>>
>>>>*JAXP 1.3 RI: (Implementation components that should be part of
>>>>
>>>>
>>>>
>>>>
>>>Xerces)*
>>>
>>>
>>>
>>>
>>>>JAXP 1.3 RI contains the implementation of following packages
>>>>
>>>>javax.xml.datatype
>>>>javax.xml.validation
>>>>javax.xml.parsers ( reset(), xinclude, etc.)
>>>>
>>>>which should reside at Xerces.
>>>>
>>>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>>>that branch. This will help
>>>>other Xerces active committers to have a chance to look at it before
>>>>these changes being finally
>>>>committed to main trunk. This process would require merging changes to
>>>>the branch and then committing
>>>>changes to main trunk, i seek help of active Xerces committers.
>>>>
>>>>
>>>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>>>
>>>>
>>>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>>>(javax.xml.xpath.*) APIs which i think, should be part of
>>>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>>>done in "javax.xml.transform" package
>>>>for ex. now application can use the same Transformer instance by
>>>>invoking reset().
>>>>
>>>>I propose the same for the Xalan/XSLTC project that we create a branch
>>>>and JAXP 1.3 Reference Implementation changes are
>>>>put there. This will help other Xalan active committers to have a chance
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>to look at it before these changes being finally
>>>>committed to main trunk. Again i seek help of Xalan committers for this
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>>process.
>>>>
>>>>
>>>>As always, all feedbacks are more than welcome.
>>>>
>>>>
>>>>Thanks,
>>>>Neeraj
>>>>
>>>>
>>>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>>>[2]
>>>>http://java.sun.com/j2se/1.5.
>>>>0/docs/api/javax/xml/validation/package-summary.html
>>>>[3]
>>>>
>>>>
>>>>
>>>>
>>>>
>>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>>>
>>>
>>>
>>>
>>>>[4]
>>>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>>>summary.html
>>>>
>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>Michael Glavassevich
>>>XML Parser Development
>>>IBM Toronto Lab
>>>E-mail: mrglavas@ca.ibm.com
>>>E-mail: mrglavas@apache.org
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xalan-dev-help@xml.apache.org
>>>
>>>
>>>
>>>
>>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Davanum Srinivas <da...@gmail.com>.
Neeraj,
my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
cvs so everyone can take a look (and then pick on the bits they
want/need)...yes, changes to xml-commons can be made ASAP (after
tagging the current code in the main trunk there) and it's upto the
xml xerces/xalan folks to start picking up stuff as/when they fit.
thanks,
dims
On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
> Thanks Michael for your response.
>
> I was just wondering what would be idle time to wait before i start work
> on this ?
> Does anyone has an opinion, Is there any other list where i should send
> this mail
> before making changes ?
>
> - Neeraj
>
> Michael Glavassevich wrote:
>
> >Hi Neeraj,
> >
> >+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
> >making a branch for the old JAXP sources on the current main trunk.
> >
> >There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
> >have been applied to the JAXP 1.2 sources. This is the branch we've used
> >for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
> >similar branch will exist for 1.3.
> >
> >Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
> >
> >
> >
> >>Hello All,
> >>
> >>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
> >>
> >>
> >
> >
> >
> >>mail bounced back with the following message
> >>
> >><error>
> >> ----- The following addresses had permanent fatal errors -----
> >><ge...@xml.apache.org>
> >> (reason: 552 ZIP attachments are not accepted here.)
> >></error>
> >>
> >>What should i do now ? Is there a way to upload sources on Apache
> >>server somewhere ?
> >>Can anyone guide me what is the procedure for such code grants ?
> >>
> >>I am looking help from the active committers of Xerces & Xalan community
> >>
> >>
> >
> >
> >
> >>to help put it in a
> >>a branch and make it work there. As i think due to large number of
> >>changes it would be a considerable
> >>amount of work. This will also help the committers & community to have a
> >>
> >>
> >
> >
> >
> >>look at the code before
> >>it is merged into the main stream work.
> >>
> >>I think i have commit access at xml-commons so i can commit the sources
> >>in xml-commons branch
> >>or main trunk (and create branch for old jaxp sources ). What is the
> >>opinion of community ? I can
> >>start this as soon as i get a consensus from the community. My
> >>preference is to put the sources on
> >>xml-commons main trunk.
> >>
> >>Please let me know how should i proceed.
> >>
> >>Thanks,
> >>
> >>- Neeraj
> >>
> >>
> >>Hello All,
> >>
> >>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>implementation to Apache XML.*
> >>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>significant advancement over JAXP 1.2 and adds whole lot of new
> >>functionalities.
> >>
> >>* New Schema Validation Framework
> >>* New Object Model neutral XPath APIs
> >>* New Java datatypes which maps to XML Schema Datatypes.
> >>* Reuse parser instance
> >>* Security enhancements
> >>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
> >>
> >>
> >
> >
> >
> >>2, XML 1.1 and XInclude)
> >>
> >>*JAXP 1.3 APIs source code is attached with this mail. *
> >>
> >>Due to large size of code base i will be sending different mails for the
> >>
> >>
> >
> >
> >
> >>source code of Xerces & Xalan.
> >>
> >>I have attached the original mail where i proposed the process of
> >>upgrading xml-commons to JAXP 1.3 APIs and
> >>integrating this donation into the main stream work of Xerces & Xalan.
> >>There was a general consensus to my proposal
> >>and we can discuss more about the technicalities of merging with in the
> >>appropriate (Xml-commons, Xerces, Xalan)
> >>community.
> >>
> >>Let's upgrade to JAXP 1.3 :-)
> >>
> >>- Neeraj
> >>
> >>
> >>
> >>Neeraj Bajaj wrote:
> >>
> >>
> >>
> >>>Geir Magnusson Jr. wrote:
> >>>
> >>>
> >>>
> >>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>
> >>>>
> >>>>
> >>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
> >>>>>on this one.
> >>>>>
> >>>>>Note: once the papers are in the Hallowed Halls, I presume that
> >>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>>>>xerces-j-dev as to how to actually check this in?
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>There is no need to wait until Hall Hallowed-ness has been achieved.
> >>>>I have received them on behalf of the ASF, and don't let the process
> >>>>hold things up.
> >>>>
> >>>>
> >>>
> >>>
> >>>Great... Thanks Geir. No more held up is good
> >>>
> >>>- Neeraj
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>
> >>>
> >>>
> >>------------------------------------------------------------------------
> >>
> >>Subject:
> >>Donation of JAXP 1.3 Sources to Apache
> >>From:
> >>Neeraj Bajaj <Ne...@Sun.COM>
> >>Date:
> >>Tue, 12 Oct 2004 17:32:14 +0530
> >>
> >>To:
> >>general@xml.apache.org
> >>CC:
> >>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
> >>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>
> >>
> >>Hello All,
> >>
> >>
> >>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
> >>
> >>
> >
> >
> >
> >>1.3 adds lots of new features in the area of XML processing.
> >>It introduces new Schema independent validation framework which
> >>decouples the validation as a process independent from parsing.
> >>It allows to compile Schema to an immutable memory representation of
> >>Grammar which can validate different instances of XML document thus
> >>greatly improving the performance of XML processing. XPath language
> >>provides a simple, concise syntax for accessing individual parts of an
> >>XML document. JAXP 1.3 defines XPath APIs which provides access to the
> >>XPath evaluation environment and expression results independent
> >>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
> >>
> >>
> >
> >
> >
> >>the Java platform which maps to some of the W3C XML Schema
> >>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
> >>the ability to reset XML Parser and Transformer instance , allowing
> >>application to reuse the same instance to process multiple XML
> >>documents. This also helps in increasing XML processing performance.
> >>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
> >>
> >>
> >
> >
> >
> >>1.1, XInclude.
> >>
> >>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> >>Reference Implementation) to Apache. *
> >>
> >>
> >>/Details of JAXP 1.3 sources to be donated:/
> >>
> >>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
> >>Implementation). RI has been done using
> >>Xerces/Xalan as code base. RI contains the implementation of newly
> >>introduced Validation Framework [2], XPath APIs [3]
> >>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
> >>Reset changes, Secured XML Processing changes.
> >>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
> >>already exist on Apache Xerces. So in the next
> >>section I have also proposed the way to merge rest of the JAXP 1.3 RI
> >>changes into Apache Xerces & Xalan project. I have also
> >>suggested where implementation component should reside i.e. Xerces or
> >>Xalan. Any idea or feedback for the smoother and
> >>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
> >>Xalan is very welcome.
> >>
> >>
> >>
> >>*JAXP 1.3 APIs: *
> >>
> >>JAXP APIs has been at xml-commons for a long time as these set of APIs
> >>are used by many different projects.
> >>With JSR 206 declared as final and many new standards emerging, we
> >>should update xml-commons to JAXP 1.3
> >>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
> >>and apply a tag.
> >>
> >>
> >>*JAXP 1.3 RI: (Implementation components that should be part of
> >>
> >>
> >Xerces)*
> >
> >
> >>JAXP 1.3 RI contains the implementation of following packages
> >>
> >>javax.xml.datatype
> >>javax.xml.validation
> >>javax.xml.parsers ( reset(), xinclude, etc.)
> >>
> >>which should reside at Xerces.
> >>
> >>I propose that we create a branch, and merge JAXP 1.3 RI changes into
> >>that branch. This will help
> >>other Xerces active committers to have a chance to look at it before
> >>these changes being finally
> >>committed to main trunk. This process would require merging changes to
> >>the branch and then committing
> >>changes to main trunk, i seek help of active Xerces committers.
> >>
> >>
> >>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
> >>
> >>
> >>JAXP 1.3 RI also has the implementation of newly developed XPath
> >>(javax.xml.xpath.*) APIs which i think, should be part of
> >>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
> >>done in "javax.xml.transform" package
> >>for ex. now application can use the same Transformer instance by
> >>invoking reset().
> >>
> >>I propose the same for the Xalan/XSLTC project that we create a branch
> >>and JAXP 1.3 Reference Implementation changes are
> >>put there. This will help other Xalan active committers to have a chance
> >>
> >>
> >
> >
> >
> >>to look at it before these changes being finally
> >>committed to main trunk. Again i seek help of Xalan committers for this
> >>
> >>
> >
> >
> >
> >>process.
> >>
> >>
> >>As always, all feedbacks are more than welcome.
> >>
> >>
> >>Thanks,
> >>Neeraj
> >>
> >>
> >>[1] http://www.jcp.org/en/jsr/detail?id=206
> >>[2]
> >>http://java.sun.com/j2se/1.5.
> >>0/docs/api/javax/xml/validation/package-summary.html
> >>[3]
> >>
> >>
> >>
> >http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
> >
> >
> >>[4]
> >>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>summary.html
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>
> >>
> >>
> >
> >Michael Glavassevich
> >XML Parser Development
> >IBM Toronto Lab
> >E-mail: mrglavas@ca.ibm.com
> >E-mail: mrglavas@apache.org
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >For additional commands, e-mail: xalan-dev-help@xml.apache.org
> >
> >
> >
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Davanum Srinivas <da...@gmail.com>.
Neeraj,
my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
cvs so everyone can take a look (and then pick on the bits they
want/need)...yes, changes to xml-commons can be made ASAP (after
tagging the current code in the main trunk there) and it's upto the
xml xerces/xalan folks to start picking up stuff as/when they fit.
thanks,
dims
On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
> Thanks Michael for your response.
>
> I was just wondering what would be idle time to wait before i start work
> on this ?
> Does anyone has an opinion, Is there any other list where i should send
> this mail
> before making changes ?
>
> - Neeraj
>
> Michael Glavassevich wrote:
>
> >Hi Neeraj,
> >
> >+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
> >making a branch for the old JAXP sources on the current main trunk.
> >
> >There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
> >have been applied to the JAXP 1.2 sources. This is the branch we've used
> >for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
> >similar branch will exist for 1.3.
> >
> >Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
> >
> >
> >
> >>Hello All,
> >>
> >>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
> >>
> >>
> >
> >
> >
> >>mail bounced back with the following message
> >>
> >><error>
> >> ----- The following addresses had permanent fatal errors -----
> >><ge...@xml.apache.org>
> >> (reason: 552 ZIP attachments are not accepted here.)
> >></error>
> >>
> >>What should i do now ? Is there a way to upload sources on Apache
> >>server somewhere ?
> >>Can anyone guide me what is the procedure for such code grants ?
> >>
> >>I am looking help from the active committers of Xerces & Xalan community
> >>
> >>
> >
> >
> >
> >>to help put it in a
> >>a branch and make it work there. As i think due to large number of
> >>changes it would be a considerable
> >>amount of work. This will also help the committers & community to have a
> >>
> >>
> >
> >
> >
> >>look at the code before
> >>it is merged into the main stream work.
> >>
> >>I think i have commit access at xml-commons so i can commit the sources
> >>in xml-commons branch
> >>or main trunk (and create branch for old jaxp sources ). What is the
> >>opinion of community ? I can
> >>start this as soon as i get a consensus from the community. My
> >>preference is to put the sources on
> >>xml-commons main trunk.
> >>
> >>Please let me know how should i proceed.
> >>
> >>Thanks,
> >>
> >>- Neeraj
> >>
> >>
> >>Hello All,
> >>
> >>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>implementation to Apache XML.*
> >>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>significant advancement over JAXP 1.2 and adds whole lot of new
> >>functionalities.
> >>
> >>* New Schema Validation Framework
> >>* New Object Model neutral XPath APIs
> >>* New Java datatypes which maps to XML Schema Datatypes.
> >>* Reuse parser instance
> >>* Security enhancements
> >>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
> >>
> >>
> >
> >
> >
> >>2, XML 1.1 and XInclude)
> >>
> >>*JAXP 1.3 APIs source code is attached with this mail. *
> >>
> >>Due to large size of code base i will be sending different mails for the
> >>
> >>
> >
> >
> >
> >>source code of Xerces & Xalan.
> >>
> >>I have attached the original mail where i proposed the process of
> >>upgrading xml-commons to JAXP 1.3 APIs and
> >>integrating this donation into the main stream work of Xerces & Xalan.
> >>There was a general consensus to my proposal
> >>and we can discuss more about the technicalities of merging with in the
> >>appropriate (Xml-commons, Xerces, Xalan)
> >>community.
> >>
> >>Let's upgrade to JAXP 1.3 :-)
> >>
> >>- Neeraj
> >>
> >>
> >>
> >>Neeraj Bajaj wrote:
> >>
> >>
> >>
> >>>Geir Magnusson Jr. wrote:
> >>>
> >>>
> >>>
> >>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>
> >>>>
> >>>>
> >>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
> >>>>>on this one.
> >>>>>
> >>>>>Note: once the papers are in the Hallowed Halls, I presume that
> >>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>>>>xerces-j-dev as to how to actually check this in?
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>There is no need to wait until Hall Hallowed-ness has been achieved.
> >>>>I have received them on behalf of the ASF, and don't let the process
> >>>>hold things up.
> >>>>
> >>>>
> >>>
> >>>
> >>>Great... Thanks Geir. No more held up is good
> >>>
> >>>- Neeraj
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>
> >>>
> >>>
> >>------------------------------------------------------------------------
> >>
> >>Subject:
> >>Donation of JAXP 1.3 Sources to Apache
> >>From:
> >>Neeraj Bajaj <Ne...@Sun.COM>
> >>Date:
> >>Tue, 12 Oct 2004 17:32:14 +0530
> >>
> >>To:
> >>general@xml.apache.org
> >>CC:
> >>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
> >>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>
> >>
> >>Hello All,
> >>
> >>
> >>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
> >>
> >>
> >
> >
> >
> >>1.3 adds lots of new features in the area of XML processing.
> >>It introduces new Schema independent validation framework which
> >>decouples the validation as a process independent from parsing.
> >>It allows to compile Schema to an immutable memory representation of
> >>Grammar which can validate different instances of XML document thus
> >>greatly improving the performance of XML processing. XPath language
> >>provides a simple, concise syntax for accessing individual parts of an
> >>XML document. JAXP 1.3 defines XPath APIs which provides access to the
> >>XPath evaluation environment and expression results independent
> >>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
> >>
> >>
> >
> >
> >
> >>the Java platform which maps to some of the W3C XML Schema
> >>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
> >>the ability to reset XML Parser and Transformer instance , allowing
> >>application to reuse the same instance to process multiple XML
> >>documents. This also helps in increasing XML processing performance.
> >>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
> >>
> >>
> >
> >
> >
> >>1.1, XInclude.
> >>
> >>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> >>Reference Implementation) to Apache. *
> >>
> >>
> >>/Details of JAXP 1.3 sources to be donated:/
> >>
> >>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
> >>Implementation). RI has been done using
> >>Xerces/Xalan as code base. RI contains the implementation of newly
> >>introduced Validation Framework [2], XPath APIs [3]
> >>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
> >>Reset changes, Secured XML Processing changes.
> >>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
> >>already exist on Apache Xerces. So in the next
> >>section I have also proposed the way to merge rest of the JAXP 1.3 RI
> >>changes into Apache Xerces & Xalan project. I have also
> >>suggested where implementation component should reside i.e. Xerces or
> >>Xalan. Any idea or feedback for the smoother and
> >>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
> >>Xalan is very welcome.
> >>
> >>
> >>
> >>*JAXP 1.3 APIs: *
> >>
> >>JAXP APIs has been at xml-commons for a long time as these set of APIs
> >>are used by many different projects.
> >>With JSR 206 declared as final and many new standards emerging, we
> >>should update xml-commons to JAXP 1.3
> >>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
> >>and apply a tag.
> >>
> >>
> >>*JAXP 1.3 RI: (Implementation components that should be part of
> >>
> >>
> >Xerces)*
> >
> >
> >>JAXP 1.3 RI contains the implementation of following packages
> >>
> >>javax.xml.datatype
> >>javax.xml.validation
> >>javax.xml.parsers ( reset(), xinclude, etc.)
> >>
> >>which should reside at Xerces.
> >>
> >>I propose that we create a branch, and merge JAXP 1.3 RI changes into
> >>that branch. This will help
> >>other Xerces active committers to have a chance to look at it before
> >>these changes being finally
> >>committed to main trunk. This process would require merging changes to
> >>the branch and then committing
> >>changes to main trunk, i seek help of active Xerces committers.
> >>
> >>
> >>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
> >>
> >>
> >>JAXP 1.3 RI also has the implementation of newly developed XPath
> >>(javax.xml.xpath.*) APIs which i think, should be part of
> >>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
> >>done in "javax.xml.transform" package
> >>for ex. now application can use the same Transformer instance by
> >>invoking reset().
> >>
> >>I propose the same for the Xalan/XSLTC project that we create a branch
> >>and JAXP 1.3 Reference Implementation changes are
> >>put there. This will help other Xalan active committers to have a chance
> >>
> >>
> >
> >
> >
> >>to look at it before these changes being finally
> >>committed to main trunk. Again i seek help of Xalan committers for this
> >>
> >>
> >
> >
> >
> >>process.
> >>
> >>
> >>As always, all feedbacks are more than welcome.
> >>
> >>
> >>Thanks,
> >>Neeraj
> >>
> >>
> >>[1] http://www.jcp.org/en/jsr/detail?id=206
> >>[2]
> >>http://java.sun.com/j2se/1.5.
> >>0/docs/api/javax/xml/validation/package-summary.html
> >>[3]
> >>
> >>
> >>
> >http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
> >
> >
> >>[4]
> >>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>summary.html
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>
> >>
> >>
> >
> >Michael Glavassevich
> >XML Parser Development
> >IBM Toronto Lab
> >E-mail: mrglavas@ca.ibm.com
> >E-mail: mrglavas@apache.org
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >For additional commands, e-mail: xalan-dev-help@xml.apache.org
> >
> >
> >
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Davanum Srinivas <da...@gmail.com>.
Neeraj,
my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
cvs so everyone can take a look (and then pick on the bits they
want/need)...yes, changes to xml-commons can be made ASAP (after
tagging the current code in the main trunk there) and it's upto the
xml xerces/xalan folks to start picking up stuff as/when they fit.
thanks,
dims
On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
> Thanks Michael for your response.
>
> I was just wondering what would be idle time to wait before i start work
> on this ?
> Does anyone has an opinion, Is there any other list where i should send
> this mail
> before making changes ?
>
> - Neeraj
>
> Michael Glavassevich wrote:
>
> >Hi Neeraj,
> >
> >+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
> >making a branch for the old JAXP sources on the current main trunk.
> >
> >There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
> >have been applied to the JAXP 1.2 sources. This is the branch we've used
> >for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
> >similar branch will exist for 1.3.
> >
> >Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
> >
> >
> >
> >>Hello All,
> >>
> >>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
> >>
> >>
> >
> >
> >
> >>mail bounced back with the following message
> >>
> >><error>
> >> ----- The following addresses had permanent fatal errors -----
> >><ge...@xml.apache.org>
> >> (reason: 552 ZIP attachments are not accepted here.)
> >></error>
> >>
> >>What should i do now ? Is there a way to upload sources on Apache
> >>server somewhere ?
> >>Can anyone guide me what is the procedure for such code grants ?
> >>
> >>I am looking help from the active committers of Xerces & Xalan community
> >>
> >>
> >
> >
> >
> >>to help put it in a
> >>a branch and make it work there. As i think due to large number of
> >>changes it would be a considerable
> >>amount of work. This will also help the committers & community to have a
> >>
> >>
> >
> >
> >
> >>look at the code before
> >>it is merged into the main stream work.
> >>
> >>I think i have commit access at xml-commons so i can commit the sources
> >>in xml-commons branch
> >>or main trunk (and create branch for old jaxp sources ). What is the
> >>opinion of community ? I can
> >>start this as soon as i get a consensus from the community. My
> >>preference is to put the sources on
> >>xml-commons main trunk.
> >>
> >>Please let me know how should i proceed.
> >>
> >>Thanks,
> >>
> >>- Neeraj
> >>
> >>
> >>Hello All,
> >>
> >>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>implementation to Apache XML.*
> >>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>significant advancement over JAXP 1.2 and adds whole lot of new
> >>functionalities.
> >>
> >>* New Schema Validation Framework
> >>* New Object Model neutral XPath APIs
> >>* New Java datatypes which maps to XML Schema Datatypes.
> >>* Reuse parser instance
> >>* Security enhancements
> >>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
> >>
> >>
> >
> >
> >
> >>2, XML 1.1 and XInclude)
> >>
> >>*JAXP 1.3 APIs source code is attached with this mail. *
> >>
> >>Due to large size of code base i will be sending different mails for the
> >>
> >>
> >
> >
> >
> >>source code of Xerces & Xalan.
> >>
> >>I have attached the original mail where i proposed the process of
> >>upgrading xml-commons to JAXP 1.3 APIs and
> >>integrating this donation into the main stream work of Xerces & Xalan.
> >>There was a general consensus to my proposal
> >>and we can discuss more about the technicalities of merging with in the
> >>appropriate (Xml-commons, Xerces, Xalan)
> >>community.
> >>
> >>Let's upgrade to JAXP 1.3 :-)
> >>
> >>- Neeraj
> >>
> >>
> >>
> >>Neeraj Bajaj wrote:
> >>
> >>
> >>
> >>>Geir Magnusson Jr. wrote:
> >>>
> >>>
> >>>
> >>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>
> >>>>
> >>>>
> >>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
> >>>>>on this one.
> >>>>>
> >>>>>Note: once the papers are in the Hallowed Halls, I presume that
> >>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>>>>xerces-j-dev as to how to actually check this in?
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>There is no need to wait until Hall Hallowed-ness has been achieved.
> >>>>I have received them on behalf of the ASF, and don't let the process
> >>>>hold things up.
> >>>>
> >>>>
> >>>
> >>>
> >>>Great... Thanks Geir. No more held up is good
> >>>
> >>>- Neeraj
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>
> >>>
> >>>
> >>------------------------------------------------------------------------
> >>
> >>Subject:
> >>Donation of JAXP 1.3 Sources to Apache
> >>From:
> >>Neeraj Bajaj <Ne...@Sun.COM>
> >>Date:
> >>Tue, 12 Oct 2004 17:32:14 +0530
> >>
> >>To:
> >>general@xml.apache.org
> >>CC:
> >>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
> >>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>
> >>
> >>Hello All,
> >>
> >>
> >>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
> >>
> >>
> >
> >
> >
> >>1.3 adds lots of new features in the area of XML processing.
> >>It introduces new Schema independent validation framework which
> >>decouples the validation as a process independent from parsing.
> >>It allows to compile Schema to an immutable memory representation of
> >>Grammar which can validate different instances of XML document thus
> >>greatly improving the performance of XML processing. XPath language
> >>provides a simple, concise syntax for accessing individual parts of an
> >>XML document. JAXP 1.3 defines XPath APIs which provides access to the
> >>XPath evaluation environment and expression results independent
> >>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
> >>
> >>
> >
> >
> >
> >>the Java platform which maps to some of the W3C XML Schema
> >>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
> >>the ability to reset XML Parser and Transformer instance , allowing
> >>application to reuse the same instance to process multiple XML
> >>documents. This also helps in increasing XML processing performance.
> >>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
> >>
> >>
> >
> >
> >
> >>1.1, XInclude.
> >>
> >>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> >>Reference Implementation) to Apache. *
> >>
> >>
> >>/Details of JAXP 1.3 sources to be donated:/
> >>
> >>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
> >>Implementation). RI has been done using
> >>Xerces/Xalan as code base. RI contains the implementation of newly
> >>introduced Validation Framework [2], XPath APIs [3]
> >>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
> >>Reset changes, Secured XML Processing changes.
> >>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
> >>already exist on Apache Xerces. So in the next
> >>section I have also proposed the way to merge rest of the JAXP 1.3 RI
> >>changes into Apache Xerces & Xalan project. I have also
> >>suggested where implementation component should reside i.e. Xerces or
> >>Xalan. Any idea or feedback for the smoother and
> >>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
> >>Xalan is very welcome.
> >>
> >>
> >>
> >>*JAXP 1.3 APIs: *
> >>
> >>JAXP APIs has been at xml-commons for a long time as these set of APIs
> >>are used by many different projects.
> >>With JSR 206 declared as final and many new standards emerging, we
> >>should update xml-commons to JAXP 1.3
> >>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
> >>and apply a tag.
> >>
> >>
> >>*JAXP 1.3 RI: (Implementation components that should be part of
> >>
> >>
> >Xerces)*
> >
> >
> >>JAXP 1.3 RI contains the implementation of following packages
> >>
> >>javax.xml.datatype
> >>javax.xml.validation
> >>javax.xml.parsers ( reset(), xinclude, etc.)
> >>
> >>which should reside at Xerces.
> >>
> >>I propose that we create a branch, and merge JAXP 1.3 RI changes into
> >>that branch. This will help
> >>other Xerces active committers to have a chance to look at it before
> >>these changes being finally
> >>committed to main trunk. This process would require merging changes to
> >>the branch and then committing
> >>changes to main trunk, i seek help of active Xerces committers.
> >>
> >>
> >>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
> >>
> >>
> >>JAXP 1.3 RI also has the implementation of newly developed XPath
> >>(javax.xml.xpath.*) APIs which i think, should be part of
> >>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
> >>done in "javax.xml.transform" package
> >>for ex. now application can use the same Transformer instance by
> >>invoking reset().
> >>
> >>I propose the same for the Xalan/XSLTC project that we create a branch
> >>and JAXP 1.3 Reference Implementation changes are
> >>put there. This will help other Xalan active committers to have a chance
> >>
> >>
> >
> >
> >
> >>to look at it before these changes being finally
> >>committed to main trunk. Again i seek help of Xalan committers for this
> >>
> >>
> >
> >
> >
> >>process.
> >>
> >>
> >>As always, all feedbacks are more than welcome.
> >>
> >>
> >>Thanks,
> >>Neeraj
> >>
> >>
> >>[1] http://www.jcp.org/en/jsr/detail?id=206
> >>[2]
> >>http://java.sun.com/j2se/1.5.
> >>0/docs/api/javax/xml/validation/package-summary.html
> >>[3]
> >>
> >>
> >>
> >http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
> >
> >
> >>[4]
> >>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>summary.html
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>
> >>
> >>
> >
> >Michael Glavassevich
> >XML Parser Development
> >IBM Toronto Lab
> >E-mail: mrglavas@ca.ibm.com
> >E-mail: mrglavas@apache.org
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >For additional commands, e-mail: xalan-dev-help@xml.apache.org
> >
> >
> >
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Davanum Srinivas <da...@gmail.com>.
Neeraj,
my 2 cents...upload the whole thing say in xml-commons/contrib/jaxp13
cvs so everyone can take a look (and then pick on the bits they
want/need)...yes, changes to xml-commons can be made ASAP (after
tagging the current code in the main trunk there) and it's upto the
xml xerces/xalan folks to start picking up stuff as/when they fit.
thanks,
dims
On Apr 4, 2005 1:07 AM, Neeraj Bajaj <Ne...@sun.com> wrote:
> Thanks Michael for your response.
>
> I was just wondering what would be idle time to wait before i start work
> on this ?
> Does anyone has an opinion, Is there any other list where i should send
> this mail
> before making changes ?
>
> - Neeraj
>
> Michael Glavassevich wrote:
>
> >Hi Neeraj,
> >
> >+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
> >making a branch for the old JAXP sources on the current main trunk.
> >
> >There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
> >have been applied to the JAXP 1.2 sources. This is the branch we've used
> >for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
> >similar branch will exist for 1.3.
> >
> >Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
> >
> >
> >
> >>Hello All,
> >>
> >>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
> >>
> >>
> >
> >
> >
> >>mail bounced back with the following message
> >>
> >><error>
> >> ----- The following addresses had permanent fatal errors -----
> >><ge...@xml.apache.org>
> >> (reason: 552 ZIP attachments are not accepted here.)
> >></error>
> >>
> >>What should i do now ? Is there a way to upload sources on Apache
> >>server somewhere ?
> >>Can anyone guide me what is the procedure for such code grants ?
> >>
> >>I am looking help from the active committers of Xerces & Xalan community
> >>
> >>
> >
> >
> >
> >>to help put it in a
> >>a branch and make it work there. As i think due to large number of
> >>changes it would be a considerable
> >>amount of work. This will also help the committers & community to have a
> >>
> >>
> >
> >
> >
> >>look at the code before
> >>it is merged into the main stream work.
> >>
> >>I think i have commit access at xml-commons so i can commit the sources
> >>in xml-commons branch
> >>or main trunk (and create branch for old jaxp sources ). What is the
> >>opinion of community ? I can
> >>start this as soon as i get a consensus from the community. My
> >>preference is to put the sources on
> >>xml-commons main trunk.
> >>
> >>Please let me know how should i proceed.
> >>
> >>Thanks,
> >>
> >>- Neeraj
> >>
> >>
> >>Hello All,
> >>
> >>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
> >>implementation to Apache XML.*
> >>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> >>significant advancement over JAXP 1.2 and adds whole lot of new
> >>functionalities.
> >>
> >>* New Schema Validation Framework
> >>* New Object Model neutral XPath APIs
> >>* New Java datatypes which maps to XML Schema Datatypes.
> >>* Reuse parser instance
> >>* Security enhancements
> >>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
> >>
> >>
> >
> >
> >
> >>2, XML 1.1 and XInclude)
> >>
> >>*JAXP 1.3 APIs source code is attached with this mail. *
> >>
> >>Due to large size of code base i will be sending different mails for the
> >>
> >>
> >
> >
> >
> >>source code of Xerces & Xalan.
> >>
> >>I have attached the original mail where i proposed the process of
> >>upgrading xml-commons to JAXP 1.3 APIs and
> >>integrating this donation into the main stream work of Xerces & Xalan.
> >>There was a general consensus to my proposal
> >>and we can discuss more about the technicalities of merging with in the
> >>appropriate (Xml-commons, Xerces, Xalan)
> >>community.
> >>
> >>Let's upgrade to JAXP 1.3 :-)
> >>
> >>- Neeraj
> >>
> >>
> >>
> >>Neeraj Bajaj wrote:
> >>
> >>
> >>
> >>>Geir Magnusson Jr. wrote:
> >>>
> >>>
> >>>
> >>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>>>
> >>>>
> >>>>
> >>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
> >>>>>on this one.
> >>>>>
> >>>>>Note: once the papers are in the Hallowed Halls, I presume that
> >>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>>>>xerces-j-dev as to how to actually check this in?
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>There is no need to wait until Hall Hallowed-ness has been achieved.
> >>>>I have received them on behalf of the ASF, and don't let the process
> >>>>hold things up.
> >>>>
> >>>>
> >>>
> >>>
> >>>Great... Thanks Geir. No more held up is good
> >>>
> >>>- Neeraj
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>>
> >>>
> >>>
> >>------------------------------------------------------------------------
> >>
> >>Subject:
> >>Donation of JAXP 1.3 Sources to Apache
> >>From:
> >>Neeraj Bajaj <Ne...@Sun.COM>
> >>Date:
> >>Tue, 12 Oct 2004 17:32:14 +0530
> >>
> >>To:
> >>general@xml.apache.org
> >>CC:
> >>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> >><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> >>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> >><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
> >>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
> >>
> >>
> >>Hello All,
> >>
> >>
> >>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
> >>
> >>
> >
> >
> >
> >>1.3 adds lots of new features in the area of XML processing.
> >>It introduces new Schema independent validation framework which
> >>decouples the validation as a process independent from parsing.
> >>It allows to compile Schema to an immutable memory representation of
> >>Grammar which can validate different instances of XML document thus
> >>greatly improving the performance of XML processing. XPath language
> >>provides a simple, concise syntax for accessing individual parts of an
> >>XML document. JAXP 1.3 defines XPath APIs which provides access to the
> >>XPath evaluation environment and expression results independent
> >>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
> >>
> >>
> >
> >
> >
> >>the Java platform which maps to some of the W3C XML Schema
> >>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
> >>the ability to reset XML Parser and Transformer instance , allowing
> >>application to reuse the same instance to process multiple XML
> >>documents. This also helps in increasing XML processing performance.
> >>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
> >>
> >>
> >
> >
> >
> >>1.1, XInclude.
> >>
> >>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> >>Reference Implementation) to Apache. *
> >>
> >>
> >>/Details of JAXP 1.3 sources to be donated:/
> >>
> >>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
> >>Implementation). RI has been done using
> >>Xerces/Xalan as code base. RI contains the implementation of newly
> >>introduced Validation Framework [2], XPath APIs [3]
> >>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
> >>Reset changes, Secured XML Processing changes.
> >>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
> >>already exist on Apache Xerces. So in the next
> >>section I have also proposed the way to merge rest of the JAXP 1.3 RI
> >>changes into Apache Xerces & Xalan project. I have also
> >>suggested where implementation component should reside i.e. Xerces or
> >>Xalan. Any idea or feedback for the smoother and
> >>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
> >>Xalan is very welcome.
> >>
> >>
> >>
> >>*JAXP 1.3 APIs: *
> >>
> >>JAXP APIs has been at xml-commons for a long time as these set of APIs
> >>are used by many different projects.
> >>With JSR 206 declared as final and many new standards emerging, we
> >>should update xml-commons to JAXP 1.3
> >>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
> >>and apply a tag.
> >>
> >>
> >>*JAXP 1.3 RI: (Implementation components that should be part of
> >>
> >>
> >Xerces)*
> >
> >
> >>JAXP 1.3 RI contains the implementation of following packages
> >>
> >>javax.xml.datatype
> >>javax.xml.validation
> >>javax.xml.parsers ( reset(), xinclude, etc.)
> >>
> >>which should reside at Xerces.
> >>
> >>I propose that we create a branch, and merge JAXP 1.3 RI changes into
> >>that branch. This will help
> >>other Xerces active committers to have a chance to look at it before
> >>these changes being finally
> >>committed to main trunk. This process would require merging changes to
> >>the branch and then committing
> >>changes to main trunk, i seek help of active Xerces committers.
> >>
> >>
> >>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
> >>
> >>
> >>JAXP 1.3 RI also has the implementation of newly developed XPath
> >>(javax.xml.xpath.*) APIs which i think, should be part of
> >>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
> >>done in "javax.xml.transform" package
> >>for ex. now application can use the same Transformer instance by
> >>invoking reset().
> >>
> >>I propose the same for the Xalan/XSLTC project that we create a branch
> >>and JAXP 1.3 Reference Implementation changes are
> >>put there. This will help other Xalan active committers to have a chance
> >>
> >>
> >
> >
> >
> >>to look at it before these changes being finally
> >>committed to main trunk. Again i seek help of Xalan committers for this
> >>
> >>
> >
> >
> >
> >>process.
> >>
> >>
> >>As always, all feedbacks are more than welcome.
> >>
> >>
> >>Thanks,
> >>Neeraj
> >>
> >>
> >>[1] http://www.jcp.org/en/jsr/detail?id=206
> >>[2]
> >>http://java.sun.com/j2se/1.5.
> >>0/docs/api/javax/xml/validation/package-summary.html
> >>[3]
> >>
> >>
> >>
> >http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
> >
> >
> >>[4]
> >>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> >>summary.html
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> >>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >>
> >>
> >>
> >
> >Michael Glavassevich
> >XML Parser Development
> >IBM Toronto Lab
> >E-mail: mrglavas@ca.ibm.com
> >E-mail: mrglavas@apache.org
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >For additional commands, e-mail: xalan-dev-help@xml.apache.org
> >
> >
> >
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi Neeraj,
I'm +1 to putting the API source on xml-commons trunk. That was
originally supposed to represent the "latest and greatest" of common XML
parsing API's; now it'll be able to do so once again. :)
I think the implementation germane to XML parsing should be put on a
branch in Xerces.
Cheers,
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
Neeraj Bajaj <Ne...@Sun.COM>
04/04/2005 01:07 AM
Please respond to
xerces-j-dev
To
xalan-dev@xml.apache.org
cc
commons-dev@xml.apache.org, xerces-j-dev@xml.apache.org, Eduardo
Pelegri-Llopart <Ed...@Sun.COM>,
general@incubator.apache.org, general@xml.apache.org, Janet Breuer
<Ja...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
Suresh.K@Sun.COM
Subject
Re: Donation of JAXP 1.3 Sources to Apache
Thanks Michael for your response.
I was just wondering what would be idle time to wait before i start work
on this ?
Does anyone has an opinion, Is there any other list where i should send
this mail
before making changes ?
- Neeraj
Michael Glavassevich wrote:
>Hi Neeraj,
>
>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>making a branch for the old JAXP sources on the current main trunk.
>
>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>have been applied to the JAXP 1.2 sources. This is the branch we've used
>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>similar branch will exist for 1.3.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>
>
>
>>Hello All,
>>
>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>
>>
>
>
>
>>mail bounced back with the following message
>>
>><error>
>> ----- The following addresses had permanent fatal errors -----
>><ge...@xml.apache.org>
>> (reason: 552 ZIP attachments are not accepted here.)
>></error>
>>
>>What should i do now ? Is there a way to upload sources on Apache
>>server somewhere ?
>>Can anyone guide me what is the procedure for such code grants ?
>>
>>I am looking help from the active committers of Xerces & Xalan community
>>
>>
>
>
>
>>to help put it in a
>>a branch and make it work there. As i think due to large number of
>>changes it would be a considerable
>>amount of work. This will also help the committers & community to have a
>>
>>
>
>
>
>>look at the code before
>>it is merged into the main stream work.
>>
>>I think i have commit access at xml-commons so i can commit the sources
>>in xml-commons branch
>>or main trunk (and create branch for old jaxp sources ). What is the
>>opinion of community ? I can
>>start this as soon as i get a consensus from the community. My
>>preference is to put the sources on
>>xml-commons main trunk.
>>
>>Please let me know how should i proceed.
>>
>>Thanks,
>>
>>- Neeraj
>>
>>
>>Hello All,
>>
>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>implementation to Apache XML.*
>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>significant advancement over JAXP 1.2 and adds whole lot of new
>>functionalities.
>>
>>* New Schema Validation Framework
>>* New Object Model neutral XPath APIs
>>* New Java datatypes which maps to XML Schema Datatypes.
>>* Reuse parser instance
>>* Security enhancements
>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>
>>
>
>
>
>>2, XML 1.1 and XInclude)
>>
>>*JAXP 1.3 APIs source code is attached with this mail. *
>>
>>Due to large size of code base i will be sending different mails for the
>>
>>
>
>
>
>>source code of Xerces & Xalan.
>>
>>I have attached the original mail where i proposed the process of
>>upgrading xml-commons to JAXP 1.3 APIs and
>>integrating this donation into the main stream work of Xerces & Xalan.
>>There was a general consensus to my proposal
>>and we can discuss more about the technicalities of merging with in the
>>appropriate (Xml-commons, Xerces, Xalan)
>>community.
>>
>>Let's upgrade to JAXP 1.3 :-)
>>
>>- Neeraj
>>
>>
>>
>>Neeraj Bajaj wrote:
>>
>>
>>
>>>Geir Magnusson Jr. wrote:
>>>
>>>
>>>
>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>
>>>>
>>>>
>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>on this one.
>>>>>
>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>xerces-j-dev as to how to actually check this in?
>>>>>
>>>>>
>>>>
>>>>
>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>I have received them on behalf of the ASF, and don't let the process
>>>>hold things up.
>>>>
>>>>
>>>
>>>
>>>Great... Thanks Geir. No more held up is good
>>>
>>>- Neeraj
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>
>>>
>>>
>>------------------------------------------------------------------------
>>
>>Subject:
>>Donation of JAXP 1.3 Sources to Apache
>>From:
>>Neeraj Bajaj <Ne...@Sun.COM>
>>Date:
>>Tue, 12 Oct 2004 17:32:14 +0530
>>
>>To:
>>general@xml.apache.org
>>CC:
>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>
>>
>>Hello All,
>>
>>
>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>
>>
>
>
>
>>1.3 adds lots of new features in the area of XML processing.
>>It introduces new Schema independent validation framework which
>>decouples the validation as a process independent from parsing.
>>It allows to compile Schema to an immutable memory representation of
>>Grammar which can validate different instances of XML document thus
>>greatly improving the performance of XML processing. XPath language
>>provides a simple, concise syntax for accessing individual parts of an
>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>XPath evaluation environment and expression results independent
>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>
>>
>
>
>
>>the Java platform which maps to some of the W3C XML Schema
>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>the ability to reset XML Parser and Transformer instance , allowing
>>application to reuse the same instance to process multiple XML
>>documents. This also helps in increasing XML processing performance.
>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>
>>
>
>
>
>>1.1, XInclude.
>>
>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>Reference Implementation) to Apache. *
>>
>>
>>/Details of JAXP 1.3 sources to be donated:/
>>
>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>Implementation). RI has been done using
>>Xerces/Xalan as code base. RI contains the implementation of newly
>>introduced Validation Framework [2], XPath APIs [3]
>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>Reset changes, Secured XML Processing changes.
>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>already exist on Apache Xerces. So in the next
>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>changes into Apache Xerces & Xalan project. I have also
>>suggested where implementation component should reside i.e. Xerces or
>>Xalan. Any idea or feedback for the smoother and
>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>Xalan is very welcome.
>>
>>
>>
>>*JAXP 1.3 APIs: *
>>
>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>are used by many different projects.
>>With JSR 206 declared as final and many new standards emerging, we
>>should update xml-commons to JAXP 1.3
>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>and apply a tag.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of
>>
>>
>Xerces)*
>
>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes to
>>the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>
>>
>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>(javax.xml.xpath.*) APIs which i think, should be part of
>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>done in "javax.xml.transform" package
>>for ex. now application can use the same Transformer instance by
>>invoking reset().
>>
>>I propose the same for the Xalan/XSLTC project that we create a branch
>>and JAXP 1.3 Reference Implementation changes are
>>put there. This will help other Xalan active committers to have a chance
>>
>>
>
>
>
>>to look at it before these changes being finally
>>committed to main trunk. Again i seek help of Xalan committers for this
>>
>>
>
>
>
>>process.
>>
>>
>>As always, all feedbacks are more than welcome.
>>
>>
>>Thanks,
>>Neeraj
>>
>>
>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>[2]
>>http://java.sun.com/j2se/1.5.
>>0/docs/api/javax/xml/validation/package-summary.html
>>[3]
>>
>>
>>
>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>
>
>>[4]
>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>summary.html
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>
>>
>>
>
>Michael Glavassevich
>XML Parser Development
>IBM Toronto Lab
>E-mail: mrglavas@ca.ibm.com
>E-mail: mrglavas@apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.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
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi Neeraj,
I'm +1 to putting the API source on xml-commons trunk. That was
originally supposed to represent the "latest and greatest" of common XML
parsing API's; now it'll be able to do so once again. :)
I think the implementation germane to XML parsing should be put on a
branch in Xerces.
Cheers,
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
Neeraj Bajaj <Ne...@Sun.COM>
04/04/2005 01:07 AM
Please respond to
xerces-j-dev
To
xalan-dev@xml.apache.org
cc
commons-dev@xml.apache.org, xerces-j-dev@xml.apache.org, Eduardo
Pelegri-Llopart <Ed...@Sun.COM>,
general@incubator.apache.org, general@xml.apache.org, Janet Breuer
<Ja...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
Suresh.K@Sun.COM
Subject
Re: Donation of JAXP 1.3 Sources to Apache
Thanks Michael for your response.
I was just wondering what would be idle time to wait before i start work
on this ?
Does anyone has an opinion, Is there any other list where i should send
this mail
before making changes ?
- Neeraj
Michael Glavassevich wrote:
>Hi Neeraj,
>
>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>making a branch for the old JAXP sources on the current main trunk.
>
>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>have been applied to the JAXP 1.2 sources. This is the branch we've used
>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>similar branch will exist for 1.3.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>
>
>
>>Hello All,
>>
>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>
>>
>
>
>
>>mail bounced back with the following message
>>
>><error>
>> ----- The following addresses had permanent fatal errors -----
>><ge...@xml.apache.org>
>> (reason: 552 ZIP attachments are not accepted here.)
>></error>
>>
>>What should i do now ? Is there a way to upload sources on Apache
>>server somewhere ?
>>Can anyone guide me what is the procedure for such code grants ?
>>
>>I am looking help from the active committers of Xerces & Xalan community
>>
>>
>
>
>
>>to help put it in a
>>a branch and make it work there. As i think due to large number of
>>changes it would be a considerable
>>amount of work. This will also help the committers & community to have a
>>
>>
>
>
>
>>look at the code before
>>it is merged into the main stream work.
>>
>>I think i have commit access at xml-commons so i can commit the sources
>>in xml-commons branch
>>or main trunk (and create branch for old jaxp sources ). What is the
>>opinion of community ? I can
>>start this as soon as i get a consensus from the community. My
>>preference is to put the sources on
>>xml-commons main trunk.
>>
>>Please let me know how should i proceed.
>>
>>Thanks,
>>
>>- Neeraj
>>
>>
>>Hello All,
>>
>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>implementation to Apache XML.*
>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>significant advancement over JAXP 1.2 and adds whole lot of new
>>functionalities.
>>
>>* New Schema Validation Framework
>>* New Object Model neutral XPath APIs
>>* New Java datatypes which maps to XML Schema Datatypes.
>>* Reuse parser instance
>>* Security enhancements
>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>
>>
>
>
>
>>2, XML 1.1 and XInclude)
>>
>>*JAXP 1.3 APIs source code is attached with this mail. *
>>
>>Due to large size of code base i will be sending different mails for the
>>
>>
>
>
>
>>source code of Xerces & Xalan.
>>
>>I have attached the original mail where i proposed the process of
>>upgrading xml-commons to JAXP 1.3 APIs and
>>integrating this donation into the main stream work of Xerces & Xalan.
>>There was a general consensus to my proposal
>>and we can discuss more about the technicalities of merging with in the
>>appropriate (Xml-commons, Xerces, Xalan)
>>community.
>>
>>Let's upgrade to JAXP 1.3 :-)
>>
>>- Neeraj
>>
>>
>>
>>Neeraj Bajaj wrote:
>>
>>
>>
>>>Geir Magnusson Jr. wrote:
>>>
>>>
>>>
>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>
>>>>
>>>>
>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>on this one.
>>>>>
>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>xerces-j-dev as to how to actually check this in?
>>>>>
>>>>>
>>>>
>>>>
>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>I have received them on behalf of the ASF, and don't let the process
>>>>hold things up.
>>>>
>>>>
>>>
>>>
>>>Great... Thanks Geir. No more held up is good
>>>
>>>- Neeraj
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>
>>>
>>>
>>------------------------------------------------------------------------
>>
>>Subject:
>>Donation of JAXP 1.3 Sources to Apache
>>From:
>>Neeraj Bajaj <Ne...@Sun.COM>
>>Date:
>>Tue, 12 Oct 2004 17:32:14 +0530
>>
>>To:
>>general@xml.apache.org
>>CC:
>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>
>>
>>Hello All,
>>
>>
>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>
>>
>
>
>
>>1.3 adds lots of new features in the area of XML processing.
>>It introduces new Schema independent validation framework which
>>decouples the validation as a process independent from parsing.
>>It allows to compile Schema to an immutable memory representation of
>>Grammar which can validate different instances of XML document thus
>>greatly improving the performance of XML processing. XPath language
>>provides a simple, concise syntax for accessing individual parts of an
>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>XPath evaluation environment and expression results independent
>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>
>>
>
>
>
>>the Java platform which maps to some of the W3C XML Schema
>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>the ability to reset XML Parser and Transformer instance , allowing
>>application to reuse the same instance to process multiple XML
>>documents. This also helps in increasing XML processing performance.
>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>
>>
>
>
>
>>1.1, XInclude.
>>
>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>Reference Implementation) to Apache. *
>>
>>
>>/Details of JAXP 1.3 sources to be donated:/
>>
>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>Implementation). RI has been done using
>>Xerces/Xalan as code base. RI contains the implementation of newly
>>introduced Validation Framework [2], XPath APIs [3]
>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>Reset changes, Secured XML Processing changes.
>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>already exist on Apache Xerces. So in the next
>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>changes into Apache Xerces & Xalan project. I have also
>>suggested where implementation component should reside i.e. Xerces or
>>Xalan. Any idea or feedback for the smoother and
>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>Xalan is very welcome.
>>
>>
>>
>>*JAXP 1.3 APIs: *
>>
>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>are used by many different projects.
>>With JSR 206 declared as final and many new standards emerging, we
>>should update xml-commons to JAXP 1.3
>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>and apply a tag.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of
>>
>>
>Xerces)*
>
>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes to
>>the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>
>>
>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>(javax.xml.xpath.*) APIs which i think, should be part of
>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>done in "javax.xml.transform" package
>>for ex. now application can use the same Transformer instance by
>>invoking reset().
>>
>>I propose the same for the Xalan/XSLTC project that we create a branch
>>and JAXP 1.3 Reference Implementation changes are
>>put there. This will help other Xalan active committers to have a chance
>>
>>
>
>
>
>>to look at it before these changes being finally
>>committed to main trunk. Again i seek help of Xalan committers for this
>>
>>
>
>
>
>>process.
>>
>>
>>As always, all feedbacks are more than welcome.
>>
>>
>>Thanks,
>>Neeraj
>>
>>
>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>[2]
>>http://java.sun.com/j2se/1.5.
>>0/docs/api/javax/xml/validation/package-summary.html
>>[3]
>>
>>
>>
>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>
>
>>[4]
>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>summary.html
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>
>>
>>
>
>Michael Glavassevich
>XML Parser Development
>IBM Toronto Lab
>E-mail: mrglavas@ca.ibm.com
>E-mail: mrglavas@apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.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
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi Neeraj,
I'm +1 to putting the API source on xml-commons trunk. That was
originally supposed to represent the "latest and greatest" of common XML
parsing API's; now it'll be able to do so once again. :)
I think the implementation germane to XML parsing should be put on a
branch in Xerces.
Cheers,
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
Neeraj Bajaj <Ne...@Sun.COM>
04/04/2005 01:07 AM
Please respond to
xerces-j-dev
To
xalan-dev@xml.apache.org
cc
commons-dev@xml.apache.org, xerces-j-dev@xml.apache.org, Eduardo
Pelegri-Llopart <Ed...@Sun.COM>,
general@incubator.apache.org, general@xml.apache.org, Janet Breuer
<Ja...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
Suresh.K@Sun.COM
Subject
Re: Donation of JAXP 1.3 Sources to Apache
Thanks Michael for your response.
I was just wondering what would be idle time to wait before i start work
on this ?
Does anyone has an opinion, Is there any other list where i should send
this mail
before making changes ?
- Neeraj
Michael Glavassevich wrote:
>Hi Neeraj,
>
>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>making a branch for the old JAXP sources on the current main trunk.
>
>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>have been applied to the JAXP 1.2 sources. This is the branch we've used
>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>similar branch will exist for 1.3.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>
>
>
>>Hello All,
>>
>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>
>>
>
>
>
>>mail bounced back with the following message
>>
>><error>
>> ----- The following addresses had permanent fatal errors -----
>><ge...@xml.apache.org>
>> (reason: 552 ZIP attachments are not accepted here.)
>></error>
>>
>>What should i do now ? Is there a way to upload sources on Apache
>>server somewhere ?
>>Can anyone guide me what is the procedure for such code grants ?
>>
>>I am looking help from the active committers of Xerces & Xalan community
>>
>>
>
>
>
>>to help put it in a
>>a branch and make it work there. As i think due to large number of
>>changes it would be a considerable
>>amount of work. This will also help the committers & community to have a
>>
>>
>
>
>
>>look at the code before
>>it is merged into the main stream work.
>>
>>I think i have commit access at xml-commons so i can commit the sources
>>in xml-commons branch
>>or main trunk (and create branch for old jaxp sources ). What is the
>>opinion of community ? I can
>>start this as soon as i get a consensus from the community. My
>>preference is to put the sources on
>>xml-commons main trunk.
>>
>>Please let me know how should i proceed.
>>
>>Thanks,
>>
>>- Neeraj
>>
>>
>>Hello All,
>>
>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>implementation to Apache XML.*
>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>significant advancement over JAXP 1.2 and adds whole lot of new
>>functionalities.
>>
>>* New Schema Validation Framework
>>* New Object Model neutral XPath APIs
>>* New Java datatypes which maps to XML Schema Datatypes.
>>* Reuse parser instance
>>* Security enhancements
>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>
>>
>
>
>
>>2, XML 1.1 and XInclude)
>>
>>*JAXP 1.3 APIs source code is attached with this mail. *
>>
>>Due to large size of code base i will be sending different mails for the
>>
>>
>
>
>
>>source code of Xerces & Xalan.
>>
>>I have attached the original mail where i proposed the process of
>>upgrading xml-commons to JAXP 1.3 APIs and
>>integrating this donation into the main stream work of Xerces & Xalan.
>>There was a general consensus to my proposal
>>and we can discuss more about the technicalities of merging with in the
>>appropriate (Xml-commons, Xerces, Xalan)
>>community.
>>
>>Let's upgrade to JAXP 1.3 :-)
>>
>>- Neeraj
>>
>>
>>
>>Neeraj Bajaj wrote:
>>
>>
>>
>>>Geir Magnusson Jr. wrote:
>>>
>>>
>>>
>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>
>>>>
>>>>
>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>on this one.
>>>>>
>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>xerces-j-dev as to how to actually check this in?
>>>>>
>>>>>
>>>>
>>>>
>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>I have received them on behalf of the ASF, and don't let the process
>>>>hold things up.
>>>>
>>>>
>>>
>>>
>>>Great... Thanks Geir. No more held up is good
>>>
>>>- Neeraj
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>
>>>
>>>
>>------------------------------------------------------------------------
>>
>>Subject:
>>Donation of JAXP 1.3 Sources to Apache
>>From:
>>Neeraj Bajaj <Ne...@Sun.COM>
>>Date:
>>Tue, 12 Oct 2004 17:32:14 +0530
>>
>>To:
>>general@xml.apache.org
>>CC:
>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>
>>
>>Hello All,
>>
>>
>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>
>>
>
>
>
>>1.3 adds lots of new features in the area of XML processing.
>>It introduces new Schema independent validation framework which
>>decouples the validation as a process independent from parsing.
>>It allows to compile Schema to an immutable memory representation of
>>Grammar which can validate different instances of XML document thus
>>greatly improving the performance of XML processing. XPath language
>>provides a simple, concise syntax for accessing individual parts of an
>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>XPath evaluation environment and expression results independent
>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>
>>
>
>
>
>>the Java platform which maps to some of the W3C XML Schema
>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>the ability to reset XML Parser and Transformer instance , allowing
>>application to reuse the same instance to process multiple XML
>>documents. This also helps in increasing XML processing performance.
>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>
>>
>
>
>
>>1.1, XInclude.
>>
>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>Reference Implementation) to Apache. *
>>
>>
>>/Details of JAXP 1.3 sources to be donated:/
>>
>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>Implementation). RI has been done using
>>Xerces/Xalan as code base. RI contains the implementation of newly
>>introduced Validation Framework [2], XPath APIs [3]
>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>Reset changes, Secured XML Processing changes.
>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>already exist on Apache Xerces. So in the next
>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>changes into Apache Xerces & Xalan project. I have also
>>suggested where implementation component should reside i.e. Xerces or
>>Xalan. Any idea or feedback for the smoother and
>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>Xalan is very welcome.
>>
>>
>>
>>*JAXP 1.3 APIs: *
>>
>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>are used by many different projects.
>>With JSR 206 declared as final and many new standards emerging, we
>>should update xml-commons to JAXP 1.3
>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>and apply a tag.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of
>>
>>
>Xerces)*
>
>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes to
>>the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>
>>
>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>(javax.xml.xpath.*) APIs which i think, should be part of
>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>done in "javax.xml.transform" package
>>for ex. now application can use the same Transformer instance by
>>invoking reset().
>>
>>I propose the same for the Xalan/XSLTC project that we create a branch
>>and JAXP 1.3 Reference Implementation changes are
>>put there. This will help other Xalan active committers to have a chance
>>
>>
>
>
>
>>to look at it before these changes being finally
>>committed to main trunk. Again i seek help of Xalan committers for this
>>
>>
>
>
>
>>process.
>>
>>
>>As always, all feedbacks are more than welcome.
>>
>>
>>Thanks,
>>Neeraj
>>
>>
>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>[2]
>>http://java.sun.com/j2se/1.5.
>>0/docs/api/javax/xml/validation/package-summary.html
>>[3]
>>
>>
>>
>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>
>
>>[4]
>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>summary.html
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>
>>
>>
>
>Michael Glavassevich
>XML Parser Development
>IBM Toronto Lab
>E-mail: mrglavas@ca.ibm.com
>E-mail: mrglavas@apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.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
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi Neeraj,
I'm +1 to putting the API source on xml-commons trunk. That was
originally supposed to represent the "latest and greatest" of common XML
parsing API's; now it'll be able to do so once again. :)
I think the implementation germane to XML parsing should be put on a
branch in Xerces.
Cheers,
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
Neeraj Bajaj <Ne...@Sun.COM>
04/04/2005 01:07 AM
Please respond to
xerces-j-dev
To
xalan-dev@xml.apache.org
cc
commons-dev@xml.apache.org, xerces-j-dev@xml.apache.org, Eduardo
Pelegri-Llopart <Ed...@Sun.COM>,
general@incubator.apache.org, general@xml.apache.org, Janet Breuer
<Ja...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
Suresh.K@Sun.COM
Subject
Re: Donation of JAXP 1.3 Sources to Apache
Thanks Michael for your response.
I was just wondering what would be idle time to wait before i start work
on this ?
Does anyone has an opinion, Is there any other list where i should send
this mail
before making changes ?
- Neeraj
Michael Glavassevich wrote:
>Hi Neeraj,
>
>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>making a branch for the old JAXP sources on the current main trunk.
>
>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>have been applied to the JAXP 1.2 sources. This is the branch we've used
>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>similar branch will exist for 1.3.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>
>
>
>>Hello All,
>>
>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>
>>
>
>
>
>>mail bounced back with the following message
>>
>><error>
>> ----- The following addresses had permanent fatal errors -----
>><ge...@xml.apache.org>
>> (reason: 552 ZIP attachments are not accepted here.)
>></error>
>>
>>What should i do now ? Is there a way to upload sources on Apache
>>server somewhere ?
>>Can anyone guide me what is the procedure for such code grants ?
>>
>>I am looking help from the active committers of Xerces & Xalan community
>>
>>
>
>
>
>>to help put it in a
>>a branch and make it work there. As i think due to large number of
>>changes it would be a considerable
>>amount of work. This will also help the committers & community to have a
>>
>>
>
>
>
>>look at the code before
>>it is merged into the main stream work.
>>
>>I think i have commit access at xml-commons so i can commit the sources
>>in xml-commons branch
>>or main trunk (and create branch for old jaxp sources ). What is the
>>opinion of community ? I can
>>start this as soon as i get a consensus from the community. My
>>preference is to put the sources on
>>xml-commons main trunk.
>>
>>Please let me know how should i proceed.
>>
>>Thanks,
>>
>>- Neeraj
>>
>>
>>Hello All,
>>
>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>implementation to Apache XML.*
>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>significant advancement over JAXP 1.2 and adds whole lot of new
>>functionalities.
>>
>>* New Schema Validation Framework
>>* New Object Model neutral XPath APIs
>>* New Java datatypes which maps to XML Schema Datatypes.
>>* Reuse parser instance
>>* Security enhancements
>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>
>>
>
>
>
>>2, XML 1.1 and XInclude)
>>
>>*JAXP 1.3 APIs source code is attached with this mail. *
>>
>>Due to large size of code base i will be sending different mails for the
>>
>>
>
>
>
>>source code of Xerces & Xalan.
>>
>>I have attached the original mail where i proposed the process of
>>upgrading xml-commons to JAXP 1.3 APIs and
>>integrating this donation into the main stream work of Xerces & Xalan.
>>There was a general consensus to my proposal
>>and we can discuss more about the technicalities of merging with in the
>>appropriate (Xml-commons, Xerces, Xalan)
>>community.
>>
>>Let's upgrade to JAXP 1.3 :-)
>>
>>- Neeraj
>>
>>
>>
>>Neeraj Bajaj wrote:
>>
>>
>>
>>>Geir Magnusson Jr. wrote:
>>>
>>>
>>>
>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>
>>>>
>>>>
>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>on this one.
>>>>>
>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>xerces-j-dev as to how to actually check this in?
>>>>>
>>>>>
>>>>
>>>>
>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>I have received them on behalf of the ASF, and don't let the process
>>>>hold things up.
>>>>
>>>>
>>>
>>>
>>>Great... Thanks Geir. No more held up is good
>>>
>>>- Neeraj
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>
>>>
>>>
>>------------------------------------------------------------------------
>>
>>Subject:
>>Donation of JAXP 1.3 Sources to Apache
>>From:
>>Neeraj Bajaj <Ne...@Sun.COM>
>>Date:
>>Tue, 12 Oct 2004 17:32:14 +0530
>>
>>To:
>>general@xml.apache.org
>>CC:
>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>
>>
>>Hello All,
>>
>>
>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>
>>
>
>
>
>>1.3 adds lots of new features in the area of XML processing.
>>It introduces new Schema independent validation framework which
>>decouples the validation as a process independent from parsing.
>>It allows to compile Schema to an immutable memory representation of
>>Grammar which can validate different instances of XML document thus
>>greatly improving the performance of XML processing. XPath language
>>provides a simple, concise syntax for accessing individual parts of an
>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>XPath evaluation environment and expression results independent
>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>
>>
>
>
>
>>the Java platform which maps to some of the W3C XML Schema
>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>the ability to reset XML Parser and Transformer instance , allowing
>>application to reuse the same instance to process multiple XML
>>documents. This also helps in increasing XML processing performance.
>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>
>>
>
>
>
>>1.1, XInclude.
>>
>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>Reference Implementation) to Apache. *
>>
>>
>>/Details of JAXP 1.3 sources to be donated:/
>>
>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>Implementation). RI has been done using
>>Xerces/Xalan as code base. RI contains the implementation of newly
>>introduced Validation Framework [2], XPath APIs [3]
>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>Reset changes, Secured XML Processing changes.
>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>already exist on Apache Xerces. So in the next
>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>changes into Apache Xerces & Xalan project. I have also
>>suggested where implementation component should reside i.e. Xerces or
>>Xalan. Any idea or feedback for the smoother and
>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>Xalan is very welcome.
>>
>>
>>
>>*JAXP 1.3 APIs: *
>>
>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>are used by many different projects.
>>With JSR 206 declared as final and many new standards emerging, we
>>should update xml-commons to JAXP 1.3
>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>and apply a tag.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of
>>
>>
>Xerces)*
>
>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes to
>>the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>
>>
>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>(javax.xml.xpath.*) APIs which i think, should be part of
>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>done in "javax.xml.transform" package
>>for ex. now application can use the same Transformer instance by
>>invoking reset().
>>
>>I propose the same for the Xalan/XSLTC project that we create a branch
>>and JAXP 1.3 Reference Implementation changes are
>>put there. This will help other Xalan active committers to have a chance
>>
>>
>
>
>
>>to look at it before these changes being finally
>>committed to main trunk. Again i seek help of Xalan committers for this
>>
>>
>
>
>
>>process.
>>
>>
>>As always, all feedbacks are more than welcome.
>>
>>
>>Thanks,
>>Neeraj
>>
>>
>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>[2]
>>http://java.sun.com/j2se/1.5.
>>0/docs/api/javax/xml/validation/package-summary.html
>>[3]
>>
>>
>>
>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>
>
>>[4]
>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>summary.html
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>
>>
>>
>
>Michael Glavassevich
>XML Parser Development
>IBM Toronto Lab
>E-mail: mrglavas@ca.ibm.com
>E-mail: mrglavas@apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.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
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi Neeraj,
I'm +1 to putting the API source on xml-commons trunk. That was
originally supposed to represent the "latest and greatest" of common XML
parsing API's; now it'll be able to do so once again. :)
I think the implementation germane to XML parsing should be put on a
branch in Xerces.
Cheers,
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
Neeraj Bajaj <Ne...@Sun.COM>
04/04/2005 01:07 AM
Please respond to
xerces-j-dev
To
xalan-dev@xml.apache.org
cc
commons-dev@xml.apache.org, xerces-j-dev@xml.apache.org, Eduardo
Pelegri-Llopart <Ed...@Sun.COM>,
general@incubator.apache.org, general@xml.apache.org, Janet Breuer
<Ja...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
Suresh.K@Sun.COM
Subject
Re: Donation of JAXP 1.3 Sources to Apache
Thanks Michael for your response.
I was just wondering what would be idle time to wait before i start work
on this ?
Does anyone has an opinion, Is there any other list where i should send
this mail
before making changes ?
- Neeraj
Michael Glavassevich wrote:
>Hi Neeraj,
>
>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>making a branch for the old JAXP sources on the current main trunk.
>
>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>have been applied to the JAXP 1.2 sources. This is the branch we've used
>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>similar branch will exist for 1.3.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>
>
>
>>Hello All,
>>
>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>
>>
>
>
>
>>mail bounced back with the following message
>>
>><error>
>> ----- The following addresses had permanent fatal errors -----
>><ge...@xml.apache.org>
>> (reason: 552 ZIP attachments are not accepted here.)
>></error>
>>
>>What should i do now ? Is there a way to upload sources on Apache
>>server somewhere ?
>>Can anyone guide me what is the procedure for such code grants ?
>>
>>I am looking help from the active committers of Xerces & Xalan community
>>
>>
>
>
>
>>to help put it in a
>>a branch and make it work there. As i think due to large number of
>>changes it would be a considerable
>>amount of work. This will also help the committers & community to have a
>>
>>
>
>
>
>>look at the code before
>>it is merged into the main stream work.
>>
>>I think i have commit access at xml-commons so i can commit the sources
>>in xml-commons branch
>>or main trunk (and create branch for old jaxp sources ). What is the
>>opinion of community ? I can
>>start this as soon as i get a consensus from the community. My
>>preference is to put the sources on
>>xml-commons main trunk.
>>
>>Please let me know how should i proceed.
>>
>>Thanks,
>>
>>- Neeraj
>>
>>
>>Hello All,
>>
>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>implementation to Apache XML.*
>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>significant advancement over JAXP 1.2 and adds whole lot of new
>>functionalities.
>>
>>* New Schema Validation Framework
>>* New Object Model neutral XPath APIs
>>* New Java datatypes which maps to XML Schema Datatypes.
>>* Reuse parser instance
>>* Security enhancements
>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>
>>
>
>
>
>>2, XML 1.1 and XInclude)
>>
>>*JAXP 1.3 APIs source code is attached with this mail. *
>>
>>Due to large size of code base i will be sending different mails for the
>>
>>
>
>
>
>>source code of Xerces & Xalan.
>>
>>I have attached the original mail where i proposed the process of
>>upgrading xml-commons to JAXP 1.3 APIs and
>>integrating this donation into the main stream work of Xerces & Xalan.
>>There was a general consensus to my proposal
>>and we can discuss more about the technicalities of merging with in the
>>appropriate (Xml-commons, Xerces, Xalan)
>>community.
>>
>>Let's upgrade to JAXP 1.3 :-)
>>
>>- Neeraj
>>
>>
>>
>>Neeraj Bajaj wrote:
>>
>>
>>
>>>Geir Magnusson Jr. wrote:
>>>
>>>
>>>
>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>
>>>>
>>>>
>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>on this one.
>>>>>
>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>xerces-j-dev as to how to actually check this in?
>>>>>
>>>>>
>>>>
>>>>
>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>I have received them on behalf of the ASF, and don't let the process
>>>>hold things up.
>>>>
>>>>
>>>
>>>
>>>Great... Thanks Geir. No more held up is good
>>>
>>>- Neeraj
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>
>>>
>>>
>>------------------------------------------------------------------------
>>
>>Subject:
>>Donation of JAXP 1.3 Sources to Apache
>>From:
>>Neeraj Bajaj <Ne...@Sun.COM>
>>Date:
>>Tue, 12 Oct 2004 17:32:14 +0530
>>
>>To:
>>general@xml.apache.org
>>CC:
>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>
>>
>>Hello All,
>>
>>
>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>
>>
>
>
>
>>1.3 adds lots of new features in the area of XML processing.
>>It introduces new Schema independent validation framework which
>>decouples the validation as a process independent from parsing.
>>It allows to compile Schema to an immutable memory representation of
>>Grammar which can validate different instances of XML document thus
>>greatly improving the performance of XML processing. XPath language
>>provides a simple, concise syntax for accessing individual parts of an
>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>XPath evaluation environment and expression results independent
>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>
>>
>
>
>
>>the Java platform which maps to some of the W3C XML Schema
>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>the ability to reset XML Parser and Transformer instance , allowing
>>application to reuse the same instance to process multiple XML
>>documents. This also helps in increasing XML processing performance.
>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>
>>
>
>
>
>>1.1, XInclude.
>>
>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>Reference Implementation) to Apache. *
>>
>>
>>/Details of JAXP 1.3 sources to be donated:/
>>
>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>Implementation). RI has been done using
>>Xerces/Xalan as code base. RI contains the implementation of newly
>>introduced Validation Framework [2], XPath APIs [3]
>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>Reset changes, Secured XML Processing changes.
>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>already exist on Apache Xerces. So in the next
>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>changes into Apache Xerces & Xalan project. I have also
>>suggested where implementation component should reside i.e. Xerces or
>>Xalan. Any idea or feedback for the smoother and
>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>Xalan is very welcome.
>>
>>
>>
>>*JAXP 1.3 APIs: *
>>
>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>are used by many different projects.
>>With JSR 206 declared as final and many new standards emerging, we
>>should update xml-commons to JAXP 1.3
>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>and apply a tag.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of
>>
>>
>Xerces)*
>
>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes to
>>the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>
>>
>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>(javax.xml.xpath.*) APIs which i think, should be part of
>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>done in "javax.xml.transform" package
>>for ex. now application can use the same Transformer instance by
>>invoking reset().
>>
>>I propose the same for the Xalan/XSLTC project that we create a branch
>>and JAXP 1.3 Reference Implementation changes are
>>put there. This will help other Xalan active committers to have a chance
>>
>>
>
>
>
>>to look at it before these changes being finally
>>committed to main trunk. Again i seek help of Xalan committers for this
>>
>>
>
>
>
>>process.
>>
>>
>>As always, all feedbacks are more than welcome.
>>
>>
>>Thanks,
>>Neeraj
>>
>>
>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>[2]
>>http://java.sun.com/j2se/1.5.
>>0/docs/api/javax/xml/validation/package-summary.html
>>[3]
>>
>>
>>
>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>
>
>>[4]
>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>summary.html
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>
>>
>>
>
>Michael Glavassevich
>XML Parser Development
>IBM Toronto Lab
>E-mail: mrglavas@ca.ibm.com
>E-mail: mrglavas@apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Thanks Michael for your response.
I was just wondering what would be idle time to wait before i start work
on this ?
Does anyone has an opinion, Is there any other list where i should send
this mail
before making changes ?
- Neeraj
Michael Glavassevich wrote:
>Hi Neeraj,
>
>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>making a branch for the old JAXP sources on the current main trunk.
>
>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>have been applied to the JAXP 1.2 sources. This is the branch we've used
>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>similar branch will exist for 1.3.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>
>
>
>>Hello All,
>>
>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>
>>
>
>
>
>>mail bounced back with the following message
>>
>><error>
>> ----- The following addresses had permanent fatal errors -----
>><ge...@xml.apache.org>
>> (reason: 552 ZIP attachments are not accepted here.)
>></error>
>>
>>What should i do now ? Is there a way to upload sources on Apache
>>server somewhere ?
>>Can anyone guide me what is the procedure for such code grants ?
>>
>>I am looking help from the active committers of Xerces & Xalan community
>>
>>
>
>
>
>>to help put it in a
>>a branch and make it work there. As i think due to large number of
>>changes it would be a considerable
>>amount of work. This will also help the committers & community to have a
>>
>>
>
>
>
>>look at the code before
>>it is merged into the main stream work.
>>
>>I think i have commit access at xml-commons so i can commit the sources
>>in xml-commons branch
>>or main trunk (and create branch for old jaxp sources ). What is the
>>opinion of community ? I can
>>start this as soon as i get a consensus from the community. My
>>preference is to put the sources on
>>xml-commons main trunk.
>>
>>Please let me know how should i proceed.
>>
>>Thanks,
>>
>>- Neeraj
>>
>>
>>Hello All,
>>
>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>implementation to Apache XML.*
>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>significant advancement over JAXP 1.2 and adds whole lot of new
>>functionalities.
>>
>>* New Schema Validation Framework
>>* New Object Model neutral XPath APIs
>>* New Java datatypes which maps to XML Schema Datatypes.
>>* Reuse parser instance
>>* Security enhancements
>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>
>>
>
>
>
>>2, XML 1.1 and XInclude)
>>
>>*JAXP 1.3 APIs source code is attached with this mail. *
>>
>>Due to large size of code base i will be sending different mails for the
>>
>>
>
>
>
>>source code of Xerces & Xalan.
>>
>>I have attached the original mail where i proposed the process of
>>upgrading xml-commons to JAXP 1.3 APIs and
>>integrating this donation into the main stream work of Xerces & Xalan.
>>There was a general consensus to my proposal
>>and we can discuss more about the technicalities of merging with in the
>>appropriate (Xml-commons, Xerces, Xalan)
>>community.
>>
>>Let's upgrade to JAXP 1.3 :-)
>>
>>- Neeraj
>>
>>
>>
>>Neeraj Bajaj wrote:
>>
>>
>>
>>>Geir Magnusson Jr. wrote:
>>>
>>>
>>>
>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>
>>>>
>>>>
>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>on this one.
>>>>>
>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>xerces-j-dev as to how to actually check this in?
>>>>>
>>>>>
>>>>
>>>>
>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>I have received them on behalf of the ASF, and don't let the process
>>>>hold things up.
>>>>
>>>>
>>>
>>>
>>>Great... Thanks Geir. No more held up is good
>>>
>>>- Neeraj
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>
>>>
>>>
>>------------------------------------------------------------------------
>>
>>Subject:
>>Donation of JAXP 1.3 Sources to Apache
>>From:
>>Neeraj Bajaj <Ne...@Sun.COM>
>>Date:
>>Tue, 12 Oct 2004 17:32:14 +0530
>>
>>To:
>>general@xml.apache.org
>>CC:
>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>
>>
>>Hello All,
>>
>>
>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>
>>
>
>
>
>>1.3 adds lots of new features in the area of XML processing.
>>It introduces new Schema independent validation framework which
>>decouples the validation as a process independent from parsing.
>>It allows to compile Schema to an immutable memory representation of
>>Grammar which can validate different instances of XML document thus
>>greatly improving the performance of XML processing. XPath language
>>provides a simple, concise syntax for accessing individual parts of an
>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>XPath evaluation environment and expression results independent
>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>
>>
>
>
>
>>the Java platform which maps to some of the W3C XML Schema
>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>the ability to reset XML Parser and Transformer instance , allowing
>>application to reuse the same instance to process multiple XML
>>documents. This also helps in increasing XML processing performance.
>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>
>>
>
>
>
>>1.1, XInclude.
>>
>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>Reference Implementation) to Apache. *
>>
>>
>>/Details of JAXP 1.3 sources to be donated:/
>>
>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>Implementation). RI has been done using
>>Xerces/Xalan as code base. RI contains the implementation of newly
>>introduced Validation Framework [2], XPath APIs [3]
>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>Reset changes, Secured XML Processing changes.
>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>already exist on Apache Xerces. So in the next
>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>changes into Apache Xerces & Xalan project. I have also
>>suggested where implementation component should reside i.e. Xerces or
>>Xalan. Any idea or feedback for the smoother and
>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>Xalan is very welcome.
>>
>>
>>
>>*JAXP 1.3 APIs: *
>>
>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>are used by many different projects.
>>With JSR 206 declared as final and many new standards emerging, we
>>should update xml-commons to JAXP 1.3
>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>and apply a tag.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of
>>
>>
>Xerces)*
>
>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes to
>>the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>
>>
>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>(javax.xml.xpath.*) APIs which i think, should be part of
>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>done in "javax.xml.transform" package
>>for ex. now application can use the same Transformer instance by
>>invoking reset().
>>
>>I propose the same for the Xalan/XSLTC project that we create a branch
>>and JAXP 1.3 Reference Implementation changes are
>>put there. This will help other Xalan active committers to have a chance
>>
>>
>
>
>
>>to look at it before these changes being finally
>>committed to main trunk. Again i seek help of Xalan committers for this
>>
>>
>
>
>
>>process.
>>
>>
>>As always, all feedbacks are more than welcome.
>>
>>
>>Thanks,
>>Neeraj
>>
>>
>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>[2]
>>http://java.sun.com/j2se/1.5.
>>0/docs/api/javax/xml/validation/package-summary.html
>>[3]
>>
>>
>>
>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>
>
>>[4]
>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>summary.html
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>
>>
>>
>
>Michael Glavassevich
>XML Parser Development
>IBM Toronto Lab
>E-mail: mrglavas@ca.ibm.com
>E-mail: mrglavas@apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Thanks Michael for your response.
I was just wondering what would be idle time to wait before i start work
on this ?
Does anyone has an opinion, Is there any other list where i should send
this mail
before making changes ?
- Neeraj
Michael Glavassevich wrote:
>Hi Neeraj,
>
>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>making a branch for the old JAXP sources on the current main trunk.
>
>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>have been applied to the JAXP 1.2 sources. This is the branch we've used
>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>similar branch will exist for 1.3.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>
>
>
>>Hello All,
>>
>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>
>>
>
>
>
>>mail bounced back with the following message
>>
>><error>
>> ----- The following addresses had permanent fatal errors -----
>><ge...@xml.apache.org>
>> (reason: 552 ZIP attachments are not accepted here.)
>></error>
>>
>>What should i do now ? Is there a way to upload sources on Apache
>>server somewhere ?
>>Can anyone guide me what is the procedure for such code grants ?
>>
>>I am looking help from the active committers of Xerces & Xalan community
>>
>>
>
>
>
>>to help put it in a
>>a branch and make it work there. As i think due to large number of
>>changes it would be a considerable
>>amount of work. This will also help the committers & community to have a
>>
>>
>
>
>
>>look at the code before
>>it is merged into the main stream work.
>>
>>I think i have commit access at xml-commons so i can commit the sources
>>in xml-commons branch
>>or main trunk (and create branch for old jaxp sources ). What is the
>>opinion of community ? I can
>>start this as soon as i get a consensus from the community. My
>>preference is to put the sources on
>>xml-commons main trunk.
>>
>>Please let me know how should i proceed.
>>
>>Thanks,
>>
>>- Neeraj
>>
>>
>>Hello All,
>>
>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>implementation to Apache XML.*
>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>significant advancement over JAXP 1.2 and adds whole lot of new
>>functionalities.
>>
>>* New Schema Validation Framework
>>* New Object Model neutral XPath APIs
>>* New Java datatypes which maps to XML Schema Datatypes.
>>* Reuse parser instance
>>* Security enhancements
>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>
>>
>
>
>
>>2, XML 1.1 and XInclude)
>>
>>*JAXP 1.3 APIs source code is attached with this mail. *
>>
>>Due to large size of code base i will be sending different mails for the
>>
>>
>
>
>
>>source code of Xerces & Xalan.
>>
>>I have attached the original mail where i proposed the process of
>>upgrading xml-commons to JAXP 1.3 APIs and
>>integrating this donation into the main stream work of Xerces & Xalan.
>>There was a general consensus to my proposal
>>and we can discuss more about the technicalities of merging with in the
>>appropriate (Xml-commons, Xerces, Xalan)
>>community.
>>
>>Let's upgrade to JAXP 1.3 :-)
>>
>>- Neeraj
>>
>>
>>
>>Neeraj Bajaj wrote:
>>
>>
>>
>>>Geir Magnusson Jr. wrote:
>>>
>>>
>>>
>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>
>>>>
>>>>
>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>on this one.
>>>>>
>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>xerces-j-dev as to how to actually check this in?
>>>>>
>>>>>
>>>>
>>>>
>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>I have received them on behalf of the ASF, and don't let the process
>>>>hold things up.
>>>>
>>>>
>>>
>>>
>>>Great... Thanks Geir. No more held up is good
>>>
>>>- Neeraj
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>
>>>
>>>
>>------------------------------------------------------------------------
>>
>>Subject:
>>Donation of JAXP 1.3 Sources to Apache
>>From:
>>Neeraj Bajaj <Ne...@Sun.COM>
>>Date:
>>Tue, 12 Oct 2004 17:32:14 +0530
>>
>>To:
>>general@xml.apache.org
>>CC:
>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>
>>
>>Hello All,
>>
>>
>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>
>>
>
>
>
>>1.3 adds lots of new features in the area of XML processing.
>>It introduces new Schema independent validation framework which
>>decouples the validation as a process independent from parsing.
>>It allows to compile Schema to an immutable memory representation of
>>Grammar which can validate different instances of XML document thus
>>greatly improving the performance of XML processing. XPath language
>>provides a simple, concise syntax for accessing individual parts of an
>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>XPath evaluation environment and expression results independent
>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>
>>
>
>
>
>>the Java platform which maps to some of the W3C XML Schema
>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>the ability to reset XML Parser and Transformer instance , allowing
>>application to reuse the same instance to process multiple XML
>>documents. This also helps in increasing XML processing performance.
>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>
>>
>
>
>
>>1.1, XInclude.
>>
>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>Reference Implementation) to Apache. *
>>
>>
>>/Details of JAXP 1.3 sources to be donated:/
>>
>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>Implementation). RI has been done using
>>Xerces/Xalan as code base. RI contains the implementation of newly
>>introduced Validation Framework [2], XPath APIs [3]
>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>Reset changes, Secured XML Processing changes.
>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>already exist on Apache Xerces. So in the next
>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>changes into Apache Xerces & Xalan project. I have also
>>suggested where implementation component should reside i.e. Xerces or
>>Xalan. Any idea or feedback for the smoother and
>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>Xalan is very welcome.
>>
>>
>>
>>*JAXP 1.3 APIs: *
>>
>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>are used by many different projects.
>>With JSR 206 declared as final and many new standards emerging, we
>>should update xml-commons to JAXP 1.3
>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>and apply a tag.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of
>>
>>
>Xerces)*
>
>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes to
>>the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>
>>
>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>(javax.xml.xpath.*) APIs which i think, should be part of
>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>done in "javax.xml.transform" package
>>for ex. now application can use the same Transformer instance by
>>invoking reset().
>>
>>I propose the same for the Xalan/XSLTC project that we create a branch
>>and JAXP 1.3 Reference Implementation changes are
>>put there. This will help other Xalan active committers to have a chance
>>
>>
>
>
>
>>to look at it before these changes being finally
>>committed to main trunk. Again i seek help of Xalan committers for this
>>
>>
>
>
>
>>process.
>>
>>
>>As always, all feedbacks are more than welcome.
>>
>>
>>Thanks,
>>Neeraj
>>
>>
>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>[2]
>>http://java.sun.com/j2se/1.5.
>>0/docs/api/javax/xml/validation/package-summary.html
>>[3]
>>
>>
>>
>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>
>
>>[4]
>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>summary.html
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>
>>
>>
>
>Michael Glavassevich
>XML Parser Development
>IBM Toronto Lab
>E-mail: mrglavas@ca.ibm.com
>E-mail: mrglavas@apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Thanks Michael for your response.
I was just wondering what would be idle time to wait before i start work
on this ?
Does anyone has an opinion, Is there any other list where i should send
this mail
before making changes ?
- Neeraj
Michael Glavassevich wrote:
>Hi Neeraj,
>
>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>making a branch for the old JAXP sources on the current main trunk.
>
>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>have been applied to the JAXP 1.2 sources. This is the branch we've used
>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>similar branch will exist for 1.3.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>
>
>
>>Hello All,
>>
>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>
>>
>
>
>
>>mail bounced back with the following message
>>
>><error>
>> ----- The following addresses had permanent fatal errors -----
>><ge...@xml.apache.org>
>> (reason: 552 ZIP attachments are not accepted here.)
>></error>
>>
>>What should i do now ? Is there a way to upload sources on Apache
>>server somewhere ?
>>Can anyone guide me what is the procedure for such code grants ?
>>
>>I am looking help from the active committers of Xerces & Xalan community
>>
>>
>
>
>
>>to help put it in a
>>a branch and make it work there. As i think due to large number of
>>changes it would be a considerable
>>amount of work. This will also help the committers & community to have a
>>
>>
>
>
>
>>look at the code before
>>it is merged into the main stream work.
>>
>>I think i have commit access at xml-commons so i can commit the sources
>>in xml-commons branch
>>or main trunk (and create branch for old jaxp sources ). What is the
>>opinion of community ? I can
>>start this as soon as i get a consensus from the community. My
>>preference is to put the sources on
>>xml-commons main trunk.
>>
>>Please let me know how should i proceed.
>>
>>Thanks,
>>
>>- Neeraj
>>
>>
>>Hello All,
>>
>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>implementation to Apache XML.*
>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>significant advancement over JAXP 1.2 and adds whole lot of new
>>functionalities.
>>
>>* New Schema Validation Framework
>>* New Object Model neutral XPath APIs
>>* New Java datatypes which maps to XML Schema Datatypes.
>>* Reuse parser instance
>>* Security enhancements
>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>
>>
>
>
>
>>2, XML 1.1 and XInclude)
>>
>>*JAXP 1.3 APIs source code is attached with this mail. *
>>
>>Due to large size of code base i will be sending different mails for the
>>
>>
>
>
>
>>source code of Xerces & Xalan.
>>
>>I have attached the original mail where i proposed the process of
>>upgrading xml-commons to JAXP 1.3 APIs and
>>integrating this donation into the main stream work of Xerces & Xalan.
>>There was a general consensus to my proposal
>>and we can discuss more about the technicalities of merging with in the
>>appropriate (Xml-commons, Xerces, Xalan)
>>community.
>>
>>Let's upgrade to JAXP 1.3 :-)
>>
>>- Neeraj
>>
>>
>>
>>Neeraj Bajaj wrote:
>>
>>
>>
>>>Geir Magnusson Jr. wrote:
>>>
>>>
>>>
>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>
>>>>
>>>>
>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>on this one.
>>>>>
>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>xerces-j-dev as to how to actually check this in?
>>>>>
>>>>>
>>>>
>>>>
>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>I have received them on behalf of the ASF, and don't let the process
>>>>hold things up.
>>>>
>>>>
>>>
>>>
>>>Great... Thanks Geir. No more held up is good
>>>
>>>- Neeraj
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>
>>>
>>>
>>------------------------------------------------------------------------
>>
>>Subject:
>>Donation of JAXP 1.3 Sources to Apache
>>From:
>>Neeraj Bajaj <Ne...@Sun.COM>
>>Date:
>>Tue, 12 Oct 2004 17:32:14 +0530
>>
>>To:
>>general@xml.apache.org
>>CC:
>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>
>>
>>Hello All,
>>
>>
>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>
>>
>
>
>
>>1.3 adds lots of new features in the area of XML processing.
>>It introduces new Schema independent validation framework which
>>decouples the validation as a process independent from parsing.
>>It allows to compile Schema to an immutable memory representation of
>>Grammar which can validate different instances of XML document thus
>>greatly improving the performance of XML processing. XPath language
>>provides a simple, concise syntax for accessing individual parts of an
>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>XPath evaluation environment and expression results independent
>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>
>>
>
>
>
>>the Java platform which maps to some of the W3C XML Schema
>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>the ability to reset XML Parser and Transformer instance , allowing
>>application to reuse the same instance to process multiple XML
>>documents. This also helps in increasing XML processing performance.
>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>
>>
>
>
>
>>1.1, XInclude.
>>
>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>Reference Implementation) to Apache. *
>>
>>
>>/Details of JAXP 1.3 sources to be donated:/
>>
>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>Implementation). RI has been done using
>>Xerces/Xalan as code base. RI contains the implementation of newly
>>introduced Validation Framework [2], XPath APIs [3]
>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>Reset changes, Secured XML Processing changes.
>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>already exist on Apache Xerces. So in the next
>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>changes into Apache Xerces & Xalan project. I have also
>>suggested where implementation component should reside i.e. Xerces or
>>Xalan. Any idea or feedback for the smoother and
>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>Xalan is very welcome.
>>
>>
>>
>>*JAXP 1.3 APIs: *
>>
>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>are used by many different projects.
>>With JSR 206 declared as final and many new standards emerging, we
>>should update xml-commons to JAXP 1.3
>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>and apply a tag.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of
>>
>>
>Xerces)*
>
>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes to
>>the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>
>>
>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>(javax.xml.xpath.*) APIs which i think, should be part of
>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>done in "javax.xml.transform" package
>>for ex. now application can use the same Transformer instance by
>>invoking reset().
>>
>>I propose the same for the Xalan/XSLTC project that we create a branch
>>and JAXP 1.3 Reference Implementation changes are
>>put there. This will help other Xalan active committers to have a chance
>>
>>
>
>
>
>>to look at it before these changes being finally
>>committed to main trunk. Again i seek help of Xalan committers for this
>>
>>
>
>
>
>>process.
>>
>>
>>As always, all feedbacks are more than welcome.
>>
>>
>>Thanks,
>>Neeraj
>>
>>
>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>[2]
>>http://java.sun.com/j2se/1.5.
>>0/docs/api/javax/xml/validation/package-summary.html
>>[3]
>>
>>
>>
>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>
>
>>[4]
>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>summary.html
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>
>>
>>
>
>Michael Glavassevich
>XML Parser Development
>IBM Toronto Lab
>E-mail: mrglavas@ca.ibm.com
>E-mail: mrglavas@apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.apache.org
>
>
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Thanks Michael for your response.
I was just wondering what would be idle time to wait before i start work
on this ?
Does anyone has an opinion, Is there any other list where i should send
this mail
before making changes ?
- Neeraj
Michael Glavassevich wrote:
>Hi Neeraj,
>
>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>making a branch for the old JAXP sources on the current main trunk.
>
>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>have been applied to the JAXP 1.2 sources. This is the branch we've used
>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>similar branch will exist for 1.3.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>
>
>
>>Hello All,
>>
>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>
>>
>
>
>
>>mail bounced back with the following message
>>
>><error>
>> ----- The following addresses had permanent fatal errors -----
>><ge...@xml.apache.org>
>> (reason: 552 ZIP attachments are not accepted here.)
>></error>
>>
>>What should i do now ? Is there a way to upload sources on Apache
>>server somewhere ?
>>Can anyone guide me what is the procedure for such code grants ?
>>
>>I am looking help from the active committers of Xerces & Xalan community
>>
>>
>
>
>
>>to help put it in a
>>a branch and make it work there. As i think due to large number of
>>changes it would be a considerable
>>amount of work. This will also help the committers & community to have a
>>
>>
>
>
>
>>look at the code before
>>it is merged into the main stream work.
>>
>>I think i have commit access at xml-commons so i can commit the sources
>>in xml-commons branch
>>or main trunk (and create branch for old jaxp sources ). What is the
>>opinion of community ? I can
>>start this as soon as i get a consensus from the community. My
>>preference is to put the sources on
>>xml-commons main trunk.
>>
>>Please let me know how should i proceed.
>>
>>Thanks,
>>
>>- Neeraj
>>
>>
>>Hello All,
>>
>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>implementation to Apache XML.*
>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>significant advancement over JAXP 1.2 and adds whole lot of new
>>functionalities.
>>
>>* New Schema Validation Framework
>>* New Object Model neutral XPath APIs
>>* New Java datatypes which maps to XML Schema Datatypes.
>>* Reuse parser instance
>>* Security enhancements
>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>
>>
>
>
>
>>2, XML 1.1 and XInclude)
>>
>>*JAXP 1.3 APIs source code is attached with this mail. *
>>
>>Due to large size of code base i will be sending different mails for the
>>
>>
>
>
>
>>source code of Xerces & Xalan.
>>
>>I have attached the original mail where i proposed the process of
>>upgrading xml-commons to JAXP 1.3 APIs and
>>integrating this donation into the main stream work of Xerces & Xalan.
>>There was a general consensus to my proposal
>>and we can discuss more about the technicalities of merging with in the
>>appropriate (Xml-commons, Xerces, Xalan)
>>community.
>>
>>Let's upgrade to JAXP 1.3 :-)
>>
>>- Neeraj
>>
>>
>>
>>Neeraj Bajaj wrote:
>>
>>
>>
>>>Geir Magnusson Jr. wrote:
>>>
>>>
>>>
>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>
>>>>
>>>>
>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>on this one.
>>>>>
>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>xerces-j-dev as to how to actually check this in?
>>>>>
>>>>>
>>>>
>>>>
>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>I have received them on behalf of the ASF, and don't let the process
>>>>hold things up.
>>>>
>>>>
>>>
>>>
>>>Great... Thanks Geir. No more held up is good
>>>
>>>- Neeraj
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>
>>>
>>>
>>------------------------------------------------------------------------
>>
>>Subject:
>>Donation of JAXP 1.3 Sources to Apache
>>From:
>>Neeraj Bajaj <Ne...@Sun.COM>
>>Date:
>>Tue, 12 Oct 2004 17:32:14 +0530
>>
>>To:
>>general@xml.apache.org
>>CC:
>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>
>>
>>Hello All,
>>
>>
>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>
>>
>
>
>
>>1.3 adds lots of new features in the area of XML processing.
>>It introduces new Schema independent validation framework which
>>decouples the validation as a process independent from parsing.
>>It allows to compile Schema to an immutable memory representation of
>>Grammar which can validate different instances of XML document thus
>>greatly improving the performance of XML processing. XPath language
>>provides a simple, concise syntax for accessing individual parts of an
>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>XPath evaluation environment and expression results independent
>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>
>>
>
>
>
>>the Java platform which maps to some of the W3C XML Schema
>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>the ability to reset XML Parser and Transformer instance , allowing
>>application to reuse the same instance to process multiple XML
>>documents. This also helps in increasing XML processing performance.
>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>
>>
>
>
>
>>1.1, XInclude.
>>
>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>Reference Implementation) to Apache. *
>>
>>
>>/Details of JAXP 1.3 sources to be donated:/
>>
>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>Implementation). RI has been done using
>>Xerces/Xalan as code base. RI contains the implementation of newly
>>introduced Validation Framework [2], XPath APIs [3]
>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>Reset changes, Secured XML Processing changes.
>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>already exist on Apache Xerces. So in the next
>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>changes into Apache Xerces & Xalan project. I have also
>>suggested where implementation component should reside i.e. Xerces or
>>Xalan. Any idea or feedback for the smoother and
>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>Xalan is very welcome.
>>
>>
>>
>>*JAXP 1.3 APIs: *
>>
>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>are used by many different projects.
>>With JSR 206 declared as final and many new standards emerging, we
>>should update xml-commons to JAXP 1.3
>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>and apply a tag.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of
>>
>>
>Xerces)*
>
>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes to
>>the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>
>>
>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>(javax.xml.xpath.*) APIs which i think, should be part of
>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>done in "javax.xml.transform" package
>>for ex. now application can use the same Transformer instance by
>>invoking reset().
>>
>>I propose the same for the Xalan/XSLTC project that we create a branch
>>and JAXP 1.3 Reference Implementation changes are
>>put there. This will help other Xalan active committers to have a chance
>>
>>
>
>
>
>>to look at it before these changes being finally
>>committed to main trunk. Again i seek help of Xalan committers for this
>>
>>
>
>
>
>>process.
>>
>>
>>As always, all feedbacks are more than welcome.
>>
>>
>>Thanks,
>>Neeraj
>>
>>
>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>[2]
>>http://java.sun.com/j2se/1.5.
>>0/docs/api/javax/xml/validation/package-summary.html
>>[3]
>>
>>
>>
>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>
>
>>[4]
>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>summary.html
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>
>>
>>
>
>Michael Glavassevich
>XML Parser Development
>IBM Toronto Lab
>E-mail: mrglavas@ca.ibm.com
>E-mail: mrglavas@apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Thanks Michael for your response.
I was just wondering what would be idle time to wait before i start work
on this ?
Does anyone has an opinion, Is there any other list where i should send
this mail
before making changes ?
- Neeraj
Michael Glavassevich wrote:
>Hi Neeraj,
>
>+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
>making a branch for the old JAXP sources on the current main trunk.
>
>There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
>have been applied to the JAXP 1.2 sources. This is the branch we've used
>for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
>similar branch will exist for 1.3.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
>
>
>
>>Hello All,
>>
>>I sent the mail below with JAXP 1.3 APIs source code attached as zip but
>>
>>
>
>
>
>>mail bounced back with the following message
>>
>><error>
>> ----- The following addresses had permanent fatal errors -----
>><ge...@xml.apache.org>
>> (reason: 552 ZIP attachments are not accepted here.)
>></error>
>>
>>What should i do now ? Is there a way to upload sources on Apache
>>server somewhere ?
>>Can anyone guide me what is the procedure for such code grants ?
>>
>>I am looking help from the active committers of Xerces & Xalan community
>>
>>
>
>
>
>>to help put it in a
>>a branch and make it work there. As i think due to large number of
>>changes it would be a considerable
>>amount of work. This will also help the committers & community to have a
>>
>>
>
>
>
>>look at the code before
>>it is merged into the main stream work.
>>
>>I think i have commit access at xml-commons so i can commit the sources
>>in xml-commons branch
>>or main trunk (and create branch for old jaxp sources ). What is the
>>opinion of community ? I can
>>start this as soon as i get a consensus from the community. My
>>preference is to put the sources on
>>xml-commons main trunk.
>>
>>Please let me know how should i proceed.
>>
>>Thanks,
>>
>>- Neeraj
>>
>>
>>Hello All,
>>
>>*Sun Microsystems donates the source code of JAXP 1.3 APIs +
>>implementation to Apache XML.*
>>JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
>>significant advancement over JAXP 1.2 and adds whole lot of new
>>functionalities.
>>
>>* New Schema Validation Framework
>>* New Object Model neutral XPath APIs
>>* New Java datatypes which maps to XML Schema Datatypes.
>>* Reuse parser instance
>>* Security enhancements
>>* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
>>
>>
>
>
>
>>2, XML 1.1 and XInclude)
>>
>>*JAXP 1.3 APIs source code is attached with this mail. *
>>
>>Due to large size of code base i will be sending different mails for the
>>
>>
>
>
>
>>source code of Xerces & Xalan.
>>
>>I have attached the original mail where i proposed the process of
>>upgrading xml-commons to JAXP 1.3 APIs and
>>integrating this donation into the main stream work of Xerces & Xalan.
>>There was a general consensus to my proposal
>>and we can discuss more about the technicalities of merging with in the
>>appropriate (Xml-commons, Xerces, Xalan)
>>community.
>>
>>Let's upgrade to JAXP 1.3 :-)
>>
>>- Neeraj
>>
>>
>>
>>Neeraj Bajaj wrote:
>>
>>
>>
>>>Geir Magnusson Jr. wrote:
>>>
>>>
>>>
>>>>On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>>>
>>>>
>>>>
>>>>>Excellent news! Thank to Sun folk and Geir for picking up the ball
>>>>>on this one.
>>>>>
>>>>>Note: once the papers are in the Hallowed Halls, I presume that
>>>>>Neeraj will get some consensus from xml-commons, xalan-dev, and
>>>>>xerces-j-dev as to how to actually check this in?
>>>>>
>>>>>
>>>>
>>>>
>>>>There is no need to wait until Hall Hallowed-ness has been achieved.
>>>>I have received them on behalf of the ASF, and don't let the process
>>>>hold things up.
>>>>
>>>>
>>>
>>>
>>>Great... Thanks Geir. No more held up is good
>>>
>>>- Neeraj
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>>
>>>
>>>
>>------------------------------------------------------------------------
>>
>>Subject:
>>Donation of JAXP 1.3 Sources to Apache
>>From:
>>Neeraj Bajaj <Ne...@Sun.COM>
>>Date:
>>Tue, 12 Oct 2004 17:32:14 +0530
>>
>>To:
>>general@xml.apache.org
>>CC:
>>xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
>><xe...@xml.apache.org>, xalan-dev@xml.apache.org,
>>xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
>><Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
>>"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>>
>>
>>Hello All,
>>
>>
>>As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
>>
>>
>
>
>
>>1.3 adds lots of new features in the area of XML processing.
>>It introduces new Schema independent validation framework which
>>decouples the validation as a process independent from parsing.
>>It allows to compile Schema to an immutable memory representation of
>>Grammar which can validate different instances of XML document thus
>>greatly improving the performance of XML processing. XPath language
>>provides a simple, concise syntax for accessing individual parts of an
>>XML document. JAXP 1.3 defines XPath APIs which provides access to the
>>XPath evaluation environment and expression results independent
>>of the underlying data object model. JAXP 1.3 also adds new Datatypes to
>>
>>
>
>
>
>>the Java platform which maps to some of the W3C XML Schema
>>Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
>>the ability to reset XML Parser and Transformer instance , allowing
>>application to reuse the same instance to process multiple XML
>>documents. This also helps in increasing XML processing performance.
>>JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
>>
>>
>
>
>
>>1.1, XInclude.
>>
>>*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
>>Reference Implementation) to Apache. *
>>
>>
>>/Details of JAXP 1.3 sources to be donated:/
>>
>>JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
>>Implementation). RI has been done using
>>Xerces/Xalan as code base. RI contains the implementation of newly
>>introduced Validation Framework [2], XPath APIs [3]
>>, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
>>Reset changes, Secured XML Processing changes.
>>Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
>>already exist on Apache Xerces. So in the next
>>section I have also proposed the way to merge rest of the JAXP 1.3 RI
>>changes into Apache Xerces & Xalan project. I have also
>>suggested where implementation component should reside i.e. Xerces or
>>Xalan. Any idea or feedback for the smoother and
>>expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
>>Xalan is very welcome.
>>
>>
>>
>>*JAXP 1.3 APIs: *
>>
>>JAXP APIs has been at xml-commons for a long time as these set of APIs
>>are used by many different projects.
>>With JSR 206 declared as final and many new standards emerging, we
>>should update xml-commons to JAXP 1.3
>>APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
>>and apply a tag.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of
>>
>>
>Xerces)*
>
>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes into
>>that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes to
>>the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>>*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>>
>>
>>JAXP 1.3 RI also has the implementation of newly developed XPath
>>(javax.xml.xpath.*) APIs which i think, should be part of
>>Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
>>done in "javax.xml.transform" package
>>for ex. now application can use the same Transformer instance by
>>invoking reset().
>>
>>I propose the same for the Xalan/XSLTC project that we create a branch
>>and JAXP 1.3 Reference Implementation changes are
>>put there. This will help other Xalan active committers to have a chance
>>
>>
>
>
>
>>to look at it before these changes being finally
>>committed to main trunk. Again i seek help of Xalan committers for this
>>
>>
>
>
>
>>process.
>>
>>
>>As always, all feedbacks are more than welcome.
>>
>>
>>Thanks,
>>Neeraj
>>
>>
>>[1] http://www.jcp.org/en/jsr/detail?id=206
>>[2]
>>http://java.sun.com/j2se/1.5.
>>0/docs/api/javax/xml/validation/package-summary.html
>>[3]
>>
>>
>>
>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
>
>
>>[4]
>>http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
>>summary.html
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
>>For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>>
>>
>>
>
>Michael Glavassevich
>XML Parser Development
>IBM Toronto Lab
>E-mail: mrglavas@ca.ibm.com
>E-mail: mrglavas@apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Neeraj,
+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
making a branch for the old JAXP sources on the current main trunk.
There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
have been applied to the JAXP 1.2 sources. This is the branch we've used
for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
similar branch will exist for 1.3.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
> Hello All,
>
> I sent the mail below with JAXP 1.3 APIs source code attached as zip but
> mail bounced back with the following message
>
> <error>
> ----- The following addresses had permanent fatal errors -----
> <ge...@xml.apache.org>
> (reason: 552 ZIP attachments are not accepted here.)
> </error>
>
> What should i do now ? Is there a way to upload sources on Apache
> server somewhere ?
> Can anyone guide me what is the procedure for such code grants ?
>
> I am looking help from the active committers of Xerces & Xalan community
> to help put it in a
> a branch and make it work there. As i think due to large number of
> changes it would be a considerable
> amount of work. This will also help the committers & community to have a
> look at the code before
> it is merged into the main stream work.
>
> I think i have commit access at xml-commons so i can commit the sources
> in xml-commons branch
> or main trunk (and create branch for old jaxp sources ). What is the
> opinion of community ? I can
> start this as soon as i get a consensus from the community. My
> preference is to put the sources on
> xml-commons main trunk.
>
> Please let me know how should i proceed.
>
> Thanks,
>
> - Neeraj
>
>
> Hello All,
>
> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> implementation to Apache XML.*
> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> significant advancement over JAXP 1.2 and adds whole lot of new
> functionalities.
>
> * New Schema Validation Framework
> * New Object Model neutral XPath APIs
> * New Java datatypes which maps to XML Schema Datatypes.
> * Reuse parser instance
> * Security enhancements
> * Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
> 2, XML 1.1 and XInclude)
>
> *JAXP 1.3 APIs source code is attached with this mail. *
>
> Due to large size of code base i will be sending different mails for the
> source code of Xerces & Xalan.
>
> I have attached the original mail where i proposed the process of
> upgrading xml-commons to JAXP 1.3 APIs and
> integrating this donation into the main stream work of Xerces & Xalan.
> There was a general consensus to my proposal
> and we can discuss more about the technicalities of merging with in the
> appropriate (Xml-commons, Xerces, Xalan)
> community.
>
> Let's upgrade to JAXP 1.3 :-)
>
> - Neeraj
>
>
>
> Neeraj Bajaj wrote:
>
> >
> >
> > Geir Magnusson Jr. wrote:
> >
> >>
> >> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>
> >>> Excellent news! Thank to Sun folk and Geir for picking up the ball
> >>> on this one.
> >>>
> >>> Note: once the papers are in the Hallowed Halls, I presume that
> >>> Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>> xerces-j-dev as to how to actually check this in?
> >>
> >>
> >>
> >>
> >> There is no need to wait until Hall Hallowed-ness has been achieved.
> >> I have received them on behalf of the ASF, and don't let the process
> >> hold things up.
> >
> >
> >
> >
> > Great... Thanks Geir. No more held up is good
> >
> > - Neeraj
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >
>
> ------------------------------------------------------------------------
>
> Subject:
> Donation of JAXP 1.3 Sources to Apache
> From:
> Neeraj Bajaj <Ne...@Sun.COM>
> Date:
> Tue, 12 Oct 2004 17:32:14 +0530
>
> To:
> general@xml.apache.org
> CC:
> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> <Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>
>
> Hello All,
>
>
> As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
> 1.3 adds lots of new features in the area of XML processing.
> It introduces new Schema independent validation framework which
> decouples the validation as a process independent from parsing.
> It allows to compile Schema to an immutable memory representation of
> Grammar which can validate different instances of XML document thus
> greatly improving the performance of XML processing. XPath language
> provides a simple, concise syntax for accessing individual parts of an
> XML document. JAXP 1.3 defines XPath APIs which provides access to the
> XPath evaluation environment and expression results independent
> of the underlying data object model. JAXP 1.3 also adds new Datatypes to
> the Java platform which maps to some of the W3C XML Schema
> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
> the ability to reset XML Parser and Transformer instance , allowing
> application to reuse the same instance to process multiple XML
> documents. This also helps in increasing XML processing performance.
> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
> 1.1, XInclude.
>
> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> Reference Implementation) to Apache. *
>
>
> /Details of JAXP 1.3 sources to be donated:/
>
> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
> Implementation). RI has been done using
> Xerces/Xalan as code base. RI contains the implementation of newly
> introduced Validation Framework [2], XPath APIs [3]
> , Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
> Reset changes, Secured XML Processing changes.
> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
> already exist on Apache Xerces. So in the next
> section I have also proposed the way to merge rest of the JAXP 1.3 RI
> changes into Apache Xerces & Xalan project. I have also
> suggested where implementation component should reside i.e. Xerces or
> Xalan. Any idea or feedback for the smoother and
> expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
> Xalan is very welcome.
>
>
>
> *JAXP 1.3 APIs: *
>
> JAXP APIs has been at xml-commons for a long time as these set of APIs
> are used by many different projects.
> With JSR 206 declared as final and many new standards emerging, we
> should update xml-commons to JAXP 1.3
> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
> and apply a tag.
>
>
> *JAXP 1.3 RI: (Implementation components that should be part of
Xerces)*
>
>
> JAXP 1.3 RI contains the implementation of following packages
>
> javax.xml.datatype
> javax.xml.validation
> javax.xml.parsers ( reset(), xinclude, etc.)
>
> which should reside at Xerces.
>
> I propose that we create a branch, and merge JAXP 1.3 RI changes into
> that branch. This will help
> other Xerces active committers to have a chance to look at it before
> these changes being finally
> committed to main trunk. This process would require merging changes to
> the branch and then committing
> changes to main trunk, i seek help of active Xerces committers.
>
>
> *JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>
>
> JAXP 1.3 RI also has the implementation of newly developed XPath
> (javax.xml.xpath.*) APIs which i think, should be part of
> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
> done in "javax.xml.transform" package
> for ex. now application can use the same Transformer instance by
> invoking reset().
>
> I propose the same for the Xalan/XSLTC project that we create a branch
> and JAXP 1.3 Reference Implementation changes are
> put there. This will help other Xalan active committers to have a chance
> to look at it before these changes being finally
> committed to main trunk. Again i seek help of Xalan committers for this
> process.
>
>
> As always, all feedbacks are more than welcome.
>
>
> Thanks,
> Neeraj
>
>
> [1] http://www.jcp.org/en/jsr/detail?id=206
> [2]
> http://java.sun.com/j2se/1.5.
> 0/docs/api/javax/xml/validation/package-summary.html
> [3]
>
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
> [4]
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> summary.html
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Neeraj,
+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
making a branch for the old JAXP sources on the current main trunk.
There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
have been applied to the JAXP 1.2 sources. This is the branch we've used
for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
similar branch will exist for 1.3.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
> Hello All,
>
> I sent the mail below with JAXP 1.3 APIs source code attached as zip but
> mail bounced back with the following message
>
> <error>
> ----- The following addresses had permanent fatal errors -----
> <ge...@xml.apache.org>
> (reason: 552 ZIP attachments are not accepted here.)
> </error>
>
> What should i do now ? Is there a way to upload sources on Apache
> server somewhere ?
> Can anyone guide me what is the procedure for such code grants ?
>
> I am looking help from the active committers of Xerces & Xalan community
> to help put it in a
> a branch and make it work there. As i think due to large number of
> changes it would be a considerable
> amount of work. This will also help the committers & community to have a
> look at the code before
> it is merged into the main stream work.
>
> I think i have commit access at xml-commons so i can commit the sources
> in xml-commons branch
> or main trunk (and create branch for old jaxp sources ). What is the
> opinion of community ? I can
> start this as soon as i get a consensus from the community. My
> preference is to put the sources on
> xml-commons main trunk.
>
> Please let me know how should i proceed.
>
> Thanks,
>
> - Neeraj
>
>
> Hello All,
>
> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> implementation to Apache XML.*
> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> significant advancement over JAXP 1.2 and adds whole lot of new
> functionalities.
>
> * New Schema Validation Framework
> * New Object Model neutral XPath APIs
> * New Java datatypes which maps to XML Schema Datatypes.
> * Reuse parser instance
> * Security enhancements
> * Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
> 2, XML 1.1 and XInclude)
>
> *JAXP 1.3 APIs source code is attached with this mail. *
>
> Due to large size of code base i will be sending different mails for the
> source code of Xerces & Xalan.
>
> I have attached the original mail where i proposed the process of
> upgrading xml-commons to JAXP 1.3 APIs and
> integrating this donation into the main stream work of Xerces & Xalan.
> There was a general consensus to my proposal
> and we can discuss more about the technicalities of merging with in the
> appropriate (Xml-commons, Xerces, Xalan)
> community.
>
> Let's upgrade to JAXP 1.3 :-)
>
> - Neeraj
>
>
>
> Neeraj Bajaj wrote:
>
> >
> >
> > Geir Magnusson Jr. wrote:
> >
> >>
> >> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>
> >>> Excellent news! Thank to Sun folk and Geir for picking up the ball
> >>> on this one.
> >>>
> >>> Note: once the papers are in the Hallowed Halls, I presume that
> >>> Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>> xerces-j-dev as to how to actually check this in?
> >>
> >>
> >>
> >>
> >> There is no need to wait until Hall Hallowed-ness has been achieved.
> >> I have received them on behalf of the ASF, and don't let the process
> >> hold things up.
> >
> >
> >
> >
> > Great... Thanks Geir. No more held up is good
> >
> > - Neeraj
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >
>
> ------------------------------------------------------------------------
>
> Subject:
> Donation of JAXP 1.3 Sources to Apache
> From:
> Neeraj Bajaj <Ne...@Sun.COM>
> Date:
> Tue, 12 Oct 2004 17:32:14 +0530
>
> To:
> general@xml.apache.org
> CC:
> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> <Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>
>
> Hello All,
>
>
> As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
> 1.3 adds lots of new features in the area of XML processing.
> It introduces new Schema independent validation framework which
> decouples the validation as a process independent from parsing.
> It allows to compile Schema to an immutable memory representation of
> Grammar which can validate different instances of XML document thus
> greatly improving the performance of XML processing. XPath language
> provides a simple, concise syntax for accessing individual parts of an
> XML document. JAXP 1.3 defines XPath APIs which provides access to the
> XPath evaluation environment and expression results independent
> of the underlying data object model. JAXP 1.3 also adds new Datatypes to
> the Java platform which maps to some of the W3C XML Schema
> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
> the ability to reset XML Parser and Transformer instance , allowing
> application to reuse the same instance to process multiple XML
> documents. This also helps in increasing XML processing performance.
> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
> 1.1, XInclude.
>
> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> Reference Implementation) to Apache. *
>
>
> /Details of JAXP 1.3 sources to be donated:/
>
> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
> Implementation). RI has been done using
> Xerces/Xalan as code base. RI contains the implementation of newly
> introduced Validation Framework [2], XPath APIs [3]
> , Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
> Reset changes, Secured XML Processing changes.
> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
> already exist on Apache Xerces. So in the next
> section I have also proposed the way to merge rest of the JAXP 1.3 RI
> changes into Apache Xerces & Xalan project. I have also
> suggested where implementation component should reside i.e. Xerces or
> Xalan. Any idea or feedback for the smoother and
> expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
> Xalan is very welcome.
>
>
>
> *JAXP 1.3 APIs: *
>
> JAXP APIs has been at xml-commons for a long time as these set of APIs
> are used by many different projects.
> With JSR 206 declared as final and many new standards emerging, we
> should update xml-commons to JAXP 1.3
> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
> and apply a tag.
>
>
> *JAXP 1.3 RI: (Implementation components that should be part of
Xerces)*
>
>
> JAXP 1.3 RI contains the implementation of following packages
>
> javax.xml.datatype
> javax.xml.validation
> javax.xml.parsers ( reset(), xinclude, etc.)
>
> which should reside at Xerces.
>
> I propose that we create a branch, and merge JAXP 1.3 RI changes into
> that branch. This will help
> other Xerces active committers to have a chance to look at it before
> these changes being finally
> committed to main trunk. This process would require merging changes to
> the branch and then committing
> changes to main trunk, i seek help of active Xerces committers.
>
>
> *JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>
>
> JAXP 1.3 RI also has the implementation of newly developed XPath
> (javax.xml.xpath.*) APIs which i think, should be part of
> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
> done in "javax.xml.transform" package
> for ex. now application can use the same Transformer instance by
> invoking reset().
>
> I propose the same for the Xalan/XSLTC project that we create a branch
> and JAXP 1.3 Reference Implementation changes are
> put there. This will help other Xalan active committers to have a chance
> to look at it before these changes being finally
> committed to main trunk. Again i seek help of Xalan committers for this
> process.
>
>
> As always, all feedbacks are more than welcome.
>
>
> Thanks,
> Neeraj
>
>
> [1] http://www.jcp.org/en/jsr/detail?id=206
> [2]
> http://java.sun.com/j2se/1.5.
> 0/docs/api/javax/xml/validation/package-summary.html
> [3]
>
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
> [4]
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> summary.html
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Neeraj,
+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
making a branch for the old JAXP sources on the current main trunk.
There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
have been applied to the JAXP 1.2 sources. This is the branch we've used
for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
similar branch will exist for 1.3.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
> Hello All,
>
> I sent the mail below with JAXP 1.3 APIs source code attached as zip but
> mail bounced back with the following message
>
> <error>
> ----- The following addresses had permanent fatal errors -----
> <ge...@xml.apache.org>
> (reason: 552 ZIP attachments are not accepted here.)
> </error>
>
> What should i do now ? Is there a way to upload sources on Apache
> server somewhere ?
> Can anyone guide me what is the procedure for such code grants ?
>
> I am looking help from the active committers of Xerces & Xalan community
> to help put it in a
> a branch and make it work there. As i think due to large number of
> changes it would be a considerable
> amount of work. This will also help the committers & community to have a
> look at the code before
> it is merged into the main stream work.
>
> I think i have commit access at xml-commons so i can commit the sources
> in xml-commons branch
> or main trunk (and create branch for old jaxp sources ). What is the
> opinion of community ? I can
> start this as soon as i get a consensus from the community. My
> preference is to put the sources on
> xml-commons main trunk.
>
> Please let me know how should i proceed.
>
> Thanks,
>
> - Neeraj
>
>
> Hello All,
>
> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> implementation to Apache XML.*
> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> significant advancement over JAXP 1.2 and adds whole lot of new
> functionalities.
>
> * New Schema Validation Framework
> * New Object Model neutral XPath APIs
> * New Java datatypes which maps to XML Schema Datatypes.
> * Reuse parser instance
> * Security enhancements
> * Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
> 2, XML 1.1 and XInclude)
>
> *JAXP 1.3 APIs source code is attached with this mail. *
>
> Due to large size of code base i will be sending different mails for the
> source code of Xerces & Xalan.
>
> I have attached the original mail where i proposed the process of
> upgrading xml-commons to JAXP 1.3 APIs and
> integrating this donation into the main stream work of Xerces & Xalan.
> There was a general consensus to my proposal
> and we can discuss more about the technicalities of merging with in the
> appropriate (Xml-commons, Xerces, Xalan)
> community.
>
> Let's upgrade to JAXP 1.3 :-)
>
> - Neeraj
>
>
>
> Neeraj Bajaj wrote:
>
> >
> >
> > Geir Magnusson Jr. wrote:
> >
> >>
> >> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>
> >>> Excellent news! Thank to Sun folk and Geir for picking up the ball
> >>> on this one.
> >>>
> >>> Note: once the papers are in the Hallowed Halls, I presume that
> >>> Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>> xerces-j-dev as to how to actually check this in?
> >>
> >>
> >>
> >>
> >> There is no need to wait until Hall Hallowed-ness has been achieved.
> >> I have received them on behalf of the ASF, and don't let the process
> >> hold things up.
> >
> >
> >
> >
> > Great... Thanks Geir. No more held up is good
> >
> > - Neeraj
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >
>
> ------------------------------------------------------------------------
>
> Subject:
> Donation of JAXP 1.3 Sources to Apache
> From:
> Neeraj Bajaj <Ne...@Sun.COM>
> Date:
> Tue, 12 Oct 2004 17:32:14 +0530
>
> To:
> general@xml.apache.org
> CC:
> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> <Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>
>
> Hello All,
>
>
> As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
> 1.3 adds lots of new features in the area of XML processing.
> It introduces new Schema independent validation framework which
> decouples the validation as a process independent from parsing.
> It allows to compile Schema to an immutable memory representation of
> Grammar which can validate different instances of XML document thus
> greatly improving the performance of XML processing. XPath language
> provides a simple, concise syntax for accessing individual parts of an
> XML document. JAXP 1.3 defines XPath APIs which provides access to the
> XPath evaluation environment and expression results independent
> of the underlying data object model. JAXP 1.3 also adds new Datatypes to
> the Java platform which maps to some of the W3C XML Schema
> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
> the ability to reset XML Parser and Transformer instance , allowing
> application to reuse the same instance to process multiple XML
> documents. This also helps in increasing XML processing performance.
> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
> 1.1, XInclude.
>
> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> Reference Implementation) to Apache. *
>
>
> /Details of JAXP 1.3 sources to be donated:/
>
> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
> Implementation). RI has been done using
> Xerces/Xalan as code base. RI contains the implementation of newly
> introduced Validation Framework [2], XPath APIs [3]
> , Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
> Reset changes, Secured XML Processing changes.
> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
> already exist on Apache Xerces. So in the next
> section I have also proposed the way to merge rest of the JAXP 1.3 RI
> changes into Apache Xerces & Xalan project. I have also
> suggested where implementation component should reside i.e. Xerces or
> Xalan. Any idea or feedback for the smoother and
> expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
> Xalan is very welcome.
>
>
>
> *JAXP 1.3 APIs: *
>
> JAXP APIs has been at xml-commons for a long time as these set of APIs
> are used by many different projects.
> With JSR 206 declared as final and many new standards emerging, we
> should update xml-commons to JAXP 1.3
> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
> and apply a tag.
>
>
> *JAXP 1.3 RI: (Implementation components that should be part of
Xerces)*
>
>
> JAXP 1.3 RI contains the implementation of following packages
>
> javax.xml.datatype
> javax.xml.validation
> javax.xml.parsers ( reset(), xinclude, etc.)
>
> which should reside at Xerces.
>
> I propose that we create a branch, and merge JAXP 1.3 RI changes into
> that branch. This will help
> other Xerces active committers to have a chance to look at it before
> these changes being finally
> committed to main trunk. This process would require merging changes to
> the branch and then committing
> changes to main trunk, i seek help of active Xerces committers.
>
>
> *JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>
>
> JAXP 1.3 RI also has the implementation of newly developed XPath
> (javax.xml.xpath.*) APIs which i think, should be part of
> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
> done in "javax.xml.transform" package
> for ex. now application can use the same Transformer instance by
> invoking reset().
>
> I propose the same for the Xalan/XSLTC project that we create a branch
> and JAXP 1.3 Reference Implementation changes are
> put there. This will help other Xalan active committers to have a chance
> to look at it before these changes being finally
> committed to main trunk. Again i seek help of Xalan committers for this
> process.
>
>
> As always, all feedbacks are more than welcome.
>
>
> Thanks,
> Neeraj
>
>
> [1] http://www.jcp.org/en/jsr/detail?id=206
> [2]
> http://java.sun.com/j2se/1.5.
> 0/docs/api/javax/xml/validation/package-summary.html
> [3]
>
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
> [4]
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> summary.html
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Neeraj,
+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
making a branch for the old JAXP sources on the current main trunk.
There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
have been applied to the JAXP 1.2 sources. This is the branch we've used
for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
similar branch will exist for 1.3.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
> Hello All,
>
> I sent the mail below with JAXP 1.3 APIs source code attached as zip but
> mail bounced back with the following message
>
> <error>
> ----- The following addresses had permanent fatal errors -----
> <ge...@xml.apache.org>
> (reason: 552 ZIP attachments are not accepted here.)
> </error>
>
> What should i do now ? Is there a way to upload sources on Apache
> server somewhere ?
> Can anyone guide me what is the procedure for such code grants ?
>
> I am looking help from the active committers of Xerces & Xalan community
> to help put it in a
> a branch and make it work there. As i think due to large number of
> changes it would be a considerable
> amount of work. This will also help the committers & community to have a
> look at the code before
> it is merged into the main stream work.
>
> I think i have commit access at xml-commons so i can commit the sources
> in xml-commons branch
> or main trunk (and create branch for old jaxp sources ). What is the
> opinion of community ? I can
> start this as soon as i get a consensus from the community. My
> preference is to put the sources on
> xml-commons main trunk.
>
> Please let me know how should i proceed.
>
> Thanks,
>
> - Neeraj
>
>
> Hello All,
>
> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> implementation to Apache XML.*
> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> significant advancement over JAXP 1.2 and adds whole lot of new
> functionalities.
>
> * New Schema Validation Framework
> * New Object Model neutral XPath APIs
> * New Java datatypes which maps to XML Schema Datatypes.
> * Reuse parser instance
> * Security enhancements
> * Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
> 2, XML 1.1 and XInclude)
>
> *JAXP 1.3 APIs source code is attached with this mail. *
>
> Due to large size of code base i will be sending different mails for the
> source code of Xerces & Xalan.
>
> I have attached the original mail where i proposed the process of
> upgrading xml-commons to JAXP 1.3 APIs and
> integrating this donation into the main stream work of Xerces & Xalan.
> There was a general consensus to my proposal
> and we can discuss more about the technicalities of merging with in the
> appropriate (Xml-commons, Xerces, Xalan)
> community.
>
> Let's upgrade to JAXP 1.3 :-)
>
> - Neeraj
>
>
>
> Neeraj Bajaj wrote:
>
> >
> >
> > Geir Magnusson Jr. wrote:
> >
> >>
> >> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>
> >>> Excellent news! Thank to Sun folk and Geir for picking up the ball
> >>> on this one.
> >>>
> >>> Note: once the papers are in the Hallowed Halls, I presume that
> >>> Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>> xerces-j-dev as to how to actually check this in?
> >>
> >>
> >>
> >>
> >> There is no need to wait until Hall Hallowed-ness has been achieved.
> >> I have received them on behalf of the ASF, and don't let the process
> >> hold things up.
> >
> >
> >
> >
> > Great... Thanks Geir. No more held up is good
> >
> > - Neeraj
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >
>
> ------------------------------------------------------------------------
>
> Subject:
> Donation of JAXP 1.3 Sources to Apache
> From:
> Neeraj Bajaj <Ne...@Sun.COM>
> Date:
> Tue, 12 Oct 2004 17:32:14 +0530
>
> To:
> general@xml.apache.org
> CC:
> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> <Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>
>
> Hello All,
>
>
> As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
> 1.3 adds lots of new features in the area of XML processing.
> It introduces new Schema independent validation framework which
> decouples the validation as a process independent from parsing.
> It allows to compile Schema to an immutable memory representation of
> Grammar which can validate different instances of XML document thus
> greatly improving the performance of XML processing. XPath language
> provides a simple, concise syntax for accessing individual parts of an
> XML document. JAXP 1.3 defines XPath APIs which provides access to the
> XPath evaluation environment and expression results independent
> of the underlying data object model. JAXP 1.3 also adds new Datatypes to
> the Java platform which maps to some of the W3C XML Schema
> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
> the ability to reset XML Parser and Transformer instance , allowing
> application to reuse the same instance to process multiple XML
> documents. This also helps in increasing XML processing performance.
> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
> 1.1, XInclude.
>
> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> Reference Implementation) to Apache. *
>
>
> /Details of JAXP 1.3 sources to be donated:/
>
> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
> Implementation). RI has been done using
> Xerces/Xalan as code base. RI contains the implementation of newly
> introduced Validation Framework [2], XPath APIs [3]
> , Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
> Reset changes, Secured XML Processing changes.
> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
> already exist on Apache Xerces. So in the next
> section I have also proposed the way to merge rest of the JAXP 1.3 RI
> changes into Apache Xerces & Xalan project. I have also
> suggested where implementation component should reside i.e. Xerces or
> Xalan. Any idea or feedback for the smoother and
> expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
> Xalan is very welcome.
>
>
>
> *JAXP 1.3 APIs: *
>
> JAXP APIs has been at xml-commons for a long time as these set of APIs
> are used by many different projects.
> With JSR 206 declared as final and many new standards emerging, we
> should update xml-commons to JAXP 1.3
> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
> and apply a tag.
>
>
> *JAXP 1.3 RI: (Implementation components that should be part of
Xerces)*
>
>
> JAXP 1.3 RI contains the implementation of following packages
>
> javax.xml.datatype
> javax.xml.validation
> javax.xml.parsers ( reset(), xinclude, etc.)
>
> which should reside at Xerces.
>
> I propose that we create a branch, and merge JAXP 1.3 RI changes into
> that branch. This will help
> other Xerces active committers to have a chance to look at it before
> these changes being finally
> committed to main trunk. This process would require merging changes to
> the branch and then committing
> changes to main trunk, i seek help of active Xerces committers.
>
>
> *JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>
>
> JAXP 1.3 RI also has the implementation of newly developed XPath
> (javax.xml.xpath.*) APIs which i think, should be part of
> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
> done in "javax.xml.transform" package
> for ex. now application can use the same Transformer instance by
> invoking reset().
>
> I propose the same for the Xalan/XSLTC project that we create a branch
> and JAXP 1.3 Reference Implementation changes are
> put there. This will help other Xalan active committers to have a chance
> to look at it before these changes being finally
> committed to main trunk. Again i seek help of Xalan committers for this
> process.
>
>
> As always, all feedbacks are more than welcome.
>
>
> Thanks,
> Neeraj
>
>
> [1] http://www.jcp.org/en/jsr/detail?id=206
> [2]
> http://java.sun.com/j2se/1.5.
> 0/docs/api/javax/xml/validation/package-summary.html
> [3]
>
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
> [4]
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> summary.html
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Neeraj,
+1 to putting the JAXP 1.3 sources on the main trunk, tagging it and
making a branch for the old JAXP sources on the current main trunk.
There exists a branch called tck-jaxp-1_2_0 where fixes and other updates
have been applied to the JAXP 1.2 sources. This is the branch we've used
for generating the xml-apis.jar shipped with Xerces and Xalan. I assume a
similar branch will exist for 1.3.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 04/03/2005 03:40:57 AM:
> Hello All,
>
> I sent the mail below with JAXP 1.3 APIs source code attached as zip but
> mail bounced back with the following message
>
> <error>
> ----- The following addresses had permanent fatal errors -----
> <ge...@xml.apache.org>
> (reason: 552 ZIP attachments are not accepted here.)
> </error>
>
> What should i do now ? Is there a way to upload sources on Apache
> server somewhere ?
> Can anyone guide me what is the procedure for such code grants ?
>
> I am looking help from the active committers of Xerces & Xalan community
> to help put it in a
> a branch and make it work there. As i think due to large number of
> changes it would be a considerable
> amount of work. This will also help the committers & community to have a
> look at the code before
> it is merged into the main stream work.
>
> I think i have commit access at xml-commons so i can commit the sources
> in xml-commons branch
> or main trunk (and create branch for old jaxp sources ). What is the
> opinion of community ? I can
> start this as soon as i get a consensus from the community. My
> preference is to put the sources on
> xml-commons main trunk.
>
> Please let me know how should i proceed.
>
> Thanks,
>
> - Neeraj
>
>
> Hello All,
>
> *Sun Microsystems donates the source code of JAXP 1.3 APIs +
> implementation to Apache XML.*
> JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
> significant advancement over JAXP 1.2 and adds whole lot of new
> functionalities.
>
> * New Schema Validation Framework
> * New Object Model neutral XPath APIs
> * New Java datatypes which maps to XML Schema Datatypes.
> * Reuse parser instance
> * Security enhancements
> * Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
> 2, XML 1.1 and XInclude)
>
> *JAXP 1.3 APIs source code is attached with this mail. *
>
> Due to large size of code base i will be sending different mails for the
> source code of Xerces & Xalan.
>
> I have attached the original mail where i proposed the process of
> upgrading xml-commons to JAXP 1.3 APIs and
> integrating this donation into the main stream work of Xerces & Xalan.
> There was a general consensus to my proposal
> and we can discuss more about the technicalities of merging with in the
> appropriate (Xml-commons, Xerces, Xalan)
> community.
>
> Let's upgrade to JAXP 1.3 :-)
>
> - Neeraj
>
>
>
> Neeraj Bajaj wrote:
>
> >
> >
> > Geir Magnusson Jr. wrote:
> >
> >>
> >> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> >>
> >>> Excellent news! Thank to Sun folk and Geir for picking up the ball
> >>> on this one.
> >>>
> >>> Note: once the papers are in the Hallowed Halls, I presume that
> >>> Neeraj will get some consensus from xml-commons, xalan-dev, and
> >>> xerces-j-dev as to how to actually check this in?
> >>
> >>
> >>
> >>
> >> There is no need to wait until Hall Hallowed-ness has been achieved.
> >> I have received them on behalf of the ASF, and don't let the process
> >> hold things up.
> >
> >
> >
> >
> > Great... Thanks Geir. No more held up is good
> >
> > - Neeraj
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
> >
>
> ------------------------------------------------------------------------
>
> Subject:
> Donation of JAXP 1.3 Sources to Apache
> From:
> Neeraj Bajaj <Ne...@Sun.COM>
> Date:
> Tue, 12 Oct 2004 17:32:14 +0530
>
> To:
> general@xml.apache.org
> CC:
> xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
> <xe...@xml.apache.org>, xalan-dev@xml.apache.org,
> xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
> <Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
> "norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
>
>
> Hello All,
>
>
> As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
> 1.3 adds lots of new features in the area of XML processing.
> It introduces new Schema independent validation framework which
> decouples the validation as a process independent from parsing.
> It allows to compile Schema to an immutable memory representation of
> Grammar which can validate different instances of XML document thus
> greatly improving the performance of XML processing. XPath language
> provides a simple, concise syntax for accessing individual parts of an
> XML document. JAXP 1.3 defines XPath APIs which provides access to the
> XPath evaluation environment and expression results independent
> of the underlying data object model. JAXP 1.3 also adds new Datatypes to
> the Java platform which maps to some of the W3C XML Schema
> Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
> the ability to reset XML Parser and Transformer instance , allowing
> application to reuse the same instance to process multiple XML
> documents. This also helps in increasing XML processing performance.
> JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
> 1.1, XInclude.
>
> *Sun Microsystems would like to donate JAXP 1.3 sources (API s +
> Reference Implementation) to Apache. *
>
>
> /Details of JAXP 1.3 sources to be donated:/
>
> JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
> Implementation). RI has been done using
> Xerces/Xalan as code base. RI contains the implementation of newly
> introduced Validation Framework [2], XPath APIs [3]
> , Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
> Reset changes, Secured XML Processing changes.
> Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
> already exist on Apache Xerces. So in the next
> section I have also proposed the way to merge rest of the JAXP 1.3 RI
> changes into Apache Xerces & Xalan project. I have also
> suggested where implementation component should reside i.e. Xerces or
> Xalan. Any idea or feedback for the smoother and
> expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
> Xalan is very welcome.
>
>
>
> *JAXP 1.3 APIs: *
>
> JAXP APIs has been at xml-commons for a long time as these set of APIs
> are used by many different projects.
> With JSR 206 declared as final and many new standards emerging, we
> should update xml-commons to JAXP 1.3
> APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
> and apply a tag.
>
>
> *JAXP 1.3 RI: (Implementation components that should be part of
Xerces)*
>
>
> JAXP 1.3 RI contains the implementation of following packages
>
> javax.xml.datatype
> javax.xml.validation
> javax.xml.parsers ( reset(), xinclude, etc.)
>
> which should reside at Xerces.
>
> I propose that we create a branch, and merge JAXP 1.3 RI changes into
> that branch. This will help
> other Xerces active committers to have a chance to look at it before
> these changes being finally
> committed to main trunk. This process would require merging changes to
> the branch and then committing
> changes to main trunk, i seek help of active Xerces committers.
>
>
> *JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
>
>
> JAXP 1.3 RI also has the implementation of newly developed XPath
> (javax.xml.xpath.*) APIs which i think, should be part of
> Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
> done in "javax.xml.transform" package
> for ex. now application can use the same Transformer instance by
> invoking reset().
>
> I propose the same for the Xalan/XSLTC project that we create a branch
> and JAXP 1.3 Reference Implementation changes are
> put there. This will help other Xalan active committers to have a chance
> to look at it before these changes being finally
> committed to main trunk. Again i seek help of Xalan committers for this
> process.
>
>
> As always, all feedbacks are more than welcome.
>
>
> Thanks,
> Neeraj
>
>
> [1] http://www.jcp.org/en/jsr/detail?id=206
> [2]
> http://java.sun.com/j2se/1.5.
> 0/docs/api/javax/xml/validation/package-summary.html
> [3]
>
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
> [4]
> http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-
> summary.html
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
I sent the mail below with JAXP 1.3 APIs source code attached as zip but
mail bounced back with the following message
<error>
----- The following addresses had permanent fatal errors -----
<ge...@xml.apache.org>
(reason: 552 ZIP attachments are not accepted here.)
</error>
What should i do now ? Is there a way to upload sources on Apache
server somewhere ?
Can anyone guide me what is the procedure for such code grants ?
I am looking help from the active committers of Xerces & Xalan community
to help put it in a
a branch and make it work there. As i think due to large number of
changes it would be a considerable
amount of work. This will also help the committers & community to have a
look at the code before
it is merged into the main stream work.
I think i have commit access at xml-commons so i can commit the sources
in xml-commons branch
or main trunk (and create branch for old jaxp sources ). What is the
opinion of community ? I can
start this as soon as i get a consensus from the community. My
preference is to put the sources on
xml-commons main trunk.
Please let me know how should i proceed.
Thanks,
- Neeraj
Hello All,
*Sun Microsystems donates the source code of JAXP 1.3 APIs +
implementation to Apache XML.*
JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
significant advancement over JAXP 1.2 and adds whole lot of new
functionalities.
* New Schema Validation Framework
* New Object Model neutral XPath APIs
* New Java datatypes which maps to XML Schema Datatypes.
* Reuse parser instance
* Security enhancements
* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
2, XML 1.1 and XInclude)
*JAXP 1.3 APIs source code is attached with this mail. *
Due to large size of code base i will be sending different mails for the
source code of Xerces & Xalan.
I have attached the original mail where i proposed the process of
upgrading xml-commons to JAXP 1.3 APIs and
integrating this donation into the main stream work of Xerces & Xalan.
There was a general consensus to my proposal
and we can discuss more about the technicalities of merging with in the
appropriate (Xml-commons, Xerces, Xalan)
community.
Let's upgrade to JAXP 1.3 :-)
- Neeraj
Neeraj Bajaj wrote:
>
>
> Geir Magnusson Jr. wrote:
>
>>
>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>
>>> Excellent news! Thank to Sun folk and Geir for picking up the ball
>>> on this one.
>>>
>>> Note: once the papers are in the Hallowed Halls, I presume that
>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>>> xerces-j-dev as to how to actually check this in?
>>
>>
>>
>>
>> There is no need to wait until Hall Hallowed-ness has been achieved.
>> I have received them on behalf of the ASF, and don't let the process
>> hold things up.
>
>
>
>
> Great... Thanks Geir. No more held up is good
>
> - Neeraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
------------------------------------------------------------------------
Subject:
Donation of JAXP 1.3 Sources to Apache
From:
Neeraj Bajaj <Ne...@Sun.COM>
Date:
Tue, 12 Oct 2004 17:32:14 +0530
To:
general@xml.apache.org
CC:
xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
<xe...@xml.apache.org>, xalan-dev@xml.apache.org,
xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
<Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
Hello All,
As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
1.3 adds lots of new features in the area of XML processing.
It introduces new Schema independent validation framework which
decouples the validation as a process independent from parsing.
It allows to compile Schema to an immutable memory representation of
Grammar which can validate different instances of XML document thus
greatly improving the performance of XML processing. XPath language
provides a simple, concise syntax for accessing individual parts of an
XML document. JAXP 1.3 defines XPath APIs which provides access to the
XPath evaluation environment and expression results independent
of the underlying data object model. JAXP 1.3 also adds new Datatypes to
the Java platform which maps to some of the W3C XML Schema
Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
the ability to reset XML Parser and Transformer instance , allowing
application to reuse the same instance to process multiple XML
documents. This also helps in increasing XML processing performance.
JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
1.1, XInclude.
*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
Reference Implementation) to Apache. *
/Details of JAXP 1.3 sources to be donated:/
JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
Implementation). RI has been done using
Xerces/Xalan as code base. RI contains the implementation of newly
introduced Validation Framework [2], XPath APIs [3]
, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
Reset changes, Secured XML Processing changes.
Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
already exist on Apache Xerces. So in the next
section I have also proposed the way to merge rest of the JAXP 1.3 RI
changes into Apache Xerces & Xalan project. I have also
suggested where implementation component should reside i.e. Xerces or
Xalan. Any idea or feedback for the smoother and
expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
Xalan is very welcome.
*JAXP 1.3 APIs: *
JAXP APIs has been at xml-commons for a long time as these set of APIs
are used by many different projects.
With JSR 206 declared as final and many new standards emerging, we
should update xml-commons to JAXP 1.3
APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
and apply a tag.
*JAXP 1.3 RI: (Implementation components that should be part of Xerces)*
JAXP 1.3 RI contains the implementation of following packages
javax.xml.datatype
javax.xml.validation
javax.xml.parsers ( reset(), xinclude, etc.)
which should reside at Xerces.
I propose that we create a branch, and merge JAXP 1.3 RI changes into
that branch. This will help
other Xerces active committers to have a chance to look at it before
these changes being finally
committed to main trunk. This process would require merging changes to
the branch and then committing
changes to main trunk, i seek help of active Xerces committers.
*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
JAXP 1.3 RI also has the implementation of newly developed XPath
(javax.xml.xpath.*) APIs which i think, should be part of
Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
done in "javax.xml.transform" package
for ex. now application can use the same Transformer instance by
invoking reset().
I propose the same for the Xalan/XSLTC project that we create a branch
and JAXP 1.3 Reference Implementation changes are
put there. This will help other Xalan active committers to have a chance
to look at it before these changes being finally
committed to main trunk. Again i seek help of Xalan committers for this
process.
As always, all feedbacks are more than welcome.
Thanks,
Neeraj
[1] http://www.jcp.org/en/jsr/detail?id=206
[2]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/validation/package-summary.html
[3]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
[4]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-summary.html
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
I sent the mail below with JAXP 1.3 APIs source code attached as zip but
mail bounced back with the following message
<error>
----- The following addresses had permanent fatal errors -----
<ge...@xml.apache.org>
(reason: 552 ZIP attachments are not accepted here.)
</error>
What should i do now ? Is there a way to upload sources on Apache
server somewhere ?
Can anyone guide me what is the procedure for such code grants ?
I am looking help from the active committers of Xerces & Xalan community
to help put it in a
a branch and make it work there. As i think due to large number of
changes it would be a considerable
amount of work. This will also help the committers & community to have a
look at the code before
it is merged into the main stream work.
I think i have commit access at xml-commons so i can commit the sources
in xml-commons branch
or main trunk (and create branch for old jaxp sources ). What is the
opinion of community ? I can
start this as soon as i get a consensus from the community. My
preference is to put the sources on
xml-commons main trunk.
Please let me know how should i proceed.
Thanks,
- Neeraj
Hello All,
*Sun Microsystems donates the source code of JAXP 1.3 APIs +
implementation to Apache XML.*
JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
significant advancement over JAXP 1.2 and adds whole lot of new
functionalities.
* New Schema Validation Framework
* New Object Model neutral XPath APIs
* New Java datatypes which maps to XML Schema Datatypes.
* Reuse parser instance
* Security enhancements
* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
2, XML 1.1 and XInclude)
*JAXP 1.3 APIs source code is attached with this mail. *
Due to large size of code base i will be sending different mails for the
source code of Xerces & Xalan.
I have attached the original mail where i proposed the process of
upgrading xml-commons to JAXP 1.3 APIs and
integrating this donation into the main stream work of Xerces & Xalan.
There was a general consensus to my proposal
and we can discuss more about the technicalities of merging with in the
appropriate (Xml-commons, Xerces, Xalan)
community.
Let's upgrade to JAXP 1.3 :-)
- Neeraj
Neeraj Bajaj wrote:
>
>
> Geir Magnusson Jr. wrote:
>
>>
>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>
>>> Excellent news! Thank to Sun folk and Geir for picking up the ball
>>> on this one.
>>>
>>> Note: once the papers are in the Hallowed Halls, I presume that
>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>>> xerces-j-dev as to how to actually check this in?
>>
>>
>>
>>
>> There is no need to wait until Hall Hallowed-ness has been achieved.
>> I have received them on behalf of the ASF, and don't let the process
>> hold things up.
>
>
>
>
> Great... Thanks Geir. No more held up is good
>
> - Neeraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
------------------------------------------------------------------------
Subject:
Donation of JAXP 1.3 Sources to Apache
From:
Neeraj Bajaj <Ne...@Sun.COM>
Date:
Tue, 12 Oct 2004 17:32:14 +0530
To:
general@xml.apache.org
CC:
xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
<xe...@xml.apache.org>, xalan-dev@xml.apache.org,
xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
<Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
Hello All,
As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
1.3 adds lots of new features in the area of XML processing.
It introduces new Schema independent validation framework which
decouples the validation as a process independent from parsing.
It allows to compile Schema to an immutable memory representation of
Grammar which can validate different instances of XML document thus
greatly improving the performance of XML processing. XPath language
provides a simple, concise syntax for accessing individual parts of an
XML document. JAXP 1.3 defines XPath APIs which provides access to the
XPath evaluation environment and expression results independent
of the underlying data object model. JAXP 1.3 also adds new Datatypes to
the Java platform which maps to some of the W3C XML Schema
Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
the ability to reset XML Parser and Transformer instance , allowing
application to reuse the same instance to process multiple XML
documents. This also helps in increasing XML processing performance.
JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
1.1, XInclude.
*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
Reference Implementation) to Apache. *
/Details of JAXP 1.3 sources to be donated:/
JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
Implementation). RI has been done using
Xerces/Xalan as code base. RI contains the implementation of newly
introduced Validation Framework [2], XPath APIs [3]
, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
Reset changes, Secured XML Processing changes.
Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
already exist on Apache Xerces. So in the next
section I have also proposed the way to merge rest of the JAXP 1.3 RI
changes into Apache Xerces & Xalan project. I have also
suggested where implementation component should reside i.e. Xerces or
Xalan. Any idea or feedback for the smoother and
expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
Xalan is very welcome.
*JAXP 1.3 APIs: *
JAXP APIs has been at xml-commons for a long time as these set of APIs
are used by many different projects.
With JSR 206 declared as final and many new standards emerging, we
should update xml-commons to JAXP 1.3
APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
and apply a tag.
*JAXP 1.3 RI: (Implementation components that should be part of Xerces)*
JAXP 1.3 RI contains the implementation of following packages
javax.xml.datatype
javax.xml.validation
javax.xml.parsers ( reset(), xinclude, etc.)
which should reside at Xerces.
I propose that we create a branch, and merge JAXP 1.3 RI changes into
that branch. This will help
other Xerces active committers to have a chance to look at it before
these changes being finally
committed to main trunk. This process would require merging changes to
the branch and then committing
changes to main trunk, i seek help of active Xerces committers.
*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
JAXP 1.3 RI also has the implementation of newly developed XPath
(javax.xml.xpath.*) APIs which i think, should be part of
Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
done in "javax.xml.transform" package
for ex. now application can use the same Transformer instance by
invoking reset().
I propose the same for the Xalan/XSLTC project that we create a branch
and JAXP 1.3 Reference Implementation changes are
put there. This will help other Xalan active committers to have a chance
to look at it before these changes being finally
committed to main trunk. Again i seek help of Xalan committers for this
process.
As always, all feedbacks are more than welcome.
Thanks,
Neeraj
[1] http://www.jcp.org/en/jsr/detail?id=206
[2]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/validation/package-summary.html
[3]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
[4]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-summary.html
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
I sent the mail below with JAXP 1.3 APIs source code attached as zip but
mail bounced back with the following message
<error>
----- The following addresses had permanent fatal errors -----
<ge...@xml.apache.org>
(reason: 552 ZIP attachments are not accepted here.)
</error>
What should i do now ? Is there a way to upload sources on Apache
server somewhere ?
Can anyone guide me what is the procedure for such code grants ?
I am looking help from the active committers of Xerces & Xalan community
to help put it in a
a branch and make it work there. As i think due to large number of
changes it would be a considerable
amount of work. This will also help the committers & community to have a
look at the code before
it is merged into the main stream work.
I think i have commit access at xml-commons so i can commit the sources
in xml-commons branch
or main trunk (and create branch for old jaxp sources ). What is the
opinion of community ? I can
start this as soon as i get a consensus from the community. My
preference is to put the sources on
xml-commons main trunk.
Please let me know how should i proceed.
Thanks,
- Neeraj
Hello All,
*Sun Microsystems donates the source code of JAXP 1.3 APIs +
implementation to Apache XML.*
JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
significant advancement over JAXP 1.2 and adds whole lot of new
functionalities.
* New Schema Validation Framework
* New Object Model neutral XPath APIs
* New Java datatypes which maps to XML Schema Datatypes.
* Reuse parser instance
* Security enhancements
* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
2, XML 1.1 and XInclude)
*JAXP 1.3 APIs source code is attached with this mail. *
Due to large size of code base i will be sending different mails for the
source code of Xerces & Xalan.
I have attached the original mail where i proposed the process of
upgrading xml-commons to JAXP 1.3 APIs and
integrating this donation into the main stream work of Xerces & Xalan.
There was a general consensus to my proposal
and we can discuss more about the technicalities of merging with in the
appropriate (Xml-commons, Xerces, Xalan)
community.
Let's upgrade to JAXP 1.3 :-)
- Neeraj
Neeraj Bajaj wrote:
>
>
> Geir Magnusson Jr. wrote:
>
>>
>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>
>>> Excellent news! Thank to Sun folk and Geir for picking up the ball
>>> on this one.
>>>
>>> Note: once the papers are in the Hallowed Halls, I presume that
>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>>> xerces-j-dev as to how to actually check this in?
>>
>>
>>
>>
>> There is no need to wait until Hall Hallowed-ness has been achieved.
>> I have received them on behalf of the ASF, and don't let the process
>> hold things up.
>
>
>
>
> Great... Thanks Geir. No more held up is good
>
> - Neeraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
------------------------------------------------------------------------
Subject:
Donation of JAXP 1.3 Sources to Apache
From:
Neeraj Bajaj <Ne...@Sun.COM>
Date:
Tue, 12 Oct 2004 17:32:14 +0530
To:
general@xml.apache.org
CC:
xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
<xe...@xml.apache.org>, xalan-dev@xml.apache.org,
xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
<Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
Hello All,
As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
1.3 adds lots of new features in the area of XML processing.
It introduces new Schema independent validation framework which
decouples the validation as a process independent from parsing.
It allows to compile Schema to an immutable memory representation of
Grammar which can validate different instances of XML document thus
greatly improving the performance of XML processing. XPath language
provides a simple, concise syntax for accessing individual parts of an
XML document. JAXP 1.3 defines XPath APIs which provides access to the
XPath evaluation environment and expression results independent
of the underlying data object model. JAXP 1.3 also adds new Datatypes to
the Java platform which maps to some of the W3C XML Schema
Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
the ability to reset XML Parser and Transformer instance , allowing
application to reuse the same instance to process multiple XML
documents. This also helps in increasing XML processing performance.
JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
1.1, XInclude.
*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
Reference Implementation) to Apache. *
/Details of JAXP 1.3 sources to be donated:/
JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
Implementation). RI has been done using
Xerces/Xalan as code base. RI contains the implementation of newly
introduced Validation Framework [2], XPath APIs [3]
, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
Reset changes, Secured XML Processing changes.
Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
already exist on Apache Xerces. So in the next
section I have also proposed the way to merge rest of the JAXP 1.3 RI
changes into Apache Xerces & Xalan project. I have also
suggested where implementation component should reside i.e. Xerces or
Xalan. Any idea or feedback for the smoother and
expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
Xalan is very welcome.
*JAXP 1.3 APIs: *
JAXP APIs has been at xml-commons for a long time as these set of APIs
are used by many different projects.
With JSR 206 declared as final and many new standards emerging, we
should update xml-commons to JAXP 1.3
APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
and apply a tag.
*JAXP 1.3 RI: (Implementation components that should be part of Xerces)*
JAXP 1.3 RI contains the implementation of following packages
javax.xml.datatype
javax.xml.validation
javax.xml.parsers ( reset(), xinclude, etc.)
which should reside at Xerces.
I propose that we create a branch, and merge JAXP 1.3 RI changes into
that branch. This will help
other Xerces active committers to have a chance to look at it before
these changes being finally
committed to main trunk. This process would require merging changes to
the branch and then committing
changes to main trunk, i seek help of active Xerces committers.
*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
JAXP 1.3 RI also has the implementation of newly developed XPath
(javax.xml.xpath.*) APIs which i think, should be part of
Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
done in "javax.xml.transform" package
for ex. now application can use the same Transformer instance by
invoking reset().
I propose the same for the Xalan/XSLTC project that we create a branch
and JAXP 1.3 Reference Implementation changes are
put there. This will help other Xalan active committers to have a chance
to look at it before these changes being finally
committed to main trunk. Again i seek help of Xalan committers for this
process.
As always, all feedbacks are more than welcome.
Thanks,
Neeraj
[1] http://www.jcp.org/en/jsr/detail?id=206
[2]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/validation/package-summary.html
[3]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
[4]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-summary.html
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
I sent the mail below with JAXP 1.3 APIs source code attached as zip but
mail bounced back with the following message
<error>
----- The following addresses had permanent fatal errors -----
<ge...@xml.apache.org>
(reason: 552 ZIP attachments are not accepted here.)
</error>
What should i do now ? Is there a way to upload sources on Apache
server somewhere ?
Can anyone guide me what is the procedure for such code grants ?
I am looking help from the active committers of Xerces & Xalan community
to help put it in a
a branch and make it work there. As i think due to large number of
changes it would be a considerable
amount of work. This will also help the committers & community to have a
look at the code before
it is merged into the main stream work.
I think i have commit access at xml-commons so i can commit the sources
in xml-commons branch
or main trunk (and create branch for old jaxp sources ). What is the
opinion of community ? I can
start this as soon as i get a consensus from the community. My
preference is to put the sources on
xml-commons main trunk.
Please let me know how should i proceed.
Thanks,
- Neeraj
Hello All,
*Sun Microsystems donates the source code of JAXP 1.3 APIs +
implementation to Apache XML.*
JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
significant advancement over JAXP 1.2 and adds whole lot of new
functionalities.
* New Schema Validation Framework
* New Object Model neutral XPath APIs
* New Java datatypes which maps to XML Schema Datatypes.
* Reuse parser instance
* Security enhancements
* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
2, XML 1.1 and XInclude)
*JAXP 1.3 APIs source code is attached with this mail. *
Due to large size of code base i will be sending different mails for the
source code of Xerces & Xalan.
I have attached the original mail where i proposed the process of
upgrading xml-commons to JAXP 1.3 APIs and
integrating this donation into the main stream work of Xerces & Xalan.
There was a general consensus to my proposal
and we can discuss more about the technicalities of merging with in the
appropriate (Xml-commons, Xerces, Xalan)
community.
Let's upgrade to JAXP 1.3 :-)
- Neeraj
Neeraj Bajaj wrote:
>
>
> Geir Magnusson Jr. wrote:
>
>>
>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>
>>> Excellent news! Thank to Sun folk and Geir for picking up the ball
>>> on this one.
>>>
>>> Note: once the papers are in the Hallowed Halls, I presume that
>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>>> xerces-j-dev as to how to actually check this in?
>>
>>
>>
>>
>> There is no need to wait until Hall Hallowed-ness has been achieved.
>> I have received them on behalf of the ASF, and don't let the process
>> hold things up.
>
>
>
>
> Great... Thanks Geir. No more held up is good
>
> - Neeraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
------------------------------------------------------------------------
Subject:
Donation of JAXP 1.3 Sources to Apache
From:
Neeraj Bajaj <Ne...@Sun.COM>
Date:
Tue, 12 Oct 2004 17:32:14 +0530
To:
general@xml.apache.org
CC:
xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
<xe...@xml.apache.org>, xalan-dev@xml.apache.org,
xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
<Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
Hello All,
As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
1.3 adds lots of new features in the area of XML processing.
It introduces new Schema independent validation framework which
decouples the validation as a process independent from parsing.
It allows to compile Schema to an immutable memory representation of
Grammar which can validate different instances of XML document thus
greatly improving the performance of XML processing. XPath language
provides a simple, concise syntax for accessing individual parts of an
XML document. JAXP 1.3 defines XPath APIs which provides access to the
XPath evaluation environment and expression results independent
of the underlying data object model. JAXP 1.3 also adds new Datatypes to
the Java platform which maps to some of the W3C XML Schema
Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
the ability to reset XML Parser and Transformer instance , allowing
application to reuse the same instance to process multiple XML
documents. This also helps in increasing XML processing performance.
JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
1.1, XInclude.
*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
Reference Implementation) to Apache. *
/Details of JAXP 1.3 sources to be donated:/
JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
Implementation). RI has been done using
Xerces/Xalan as code base. RI contains the implementation of newly
introduced Validation Framework [2], XPath APIs [3]
, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
Reset changes, Secured XML Processing changes.
Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
already exist on Apache Xerces. So in the next
section I have also proposed the way to merge rest of the JAXP 1.3 RI
changes into Apache Xerces & Xalan project. I have also
suggested where implementation component should reside i.e. Xerces or
Xalan. Any idea or feedback for the smoother and
expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
Xalan is very welcome.
*JAXP 1.3 APIs: *
JAXP APIs has been at xml-commons for a long time as these set of APIs
are used by many different projects.
With JSR 206 declared as final and many new standards emerging, we
should update xml-commons to JAXP 1.3
APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
and apply a tag.
*JAXP 1.3 RI: (Implementation components that should be part of Xerces)*
JAXP 1.3 RI contains the implementation of following packages
javax.xml.datatype
javax.xml.validation
javax.xml.parsers ( reset(), xinclude, etc.)
which should reside at Xerces.
I propose that we create a branch, and merge JAXP 1.3 RI changes into
that branch. This will help
other Xerces active committers to have a chance to look at it before
these changes being finally
committed to main trunk. This process would require merging changes to
the branch and then committing
changes to main trunk, i seek help of active Xerces committers.
*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
JAXP 1.3 RI also has the implementation of newly developed XPath
(javax.xml.xpath.*) APIs which i think, should be part of
Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
done in "javax.xml.transform" package
for ex. now application can use the same Transformer instance by
invoking reset().
I propose the same for the Xalan/XSLTC project that we create a branch
and JAXP 1.3 Reference Implementation changes are
put there. This will help other Xalan active committers to have a chance
to look at it before these changes being finally
committed to main trunk. Again i seek help of Xalan committers for this
process.
As always, all feedbacks are more than welcome.
Thanks,
Neeraj
[1] http://www.jcp.org/en/jsr/detail?id=206
[2]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/validation/package-summary.html
[3]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
[4]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-summary.html
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
I sent the mail below with JAXP 1.3 APIs source code attached as zip but
mail bounced back with the following message
<error>
----- The following addresses had permanent fatal errors -----
<ge...@xml.apache.org>
(reason: 552 ZIP attachments are not accepted here.)
</error>
What should i do now ? Is there a way to upload sources on Apache
server somewhere ?
Can anyone guide me what is the procedure for such code grants ?
I am looking help from the active committers of Xerces & Xalan community
to help put it in a
a branch and make it work there. As i think due to large number of
changes it would be a considerable
amount of work. This will also help the committers & community to have a
look at the code before
it is merged into the main stream work.
I think i have commit access at xml-commons so i can commit the sources
in xml-commons branch
or main trunk (and create branch for old jaxp sources ). What is the
opinion of community ? I can
start this as soon as i get a consensus from the community. My
preference is to put the sources on
xml-commons main trunk.
Please let me know how should i proceed.
Thanks,
- Neeraj
Hello All,
*Sun Microsystems donates the source code of JAXP 1.3 APIs +
implementation to Apache XML.*
JAXP 1.3 (JSR 206 <http://www.jcp.org/en/jsr/detail?id=206>) is
significant advancement over JAXP 1.2 and adds whole lot of new
functionalities.
* New Schema Validation Framework
* New Object Model neutral XPath APIs
* New Java datatypes which maps to XML Schema Datatypes.
* Reuse parser instance
* Security enhancements
* Support for the latest standards (DOM L3 Core, DOM L3 Load & Save, SAX
2, XML 1.1 and XInclude)
*JAXP 1.3 APIs source code is attached with this mail. *
Due to large size of code base i will be sending different mails for the
source code of Xerces & Xalan.
I have attached the original mail where i proposed the process of
upgrading xml-commons to JAXP 1.3 APIs and
integrating this donation into the main stream work of Xerces & Xalan.
There was a general consensus to my proposal
and we can discuss more about the technicalities of merging with in the
appropriate (Xml-commons, Xerces, Xalan)
community.
Let's upgrade to JAXP 1.3 :-)
- Neeraj
Neeraj Bajaj wrote:
>
>
> Geir Magnusson Jr. wrote:
>
>>
>> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>>
>>> Excellent news! Thank to Sun folk and Geir for picking up the ball
>>> on this one.
>>>
>>> Note: once the papers are in the Hallowed Halls, I presume that
>>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>>> xerces-j-dev as to how to actually check this in?
>>
>>
>>
>>
>> There is no need to wait until Hall Hallowed-ness has been achieved.
>> I have received them on behalf of the ASF, and don't let the process
>> hold things up.
>
>
>
>
> Great... Thanks Geir. No more held up is good
>
> - Neeraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
------------------------------------------------------------------------
Subject:
Donation of JAXP 1.3 Sources to Apache
From:
Neeraj Bajaj <Ne...@Sun.COM>
Date:
Tue, 12 Oct 2004 17:32:14 +0530
To:
general@xml.apache.org
CC:
xerces-j-dev <xe...@xml.apache.org>, xerces-j-user
<xe...@xml.apache.org>, xalan-dev@xml.apache.org,
xalan-j-users@xml.apache.org, Eduardo Pelegri-Llopart
<Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
"norman.walsh" <No...@Sun.COM>, Suresh.K@Sun.COM
Hello All,
As most of you already know JSR 206 [1] JAXP 1.3 has become final. JAXP
1.3 adds lots of new features in the area of XML processing.
It introduces new Schema independent validation framework which
decouples the validation as a process independent from parsing.
It allows to compile Schema to an immutable memory representation of
Grammar which can validate different instances of XML document thus
greatly improving the performance of XML processing. XPath language
provides a simple, concise syntax for accessing individual parts of an
XML document. JAXP 1.3 defines XPath APIs which provides access to the
XPath evaluation environment and expression results independent
of the underlying data object model. JAXP 1.3 also adds new Datatypes to
the Java platform which maps to some of the W3C XML Schema
Datatypes, Features for Secured XML processing etc. JAXP 1.3 also adds
the ability to reset XML Parser and Transformer instance , allowing
application to reuse the same instance to process multiple XML
documents. This also helps in increasing XML processing performance.
JAXP 1.3 also upgrades to the W3C stds. like DOM L3 Core DOM L3 L/S, XML
1.1, XInclude.
*Sun Microsystems would like to donate JAXP 1.3 sources (API s +
Reference Implementation) to Apache. *
/Details of JAXP 1.3 sources to be donated:/
JAXP 1.3 sources contains the new JAXP 1.3 APIs and the RI (Reference
Implementation). RI has been done using
Xerces/Xalan as code base. RI contains the implementation of newly
introduced Validation Framework [2], XPath APIs [3]
, Datatypes [4] implementation, SAXParser, DocumentBuilder, Transformer
Reset changes, Secured XML Processing changes.
Implementation of W3C stds. DOM L3 Core, DOM L3 L/S, XML 1.1, XInclude
already exist on Apache Xerces. So in the next
section I have also proposed the way to merge rest of the JAXP 1.3 RI
changes into Apache Xerces & Xalan project. I have also
suggested where implementation component should reside i.e. Xerces or
Xalan. Any idea or feedback for the smoother and
expedited merger of JAXP 1.3 sources into Apache xml-commons, Xerces &
Xalan is very welcome.
*JAXP 1.3 APIs: *
JAXP APIs has been at xml-commons for a long time as these set of APIs
are used by many different projects.
With JSR 206 declared as final and many new standards emerging, we
should update xml-commons to JAXP 1.3
APIs. I propose JAXP 1.3 APIs to be committed to xml-commons main trunk
and apply a tag.
*JAXP 1.3 RI: (Implementation components that should be part of Xerces)*
JAXP 1.3 RI contains the implementation of following packages
javax.xml.datatype
javax.xml.validation
javax.xml.parsers ( reset(), xinclude, etc.)
which should reside at Xerces.
I propose that we create a branch, and merge JAXP 1.3 RI changes into
that branch. This will help
other Xerces active committers to have a chance to look at it before
these changes being finally
committed to main trunk. This process would require merging changes to
the branch and then committing
changes to main trunk, i seek help of active Xerces committers.
*JAXP 1.3 RI: (Implementation components that should be part of Xalan)*
JAXP 1.3 RI also has the implementation of newly developed XPath
(javax.xml.xpath.*) APIs which i think, should be part of
Xalan/XSLTC project. Besdies this, JAXP 1.3 RI also contains changes
done in "javax.xml.transform" package
for ex. now application can use the same Transformer instance by
invoking reset().
I propose the same for the Xalan/XSLTC project that we create a branch
and JAXP 1.3 Reference Implementation changes are
put there. This will help other Xalan active committers to have a chance
to look at it before these changes being finally
committed to main trunk. Again i seek help of Xalan committers for this
process.
As always, all feedbacks are more than welcome.
Thanks,
Neeraj
[1] http://www.jcp.org/en/jsr/detail?id=206
[2]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/validation/package-summary.html
[3]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
[4]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/datatype/package-summary.html
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>
>> Excellent news! Thank to Sun folk and Geir for picking up the ball
>> on this one.
>>
>> Note: once the papers are in the Hallowed Halls, I presume that
>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>> xerces-j-dev as to how to actually check this in?
>
>
> There is no need to wait until Hall Hallowed-ness has been achieved.
> I have received them on behalf of the ASF, and don't let the process
> hold things up.
Great... Thanks Geir. No more held up is good
- Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>
>> Excellent news! Thank to Sun folk and Geir for picking up the ball
>> on this one.
>>
>> Note: once the papers are in the Hallowed Halls, I presume that
>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>> xerces-j-dev as to how to actually check this in?
>
>
> There is no need to wait until Hall Hallowed-ness has been achieved.
> I have received them on behalf of the ASF, and don't let the process
> hold things up.
Great... Thanks Geir. No more held up is good
- Neeraj
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>
>> Excellent news! Thank to Sun folk and Geir for picking up the ball
>> on this one.
>>
>> Note: once the papers are in the Hallowed Halls, I presume that
>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>> xerces-j-dev as to how to actually check this in?
>
>
> There is no need to wait until Hall Hallowed-ness has been achieved.
> I have received them on behalf of the ASF, and don't let the process
> hold things up.
Great... Thanks Geir. No more held up is good
- Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>
>> Excellent news! Thank to Sun folk and Geir for picking up the ball
>> on this one.
>>
>> Note: once the papers are in the Hallowed Halls, I presume that
>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>> xerces-j-dev as to how to actually check this in?
>
>
> There is no need to wait until Hall Hallowed-ness has been achieved.
> I have received them on behalf of the ASF, and don't let the process
> hold things up.
Great... Thanks Geir. No more held up is good
- Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
>
>> Excellent news! Thank to Sun folk and Geir for picking up the ball
>> on this one.
>>
>> Note: once the papers are in the Hallowed Halls, I presume that
>> Neeraj will get some consensus from xml-commons, xalan-dev, and
>> xerces-j-dev as to how to actually check this in?
>
>
> There is no need to wait until Hall Hallowed-ness has been achieved.
> I have received them on behalf of the ASF, and don't let the process
> hold things up.
Great... Thanks Geir. No more held up is good
- Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> Excellent news! Thank to Sun folk and Geir for picking up the ball on
> this one.
>
> Note: once the papers are in the Hallowed Halls, I presume that Neeraj
> will get some consensus from xml-commons, xalan-dev, and xerces-j-dev
> as to how to actually check this in?
There is no need to wait until Hall Hallowed-ness has been achieved. I
have received them on behalf of the ASF, and don't let the process hold
things up.
> I'm presuming you have someone with commit access to xml-commons,
> which is the pre-existing home for JAXP. (Although incubator should
> check the legal issues, I don't think the code needs to checkin thru
> there).
>
> But I know Xerces and Xalan may have specific dependencies on
> xml-commons code, so we probably need to branch to allow current
> versions to work as-is and let them plan new versions with 1.3
> support.
>
> - Shane
>
> Neeraj Bajaj wrote:
>> xml-common, xerces & xalan communities,
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>> Best Regards,
>> - Neeraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> Excellent news! Thank to Sun folk and Geir for picking up the ball on
> this one.
>
> Note: once the papers are in the Hallowed Halls, I presume that Neeraj
> will get some consensus from xml-commons, xalan-dev, and xerces-j-dev
> as to how to actually check this in?
There is no need to wait until Hall Hallowed-ness has been achieved. I
have received them on behalf of the ASF, and don't let the process hold
things up.
> I'm presuming you have someone with commit access to xml-commons,
> which is the pre-existing home for JAXP. (Although incubator should
> check the legal issues, I don't think the code needs to checkin thru
> there).
>
> But I know Xerces and Xalan may have specific dependencies on
> xml-commons code, so we probably need to branch to allow current
> versions to work as-is and let them plan new versions with 1.3
> support.
>
> - Shane
>
> Neeraj Bajaj wrote:
>> xml-common, xerces & xalan communities,
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>> Best Regards,
>> - Neeraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Apr 6, 2005, at 5:44 PM, Brian Minchau wrote:
> Geir,
> I could contact IBM legal if need be. I'm not in any legal department,
> I
> just looking at this from my role as a member of the Xalan PMC.
>
> Now that the CCLAs that you mention are signed, does it mean that ASF
> doesn't have to ever have to worry again about individial CLAs signed
> by
> IBM or Sun employees, either in the past or in the future?
No. Any committer, covered by a CCLA or not, *must* sign a ICLA.
That's what really matters to us. The original intent of the CCLA is
to ensure that an individual committer can be assured that their
employer is aware and approves, which really is protection for the
committer.
Just having a CCLA doesn't absolve the individual from needing an ICLA.
That said, the new CCLA is a bit confusing, as it can also be used for
a software grant, which is exactly what was done in this case.
In summary, the ICLA is required of any committer.
>
> Perhaps in the future, new IBM or Sun employees could become Apache
> committers without the need to sign individual CLAs. Is that correct?
No. :)
geir
>
> Thanks,
> - Brian
> - - - - - - - - - - - - - - - - - - - -
> Brian Minchau
> e-mail: minchau@ca.ibm.com
>
>
>
>
> "Geir Magnusson
> Jr."
> <geirm@apache.org
> To
>> Brian Minchau/Toronto/IBM@IBMCA
>
> cc
> 04/06/2005 05:29 xalan-dev@xml.apache.org,
> PM general@xml.apache.org
>
> Subject
> Re: Donation of JAXP 1.3
> Sources to
> Apache
>
>
>
>
>
>
>
>
>
>
>
> On Apr 6, 2005, at 5:25 PM, Brian Minchau wrote:
>
>> My understanding is that Sun is signing a CCLA for their contribution
>> of
>> JAXP 1.3.
>
> yes. it's really a software grant, in effect.
>
>>
>> I presume that like any code, the JAXP 1.3 code will have bugs, and
>> will
>> develop over time, and will need fixes by someone. In the short term
>> that
>> would most likely be Sun employees. As a Xalan PMC member it is my
>> responsibility to verify the pedigree of contributions before
>> accepting
>> changes into the code base.
>>
>> Are individual people listed in the CCLA that Sun is signing?
>
> No.
>
>> If so, then
>> how can I find out who is listed, so that I can feel more confident
>> about
>> accepting further contributions. Looking at
>> http://www.apache.org/licenses/cla-corporate.txt I don't think that
>> individuals are listed.
>
> yes, there's a bit of a mess there (need to fix the site). Sun signed
> the same CCLA that IBM signed for Derby, which is a CCLA and
> simultaneous grant. So they are using it for the grant part.
>
>>
>> Also, in the past there seems to be some code that was contributed
>> to
>> Apache by Sun employees who were committers, but who have never signed
>> a
>> CLA. I think that at that time CCLAs did not exist. So I find the
>> phrase in
>> the CCLA most interesting:
>> "Your "Contributions" means all of your past, present and future
>> contributions ..."
>>
>>> From reading that CCLA form it looks like all past, present and
>>> future
>> contributions of all Sun employees have their licensing rights given
>> to the
>> ASF, unless the contributions were donated with "Not a contribution"
>> or
>> some other conspicuous, but similar phrase. If this is true then I
>> feel
>> better about past contributions by people who were Sun employees at
>> that
>> time, and who have never signed a CLA.
>
> There are no people listed. I'll be happy to fax you a copy if that
> helps. IBM legal has the document - it's the same that they used for
> Derby and the recent JSR-105 contribution.
>
> geir
>
>>
>>
>> - Brian
>> - - - - - - - - - - - - - - - - - - - -
>> Brian Minchau
>> Apache Xalan PMC Member
>> e-mail: minchau@ca.ibm.com
>>
>>
>>
>>
>> Shane Curcuru
>> <shane_curcuru@ya
>> hoo.com>
>> To
>> general@xml.apache.org
>> 03/31/2005 12:18
>> cc
>> PM xerces-j-dev@xml.apache.org,
>> general@incubator.apache.org,
>> Eduardo Pelegri-Llopart
>> Please respond to
>> <Ed...@Sun.COM>,
>> general Jeff Suttor
>> <Je...@Sun.COM>,
>> xalan-dev@xml.apache.org,
>> commons-dev@xml.apache.org,
>> Suresh.K@Sun.COM
>>
>> Subject
>> Re: Donation of JAXP 1.3
>> Sources to
>> Apache
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Excellent news! Thank to Sun folk and Geir for picking up the ball on
>> this one.
>>
>> Note: once the papers are in the Hallowed Halls, I presume that Neeraj
>> will get some consensus from xml-commons, xalan-dev, and xerces-j-dev
>> as
>> to how to actually check this in? I'm presuming you have someone with
>> commit access to xml-commons, which is the pre-existing home for JAXP.
>> (Although incubator should check the legal issues, I don't think the
>> code needs to checkin thru there).
>>
>> But I know Xerces and Xalan may have specific dependencies on
>> xml-commons code, so we probably need to branch to allow current
>> versions to work as-is and let them plan new versions with 1.3
>> support.
>>
>> - Shane
>>
>> Neeraj Bajaj wrote:
>>> xml-common, xerces & xalan communities,
>>>
>>> I have learnt that legal issues regarding donation has been resolved
>>> and
>>> latest version of CCLA has been signed.
>>> So would like to make the actual code grant of JAXP 1.3 APIs +
>>> implementation ASAP. I will start the preparation
>>> today and will be back with actual code grant with in 2 days.
>>>
>>>
>>> Best Regards,
>>>
>>> - Neeraj
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.apache.org
>>
>>
>>
>>
> --
> Geir Magnusson Jr +1-203-665-6437
> geirm@apache.org
>
>
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Brian Minchau <mi...@ca.ibm.com>.
Geir,
I could contact IBM legal if need be. I'm not in any legal department, I
just looking at this from my role as a member of the Xalan PMC.
Now that the CCLAs that you mention are signed, does it mean that ASF
doesn't have to ever have to worry again about individial CLAs signed by
IBM or Sun employees, either in the past or in the future?
Perhaps in the future, new IBM or Sun employees could become Apache
committers without the need to sign individual CLAs. Is that correct?
Thanks,
- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
e-mail: minchau@ca.ibm.com
"Geir Magnusson
Jr."
<geirm@apache.org To
> Brian Minchau/Toronto/IBM@IBMCA
cc
04/06/2005 05:29 xalan-dev@xml.apache.org,
PM general@xml.apache.org
Subject
Re: Donation of JAXP 1.3 Sources to
Apache
On Apr 6, 2005, at 5:25 PM, Brian Minchau wrote:
> My understanding is that Sun is signing a CCLA for their contribution
> of
> JAXP 1.3.
yes. it's really a software grant, in effect.
>
> I presume that like any code, the JAXP 1.3 code will have bugs, and
> will
> develop over time, and will need fixes by someone. In the short term
> that
> would most likely be Sun employees. As a Xalan PMC member it is my
> responsibility to verify the pedigree of contributions before accepting
> changes into the code base.
>
> Are individual people listed in the CCLA that Sun is signing?
No.
> If so, then
> how can I find out who is listed, so that I can feel more confident
> about
> accepting further contributions. Looking at
> http://www.apache.org/licenses/cla-corporate.txt I don't think that
> individuals are listed.
yes, there's a bit of a mess there (need to fix the site). Sun signed
the same CCLA that IBM signed for Derby, which is a CCLA and
simultaneous grant. So they are using it for the grant part.
>
> Also, in the past there seems to be some code that was contributed to
> Apache by Sun employees who were committers, but who have never signed
> a
> CLA. I think that at that time CCLAs did not exist. So I find the
> phrase in
> the CCLA most interesting:
> "Your "Contributions" means all of your past, present and future
> contributions ..."
>
>> From reading that CCLA form it looks like all past, present and future
> contributions of all Sun employees have their licensing rights given
> to the
> ASF, unless the contributions were donated with "Not a contribution" or
> some other conspicuous, but similar phrase. If this is true then I
> feel
> better about past contributions by people who were Sun employees at
> that
> time, and who have never signed a CLA.
There are no people listed. I'll be happy to fax you a copy if that
helps. IBM legal has the document - it's the same that they used for
Derby and the recent JSR-105 contribution.
geir
>
>
> - Brian
> - - - - - - - - - - - - - - - - - - - -
> Brian Minchau
> Apache Xalan PMC Member
> e-mail: minchau@ca.ibm.com
>
>
>
>
> Shane Curcuru
> <shane_curcuru@ya
> hoo.com>
> To
> general@xml.apache.org
> 03/31/2005 12:18
> cc
> PM xerces-j-dev@xml.apache.org,
> general@incubator.apache.org,
> Eduardo Pelegri-Llopart
> Please respond to
> <Ed...@Sun.COM>,
> general Jeff Suttor
> <Je...@Sun.COM>,
> xalan-dev@xml.apache.org,
> commons-dev@xml.apache.org,
> Suresh.K@Sun.COM
>
> Subject
> Re: Donation of JAXP 1.3
> Sources to
> Apache
>
>
>
>
>
>
>
>
>
>
> Excellent news! Thank to Sun folk and Geir for picking up the ball on
> this one.
>
> Note: once the papers are in the Hallowed Halls, I presume that Neeraj
> will get some consensus from xml-commons, xalan-dev, and xerces-j-dev
> as
> to how to actually check this in? I'm presuming you have someone with
> commit access to xml-commons, which is the pre-existing home for JAXP.
> (Although incubator should check the legal issues, I don't think the
> code needs to checkin thru there).
>
> But I know Xerces and Xalan may have specific dependencies on
> xml-commons code, so we probably need to branch to allow current
> versions to work as-is and let them plan new versions with 1.3 support.
>
> - Shane
>
> Neeraj Bajaj wrote:
>> xml-common, xerces & xalan communities,
>>
>> I have learnt that legal issues regarding donation has been resolved
>> and
>> latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>>
>>
>> Best Regards,
>>
>> - Neeraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
>
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Brian Minchau <mi...@ca.ibm.com>.
Geir,
I could contact IBM legal if need be. I'm not in any legal department, I
just looking at this from my role as a member of the Xalan PMC.
Now that the CCLAs that you mention are signed, does it mean that ASF
doesn't have to ever have to worry again about individial CLAs signed by
IBM or Sun employees, either in the past or in the future?
Perhaps in the future, new IBM or Sun employees could become Apache
committers without the need to sign individual CLAs. Is that correct?
Thanks,
- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
e-mail: minchau@ca.ibm.com
"Geir Magnusson
Jr."
<geirm@apache.org To
> Brian Minchau/Toronto/IBM@IBMCA
cc
04/06/2005 05:29 xalan-dev@xml.apache.org,
PM general@xml.apache.org
Subject
Re: Donation of JAXP 1.3 Sources to
Apache
On Apr 6, 2005, at 5:25 PM, Brian Minchau wrote:
> My understanding is that Sun is signing a CCLA for their contribution
> of
> JAXP 1.3.
yes. it's really a software grant, in effect.
>
> I presume that like any code, the JAXP 1.3 code will have bugs, and
> will
> develop over time, and will need fixes by someone. In the short term
> that
> would most likely be Sun employees. As a Xalan PMC member it is my
> responsibility to verify the pedigree of contributions before accepting
> changes into the code base.
>
> Are individual people listed in the CCLA that Sun is signing?
No.
> If so, then
> how can I find out who is listed, so that I can feel more confident
> about
> accepting further contributions. Looking at
> http://www.apache.org/licenses/cla-corporate.txt I don't think that
> individuals are listed.
yes, there's a bit of a mess there (need to fix the site). Sun signed
the same CCLA that IBM signed for Derby, which is a CCLA and
simultaneous grant. So they are using it for the grant part.
>
> Also, in the past there seems to be some code that was contributed to
> Apache by Sun employees who were committers, but who have never signed
> a
> CLA. I think that at that time CCLAs did not exist. So I find the
> phrase in
> the CCLA most interesting:
> "Your "Contributions" means all of your past, present and future
> contributions ..."
>
>> From reading that CCLA form it looks like all past, present and future
> contributions of all Sun employees have their licensing rights given
> to the
> ASF, unless the contributions were donated with "Not a contribution" or
> some other conspicuous, but similar phrase. If this is true then I
> feel
> better about past contributions by people who were Sun employees at
> that
> time, and who have never signed a CLA.
There are no people listed. I'll be happy to fax you a copy if that
helps. IBM legal has the document - it's the same that they used for
Derby and the recent JSR-105 contribution.
geir
>
>
> - Brian
> - - - - - - - - - - - - - - - - - - - -
> Brian Minchau
> Apache Xalan PMC Member
> e-mail: minchau@ca.ibm.com
>
>
>
>
> Shane Curcuru
> <shane_curcuru@ya
> hoo.com>
> To
> general@xml.apache.org
> 03/31/2005 12:18
> cc
> PM xerces-j-dev@xml.apache.org,
> general@incubator.apache.org,
> Eduardo Pelegri-Llopart
> Please respond to
> <Ed...@Sun.COM>,
> general Jeff Suttor
> <Je...@Sun.COM>,
> xalan-dev@xml.apache.org,
> commons-dev@xml.apache.org,
> Suresh.K@Sun.COM
>
> Subject
> Re: Donation of JAXP 1.3
> Sources to
> Apache
>
>
>
>
>
>
>
>
>
>
> Excellent news! Thank to Sun folk and Geir for picking up the ball on
> this one.
>
> Note: once the papers are in the Hallowed Halls, I presume that Neeraj
> will get some consensus from xml-commons, xalan-dev, and xerces-j-dev
> as
> to how to actually check this in? I'm presuming you have someone with
> commit access to xml-commons, which is the pre-existing home for JAXP.
> (Although incubator should check the legal issues, I don't think the
> code needs to checkin thru there).
>
> But I know Xerces and Xalan may have specific dependencies on
> xml-commons code, so we probably need to branch to allow current
> versions to work as-is and let them plan new versions with 1.3 support.
>
> - Shane
>
> Neeraj Bajaj wrote:
>> xml-common, xerces & xalan communities,
>>
>> I have learnt that legal issues regarding donation has been resolved
>> and
>> latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>>
>>
>> Best Regards,
>>
>> - Neeraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
>
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Apr 6, 2005, at 5:25 PM, Brian Minchau wrote:
> My understanding is that Sun is signing a CCLA for their contribution
> of
> JAXP 1.3.
yes. it's really a software grant, in effect.
>
> I presume that like any code, the JAXP 1.3 code will have bugs, and
> will
> develop over time, and will need fixes by someone. In the short term
> that
> would most likely be Sun employees. As a Xalan PMC member it is my
> responsibility to verify the pedigree of contributions before accepting
> changes into the code base.
>
> Are individual people listed in the CCLA that Sun is signing?
No.
> If so, then
> how can I find out who is listed, so that I can feel more confident
> about
> accepting further contributions. Looking at
> http://www.apache.org/licenses/cla-corporate.txt I don't think that
> individuals are listed.
yes, there's a bit of a mess there (need to fix the site). Sun signed
the same CCLA that IBM signed for Derby, which is a CCLA and
simultaneous grant. So they are using it for the grant part.
>
> Also, in the past there seems to be some code that was contributed to
> Apache by Sun employees who were committers, but who have never signed
> a
> CLA. I think that at that time CCLAs did not exist. So I find the
> phrase in
> the CCLA most interesting:
> "Your "Contributions" means all of your past, present and future
> contributions ..."
>
>> From reading that CCLA form it looks like all past, present and future
> contributions of all Sun employees have their licensing rights given
> to the
> ASF, unless the contributions were donated with "Not a contribution" or
> some other conspicuous, but similar phrase. If this is true then I
> feel
> better about past contributions by people who were Sun employees at
> that
> time, and who have never signed a CLA.
There are no people listed. I'll be happy to fax you a copy if that
helps. IBM legal has the document - it's the same that they used for
Derby and the recent JSR-105 contribution.
geir
>
>
> - Brian
> - - - - - - - - - - - - - - - - - - - -
> Brian Minchau
> Apache Xalan PMC Member
> e-mail: minchau@ca.ibm.com
>
>
>
>
> Shane Curcuru
> <shane_curcuru@ya
> hoo.com>
> To
> general@xml.apache.org
> 03/31/2005 12:18
> cc
> PM xerces-j-dev@xml.apache.org,
> general@incubator.apache.org,
> Eduardo Pelegri-Llopart
> Please respond to
> <Ed...@Sun.COM>,
> general Jeff Suttor
> <Je...@Sun.COM>,
> xalan-dev@xml.apache.org,
> commons-dev@xml.apache.org,
> Suresh.K@Sun.COM
>
> Subject
> Re: Donation of JAXP 1.3
> Sources to
> Apache
>
>
>
>
>
>
>
>
>
>
> Excellent news! Thank to Sun folk and Geir for picking up the ball on
> this one.
>
> Note: once the papers are in the Hallowed Halls, I presume that Neeraj
> will get some consensus from xml-commons, xalan-dev, and xerces-j-dev
> as
> to how to actually check this in? I'm presuming you have someone with
> commit access to xml-commons, which is the pre-existing home for JAXP.
> (Although incubator should check the legal issues, I don't think the
> code needs to checkin thru there).
>
> But I know Xerces and Xalan may have specific dependencies on
> xml-commons code, so we probably need to branch to allow current
> versions to work as-is and let them plan new versions with 1.3 support.
>
> - Shane
>
> Neeraj Bajaj wrote:
>> xml-common, xerces & xalan communities,
>>
>> I have learnt that legal issues regarding donation has been resolved
>> and
>> latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>>
>>
>> Best Regards,
>>
>> - Neeraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
>
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Brian Minchau <mi...@ca.ibm.com>.
My understanding is that Sun is signing a CCLA for their contribution of
JAXP 1.3.
I presume that like any code, the JAXP 1.3 code will have bugs, and will
develop over time, and will need fixes by someone. In the short term that
would most likely be Sun employees. As a Xalan PMC member it is my
responsibility to verify the pedigree of contributions before accepting
changes into the code base.
Are individual people listed in the CCLA that Sun is signing? If so, then
how can I find out who is listed, so that I can feel more confident about
accepting further contributions. Looking at
http://www.apache.org/licenses/cla-corporate.txt I don't think that
individuals are listed.
Also, in the past there seems to be some code that was contributed to
Apache by Sun employees who were committers, but who have never signed a
CLA. I think that at that time CCLAs did not exist. So I find the phrase in
the CCLA most interesting:
"Your "Contributions" means all of your past, present and future
contributions ..."
>From reading that CCLA form it looks like all past, present and future
contributions of all Sun employees have their licensing rights given to the
ASF, unless the contributions were donated with "Not a contribution" or
some other conspicuous, but similar phrase. If this is true then I feel
better about past contributions by people who were Sun employees at that
time, and who have never signed a CLA.
- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
Apache Xalan PMC Member
e-mail: minchau@ca.ibm.com
Shane Curcuru
<shane_curcuru@ya
hoo.com> To
general@xml.apache.org
03/31/2005 12:18 cc
PM xerces-j-dev@xml.apache.org,
general@incubator.apache.org,
Eduardo Pelegri-Llopart
Please respond to <Ed...@Sun.COM>,
general Jeff Suttor <Je...@Sun.COM>,
xalan-dev@xml.apache.org,
commons-dev@xml.apache.org,
Suresh.K@Sun.COM
Subject
Re: Donation of JAXP 1.3 Sources to
Apache
Excellent news! Thank to Sun folk and Geir for picking up the ball on
this one.
Note: once the papers are in the Hallowed Halls, I presume that Neeraj
will get some consensus from xml-commons, xalan-dev, and xerces-j-dev as
to how to actually check this in? I'm presuming you have someone with
commit access to xml-commons, which is the pre-existing home for JAXP.
(Although incubator should check the legal issues, I don't think the
code needs to checkin thru there).
But I know Xerces and Xalan may have specific dependencies on
xml-commons code, so we probably need to branch to allow current
versions to work as-is and let them plan new versions with 1.3 support.
- Shane
Neeraj Bajaj wrote:
> xml-common, xerces & xalan communities,
>
> I have learnt that legal issues regarding donation has been resolved and
> latest version of CCLA has been signed.
> So would like to make the actual code grant of JAXP 1.3 APIs +
> implementation ASAP. I will start the preparation
> today and will be back with actual code grant with in 2 days.
>
>
> Best Regards,
>
> - Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> Excellent news! Thank to Sun folk and Geir for picking up the ball on
> this one.
>
> Note: once the papers are in the Hallowed Halls, I presume that Neeraj
> will get some consensus from xml-commons, xalan-dev, and xerces-j-dev
> as to how to actually check this in?
There is no need to wait until Hall Hallowed-ness has been achieved. I
have received them on behalf of the ASF, and don't let the process hold
things up.
> I'm presuming you have someone with commit access to xml-commons,
> which is the pre-existing home for JAXP. (Although incubator should
> check the legal issues, I don't think the code needs to checkin thru
> there).
>
> But I know Xerces and Xalan may have specific dependencies on
> xml-commons code, so we probably need to branch to allow current
> versions to work as-is and let them plan new versions with 1.3
> support.
>
> - Shane
>
> Neeraj Bajaj wrote:
>> xml-common, xerces & xalan communities,
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>> Best Regards,
>> - Neeraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Mar 31, 2005, at 12:18 PM, Shane Curcuru wrote:
> Excellent news! Thank to Sun folk and Geir for picking up the ball on
> this one.
>
> Note: once the papers are in the Hallowed Halls, I presume that Neeraj
> will get some consensus from xml-commons, xalan-dev, and xerces-j-dev
> as to how to actually check this in?
There is no need to wait until Hall Hallowed-ness has been achieved. I
have received them on behalf of the ASF, and don't let the process hold
things up.
> I'm presuming you have someone with commit access to xml-commons,
> which is the pre-existing home for JAXP. (Although incubator should
> check the legal issues, I don't think the code needs to checkin thru
> there).
>
> But I know Xerces and Xalan may have specific dependencies on
> xml-commons code, so we probably need to branch to allow current
> versions to work as-is and let them plan new versions with 1.3
> support.
>
> - Shane
>
> Neeraj Bajaj wrote:
>> xml-common, xerces & xalan communities,
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>> Best Regards,
>> - Neeraj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Brian Minchau <mi...@ca.ibm.com>.
My understanding is that Sun is signing a CCLA for their contribution of
JAXP 1.3.
I presume that like any code, the JAXP 1.3 code will have bugs, and will
develop over time, and will need fixes by someone. In the short term that
would most likely be Sun employees. As a Xalan PMC member it is my
responsibility to verify the pedigree of contributions before accepting
changes into the code base.
Are individual people listed in the CCLA that Sun is signing? If so, then
how can I find out who is listed, so that I can feel more confident about
accepting further contributions. Looking at
http://www.apache.org/licenses/cla-corporate.txt I don't think that
individuals are listed.
Also, in the past there seems to be some code that was contributed to
Apache by Sun employees who were committers, but who have never signed a
CLA. I think that at that time CCLAs did not exist. So I find the phrase in
the CCLA most interesting:
"Your "Contributions" means all of your past, present and future
contributions ..."
>From reading that CCLA form it looks like all past, present and future
contributions of all Sun employees have their licensing rights given to the
ASF, unless the contributions were donated with "Not a contribution" or
some other conspicuous, but similar phrase. If this is true then I feel
better about past contributions by people who were Sun employees at that
time, and who have never signed a CLA.
- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
Apache Xalan PMC Member
e-mail: minchau@ca.ibm.com
Shane Curcuru
<shane_curcuru@ya
hoo.com> To
general@xml.apache.org
03/31/2005 12:18 cc
PM xerces-j-dev@xml.apache.org,
general@incubator.apache.org,
Eduardo Pelegri-Llopart
Please respond to <Ed...@Sun.COM>,
general Jeff Suttor <Je...@Sun.COM>,
xalan-dev@xml.apache.org,
commons-dev@xml.apache.org,
Suresh.K@Sun.COM
Subject
Re: Donation of JAXP 1.3 Sources to
Apache
Excellent news! Thank to Sun folk and Geir for picking up the ball on
this one.
Note: once the papers are in the Hallowed Halls, I presume that Neeraj
will get some consensus from xml-commons, xalan-dev, and xerces-j-dev as
to how to actually check this in? I'm presuming you have someone with
commit access to xml-commons, which is the pre-existing home for JAXP.
(Although incubator should check the legal issues, I don't think the
code needs to checkin thru there).
But I know Xerces and Xalan may have specific dependencies on
xml-commons code, so we probably need to branch to allow current
versions to work as-is and let them plan new versions with 1.3 support.
- Shane
Neeraj Bajaj wrote:
> xml-common, xerces & xalan communities,
>
> I have learnt that legal issues regarding donation has been resolved and
> latest version of CCLA has been signed.
> So would like to make the actual code grant of JAXP 1.3 APIs +
> implementation ASAP. I will start the preparation
> today and will be back with actual code grant with in 2 days.
>
>
> Best Regards,
>
> - Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Shane Curcuru <sh...@yahoo.com>.
Excellent news! Thank to Sun folk and Geir for picking up the ball on
this one.
Note: once the papers are in the Hallowed Halls, I presume that Neeraj
will get some consensus from xml-commons, xalan-dev, and xerces-j-dev as
to how to actually check this in? I'm presuming you have someone with
commit access to xml-commons, which is the pre-existing home for JAXP.
(Although incubator should check the legal issues, I don't think the
code needs to checkin thru there).
But I know Xerces and Xalan may have specific dependencies on
xml-commons code, so we probably need to branch to allow current
versions to work as-is and let them plan new versions with 1.3 support.
- Shane
Neeraj Bajaj wrote:
> xml-common, xerces & xalan communities,
>
> I have learnt that legal issues regarding donation has been resolved and
> latest version of CCLA has been signed.
> So would like to make the actual code grant of JAXP 1.3 APIs +
> implementation ASAP. I will start the preparation
> today and will be back with actual code grant with in 2 days.
>
>
> Best Regards,
>
> - Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hello all,
I just thought I'd echo Eduardo's sentiments in being very glad that this
is moving forward! We've had a lot of new functionality in Xerces for a
long time (DOM Level 3 was completed months ago :) ), and it'll be great
to get that into people's hands, paired with an implementation of the rest
of JAXP 1.3. It having been over a year since Xerces-J's last release,
and 6 months since JAXP 1.3 was finalized, I'm sure there are lots of
folks out there who are more than ready for a JAXP 1.3-compliant Xerces
and Xalan.
Much thanks to the good folks at Sun for having surmounted all obstacles
and got this done!
Cheers,
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
Eduardo Pelegri-Llopart <Ed...@Sun.COM>
03/31/2005 11:41 AM
Please respond to
xerces-j-dev
To
"Geir Magnusson Jr." <ge...@apache.org>
cc
general@incubator.apache.org, Eduardo Pelegri-Llopart
<Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
general@xml.apache.org, xalan-dev@xml.apache.org,
commons-dev@xml.apache.org, Suresh.K@Sun.COM, xerces-j-dev@xml.apache.org
Subject
Re: Donation of JAXP 1.3 Sources to Apache
Thanks. It is good to see this issue moving forward.
- eduard/o
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
>
>> xml-common, xerces & xalan communities,
>>
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>
>
> I have that CCLA (picked it up on a visit to Sun) and will be forwarding
> to Jim (ASF Secretary) for emplacement in the Hallowed Vaults of the
ASF.
>
> geir
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hello all,
I just thought I'd echo Eduardo's sentiments in being very glad that this
is moving forward! We've had a lot of new functionality in Xerces for a
long time (DOM Level 3 was completed months ago :) ), and it'll be great
to get that into people's hands, paired with an implementation of the rest
of JAXP 1.3. It having been over a year since Xerces-J's last release,
and 6 months since JAXP 1.3 was finalized, I'm sure there are lots of
folks out there who are more than ready for a JAXP 1.3-compliant Xerces
and Xalan.
Much thanks to the good folks at Sun for having surmounted all obstacles
and got this done!
Cheers,
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
Eduardo Pelegri-Llopart <Ed...@Sun.COM>
03/31/2005 11:41 AM
Please respond to
xerces-j-dev
To
"Geir Magnusson Jr." <ge...@apache.org>
cc
general@incubator.apache.org, Eduardo Pelegri-Llopart
<Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
general@xml.apache.org, xalan-dev@xml.apache.org,
commons-dev@xml.apache.org, Suresh.K@Sun.COM, xerces-j-dev@xml.apache.org
Subject
Re: Donation of JAXP 1.3 Sources to Apache
Thanks. It is good to see this issue moving forward.
- eduard/o
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
>
>> xml-common, xerces & xalan communities,
>>
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>
>
> I have that CCLA (picked it up on a visit to Sun) and will be forwarding
> to Jim (ASF Secretary) for emplacement in the Hallowed Vaults of the
ASF.
>
> geir
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hello all,
I just thought I'd echo Eduardo's sentiments in being very glad that this
is moving forward! We've had a lot of new functionality in Xerces for a
long time (DOM Level 3 was completed months ago :) ), and it'll be great
to get that into people's hands, paired with an implementation of the rest
of JAXP 1.3. It having been over a year since Xerces-J's last release,
and 6 months since JAXP 1.3 was finalized, I'm sure there are lots of
folks out there who are more than ready for a JAXP 1.3-compliant Xerces
and Xalan.
Much thanks to the good folks at Sun for having surmounted all obstacles
and got this done!
Cheers,
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
Eduardo Pelegri-Llopart <Ed...@Sun.COM>
03/31/2005 11:41 AM
Please respond to
xerces-j-dev
To
"Geir Magnusson Jr." <ge...@apache.org>
cc
general@incubator.apache.org, Eduardo Pelegri-Llopart
<Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
general@xml.apache.org, xalan-dev@xml.apache.org,
commons-dev@xml.apache.org, Suresh.K@Sun.COM, xerces-j-dev@xml.apache.org
Subject
Re: Donation of JAXP 1.3 Sources to Apache
Thanks. It is good to see this issue moving forward.
- eduard/o
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
>
>> xml-common, xerces & xalan communities,
>>
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>
>
> I have that CCLA (picked it up on a visit to Sun) and will be forwarding
> to Jim (ASF Secretary) for emplacement in the Hallowed Vaults of the
ASF.
>
> geir
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hello all,
I just thought I'd echo Eduardo's sentiments in being very glad that this
is moving forward! We've had a lot of new functionality in Xerces for a
long time (DOM Level 3 was completed months ago :) ), and it'll be great
to get that into people's hands, paired with an implementation of the rest
of JAXP 1.3. It having been over a year since Xerces-J's last release,
and 6 months since JAXP 1.3 was finalized, I'm sure there are lots of
folks out there who are more than ready for a JAXP 1.3-compliant Xerces
and Xalan.
Much thanks to the good folks at Sun for having surmounted all obstacles
and got this done!
Cheers,
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
Eduardo Pelegri-Llopart <Ed...@Sun.COM>
03/31/2005 11:41 AM
Please respond to
xerces-j-dev
To
"Geir Magnusson Jr." <ge...@apache.org>
cc
general@incubator.apache.org, Eduardo Pelegri-Llopart
<Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
general@xml.apache.org, xalan-dev@xml.apache.org,
commons-dev@xml.apache.org, Suresh.K@Sun.COM, xerces-j-dev@xml.apache.org
Subject
Re: Donation of JAXP 1.3 Sources to Apache
Thanks. It is good to see this issue moving forward.
- eduard/o
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
>
>> xml-common, xerces & xalan communities,
>>
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>
>
> I have that CCLA (picked it up on a visit to Sun) and will be forwarding
> to Jim (ASF Secretary) for emplacement in the Hallowed Vaults of the
ASF.
>
> geir
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hello all,
I just thought I'd echo Eduardo's sentiments in being very glad that this
is moving forward! We've had a lot of new functionality in Xerces for a
long time (DOM Level 3 was completed months ago :) ), and it'll be great
to get that into people's hands, paired with an implementation of the rest
of JAXP 1.3. It having been over a year since Xerces-J's last release,
and 6 months since JAXP 1.3 was finalized, I'm sure there are lots of
folks out there who are more than ready for a JAXP 1.3-compliant Xerces
and Xalan.
Much thanks to the good folks at Sun for having surmounted all obstacles
and got this done!
Cheers,
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
Eduardo Pelegri-Llopart <Ed...@Sun.COM>
03/31/2005 11:41 AM
Please respond to
xerces-j-dev
To
"Geir Magnusson Jr." <ge...@apache.org>
cc
general@incubator.apache.org, Eduardo Pelegri-Llopart
<Ed...@Sun.COM>, Jeff Suttor <Je...@Sun.COM>,
general@xml.apache.org, xalan-dev@xml.apache.org,
commons-dev@xml.apache.org, Suresh.K@Sun.COM, xerces-j-dev@xml.apache.org
Subject
Re: Donation of JAXP 1.3 Sources to Apache
Thanks. It is good to see this issue moving forward.
- eduard/o
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
>
>> xml-common, xerces & xalan communities,
>>
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>
>
> I have that CCLA (picked it up on a visit to Sun) and will be forwarding
> to Jim (ASF Secretary) for emplacement in the Hallowed Vaults of the
ASF.
>
> geir
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Eduardo Pelegri-Llopart <Ed...@Sun.COM>.
Thanks. It is good to see this issue moving forward.
- eduard/o
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
>
>> xml-common, xerces & xalan communities,
>>
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>
>
> I have that CCLA (picked it up on a visit to Sun) and will be forwarding
> to Jim (ASF Secretary) for emplacement in the Hallowed Vaults of the ASF.
>
> geir
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Eduardo Pelegri-Llopart <Ed...@Sun.COM>.
Thanks. It is good to see this issue moving forward.
- eduard/o
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
>
>> xml-common, xerces & xalan communities,
>>
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>
>
> I have that CCLA (picked it up on a visit to Sun) and will be forwarding
> to Jim (ASF Secretary) for emplacement in the Hallowed Vaults of the ASF.
>
> geir
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Eduardo Pelegri-Llopart <Ed...@Sun.COM>.
Thanks. It is good to see this issue moving forward.
- eduard/o
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
>
>> xml-common, xerces & xalan communities,
>>
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>
>
> I have that CCLA (picked it up on a visit to Sun) and will be forwarding
> to Jim (ASF Secretary) for emplacement in the Hallowed Vaults of the ASF.
>
> geir
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Eduardo Pelegri-Llopart <Ed...@Sun.COM>.
Thanks. It is good to see this issue moving forward.
- eduard/o
Geir Magnusson Jr. wrote:
>
> On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
>
>> xml-common, xerces & xalan communities,
>>
>> I have learnt that legal issues regarding donation has been resolved
>> and latest version of CCLA has been signed.
>> So would like to make the actual code grant of JAXP 1.3 APIs +
>> implementation ASAP. I will start the preparation
>> today and will be back with actual code grant with in 2 days.
>
>
> I have that CCLA (picked it up on a visit to Sun) and will be forwarding
> to Jim (ASF Secretary) for emplacement in the Hallowed Vaults of the ASF.
>
> geir
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
> xml-common, xerces & xalan communities,
>
> I have learnt that legal issues regarding donation has been resolved
> and latest version of CCLA has been signed.
> So would like to make the actual code grant of JAXP 1.3 APIs +
> implementation ASAP. I will start the preparation
> today and will be back with actual code grant with in 2 days.
I have that CCLA (picked it up on a visit to Sun) and will be
forwarding to Jim (ASF Secretary) for emplacement in the Hallowed
Vaults of the ASF.
geir
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Shane Curcuru <sh...@yahoo.com>.
Excellent news! Thank to Sun folk and Geir for picking up the ball on
this one.
Note: once the papers are in the Hallowed Halls, I presume that Neeraj
will get some consensus from xml-commons, xalan-dev, and xerces-j-dev as
to how to actually check this in? I'm presuming you have someone with
commit access to xml-commons, which is the pre-existing home for JAXP.
(Although incubator should check the legal issues, I don't think the
code needs to checkin thru there).
But I know Xerces and Xalan may have specific dependencies on
xml-commons code, so we probably need to branch to allow current
versions to work as-is and let them plan new versions with 1.3 support.
- Shane
Neeraj Bajaj wrote:
> xml-common, xerces & xalan communities,
>
> I have learnt that legal issues regarding donation has been resolved and
> latest version of CCLA has been signed.
> So would like to make the actual code grant of JAXP 1.3 APIs +
> implementation ASAP. I will start the preparation
> today and will be back with actual code grant with in 2 days.
>
>
> Best Regards,
>
> - Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Shane Curcuru <sh...@yahoo.com>.
Excellent news! Thank to Sun folk and Geir for picking up the ball on
this one.
Note: once the papers are in the Hallowed Halls, I presume that Neeraj
will get some consensus from xml-commons, xalan-dev, and xerces-j-dev as
to how to actually check this in? I'm presuming you have someone with
commit access to xml-commons, which is the pre-existing home for JAXP.
(Although incubator should check the legal issues, I don't think the
code needs to checkin thru there).
But I know Xerces and Xalan may have specific dependencies on
xml-commons code, so we probably need to branch to allow current
versions to work as-is and let them plan new versions with 1.3 support.
- Shane
Neeraj Bajaj wrote:
> xml-common, xerces & xalan communities,
>
> I have learnt that legal issues regarding donation has been resolved and
> latest version of CCLA has been signed.
> So would like to make the actual code grant of JAXP 1.3 APIs +
> implementation ASAP. I will start the preparation
> today and will be back with actual code grant with in 2 days.
>
>
> Best Regards,
>
> - Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Shane Curcuru <sh...@yahoo.com>.
Excellent news! Thank to Sun folk and Geir for picking up the ball on
this one.
Note: once the papers are in the Hallowed Halls, I presume that Neeraj
will get some consensus from xml-commons, xalan-dev, and xerces-j-dev as
to how to actually check this in? I'm presuming you have someone with
commit access to xml-commons, which is the pre-existing home for JAXP.
(Although incubator should check the legal issues, I don't think the
code needs to checkin thru there).
But I know Xerces and Xalan may have specific dependencies on
xml-commons code, so we probably need to branch to allow current
versions to work as-is and let them plan new versions with 1.3 support.
- Shane
Neeraj Bajaj wrote:
> xml-common, xerces & xalan communities,
>
> I have learnt that legal issues regarding donation has been resolved and
> latest version of CCLA has been signed.
> So would like to make the actual code grant of JAXP 1.3 APIs +
> implementation ASAP. I will start the preparation
> today and will be back with actual code grant with in 2 days.
>
>
> Best Regards,
>
> - Neeraj
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
> xml-common, xerces & xalan communities,
>
> I have learnt that legal issues regarding donation has been resolved
> and latest version of CCLA has been signed.
> So would like to make the actual code grant of JAXP 1.3 APIs +
> implementation ASAP. I will start the preparation
> today and will be back with actual code grant with in 2 days.
I have that CCLA (picked it up on a visit to Sun) and will be
forwarding to Jim (ASF Secretary) for emplacement in the Hallowed
Vaults of the ASF.
geir
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
> xml-common, xerces & xalan communities,
>
> I have learnt that legal issues regarding donation has been resolved
> and latest version of CCLA has been signed.
> So would like to make the actual code grant of JAXP 1.3 APIs +
> implementation ASAP. I will start the preparation
> today and will be back with actual code grant with in 2 days.
I have that CCLA (picked it up on a visit to Sun) and will be
forwarding to Jim (ASF Secretary) for emplacement in the Hallowed
Vaults of the ASF.
geir
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Shane Curcuru <sh...@yahoo.com>.
Excellent news! Thank to Sun folk and Geir for picking up the ball on
this one.
Note: once the papers are in the Hallowed Halls, I presume that Neeraj
will get some consensus from xml-commons, xalan-dev, and xerces-j-dev as
to how to actually check this in? I'm presuming you have someone with
commit access to xml-commons, which is the pre-existing home for JAXP.
(Although incubator should check the legal issues, I don't think the
code needs to checkin thru there).
But I know Xerces and Xalan may have specific dependencies on
xml-commons code, so we probably need to branch to allow current
versions to work as-is and let them plan new versions with 1.3 support.
- Shane
Neeraj Bajaj wrote:
> xml-common, xerces & xalan communities,
>
> I have learnt that legal issues regarding donation has been resolved and
> latest version of CCLA has been signed.
> So would like to make the actual code grant of JAXP 1.3 APIs +
> implementation ASAP. I will start the preparation
> today and will be back with actual code grant with in 2 days.
>
>
> Best Regards,
>
> - Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Mar 31, 2005, at 11:09 AM, Neeraj Bajaj wrote:
> xml-common, xerces & xalan communities,
>
> I have learnt that legal issues regarding donation has been resolved
> and latest version of CCLA has been signed.
> So would like to make the actual code grant of JAXP 1.3 APIs +
> implementation ASAP. I will start the preparation
> today and will be back with actual code grant with in 2 days.
I have that CCLA (picked it up on a visit to Sun) and will be
forwarding to Jim (ASF Secretary) for emplacement in the Hallowed
Vaults of the ASF.
geir
--
Geir Magnusson Jr +1-203-665-6437
geirm@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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
xml-common, xerces & xalan communities,
I have learnt that legal issues regarding donation has been resolved and
latest version of CCLA has been signed.
So would like to make the actual code grant of JAXP 1.3 APIs +
implementation ASAP. I will start the preparation
today and will be back with actual code grant with in 2 days.
Best Regards,
- Neeraj
Geir Magnusson Jr. wrote:
>
> On Oct 19, 2004, at 1:40 AM, Neeraj Bajaj wrote:
>
>>
>>
>> Geir Magnusson Jr. wrote:
>>
>>>
>>>
>>> This is an update to the existing code that is already there.
>>>
>>> It is, I suppose, a new grant of software to an existing community,
>>> so I think that what we need is the grant documentation from Sun*,
>>> have that entered into the incubator, and move from there.
>>
>>
>> Code grant details can be found at :
>>
>> http://www.apache.org/licenses/#grants
>>
>> I checked on this one, This work involves legal and is being worked
>> with legal now.
>
>
> Please don't have them use that. We are working on a new version.
> Who in Sun legal is doing this? I've worked w/ a few people there for
> various projects, and happy to talk to them.
>
> geir
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
xml-common, xerces & xalan communities,
I have learnt that legal issues regarding donation has been resolved and
latest version of CCLA has been signed.
So would like to make the actual code grant of JAXP 1.3 APIs +
implementation ASAP. I will start the preparation
today and will be back with actual code grant with in 2 days.
Best Regards,
- Neeraj
Geir Magnusson Jr. wrote:
>
> On Oct 19, 2004, at 1:40 AM, Neeraj Bajaj wrote:
>
>>
>>
>> Geir Magnusson Jr. wrote:
>>
>>>
>>>
>>> This is an update to the existing code that is already there.
>>>
>>> It is, I suppose, a new grant of software to an existing community,
>>> so I think that what we need is the grant documentation from Sun*,
>>> have that entered into the incubator, and move from there.
>>
>>
>> Code grant details can be found at :
>>
>> http://www.apache.org/licenses/#grants
>>
>> I checked on this one, This work involves legal and is being worked
>> with legal now.
>
>
> Please don't have them use that. We are working on a new version.
> Who in Sun legal is doing this? I've worked w/ a few people there for
> various projects, and happy to talk to them.
>
> geir
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
xml-common, xerces & xalan communities,
I have learnt that legal issues regarding donation has been resolved and
latest version of CCLA has been signed.
So would like to make the actual code grant of JAXP 1.3 APIs +
implementation ASAP. I will start the preparation
today and will be back with actual code grant with in 2 days.
Best Regards,
- Neeraj
Geir Magnusson Jr. wrote:
>
> On Oct 19, 2004, at 1:40 AM, Neeraj Bajaj wrote:
>
>>
>>
>> Geir Magnusson Jr. wrote:
>>
>>>
>>>
>>> This is an update to the existing code that is already there.
>>>
>>> It is, I suppose, a new grant of software to an existing community,
>>> so I think that what we need is the grant documentation from Sun*,
>>> have that entered into the incubator, and move from there.
>>
>>
>> Code grant details can be found at :
>>
>> http://www.apache.org/licenses/#grants
>>
>> I checked on this one, This work involves legal and is being worked
>> with legal now.
>
>
> Please don't have them use that. We are working on a new version.
> Who in Sun legal is doing this? I've worked w/ a few people there for
> various projects, and happy to talk to them.
>
> geir
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
xml-common, xerces & xalan communities,
I have learnt that legal issues regarding donation has been resolved and
latest version of CCLA has been signed.
So would like to make the actual code grant of JAXP 1.3 APIs +
implementation ASAP. I will start the preparation
today and will be back with actual code grant with in 2 days.
Best Regards,
- Neeraj
Geir Magnusson Jr. wrote:
>
> On Oct 19, 2004, at 1:40 AM, Neeraj Bajaj wrote:
>
>>
>>
>> Geir Magnusson Jr. wrote:
>>
>>>
>>>
>>> This is an update to the existing code that is already there.
>>>
>>> It is, I suppose, a new grant of software to an existing community,
>>> so I think that what we need is the grant documentation from Sun*,
>>> have that entered into the incubator, and move from there.
>>
>>
>> Code grant details can be found at :
>>
>> http://www.apache.org/licenses/#grants
>>
>> I checked on this one, This work involves legal and is being worked
>> with legal now.
>
>
> Please don't have them use that. We are working on a new version.
> Who in Sun legal is doing this? I've worked w/ a few people there for
> various projects, and happy to talk to them.
>
> geir
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
xml-common, xerces & xalan communities,
I have learnt that legal issues regarding donation has been resolved and
latest version of CCLA has been signed.
So would like to make the actual code grant of JAXP 1.3 APIs +
implementation ASAP. I will start the preparation
today and will be back with actual code grant with in 2 days.
Best Regards,
- Neeraj
Geir Magnusson Jr. wrote:
>
> On Oct 19, 2004, at 1:40 AM, Neeraj Bajaj wrote:
>
>>
>>
>> Geir Magnusson Jr. wrote:
>>
>>>
>>>
>>> This is an update to the existing code that is already there.
>>>
>>> It is, I suppose, a new grant of software to an existing community,
>>> so I think that what we need is the grant documentation from Sun*,
>>> have that entered into the incubator, and move from there.
>>
>>
>> Code grant details can be found at :
>>
>> http://www.apache.org/licenses/#grants
>>
>> I checked on this one, This work involves legal and is being worked
>> with legal now.
>
>
> Please don't have them use that. We are working on a new version.
> Who in Sun legal is doing this? I've worked w/ a few people there for
> various projects, and happy to talk to them.
>
> geir
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Oct 19, 2004, at 1:40 AM, Neeraj Bajaj wrote:
>
>
> Geir Magnusson Jr. wrote:
>>
>>
>> This is an update to the existing code that is already there.
>>
>> It is, I suppose, a new grant of software to an existing community,
>> so I think that what we need is the grant documentation from Sun*,
>> have that entered into the incubator, and move from there.
>
> Code grant details can be found at :
>
> http://www.apache.org/licenses/#grants
>
> I checked on this one, This work involves legal and is being worked
> with legal now.
Please don't have them use that. We are working on a new version. Who
in Sun legal is doing this? I've worked w/ a few people there for
various projects, and happy to talk to them.
geir
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Wednesday 20 October 2004 01:56, Neil Graham wrote:
> I'd also be curious to know what proportion of Apache projects have
> migrated to SVN so far?
http://svn.apache.org/repos/asf/
Is the current complete set of projects migrated, some larger than others.
Niclas
--
+------//-------------------+
/ http://www.bali.ac /
/ http://niclas.hedhman.org /
+------//-------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: SVN migration (Was: Donation of JAXP 1.3 Sources to Apache)
Posted by David Crossley <cr...@apache.org>.
Neil Graham wrote:
> David Crossley wrote:
> >
> > I was not intending that the two get tangled.
> > Either do the move before or after.
> >
> > Just that when "legal delays" were mentioned,
> > i thought that there would be plenty of time.
>
> Can we be optimistic and hope not? :)
Okay then, just this once :-)
> > Afterwards is fine by me. I was responding to the
> > infrastructure@a.o request to consider moving soon.
>
> Guess this was only sent to folks subscribed to infrastructure@; I haven't
> seen it on any list I'm subscribed to anyway. ...
Not only infrastructure, here too. There were a couple of
mentions earlier in the initial thread. Here is one:
http://marc.theaimsgroup.com/?l=xml-commons-dev&m=109775743126537
I agree with your sentiment though - infra@ should
announce more widely the general desire to move to SVN.
> ... Good to know that they
> consider this set-up stable now; but if they really want to encourage
> projects to migrate, perhaps it might not be a bad idea to (a) let them
> know directly and (b) sell them on how worthwhile the pain will be. I'm
> sure the pain's worthwhile from my perspective; I'd just rather wait until
> we're sure we're in a period of calm than embark on something now only to
> discover next week that things will get complicated.
We definitely do not want to risk holding up the
JAXP update.
--David
> > Apache Forrest was one of the early ones to move.
> > The transition was a breeze and we love it now.
>
> Cool!
>
> Cheers!
> Neil
> Neil Graham
> Manager, XML Parser Development
> IBM Toronto Lab
> Phone: 905-413-3519, T/L 969-3519
> E-mail: neilg@ca.ibm.com
Re: SVN migration (Was: Donation of JAXP 1.3 Sources to Apache)
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi David,
David Crossley <cr...@apache.org> wrote on 10/20/2004 03:20:26 AM:
> Neil Graham wrote:
> > >
> > > So would this be an appropriate time to move the
> > > xml-commons repository to SVN?
> >
> > Well, I don't know about you, but I generally prefer to ease my way
into
> > new software tools, rather than dive right into advanced usage. So,
> > speaking for myself, I'd prefer to wait for a period of calm, where
the
> > move to SVN would be the only change, rather than combine the move to
SVN
> > with an update to most of the code in the xml-commons repository and
> > whatever tinkering with branches that this also might end up implying.
>
> I was not intending that the two get tangled.
> Either do the move before or after.
>
> Just that when "legal delays" were mentioned,
> i thought that there would be plenty of time.
Can we be optimistic and hope not? :)
> Afterwards is fine by me. I was responding to the
> infrastructure@a.o request to consider moving soon.
Guess this was only sent to folks subscribed to infrastructure@; I haven't
seen it on any list I'm subscribed to anyway. Good to know that they
consider this set-up stable now; but if they really want to encourage
projects to migrate, perhaps it might not be a bad idea to (a) let them
know directly and (b) sell them on how worthwhile the pain will be. I'm
sure the pain's worthwhile from my perspective; I'd just rather wait until
we're sure we're in a period of calm than embark on something now only to
discover next week that things will get complicated.
> Apache Forrest was one of the early ones to move.
> The transition was a breeze and we love it now.
Cool!
Cheers!
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
SVN migration (Was: Donation of JAXP 1.3 Sources to Apache)
Posted by David Crossley <cr...@apache.org>.
Neil Graham wrote:
> >
> > So would this be an appropriate time to move the
> > xml-commons repository to SVN?
>
> Well, I don't know about you, but I generally prefer to ease my way into
> new software tools, rather than dive right into advanced usage. So,
> speaking for myself, I'd prefer to wait for a period of calm, where the
> move to SVN would be the only change, rather than combine the move to SVN
> with an update to most of the code in the xml-commons repository and
> whatever tinkering with branches that this also might end up implying.
I was not intending that the two get tangled.
Either do the move before or after.
Just that when "legal delays" were mentioned,
i thought that there would be plenty of time.
Afterwards is fine by me. I was responding to the
infrastructure@a.o request to consider moving soon.
> I'd also be curious to know what proportion of Apache projects have
> migrated to SVN so far? There would be a significantly higher amount of
> churn caused to the community by an SVN migration than was caused by our
> earlier Jira migration; so I'd prefer to go down a well-trod path than be
> on the bleeding edge in this particular instance.
Apache Forrest was one of the early ones to move.
The transition was a breeze and we love it now.
We are mainly using the trunk, with small experimental
branches which we merge early. Different to xml-commons.
--
David Crossley
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Wednesday 20 October 2004 01:56, Neil Graham wrote:
> I'd also be curious to know what proportion of Apache projects have
> migrated to SVN so far?
http://svn.apache.org/repos/asf/
Is the current complete set of projects migrated, some larger than others.
Niclas
--
+------//-------------------+
/ http://www.bali.ac /
/ http://niclas.hedhman.org /
+------//-------------------+
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Wednesday 20 October 2004 01:56, Neil Graham wrote:
> I'd also be curious to know what proportion of Apache projects have
> migrated to SVN so far?
http://svn.apache.org/repos/asf/
Is the current complete set of projects migrated, some larger than others.
Niclas
--
+------//-------------------+
/ http://www.bali.ac /
/ http://niclas.hedhman.org /
+------//-------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Wednesday 20 October 2004 01:56, Neil Graham wrote:
> I'd also be curious to know what proportion of Apache projects have
> migrated to SVN so far?
http://svn.apache.org/repos/asf/
Is the current complete set of projects migrated, some larger than others.
Niclas
--
+------//-------------------+
/ http://www.bali.ac /
/ http://niclas.hedhman.org /
+------//-------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Percentage of projects using Subversion was Re: Donation of JAXP 1.3 Sources to Apache
Posted by Craig McClanahan <cr...@gmail.com>.
On Tue, 19 Oct 2004 11:40:47 -0700, Justin Erenkrantz
<ju...@erenkrantz.com> wrote:
> --On Tuesday, October 19, 2004 1:56 PM -0400 Neil Graham <ne...@ca.ibm.com>
> wrote:
>
> > I'd also be curious to know what proportion of Apache projects have
> > migrated to SVN so far? There would be a significantly higher amount of
> > churn caused to the community by an SVN migration than was caused by our
> > earlier Jira migration; so I'd prefer to go down a well-trod path than be
> > on the bleeding edge in this particular instance.
>
> <http://svn.apache.org/repos/asf/>
>
> A fair number of projects have already converted and a few more (such as
> httpd) have already agreed to convert, but are waiting for the 'right' time
> to convert. (My hunch is a bunch more might migrate at upcoming AC'04.)
>
FWIW, we (Struts) just switched, and once you take advantage of "svn
copy" and "svn move", or the ability to actually delete a directory,
or cheap tag==branch, you'll never look back :-).
> For more info, please see: <http://www.apache.org/dev/cvs2svn.html>
This tool did a really good job of importing our CVS history logs, too.
>
> HTH. -- justin
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Percentage of projects using Subversion was Re: Donation of
JAXP 1.3 Sources to Apache
Posted by Santiago Gala <sg...@hisitech.com>.
El mar, 19-10-2004 a las 11:40 -0700, Justin Erenkrantz escribió:
> --On Tuesday, October 19, 2004 1:56 PM -0400 Neil Graham <ne...@ca.ibm.com>
> wrote:
>
> > I'd also be curious to know what proportion of Apache projects have
> > migrated to SVN so far? There would be a significantly higher amount of
> > churn caused to the community by an SVN migration than was caused by our
> > earlier Jira migration; so I'd prefer to go down a well-trod path than be
> > on the bleeding edge in this particular instance.
>
> <http://svn.apache.org/repos/asf/>
>
> A fair number of projects have already converted and a few more (such as
> httpd) have already agreed to convert, but are waiting for the 'right' time
> to convert. (My hunch is a bunch more might migrate at upcoming AC'04.)
>
portals is half way. Jetspeed-1 will be converted after the next
release, and Jetspeed-2 too. Site and pluto are already using svn.
The only nit I have it I was never able to make subclipse work under
linux-ppc, which is what I'm currently using. Not that I use eclipse
that much, though.
Ah!, and getting updatedb ignore the .svn trees would be nice too.
Regards
> For more info, please see: <http://www.apache.org/dev/cvs2svn.html>
>
> HTH. -- justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
--
Santiago Gala <sg...@hisitech.com>
High Sierra Technology, SLU
Re: Percentage of projects using Subversion was Re: Donation of
JAXP 1.3 Sources to Apache
Posted by Santiago Gala <sg...@hisitech.com>.
El mar, 19-10-2004 a las 11:40 -0700, Justin Erenkrantz escribió:
> --On Tuesday, October 19, 2004 1:56 PM -0400 Neil Graham <ne...@ca.ibm.com>
> wrote:
>
> > I'd also be curious to know what proportion of Apache projects have
> > migrated to SVN so far? There would be a significantly higher amount of
> > churn caused to the community by an SVN migration than was caused by our
> > earlier Jira migration; so I'd prefer to go down a well-trod path than be
> > on the bleeding edge in this particular instance.
>
> <http://svn.apache.org/repos/asf/>
>
> A fair number of projects have already converted and a few more (such as
> httpd) have already agreed to convert, but are waiting for the 'right' time
> to convert. (My hunch is a bunch more might migrate at upcoming AC'04.)
>
portals is half way. Jetspeed-1 will be converted after the next
release, and Jetspeed-2 too. Site and pluto are already using svn.
The only nit I have it I was never able to make subclipse work under
linux-ppc, which is what I'm currently using. Not that I use eclipse
that much, though.
Ah!, and getting updatedb ignore the .svn trees would be nice too.
Regards
> For more info, please see: <http://www.apache.org/dev/cvs2svn.html>
>
> HTH. -- justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
--
Santiago Gala <sg...@hisitech.com>
High Sierra Technology, SLU
Re: Percentage of projects using Subversion was Re: Donation of
JAXP 1.3 Sources to Apache
Posted by Santiago Gala <sg...@hisitech.com>.
El mar, 19-10-2004 a las 11:40 -0700, Justin Erenkrantz escribió:
> --On Tuesday, October 19, 2004 1:56 PM -0400 Neil Graham <ne...@ca.ibm.com>
> wrote:
>
> > I'd also be curious to know what proportion of Apache projects have
> > migrated to SVN so far? There would be a significantly higher amount of
> > churn caused to the community by an SVN migration than was caused by our
> > earlier Jira migration; so I'd prefer to go down a well-trod path than be
> > on the bleeding edge in this particular instance.
>
> <http://svn.apache.org/repos/asf/>
>
> A fair number of projects have already converted and a few more (such as
> httpd) have already agreed to convert, but are waiting for the 'right' time
> to convert. (My hunch is a bunch more might migrate at upcoming AC'04.)
>
portals is half way. Jetspeed-1 will be converted after the next
release, and Jetspeed-2 too. Site and pluto are already using svn.
The only nit I have it I was never able to make subclipse work under
linux-ppc, which is what I'm currently using. Not that I use eclipse
that much, though.
Ah!, and getting updatedb ignore the .svn trees would be nice too.
Regards
> For more info, please see: <http://www.apache.org/dev/cvs2svn.html>
>
> HTH. -- justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
--
Santiago Gala <sg...@hisitech.com>
High Sierra Technology, SLU
Re: Percentage of projects using Subversion was Re: Donation of JAXP 1.3 Sources to Apache
Posted by Dain Sundstrom <ds...@gluecode.com>.
On Oct 19, 2004, at 12:04 PM, Justin Erenkrantz wrote:
> --On Tuesday, October 19, 2004 12:01 PM -0700 Geir Magnusson Jr
> <ge...@4quarters.com> wrote:
>
>> I'm happy w/ svn. I really wish I had some minimal support in IDEA,
>> but
>> "svn stat" and "svn move" make up for it :)
>
> <http://svnup.tigris.org/>
Hate to be the one to break the news to you, but svnup doesn't seem to
work anymore. Also, there are no binaries for OSX. I love svn and
would never go back to cvs but the lack of IntelliJ support sucks.
-dain
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Percentage of projects using Subversion was Re: Donation of
JAXP 1.3 Sources to Apache
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Tuesday, October 19, 2004 12:01 PM -0700 Geir Magnusson Jr
<ge...@4quarters.com> wrote:
> I'm happy w/ svn. I really wish I had some minimal support in IDEA, but
> "svn stat" and "svn move" make up for it :)
<http://svnup.tigris.org/>
HTH. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Percentage of projects using Subversion was Re: Donation of JAXP 1.3 Sources to Apache
Posted by Geir Magnusson Jr <ge...@4quarters.com>.
On Oct 19, 2004, at 11:40 AM, Justin Erenkrantz wrote:
> --On Tuesday, October 19, 2004 1:56 PM -0400 Neil Graham
> <ne...@ca.ibm.com> wrote:
>
>> I'd also be curious to know what proportion of Apache projects have
>> migrated to SVN so far? There would be a significantly higher amount
>> of
>> churn caused to the community by an SVN migration than was caused by
>> our
>> earlier Jira migration; so I'd prefer to go down a well-trod path
>> than be
>> on the bleeding edge in this particular instance.
>
> <http://svn.apache.org/repos/asf/>
>
> A fair number of projects have already converted and a few more (such
> as httpd) have already agreed to convert, but are waiting for the
> 'right' time to convert. (My hunch is a bunch more might migrate at
> upcoming AC'04.)
>
> For more info, please see: <http://www.apache.org/dev/cvs2svn.html>
I'm happy w/ svn. I really wish I had some minimal support in IDEA,
but "svn stat" and "svn move" make up for it :)
geir
>
> HTH. -- justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Percentage of projects using Subversion was Re: Donation of JAXP
1.3 Sources to Apache
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Tuesday, October 19, 2004 1:56 PM -0400 Neil Graham <ne...@ca.ibm.com>
wrote:
> I'd also be curious to know what proportion of Apache projects have
> migrated to SVN so far? There would be a significantly higher amount of
> churn caused to the community by an SVN migration than was caused by our
> earlier Jira migration; so I'd prefer to go down a well-trod path than be
> on the bleeding edge in this particular instance.
<http://svn.apache.org/repos/asf/>
A fair number of projects have already converted and a few more (such as
httpd) have already agreed to convert, but are waiting for the 'right' time
to convert. (My hunch is a bunch more might migrate at upcoming AC'04.)
For more info, please see: <http://www.apache.org/dev/cvs2svn.html>
HTH. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Percentage of projects using Subversion was Re: Donation of JAXP
1.3 Sources to Apache
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Tuesday, October 19, 2004 1:56 PM -0400 Neil Graham <ne...@ca.ibm.com>
wrote:
> I'd also be curious to know what proportion of Apache projects have
> migrated to SVN so far? There would be a significantly higher amount of
> churn caused to the community by an SVN migration than was caused by our
> earlier Jira migration; so I'd prefer to go down a well-trod path than be
> on the bleeding edge in this particular instance.
<http://svn.apache.org/repos/asf/>
A fair number of projects have already converted and a few more (such as
httpd) have already agreed to convert, but are waiting for the 'right' time
to convert. (My hunch is a bunch more might migrate at upcoming AC'04.)
For more info, please see: <http://www.apache.org/dev/cvs2svn.html>
HTH. -- justin
Percentage of projects using Subversion was Re: Donation of JAXP
1.3 Sources to Apache
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Tuesday, October 19, 2004 1:56 PM -0400 Neil Graham <ne...@ca.ibm.com>
wrote:
> I'd also be curious to know what proportion of Apache projects have
> migrated to SVN so far? There would be a significantly higher amount of
> churn caused to the community by an SVN migration than was caused by our
> earlier Jira migration; so I'd prefer to go down a well-trod path than be
> on the bleeding edge in this particular instance.
<http://svn.apache.org/repos/asf/>
A fair number of projects have already converted and a few more (such as
httpd) have already agreed to convert, but are waiting for the 'right' time
to convert. (My hunch is a bunch more might migrate at upcoming AC'04.)
For more info, please see: <http://www.apache.org/dev/cvs2svn.html>
HTH. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Percentage of projects using Subversion was Re: Donation of JAXP
1.3 Sources to Apache
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Tuesday, October 19, 2004 1:56 PM -0400 Neil Graham <ne...@ca.ibm.com>
wrote:
> I'd also be curious to know what proportion of Apache projects have
> migrated to SVN so far? There would be a significantly higher amount of
> churn caused to the community by an SVN migration than was caused by our
> earlier Jira migration; so I'd prefer to go down a well-trod path than be
> on the bleeding edge in this particular instance.
<http://svn.apache.org/repos/asf/>
A fair number of projects have already converted and a few more (such as
httpd) have already agreed to convert, but are waiting for the 'right' time
to convert. (My hunch is a bunch more might migrate at upcoming AC'04.)
For more info, please see: <http://www.apache.org/dev/cvs2svn.html>
HTH. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi David,
>
> So would this be an appropriate time to move the
> xml-commons repository to SVN?
Well, I don't know about you, but I generally prefer to ease my way into
new software tools, rather than dive right into advanced usage. So,
speaking for myself, I'd prefer to wait for a period of calm, where the
move to SVN would be the only change, rather than combine the move to SVN
with an update to most of the code in the xml-commons repository and
whatever tinkering with branches that this also might end up implying.
I'd also be curious to know what proportion of Apache projects have
migrated to SVN so far? There would be a significantly higher amount of
churn caused to the community by an SVN migration than was caused by our
earlier Jira migration; so I'd prefer to go down a well-trod path than be
on the bleeding edge in this particular instance.
Cheers!
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi David,
>
> So would this be an appropriate time to move the
> xml-commons repository to SVN?
Well, I don't know about you, but I generally prefer to ease my way into
new software tools, rather than dive right into advanced usage. So,
speaking for myself, I'd prefer to wait for a period of calm, where the
move to SVN would be the only change, rather than combine the move to SVN
with an update to most of the code in the xml-commons repository and
whatever tinkering with branches that this also might end up implying.
I'd also be curious to know what proportion of Apache projects have
migrated to SVN so far? There would be a significantly higher amount of
churn caused to the community by an SVN migration than was caused by our
earlier Jira migration; so I'd prefer to go down a well-trod path than be
on the bleeding edge in this particular instance.
Cheers!
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi David,
>
> So would this be an appropriate time to move the
> xml-commons repository to SVN?
Well, I don't know about you, but I generally prefer to ease my way into
new software tools, rather than dive right into advanced usage. So,
speaking for myself, I'd prefer to wait for a period of calm, where the
move to SVN would be the only change, rather than combine the move to SVN
with an update to most of the code in the xml-commons repository and
whatever tinkering with branches that this also might end up implying.
I'd also be curious to know what proportion of Apache projects have
migrated to SVN so far? There would be a significantly higher amount of
churn caused to the community by an SVN migration than was caused by our
earlier Jira migration; so I'd prefer to go down a well-trod path than be
on the bleeding edge in this particular instance.
Cheers!
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi David,
>
> So would this be an appropriate time to move the
> xml-commons repository to SVN?
Well, I don't know about you, but I generally prefer to ease my way into
new software tools, rather than dive right into advanced usage. So,
speaking for myself, I'd prefer to wait for a period of calm, where the
move to SVN would be the only change, rather than combine the move to SVN
with an update to most of the code in the xml-commons repository and
whatever tinkering with branches that this also might end up implying.
I'd also be curious to know what proportion of Apache projects have
migrated to SVN so far? There would be a significantly higher amount of
churn caused to the community by an SVN migration than was caused by our
earlier Jira migration; so I'd prefer to go down a well-trod path than be
on the bleeding edge in this particular instance.
Cheers!
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi David,
>
> So would this be an appropriate time to move the
> xml-commons repository to SVN?
Well, I don't know about you, but I generally prefer to ease my way into
new software tools, rather than dive right into advanced usage. So,
speaking for myself, I'd prefer to wait for a period of calm, where the
move to SVN would be the only change, rather than combine the move to SVN
with an update to most of the code in the xml-commons repository and
whatever tinkering with branches that this also might end up implying.
I'd also be curious to know what proportion of Apache projects have
migrated to SVN so far? There would be a significantly higher amount of
churn caused to the community by an SVN migration than was caused by our
earlier Jira migration; so I'd prefer to go down a well-trod path than be
on the bleeding edge in this particular instance.
Cheers!
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by David Crossley <cr...@apache.org>.
Neeraj Bajaj wrote:
>
> I checked on this one, This work involves legal and is being worked with
> legal now.
> I guess this process would take some time so wanted to update the
> community about the status.
So would this be an appropriate time to move the
xml-commons repository to SVN?
--
David Crossley
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Oct 19, 2004, at 1:40 AM, Neeraj Bajaj wrote:
>
>
> Geir Magnusson Jr. wrote:
>>
>>
>> This is an update to the existing code that is already there.
>>
>> It is, I suppose, a new grant of software to an existing community,
>> so I think that what we need is the grant documentation from Sun*,
>> have that entered into the incubator, and move from there.
>
> Code grant details can be found at :
>
> http://www.apache.org/licenses/#grants
>
> I checked on this one, This work involves legal and is being worked
> with legal now.
Please don't have them use that. We are working on a new version. Who
in Sun legal is doing this? I've worked w/ a few people there for
various projects, and happy to talk to them.
geir
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by David Crossley <cr...@apache.org>.
Neeraj Bajaj wrote:
>
> I checked on this one, This work involves legal and is being worked with
> legal now.
> I guess this process would take some time so wanted to update the
> community about the status.
So would this be an appropriate time to move the
xml-commons repository to SVN?
--
David Crossley
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by David Crossley <cr...@apache.org>.
Neeraj Bajaj wrote:
>
> I checked on this one, This work involves legal and is being worked with
> legal now.
> I guess this process would take some time so wanted to update the
> community about the status.
So would this be an appropriate time to move the
xml-commons repository to SVN?
--
David Crossley
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Oct 19, 2004, at 1:40 AM, Neeraj Bajaj wrote:
>
>
> Geir Magnusson Jr. wrote:
>>
>>
>> This is an update to the existing code that is already there.
>>
>> It is, I suppose, a new grant of software to an existing community,
>> so I think that what we need is the grant documentation from Sun*,
>> have that entered into the incubator, and move from there.
>
> Code grant details can be found at :
>
> http://www.apache.org/licenses/#grants
>
> I checked on this one, This work involves legal and is being worked
> with legal now.
Please don't have them use that. We are working on a new version. Who
in Sun legal is doing this? I've worked w/ a few people there for
various projects, and happy to talk to them.
geir
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by David Crossley <cr...@apache.org>.
Neeraj Bajaj wrote:
>
> I checked on this one, This work involves legal and is being worked with
> legal now.
> I guess this process would take some time so wanted to update the
> community about the status.
So would this be an appropriate time to move the
xml-commons repository to SVN?
--
David Crossley
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Oct 19, 2004, at 1:40 AM, Neeraj Bajaj wrote:
>
>
> Geir Magnusson Jr. wrote:
>>
>>
>> This is an update to the existing code that is already there.
>>
>> It is, I suppose, a new grant of software to an existing community,
>> so I think that what we need is the grant documentation from Sun*,
>> have that entered into the incubator, and move from there.
>
> Code grant details can be found at :
>
> http://www.apache.org/licenses/#grants
>
> I checked on this one, This work involves legal and is being worked
> with legal now.
Please don't have them use that. We are working on a new version. Who
in Sun legal is doing this? I've worked w/ a few people there for
various projects, and happy to talk to them.
geir
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir Magnusson Jr. wrote:
> I worked on the some of the legal aspects with Eduardo, so going to
> jump in here.
>
> On Oct 13, 2004, at 3:59 PM, Berin Lautenbach wrote:
>
>> Neeraj Bajaj wrote:
>>
>>> Hello All,
>>> I was wondering when can we start merging the JAXP 1.3 sources ?
>>> Merging the code in branch/review/testing/committing to main trunk
>>> would take time so at least from my side i would like to see this
>>> work started as early as possible say from tomorrow. What is the
>>> general procedure ? Is there any formality that needs to be
>>> completed first ? What is the opinion of
>>> (Xml-commons/Xerces/Xalan) committers ?
>>
>>
>> I'm assuming that this is something that XML-Commons/Xerces/Xalan
>> wish to do?
>>
>> I've CCd general@incubator as well, as I'd like Noel's opinion, but
>> my feeling is that *if* the Xerces/Xalan and/or XML-Commons
>> community want this code to be imported (and it sounds like they do
>> - but I'd like to see that formalised), then the community side is
>> already there.
>>
>> If that's the case, then I don't think we need to go through the
>> full incubation process (Noel - thoughts appreciated!) - we only
>> need a code grant from Sun (we can't take something into our
>> repository until we are sure we have appropriate legal rights to do
>> so) + someone needs to fill out the incubation docs to show that
>> everything is AOK. I'm happy to help out with the latter part.
>
>
> This is an update to the existing code that is already there.
>
> It is, I suppose, a new grant of software to an existing community,
> so I think that what we need is the grant documentation from Sun*,
> have that entered into the incubator, and move from there.
Code grant details can be found at :
http://www.apache.org/licenses/#grants
I checked on this one, This work involves legal and is being worked with
legal now.
I guess this process would take some time so wanted to update the
community about the status.
Regards,
Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir Magnusson Jr. wrote:
> I worked on the some of the legal aspects with Eduardo, so going to
> jump in here.
>
> On Oct 13, 2004, at 3:59 PM, Berin Lautenbach wrote:
>
>> Neeraj Bajaj wrote:
>>
>>> Hello All,
>>> I was wondering when can we start merging the JAXP 1.3 sources ?
>>> Merging the code in branch/review/testing/committing to main trunk
>>> would take time so at least from my side i would like to see this
>>> work started as early as possible say from tomorrow. What is the
>>> general procedure ? Is there any formality that needs to be
>>> completed first ? What is the opinion of
>>> (Xml-commons/Xerces/Xalan) committers ?
>>
>>
>> I'm assuming that this is something that XML-Commons/Xerces/Xalan
>> wish to do?
>>
>> I've CCd general@incubator as well, as I'd like Noel's opinion, but
>> my feeling is that *if* the Xerces/Xalan and/or XML-Commons
>> community want this code to be imported (and it sounds like they do
>> - but I'd like to see that formalised), then the community side is
>> already there.
>>
>> If that's the case, then I don't think we need to go through the
>> full incubation process (Noel - thoughts appreciated!) - we only
>> need a code grant from Sun (we can't take something into our
>> repository until we are sure we have appropriate legal rights to do
>> so) + someone needs to fill out the incubation docs to show that
>> everything is AOK. I'm happy to help out with the latter part.
>
>
> This is an update to the existing code that is already there.
>
> It is, I suppose, a new grant of software to an existing community,
> so I think that what we need is the grant documentation from Sun*,
> have that entered into the incubator, and move from there.
Code grant details can be found at :
http://www.apache.org/licenses/#grants
I checked on this one, This work involves legal and is being worked with
legal now.
I guess this process would take some time so wanted to update the
community about the status.
Regards,
Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir Magnusson Jr. wrote:
> I worked on the some of the legal aspects with Eduardo, so going to
> jump in here.
>
> On Oct 13, 2004, at 3:59 PM, Berin Lautenbach wrote:
>
>> Neeraj Bajaj wrote:
>>
>>> Hello All,
>>> I was wondering when can we start merging the JAXP 1.3 sources ?
>>> Merging the code in branch/review/testing/committing to main trunk
>>> would take time so at least from my side i would like to see this
>>> work started as early as possible say from tomorrow. What is the
>>> general procedure ? Is there any formality that needs to be
>>> completed first ? What is the opinion of
>>> (Xml-commons/Xerces/Xalan) committers ?
>>
>>
>> I'm assuming that this is something that XML-Commons/Xerces/Xalan
>> wish to do?
>>
>> I've CCd general@incubator as well, as I'd like Noel's opinion, but
>> my feeling is that *if* the Xerces/Xalan and/or XML-Commons
>> community want this code to be imported (and it sounds like they do
>> - but I'd like to see that formalised), then the community side is
>> already there.
>>
>> If that's the case, then I don't think we need to go through the
>> full incubation process (Noel - thoughts appreciated!) - we only
>> need a code grant from Sun (we can't take something into our
>> repository until we are sure we have appropriate legal rights to do
>> so) + someone needs to fill out the incubation docs to show that
>> everything is AOK. I'm happy to help out with the latter part.
>
>
> This is an update to the existing code that is already there.
>
> It is, I suppose, a new grant of software to an existing community,
> so I think that what we need is the grant documentation from Sun*,
> have that entered into the incubator, and move from there.
Code grant details can be found at :
http://www.apache.org/licenses/#grants
I checked on this one, This work involves legal and is being worked with
legal now.
I guess this process would take some time so wanted to update the
community about the status.
Regards,
Neeraj
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Geir Magnusson Jr. wrote:
> I worked on the some of the legal aspects with Eduardo, so going to
> jump in here.
>
> On Oct 13, 2004, at 3:59 PM, Berin Lautenbach wrote:
>
>> Neeraj Bajaj wrote:
>>
>>> Hello All,
>>> I was wondering when can we start merging the JAXP 1.3 sources ?
>>> Merging the code in branch/review/testing/committing to main trunk
>>> would take time so at least from my side i would like to see this
>>> work started as early as possible say from tomorrow. What is the
>>> general procedure ? Is there any formality that needs to be
>>> completed first ? What is the opinion of
>>> (Xml-commons/Xerces/Xalan) committers ?
>>
>>
>> I'm assuming that this is something that XML-Commons/Xerces/Xalan
>> wish to do?
>>
>> I've CCd general@incubator as well, as I'd like Noel's opinion, but
>> my feeling is that *if* the Xerces/Xalan and/or XML-Commons
>> community want this code to be imported (and it sounds like they do
>> - but I'd like to see that formalised), then the community side is
>> already there.
>>
>> If that's the case, then I don't think we need to go through the
>> full incubation process (Noel - thoughts appreciated!) - we only
>> need a code grant from Sun (we can't take something into our
>> repository until we are sure we have appropriate legal rights to do
>> so) + someone needs to fill out the incubation docs to show that
>> everything is AOK. I'm happy to help out with the latter part.
>
>
> This is an update to the existing code that is already there.
>
> It is, I suppose, a new grant of software to an existing community,
> so I think that what we need is the grant documentation from Sun*,
> have that entered into the incubator, and move from there.
Code grant details can be found at :
http://www.apache.org/licenses/#grants
I checked on this one, This work involves legal and is being worked with
legal now.
I guess this process would take some time so wanted to update the
community about the status.
Regards,
Neeraj
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
I worked on the some of the legal aspects with Eduardo, so going to
jump in here.
On Oct 13, 2004, at 3:59 PM, Berin Lautenbach wrote:
> Neeraj Bajaj wrote:
>> Hello All,
>> I was wondering when can we start merging the JAXP 1.3 sources ?
>> Merging the code in branch/review/testing/committing to main trunk
>> would take time so at least from my side i would like to see this
>> work started as early as possible say from tomorrow. What is the
>> general procedure ? Is there any formality that needs to be completed
>> first ? What is the opinion of
>> (Xml-commons/Xerces/Xalan) committers ?
>
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
>
> I've CCd general@incubator as well, as I'd like Noel's opinion, but my
> feeling is that *if* the Xerces/Xalan and/or XML-Commons community
> want this code to be imported (and it sounds like they do - but I'd
> like to see that formalised), then the community side is already
> there.
>
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a
> code grant from Sun (we can't take something into our repository until
> we are sure we have appropriate legal rights to do so) + someone needs
> to fill out the incubation docs to show that everything is AOK. I'm
> happy to help out with the latter part.
This is an update to the existing code that is already there.
It is, I suppose, a new grant of software to an existing community, so
I think that what we need is the grant documentation from Sun*, have
that entered into the incubator, and move from there.
geir
*The current grant is said to be incompatible with AL2. There are
multiple things being held up by a clear grant process. We'll try to
fix this ASAP. Given the broad distribution of this note, I'll leave
it at that :)
>
> Code grant details can be found at :
>
> http://www.apache.org/licenses/#grants
>
>> As the sources would be put in a branch so it won't affect normal
>> development but it would be good if we can restrict
>> large chunk of changes to the main trunk and fix only critical
>> changes. It would help merging the changes back to main
>> trunk. What do others think ?
>> Thanks,
>> Neeraj
>> Neeraj Bajaj wrote:
>>>
>>>
>>> Ramesh Mandava wrote:
>>>
>>>>>
>>>>>
>>>>> - Both Elliotte's and Clay's questions below are important. If
>>>>> someone
>>>>> familiar with the code could comment on: For either the main
>>>>> trunk, or
>>>>> a temporary working branch for integration:
>>>>>
>>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>>
>>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>>> sources should run on other JVMs as well.
>>>>
>>>>>
>>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>>
>>>>
>>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources
>>>> on Sun JVM. But as there is no Sun JVM specific codem these
>>>> sources should work on other JVMs without modification ( we have to
>>>> try it out though :-) ).
>>>
>>>
>>>
>>> Right. This hasn't been tried but i don't see any reason why it
>>> shouldn't work on any other JVM as there isn't any Sun JVM specific
>>> code.
>>>
>>> In other mail i have suggested that active Xerces/Xalan committers
>>> can try this before committin on main truck as the plan is to put
>>> the code
>>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>>> xml-commons main trunk but i am totally fine with creating a branch
>>> first to test
>>> the compatibility with other JVM.
>>>
>>> Neeraj
>>>
>>>>
>>>>
>>>>>
>>>>> We need to *clearly* document which versions this stuff works on,
>>>>> and
>>>>> should conditionally compile or something if it won't compile on at
>>>>> least 1.3
>>>>
>>>>
>>>>
>>>> Right now we face compilation problems in couple of file with J2SE
>>>> 1.3, but these should be worked around though. We can atleast have
>>>> a switch to achieve the requirement of compiling on J2SE 1.3.
>>>>
>>>>> (since we still have a lot of older JDK version users here).
>>>>>
>>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>>> both recent Sun and IBM JVMs at least before we put this on the
>>>>> main
>>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>>
>>>>
>>>>
>>>>
>>>> I agree.
>>>>
>>>> Regards
>>>> -Ramesh
>>>>
>>>>> (anyone still
>>>>> working on kaffe? 8-)
>>>>>
>>>>
>>>>
>>>>>
>>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>>
>>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>>
>>>>>>> Are these APIs and implementation thereof independent of Java
>>>>>>> 1.5? i.e. can they be compiled and used in a Java
>>>>>>> 1.2/1.3/1.4
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> environment?
>>>>>>> If not, could they be backported to work in such environments?
>>>>>>>
>>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>>> ref%3Dnosim
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>>
>>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>>> non-Sun implementation of Java...)?
>>>>>>
>>>>>> Web Maestro Clay
>>>>>>
>>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>>> Sun! Love your logo!
>>>>>> --
>>>>>> Clay Leeds - <cl...@medata.com>
>>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> =====
>>>>> - Shane
>>>>>
>>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> --
>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Berin Lautenbach wrote:
> Neeraj Bajaj wrote:
>
>> Hello All,
>>
>> I was wondering when can we start merging the JAXP 1.3 sources ?
>> Merging the code in branch/review/testing/committing to main trunk
>> would take time so at least from my side i would like to see this
>> work started as early as possible say from tomorrow. What is the
>> general procedure ? Is there any formality that needs to be completed
>> first ? What is the opinion of
>> (Xml-commons/Xerces/Xalan) committers ?
>
>
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
>
> I've CCd general@incubator as well, as I'd like Noel's opinion, but my
> feeling is that *if* the Xerces/Xalan and/or XML-Commons community
> want this code to be imported (and it sounds like they do - but I'd
> like to see that formalised), then the community side is already there.
From the response so far it seems that there is general acceptance and
community wants this code.
>
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a
> code grant from Sun (we can't take something into our repository until
> we are sure we have appropriate legal rights to do so) + someone needs
> to fill out the incubation docs to show that everything is AOK.
I believe legal aspect was cleared but i am not sure if some form or
document has been filled. Eduardo will be the right person to comment
on this issue.
Thanks,
Neeraj
> I'm happy to help out with the latter part.
>
> Code grant details can be found at :
>
> http://www.apache.org/licenses/#grants
>
>>
>> As the sources would be put in a branch so it won't affect normal
>> development but it would be good if we can restrict
>> large chunk of changes to the main trunk and fix only critical
>> changes. It would help merging the changes back to main
>> trunk. What do others think ?
>>
>> Thanks,
>> Neeraj
>>
>>
>> Neeraj Bajaj wrote:
>>
>>>
>>>
>>> Ramesh Mandava wrote:
>>>
>>>>>
>>>>>
>>>>> - Both Elliotte's and Clay's questions below are important. If
>>>>> someone
>>>>> familiar with the code could comment on: For either the main
>>>>> trunk, or
>>>>> a temporary working branch for integration:
>>>>>
>>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>>
>>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>>> sources should run on other JVMs as well.
>>>>
>>>>>
>>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>>
>>>>
>>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources
>>>> on Sun JVM. But as there is no Sun JVM specific codem these
>>>> sources should work on other JVMs without modification ( we have to
>>>> try it out though :-) ).
>>>
>>>
>>>
>>>
>>> Right. This hasn't been tried but i don't see any reason why it
>>> shouldn't work on any other JVM as there isn't any Sun JVM specific
>>> code.
>>>
>>> In other mail i have suggested that active Xerces/Xalan committers
>>> can try this before committin on main truck as the plan is to put
>>> the code
>>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>>> xml-commons main trunk but i am totally fine with creating a branch
>>> first to test
>>> the compatibility with other JVM.
>>>
>>> Neeraj
>>>
>>>>
>>>>
>>>>>
>>>>> We need to *clearly* document which versions this stuff works on, and
>>>>> should conditionally compile or something if it won't compile on at
>>>>> least 1.3
>>>>
>>>>
>>>>
>>>>
>>>> Right now we face compilation problems in couple of file with J2SE
>>>> 1.3, but these should be worked around though. We can atleast have
>>>> a switch to achieve the requirement of compiling on J2SE 1.3.
>>>>
>>>>> (since we still have a lot of older JDK version users here).
>>>>>
>>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>>> both recent Sun and IBM JVMs at least before we put this on the main
>>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> I agree.
>>>>
>>>> Regards
>>>> -Ramesh
>>>>
>>>>> (anyone still
>>>>> working on kaffe? 8-)
>>>>>
>>>>
>>>>
>>>>>
>>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>>
>>>>>
>>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>>
>>>>>>
>>>>>>> Are these APIs and implementation thereof independent of Java
>>>>>>> 1.5? i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> environment?
>>>>>>
>>>>>>> If not, could they be backported to work in such environments?
>>>>>>>
>>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>>> ref%3Dnosim
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>>
>>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>>> non-Sun implementation of Java...)?
>>>>>>
>>>>>> Web Maestro Clay
>>>>>>
>>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>>> Sun! Love your logo!
>>>>>> --
>>>>>> Clay Leeds - <cl...@medata.com>
>>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> =====
>>>>> - Shane
>>>>>
>>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.apache.org
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Berin Lautenbach wrote:
> Neeraj Bajaj wrote:
>
>> Hello All,
>>
>> I was wondering when can we start merging the JAXP 1.3 sources ?
>> Merging the code in branch/review/testing/committing to main trunk
>> would take time so at least from my side i would like to see this
>> work started as early as possible say from tomorrow. What is the
>> general procedure ? Is there any formality that needs to be completed
>> first ? What is the opinion of
>> (Xml-commons/Xerces/Xalan) committers ?
>
>
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
>
> I've CCd general@incubator as well, as I'd like Noel's opinion, but my
> feeling is that *if* the Xerces/Xalan and/or XML-Commons community
> want this code to be imported (and it sounds like they do - but I'd
> like to see that formalised), then the community side is already there.
From the response so far it seems that there is general acceptance and
community wants this code.
>
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a
> code grant from Sun (we can't take something into our repository until
> we are sure we have appropriate legal rights to do so) + someone needs
> to fill out the incubation docs to show that everything is AOK.
I believe legal aspect was cleared but i am not sure if some form or
document has been filled. Eduardo will be the right person to comment
on this issue.
Thanks,
Neeraj
> I'm happy to help out with the latter part.
>
> Code grant details can be found at :
>
> http://www.apache.org/licenses/#grants
>
>>
>> As the sources would be put in a branch so it won't affect normal
>> development but it would be good if we can restrict
>> large chunk of changes to the main trunk and fix only critical
>> changes. It would help merging the changes back to main
>> trunk. What do others think ?
>>
>> Thanks,
>> Neeraj
>>
>>
>> Neeraj Bajaj wrote:
>>
>>>
>>>
>>> Ramesh Mandava wrote:
>>>
>>>>>
>>>>>
>>>>> - Both Elliotte's and Clay's questions below are important. If
>>>>> someone
>>>>> familiar with the code could comment on: For either the main
>>>>> trunk, or
>>>>> a temporary working branch for integration:
>>>>>
>>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>>
>>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>>> sources should run on other JVMs as well.
>>>>
>>>>>
>>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>>
>>>>
>>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources
>>>> on Sun JVM. But as there is no Sun JVM specific codem these
>>>> sources should work on other JVMs without modification ( we have to
>>>> try it out though :-) ).
>>>
>>>
>>>
>>>
>>> Right. This hasn't been tried but i don't see any reason why it
>>> shouldn't work on any other JVM as there isn't any Sun JVM specific
>>> code.
>>>
>>> In other mail i have suggested that active Xerces/Xalan committers
>>> can try this before committin on main truck as the plan is to put
>>> the code
>>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>>> xml-commons main trunk but i am totally fine with creating a branch
>>> first to test
>>> the compatibility with other JVM.
>>>
>>> Neeraj
>>>
>>>>
>>>>
>>>>>
>>>>> We need to *clearly* document which versions this stuff works on, and
>>>>> should conditionally compile or something if it won't compile on at
>>>>> least 1.3
>>>>
>>>>
>>>>
>>>>
>>>> Right now we face compilation problems in couple of file with J2SE
>>>> 1.3, but these should be worked around though. We can atleast have
>>>> a switch to achieve the requirement of compiling on J2SE 1.3.
>>>>
>>>>> (since we still have a lot of older JDK version users here).
>>>>>
>>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>>> both recent Sun and IBM JVMs at least before we put this on the main
>>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> I agree.
>>>>
>>>> Regards
>>>> -Ramesh
>>>>
>>>>> (anyone still
>>>>> working on kaffe? 8-)
>>>>>
>>>>
>>>>
>>>>>
>>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>>
>>>>>
>>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>>
>>>>>>
>>>>>>> Are these APIs and implementation thereof independent of Java
>>>>>>> 1.5? i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> environment?
>>>>>>
>>>>>>> If not, could they be backported to work in such environments?
>>>>>>>
>>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>>> ref%3Dnosim
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>>
>>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>>> non-Sun implementation of Java...)?
>>>>>>
>>>>>> Web Maestro Clay
>>>>>>
>>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>>> Sun! Love your logo!
>>>>>> --
>>>>>> Clay Leeds - <cl...@medata.com>
>>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> =====
>>>>> - Shane
>>>>>
>>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.apache.org
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
I worked on the some of the legal aspects with Eduardo, so going to
jump in here.
On Oct 13, 2004, at 3:59 PM, Berin Lautenbach wrote:
> Neeraj Bajaj wrote:
>> Hello All,
>> I was wondering when can we start merging the JAXP 1.3 sources ?
>> Merging the code in branch/review/testing/committing to main trunk
>> would take time so at least from my side i would like to see this
>> work started as early as possible say from tomorrow. What is the
>> general procedure ? Is there any formality that needs to be completed
>> first ? What is the opinion of
>> (Xml-commons/Xerces/Xalan) committers ?
>
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
>
> I've CCd general@incubator as well, as I'd like Noel's opinion, but my
> feeling is that *if* the Xerces/Xalan and/or XML-Commons community
> want this code to be imported (and it sounds like they do - but I'd
> like to see that formalised), then the community side is already
> there.
>
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a
> code grant from Sun (we can't take something into our repository until
> we are sure we have appropriate legal rights to do so) + someone needs
> to fill out the incubation docs to show that everything is AOK. I'm
> happy to help out with the latter part.
This is an update to the existing code that is already there.
It is, I suppose, a new grant of software to an existing community, so
I think that what we need is the grant documentation from Sun*, have
that entered into the incubator, and move from there.
geir
*The current grant is said to be incompatible with AL2. There are
multiple things being held up by a clear grant process. We'll try to
fix this ASAP. Given the broad distribution of this note, I'll leave
it at that :)
>
> Code grant details can be found at :
>
> http://www.apache.org/licenses/#grants
>
>> As the sources would be put in a branch so it won't affect normal
>> development but it would be good if we can restrict
>> large chunk of changes to the main trunk and fix only critical
>> changes. It would help merging the changes back to main
>> trunk. What do others think ?
>> Thanks,
>> Neeraj
>> Neeraj Bajaj wrote:
>>>
>>>
>>> Ramesh Mandava wrote:
>>>
>>>>>
>>>>>
>>>>> - Both Elliotte's and Clay's questions below are important. If
>>>>> someone
>>>>> familiar with the code could comment on: For either the main
>>>>> trunk, or
>>>>> a temporary working branch for integration:
>>>>>
>>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>>
>>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>>> sources should run on other JVMs as well.
>>>>
>>>>>
>>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>>
>>>>
>>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources
>>>> on Sun JVM. But as there is no Sun JVM specific codem these
>>>> sources should work on other JVMs without modification ( we have to
>>>> try it out though :-) ).
>>>
>>>
>>>
>>> Right. This hasn't been tried but i don't see any reason why it
>>> shouldn't work on any other JVM as there isn't any Sun JVM specific
>>> code.
>>>
>>> In other mail i have suggested that active Xerces/Xalan committers
>>> can try this before committin on main truck as the plan is to put
>>> the code
>>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>>> xml-commons main trunk but i am totally fine with creating a branch
>>> first to test
>>> the compatibility with other JVM.
>>>
>>> Neeraj
>>>
>>>>
>>>>
>>>>>
>>>>> We need to *clearly* document which versions this stuff works on,
>>>>> and
>>>>> should conditionally compile or something if it won't compile on at
>>>>> least 1.3
>>>>
>>>>
>>>>
>>>> Right now we face compilation problems in couple of file with J2SE
>>>> 1.3, but these should be worked around though. We can atleast have
>>>> a switch to achieve the requirement of compiling on J2SE 1.3.
>>>>
>>>>> (since we still have a lot of older JDK version users here).
>>>>>
>>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>>> both recent Sun and IBM JVMs at least before we put this on the
>>>>> main
>>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>>
>>>>
>>>>
>>>>
>>>> I agree.
>>>>
>>>> Regards
>>>> -Ramesh
>>>>
>>>>> (anyone still
>>>>> working on kaffe? 8-)
>>>>>
>>>>
>>>>
>>>>>
>>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>>
>>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>>
>>>>>>> Are these APIs and implementation thereof independent of Java
>>>>>>> 1.5? i.e. can they be compiled and used in a Java
>>>>>>> 1.2/1.3/1.4
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> environment?
>>>>>>> If not, could they be backported to work in such environments?
>>>>>>>
>>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>>> ref%3Dnosim
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>>
>>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>>> non-Sun implementation of Java...)?
>>>>>>
>>>>>> Web Maestro Clay
>>>>>>
>>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>>> Sun! Love your logo!
>>>>>> --
>>>>>> Clay Leeds - <cl...@medata.com>
>>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> =====
>>>>> - Shane
>>>>>
>>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> --
>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
I worked on the some of the legal aspects with Eduardo, so going to
jump in here.
On Oct 13, 2004, at 3:59 PM, Berin Lautenbach wrote:
> Neeraj Bajaj wrote:
>> Hello All,
>> I was wondering when can we start merging the JAXP 1.3 sources ?
>> Merging the code in branch/review/testing/committing to main trunk
>> would take time so at least from my side i would like to see this
>> work started as early as possible say from tomorrow. What is the
>> general procedure ? Is there any formality that needs to be completed
>> first ? What is the opinion of
>> (Xml-commons/Xerces/Xalan) committers ?
>
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
>
> I've CCd general@incubator as well, as I'd like Noel's opinion, but my
> feeling is that *if* the Xerces/Xalan and/or XML-Commons community
> want this code to be imported (and it sounds like they do - but I'd
> like to see that formalised), then the community side is already
> there.
>
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a
> code grant from Sun (we can't take something into our repository until
> we are sure we have appropriate legal rights to do so) + someone needs
> to fill out the incubation docs to show that everything is AOK. I'm
> happy to help out with the latter part.
This is an update to the existing code that is already there.
It is, I suppose, a new grant of software to an existing community, so
I think that what we need is the grant documentation from Sun*, have
that entered into the incubator, and move from there.
geir
*The current grant is said to be incompatible with AL2. There are
multiple things being held up by a clear grant process. We'll try to
fix this ASAP. Given the broad distribution of this note, I'll leave
it at that :)
>
> Code grant details can be found at :
>
> http://www.apache.org/licenses/#grants
>
>> As the sources would be put in a branch so it won't affect normal
>> development but it would be good if we can restrict
>> large chunk of changes to the main trunk and fix only critical
>> changes. It would help merging the changes back to main
>> trunk. What do others think ?
>> Thanks,
>> Neeraj
>> Neeraj Bajaj wrote:
>>>
>>>
>>> Ramesh Mandava wrote:
>>>
>>>>>
>>>>>
>>>>> - Both Elliotte's and Clay's questions below are important. If
>>>>> someone
>>>>> familiar with the code could comment on: For either the main
>>>>> trunk, or
>>>>> a temporary working branch for integration:
>>>>>
>>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>>
>>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>>> sources should run on other JVMs as well.
>>>>
>>>>>
>>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>>
>>>>
>>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources
>>>> on Sun JVM. But as there is no Sun JVM specific codem these
>>>> sources should work on other JVMs without modification ( we have to
>>>> try it out though :-) ).
>>>
>>>
>>>
>>> Right. This hasn't been tried but i don't see any reason why it
>>> shouldn't work on any other JVM as there isn't any Sun JVM specific
>>> code.
>>>
>>> In other mail i have suggested that active Xerces/Xalan committers
>>> can try this before committin on main truck as the plan is to put
>>> the code
>>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>>> xml-commons main trunk but i am totally fine with creating a branch
>>> first to test
>>> the compatibility with other JVM.
>>>
>>> Neeraj
>>>
>>>>
>>>>
>>>>>
>>>>> We need to *clearly* document which versions this stuff works on,
>>>>> and
>>>>> should conditionally compile or something if it won't compile on at
>>>>> least 1.3
>>>>
>>>>
>>>>
>>>> Right now we face compilation problems in couple of file with J2SE
>>>> 1.3, but these should be worked around though. We can atleast have
>>>> a switch to achieve the requirement of compiling on J2SE 1.3.
>>>>
>>>>> (since we still have a lot of older JDK version users here).
>>>>>
>>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>>> both recent Sun and IBM JVMs at least before we put this on the
>>>>> main
>>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>>
>>>>
>>>>
>>>>
>>>> I agree.
>>>>
>>>> Regards
>>>> -Ramesh
>>>>
>>>>> (anyone still
>>>>> working on kaffe? 8-)
>>>>>
>>>>
>>>>
>>>>>
>>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>>
>>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>>
>>>>>>> Are these APIs and implementation thereof independent of Java
>>>>>>> 1.5? i.e. can they be compiled and used in a Java
>>>>>>> 1.2/1.3/1.4
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> environment?
>>>>>>> If not, could they be backported to work in such environments?
>>>>>>>
>>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>>> ref%3Dnosim
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>>
>>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>>> non-Sun implementation of Java...)?
>>>>>>
>>>>>> Web Maestro Clay
>>>>>>
>>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>>> Sun! Love your logo!
>>>>>> --
>>>>>> Clay Leeds - <cl...@medata.com>
>>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> =====
>>>>> - Shane
>>>>>
>>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> --
>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
I worked on the some of the legal aspects with Eduardo, so going to
jump in here.
On Oct 13, 2004, at 3:59 PM, Berin Lautenbach wrote:
> Neeraj Bajaj wrote:
>> Hello All,
>> I was wondering when can we start merging the JAXP 1.3 sources ?
>> Merging the code in branch/review/testing/committing to main trunk
>> would take time so at least from my side i would like to see this
>> work started as early as possible say from tomorrow. What is the
>> general procedure ? Is there any formality that needs to be completed
>> first ? What is the opinion of
>> (Xml-commons/Xerces/Xalan) committers ?
>
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
>
> I've CCd general@incubator as well, as I'd like Noel's opinion, but my
> feeling is that *if* the Xerces/Xalan and/or XML-Commons community
> want this code to be imported (and it sounds like they do - but I'd
> like to see that formalised), then the community side is already
> there.
>
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a
> code grant from Sun (we can't take something into our repository until
> we are sure we have appropriate legal rights to do so) + someone needs
> to fill out the incubation docs to show that everything is AOK. I'm
> happy to help out with the latter part.
This is an update to the existing code that is already there.
It is, I suppose, a new grant of software to an existing community, so
I think that what we need is the grant documentation from Sun*, have
that entered into the incubator, and move from there.
geir
*The current grant is said to be incompatible with AL2. There are
multiple things being held up by a clear grant process. We'll try to
fix this ASAP. Given the broad distribution of this note, I'll leave
it at that :)
>
> Code grant details can be found at :
>
> http://www.apache.org/licenses/#grants
>
>> As the sources would be put in a branch so it won't affect normal
>> development but it would be good if we can restrict
>> large chunk of changes to the main trunk and fix only critical
>> changes. It would help merging the changes back to main
>> trunk. What do others think ?
>> Thanks,
>> Neeraj
>> Neeraj Bajaj wrote:
>>>
>>>
>>> Ramesh Mandava wrote:
>>>
>>>>>
>>>>>
>>>>> - Both Elliotte's and Clay's questions below are important. If
>>>>> someone
>>>>> familiar with the code could comment on: For either the main
>>>>> trunk, or
>>>>> a temporary working branch for integration:
>>>>>
>>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>>
>>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>>> sources should run on other JVMs as well.
>>>>
>>>>>
>>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>>
>>>>
>>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources
>>>> on Sun JVM. But as there is no Sun JVM specific codem these
>>>> sources should work on other JVMs without modification ( we have to
>>>> try it out though :-) ).
>>>
>>>
>>>
>>> Right. This hasn't been tried but i don't see any reason why it
>>> shouldn't work on any other JVM as there isn't any Sun JVM specific
>>> code.
>>>
>>> In other mail i have suggested that active Xerces/Xalan committers
>>> can try this before committin on main truck as the plan is to put
>>> the code
>>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>>> xml-commons main trunk but i am totally fine with creating a branch
>>> first to test
>>> the compatibility with other JVM.
>>>
>>> Neeraj
>>>
>>>>
>>>>
>>>>>
>>>>> We need to *clearly* document which versions this stuff works on,
>>>>> and
>>>>> should conditionally compile or something if it won't compile on at
>>>>> least 1.3
>>>>
>>>>
>>>>
>>>> Right now we face compilation problems in couple of file with J2SE
>>>> 1.3, but these should be worked around though. We can atleast have
>>>> a switch to achieve the requirement of compiling on J2SE 1.3.
>>>>
>>>>> (since we still have a lot of older JDK version users here).
>>>>>
>>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>>> both recent Sun and IBM JVMs at least before we put this on the
>>>>> main
>>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>>
>>>>
>>>>
>>>>
>>>> I agree.
>>>>
>>>> Regards
>>>> -Ramesh
>>>>
>>>>> (anyone still
>>>>> working on kaffe? 8-)
>>>>>
>>>>
>>>>
>>>>>
>>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>>
>>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>>
>>>>>>> Are these APIs and implementation thereof independent of Java
>>>>>>> 1.5? i.e. can they be compiled and used in a Java
>>>>>>> 1.2/1.3/1.4
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> environment?
>>>>>>> If not, could they be backported to work in such environments?
>>>>>>>
>>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>>> ref%3Dnosim
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>>
>>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>>> non-Sun implementation of Java...)?
>>>>>>
>>>>>> Web Maestro Clay
>>>>>>
>>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>>> Sun! Love your logo!
>>>>>> --
>>>>>> Clay Leeds - <cl...@medata.com>
>>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> =====
>>>>> - Shane
>>>>>
>>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> --
>>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: general-help@xml.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: Donation of JAXP 1.3 Sources to Apache
Posted by "Noel J. Bergman" <no...@devtech.com>.
Berin,
Judging from yours, Geir's and David's messages, this sounds like mostly a
matter of clearing the IP (use the template), but is otherwise eagerly
awaited by a community already working with its precursor.
As for where it goes, I think that can be left to the community working with
the code. Of course, the sooner that we switch to SVN ... ;-)
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi all,
Berin Lautenbach <be...@wingsofhermes.org> wrote on 10/13/2004 06:59:22
PM:
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
Here's a +1 from someone who's committed to Xerces-J and xml-commons. If
either project didn't want to move up to the latest standard API's, that
sure would be an interesting situation. :)
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a code
> grant from Sun (we can't take something into our repository until we are
> sure we have appropriate legal rights to do so) + someone needs to fill
> out the incubation docs to show that everything is AOK.
As I've argued before, it seems to me that this is a case where some
Apache committers have simply gone away for a while, developed some code
based on the Apache projects to which they have commit privileges, and now
have reached a point where they can commit the code back. It's not a case
where a new component is being added; simply where a rather large update
is being undertaken.
But I'm no lawyer, so I have no allusions that this argument will actually
count for anything. :) But given the apparent unanimity in the
communities about this being a good thing, and the fact this thread's been
pretty quiet the last couple of days, it would be nice to get some status
on when the granting/incubating formalities might be done with.
Cheers!
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi all,
Berin Lautenbach <be...@wingsofhermes.org> wrote on 10/13/2004 06:59:22
PM:
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
Here's a +1 from someone who's committed to Xerces-J and xml-commons. If
either project didn't want to move up to the latest standard API's, that
sure would be an interesting situation. :)
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a code
> grant from Sun (we can't take something into our repository until we are
> sure we have appropriate legal rights to do so) + someone needs to fill
> out the incubation docs to show that everything is AOK.
As I've argued before, it seems to me that this is a case where some
Apache committers have simply gone away for a while, developed some code
based on the Apache projects to which they have commit privileges, and now
have reached a point where they can commit the code back. It's not a case
where a new component is being added; simply where a rather large update
is being undertaken.
But I'm no lawyer, so I have no allusions that this argument will actually
count for anything. :) But given the apparent unanimity in the
communities about this being a good thing, and the fact this thread's been
pretty quiet the last couple of days, it would be nice to get some status
on when the granting/incubating formalities might be done with.
Cheers!
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
RE: Donation of JAXP 1.3 Sources to Apache
Posted by "Noel J. Bergman" <no...@devtech.com>.
Berin,
Judging from yours, Geir's and David's messages, this sounds like mostly a
matter of clearing the IP (use the template), but is otherwise eagerly
awaited by a community already working with its precursor.
As for where it goes, I think that can be left to the community working with
the code. Of course, the sooner that we switch to SVN ... ;-)
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
RE: Donation of JAXP 1.3 Sources to Apache
Posted by "Noel J. Bergman" <no...@devtech.com>.
Berin,
Judging from yours, Geir's and David's messages, this sounds like mostly a
matter of clearing the IP (use the template), but is otherwise eagerly
awaited by a community already working with its precursor.
As for where it goes, I think that can be left to the community working with
the code. Of course, the sooner that we switch to SVN ... ;-)
--- Noel
RE: Donation of JAXP 1.3 Sources to Apache
Posted by "Noel J. Bergman" <no...@devtech.com>.
Berin,
Judging from yours, Geir's and David's messages, this sounds like mostly a
matter of clearing the IP (use the template), but is otherwise eagerly
awaited by a community already working with its precursor.
As for where it goes, I think that can be left to the community working with
the code. Of course, the sooner that we switch to SVN ... ;-)
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi all,
Berin Lautenbach <be...@wingsofhermes.org> wrote on 10/13/2004 06:59:22
PM:
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
Here's a +1 from someone who's committed to Xerces-J and xml-commons. If
either project didn't want to move up to the latest standard API's, that
sure would be an interesting situation. :)
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a code
> grant from Sun (we can't take something into our repository until we are
> sure we have appropriate legal rights to do so) + someone needs to fill
> out the incubation docs to show that everything is AOK.
As I've argued before, it seems to me that this is a case where some
Apache committers have simply gone away for a while, developed some code
based on the Apache projects to which they have commit privileges, and now
have reached a point where they can commit the code back. It's not a case
where a new component is being added; simply where a rather large update
is being undertaken.
But I'm no lawyer, so I have no allusions that this argument will actually
count for anything. :) But given the apparent unanimity in the
communities about this being a good thing, and the fact this thread's been
pretty quiet the last couple of days, it would be nice to get some status
on when the granting/incubating formalities might be done with.
Cheers!
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi all,
Berin Lautenbach <be...@wingsofhermes.org> wrote on 10/13/2004 06:59:22
PM:
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
Here's a +1 from someone who's committed to Xerces-J and xml-commons. If
either project didn't want to move up to the latest standard API's, that
sure would be an interesting situation. :)
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a code
> grant from Sun (we can't take something into our repository until we are
> sure we have appropriate legal rights to do so) + someone needs to fill
> out the incubation docs to show that everything is AOK.
As I've argued before, it seems to me that this is a case where some
Apache committers have simply gone away for a while, developed some code
based on the Apache projects to which they have commit privileges, and now
have reached a point where they can commit the code back. It's not a case
where a new component is being added; simply where a rather large update
is being undertaken.
But I'm no lawyer, so I have no allusions that this argument will actually
count for anything. :) But given the apparent unanimity in the
communities about this being a good thing, and the fact this thread's been
pretty quiet the last couple of days, it would be nice to get some status
on when the granting/incubating formalities might be done with.
Cheers!
Neil
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi all,
Berin Lautenbach <be...@wingsofhermes.org> wrote on 10/13/2004 06:59:22
PM:
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
Here's a +1 from someone who's committed to Xerces-J and xml-commons. If
either project didn't want to move up to the latest standard API's, that
sure would be an interesting situation. :)
> If that's the case, then I don't think we need to go through the full
> incubation process (Noel - thoughts appreciated!) - we only need a code
> grant from Sun (we can't take something into our repository until we are
> sure we have appropriate legal rights to do so) + someone needs to fill
> out the incubation docs to show that everything is AOK.
As I've argued before, it seems to me that this is a case where some
Apache committers have simply gone away for a while, developed some code
based on the Apache projects to which they have commit privileges, and now
have reached a point where they can commit the code back. It's not a case
where a new component is being added; simply where a rather large update
is being undertaken.
But I'm no lawyer, so I have no allusions that this argument will actually
count for anything. :) But given the apparent unanimity in the
communities about this being a good thing, and the fact this thread's been
pretty quiet the last couple of days, it would be nice to get some status
on when the granting/incubating formalities might be done with.
Cheers!
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Berin Lautenbach <be...@wingsofhermes.org>.
Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow. What is the general
> procedure ? Is there any formality that needs to be completed first ?
> What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
to do?
I've CCd general@incubator as well, as I'd like Noel's opinion, but my
feeling is that *if* the Xerces/Xalan and/or XML-Commons community want
this code to be imported (and it sounds like they do - but I'd like to
see that formalised), then the community side is already there.
If that's the case, then I don't think we need to go through the full
incubation process (Noel - thoughts appreciated!) - we only need a code
grant from Sun (we can't take something into our repository until we are
sure we have appropriate legal rights to do so) + someone needs to fill
out the incubation docs to show that everything is AOK. I'm happy to
help out with the latter part.
Code grant details can be found at :
http://www.apache.org/licenses/#grants
>
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
>
> Thanks,
> Neeraj
>
>
> Neeraj Bajaj wrote:
>
>>
>>
>> Ramesh Mandava wrote:
>>
>>>>
>>>>
>>>> - Both Elliotte's and Clay's questions below are important. If someone
>>>> familiar with the code could comment on: For either the main trunk, or
>>>> a temporary working branch for integration:
>>>>
>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>
>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>> sources should run on other JVMs as well.
>>>
>>>>
>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>
>>>
>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
>>> Sun JVM. But as there is no Sun JVM specific codem these sources
>>> should work on other JVMs without modification ( we have to try it
>>> out though :-) ).
>>
>>
>>
>> Right. This hasn't been tried but i don't see any reason why it
>> shouldn't work on any other JVM as there isn't any Sun JVM specific code.
>>
>> In other mail i have suggested that active Xerces/Xalan committers can
>> try this before committin on main truck as the plan is to put the code
>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>> xml-commons main trunk but i am totally fine with creating a branch
>> first to test
>> the compatibility with other JVM.
>>
>> Neeraj
>>
>>>
>>>
>>>>
>>>> We need to *clearly* document which versions this stuff works on, and
>>>> should conditionally compile or something if it won't compile on at
>>>> least 1.3
>>>
>>>
>>>
>>> Right now we face compilation problems in couple of file with J2SE
>>> 1.3, but these should be worked around though. We can atleast have a
>>> switch to achieve the requirement of compiling on J2SE 1.3.
>>>
>>>> (since we still have a lot of older JDK version users here).
>>>>
>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>> both recent Sun and IBM JVMs at least before we put this on the main
>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>
>>>
>>>
>>>
>>> I agree.
>>>
>>> Regards
>>> -Ramesh
>>>
>>>> (anyone still
>>>> working on kaffe? 8-)
>>>>
>>>
>>>
>>>>
>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>
>>>>
>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>
>>>>>
>>>>>> Are these APIs and implementation thereof independent of Java 1.5?
>>>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> environment?
>>>>>
>>>>>> If not, could they be backported to work in such environments?
>>>>>>
>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>> ref%3Dnosim
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>
>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>> non-Sun implementation of Java...)?
>>>>>
>>>>> Web Maestro Clay
>>>>>
>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>> Sun! Love your logo!
>>>>> --
>>>>> Clay Leeds - <cl...@medata.com>
>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> =====
>>>> - Shane
>>>>
>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Berin Lautenbach <be...@wingsofhermes.org>.
Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow. What is the general
> procedure ? Is there any formality that needs to be completed first ?
> What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
to do?
I've CCd general@incubator as well, as I'd like Noel's opinion, but my
feeling is that *if* the Xerces/Xalan and/or XML-Commons community want
this code to be imported (and it sounds like they do - but I'd like to
see that formalised), then the community side is already there.
If that's the case, then I don't think we need to go through the full
incubation process (Noel - thoughts appreciated!) - we only need a code
grant from Sun (we can't take something into our repository until we are
sure we have appropriate legal rights to do so) + someone needs to fill
out the incubation docs to show that everything is AOK. I'm happy to
help out with the latter part.
Code grant details can be found at :
http://www.apache.org/licenses/#grants
>
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
>
> Thanks,
> Neeraj
>
>
> Neeraj Bajaj wrote:
>
>>
>>
>> Ramesh Mandava wrote:
>>
>>>>
>>>>
>>>> - Both Elliotte's and Clay's questions below are important. If someone
>>>> familiar with the code could comment on: For either the main trunk, or
>>>> a temporary working branch for integration:
>>>>
>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>
>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>> sources should run on other JVMs as well.
>>>
>>>>
>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>
>>>
>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
>>> Sun JVM. But as there is no Sun JVM specific codem these sources
>>> should work on other JVMs without modification ( we have to try it
>>> out though :-) ).
>>
>>
>>
>> Right. This hasn't been tried but i don't see any reason why it
>> shouldn't work on any other JVM as there isn't any Sun JVM specific code.
>>
>> In other mail i have suggested that active Xerces/Xalan committers can
>> try this before committin on main truck as the plan is to put the code
>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>> xml-commons main trunk but i am totally fine with creating a branch
>> first to test
>> the compatibility with other JVM.
>>
>> Neeraj
>>
>>>
>>>
>>>>
>>>> We need to *clearly* document which versions this stuff works on, and
>>>> should conditionally compile or something if it won't compile on at
>>>> least 1.3
>>>
>>>
>>>
>>> Right now we face compilation problems in couple of file with J2SE
>>> 1.3, but these should be worked around though. We can atleast have a
>>> switch to achieve the requirement of compiling on J2SE 1.3.
>>>
>>>> (since we still have a lot of older JDK version users here).
>>>>
>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>> both recent Sun and IBM JVMs at least before we put this on the main
>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>
>>>
>>>
>>>
>>> I agree.
>>>
>>> Regards
>>> -Ramesh
>>>
>>>> (anyone still
>>>> working on kaffe? 8-)
>>>>
>>>
>>>
>>>>
>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>
>>>>
>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>
>>>>>
>>>>>> Are these APIs and implementation thereof independent of Java 1.5?
>>>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> environment?
>>>>>
>>>>>> If not, could they be backported to work in such environments?
>>>>>>
>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>> ref%3Dnosim
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>
>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>> non-Sun implementation of Java...)?
>>>>>
>>>>> Web Maestro Clay
>>>>>
>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>> Sun! Love your logo!
>>>>> --
>>>>> Clay Leeds - <cl...@medata.com>
>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> =====
>>>> - Shane
>>>>
>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Berin Lautenbach <be...@wingsofhermes.org>.
Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow. What is the general
> procedure ? Is there any formality that needs to be completed first ?
> What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
to do?
I've CCd general@incubator as well, as I'd like Noel's opinion, but my
feeling is that *if* the Xerces/Xalan and/or XML-Commons community want
this code to be imported (and it sounds like they do - but I'd like to
see that formalised), then the community side is already there.
If that's the case, then I don't think we need to go through the full
incubation process (Noel - thoughts appreciated!) - we only need a code
grant from Sun (we can't take something into our repository until we are
sure we have appropriate legal rights to do so) + someone needs to fill
out the incubation docs to show that everything is AOK. I'm happy to
help out with the latter part.
Code grant details can be found at :
http://www.apache.org/licenses/#grants
>
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
>
> Thanks,
> Neeraj
>
>
> Neeraj Bajaj wrote:
>
>>
>>
>> Ramesh Mandava wrote:
>>
>>>>
>>>>
>>>> - Both Elliotte's and Clay's questions below are important. If someone
>>>> familiar with the code could comment on: For either the main trunk, or
>>>> a temporary working branch for integration:
>>>>
>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>
>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>> sources should run on other JVMs as well.
>>>
>>>>
>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>
>>>
>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
>>> Sun JVM. But as there is no Sun JVM specific codem these sources
>>> should work on other JVMs without modification ( we have to try it
>>> out though :-) ).
>>
>>
>>
>> Right. This hasn't been tried but i don't see any reason why it
>> shouldn't work on any other JVM as there isn't any Sun JVM specific code.
>>
>> In other mail i have suggested that active Xerces/Xalan committers can
>> try this before committin on main truck as the plan is to put the code
>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>> xml-commons main trunk but i am totally fine with creating a branch
>> first to test
>> the compatibility with other JVM.
>>
>> Neeraj
>>
>>>
>>>
>>>>
>>>> We need to *clearly* document which versions this stuff works on, and
>>>> should conditionally compile or something if it won't compile on at
>>>> least 1.3
>>>
>>>
>>>
>>> Right now we face compilation problems in couple of file with J2SE
>>> 1.3, but these should be worked around though. We can atleast have a
>>> switch to achieve the requirement of compiling on J2SE 1.3.
>>>
>>>> (since we still have a lot of older JDK version users here).
>>>>
>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>> both recent Sun and IBM JVMs at least before we put this on the main
>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>
>>>
>>>
>>>
>>> I agree.
>>>
>>> Regards
>>> -Ramesh
>>>
>>>> (anyone still
>>>> working on kaffe? 8-)
>>>>
>>>
>>>
>>>>
>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>
>>>>
>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>
>>>>>
>>>>>> Are these APIs and implementation thereof independent of Java 1.5?
>>>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> environment?
>>>>>
>>>>>> If not, could they be backported to work in such environments?
>>>>>>
>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>> ref%3Dnosim
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>
>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>> non-Sun implementation of Java...)?
>>>>>
>>>>> Web Maestro Clay
>>>>>
>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>> Sun! Love your logo!
>>>>> --
>>>>> Clay Leeds - <cl...@medata.com>
>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> =====
>>>> - Shane
>>>>
>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
>
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by David Crossley <cr...@apache.org>.
(I notice that some individuals got dropped from the
original posting. Are they on the *.apache mailing lists?)
Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow.
> What is the general procedure ? Is there any formality that needs to be
> completed first ?
Others have mentioned the legal side, so my comments
are about code and community issues.
> What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I am an xml-commons committer and user of this stuff
in Apache Cocoon and Apache Forrest. So i am looking
forward to more people working at Xml-commons to
provide reliability.
One thing that we must have this time around, is a
version number on the xml-apis.jar filename. [1]
I suppose that is an Xml-commons "build" issue.
By the way, that build system is seriously in need
of improvement, but it gets us by.
You would have noticed that there is very little
activity with the xml-commons CVS, so it would be
fine to work on trunk.
At some stage soon, we need to move xml-commons to SVN.
Hopefully that will not disrupt progress.
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
I am a little confused about your planned procedure.
Are you suggesting to add a copy of the core code
to Xerces/Xalan then moving it to Xml-commons later?
It worries me that we end up with copies.
On related matters, there is past discussion, e.g.
[1] http://marc.theaimsgroup.com/?t=106739445900002
--
David Crossley
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by David Crossley <cr...@apache.org>.
(I notice that some individuals got dropped from the
original posting. Are they on the *.apache mailing lists?)
Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow.
> What is the general procedure ? Is there any formality that needs to be
> completed first ?
Others have mentioned the legal side, so my comments
are about code and community issues.
> What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I am an xml-commons committer and user of this stuff
in Apache Cocoon and Apache Forrest. So i am looking
forward to more people working at Xml-commons to
provide reliability.
One thing that we must have this time around, is a
version number on the xml-apis.jar filename. [1]
I suppose that is an Xml-commons "build" issue.
By the way, that build system is seriously in need
of improvement, but it gets us by.
You would have noticed that there is very little
activity with the xml-commons CVS, so it would be
fine to work on trunk.
At some stage soon, we need to move xml-commons to SVN.
Hopefully that will not disrupt progress.
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
I am a little confused about your planned procedure.
Are you suggesting to add a copy of the core code
to Xerces/Xalan then moving it to Xml-commons later?
It worries me that we end up with copies.
On related matters, there is past discussion, e.g.
[1] http://marc.theaimsgroup.com/?t=106739445900002
--
David Crossley
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Berin Lautenbach <be...@wingsofhermes.org>.
Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow. What is the general
> procedure ? Is there any formality that needs to be completed first ?
> What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
to do?
I've CCd general@incubator as well, as I'd like Noel's opinion, but my
feeling is that *if* the Xerces/Xalan and/or XML-Commons community want
this code to be imported (and it sounds like they do - but I'd like to
see that formalised), then the community side is already there.
If that's the case, then I don't think we need to go through the full
incubation process (Noel - thoughts appreciated!) - we only need a code
grant from Sun (we can't take something into our repository until we are
sure we have appropriate legal rights to do so) + someone needs to fill
out the incubation docs to show that everything is AOK. I'm happy to
help out with the latter part.
Code grant details can be found at :
http://www.apache.org/licenses/#grants
>
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
>
> Thanks,
> Neeraj
>
>
> Neeraj Bajaj wrote:
>
>>
>>
>> Ramesh Mandava wrote:
>>
>>>>
>>>>
>>>> - Both Elliotte's and Clay's questions below are important. If someone
>>>> familiar with the code could comment on: For either the main trunk, or
>>>> a temporary working branch for integration:
>>>>
>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>
>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>> sources should run on other JVMs as well.
>>>
>>>>
>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>
>>>
>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
>>> Sun JVM. But as there is no Sun JVM specific codem these sources
>>> should work on other JVMs without modification ( we have to try it
>>> out though :-) ).
>>
>>
>>
>> Right. This hasn't been tried but i don't see any reason why it
>> shouldn't work on any other JVM as there isn't any Sun JVM specific code.
>>
>> In other mail i have suggested that active Xerces/Xalan committers can
>> try this before committin on main truck as the plan is to put the code
>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>> xml-commons main trunk but i am totally fine with creating a branch
>> first to test
>> the compatibility with other JVM.
>>
>> Neeraj
>>
>>>
>>>
>>>>
>>>> We need to *clearly* document which versions this stuff works on, and
>>>> should conditionally compile or something if it won't compile on at
>>>> least 1.3
>>>
>>>
>>>
>>> Right now we face compilation problems in couple of file with J2SE
>>> 1.3, but these should be worked around though. We can atleast have a
>>> switch to achieve the requirement of compiling on J2SE 1.3.
>>>
>>>> (since we still have a lot of older JDK version users here).
>>>>
>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>> both recent Sun and IBM JVMs at least before we put this on the main
>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>
>>>
>>>
>>>
>>> I agree.
>>>
>>> Regards
>>> -Ramesh
>>>
>>>> (anyone still
>>>> working on kaffe? 8-)
>>>>
>>>
>>>
>>>>
>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>
>>>>
>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>
>>>>>
>>>>>> Are these APIs and implementation thereof independent of Java 1.5?
>>>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> environment?
>>>>>
>>>>>> If not, could they be backported to work in such environments?
>>>>>>
>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>> ref%3Dnosim
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>
>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>> non-Sun implementation of Java...)?
>>>>>
>>>>> Web Maestro Clay
>>>>>
>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>> Sun! Love your logo!
>>>>> --
>>>>> Clay Leeds - <cl...@medata.com>
>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> =====
>>>> - Shane
>>>>
>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Berin Lautenbach <be...@wingsofhermes.org>.
Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow. What is the general
> procedure ? Is there any formality that needs to be completed first ?
> What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
to do?
I've CCd general@incubator as well, as I'd like Noel's opinion, but my
feeling is that *if* the Xerces/Xalan and/or XML-Commons community want
this code to be imported (and it sounds like they do - but I'd like to
see that formalised), then the community side is already there.
If that's the case, then I don't think we need to go through the full
incubation process (Noel - thoughts appreciated!) - we only need a code
grant from Sun (we can't take something into our repository until we are
sure we have appropriate legal rights to do so) + someone needs to fill
out the incubation docs to show that everything is AOK. I'm happy to
help out with the latter part.
Code grant details can be found at :
http://www.apache.org/licenses/#grants
>
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
>
> Thanks,
> Neeraj
>
>
> Neeraj Bajaj wrote:
>
>>
>>
>> Ramesh Mandava wrote:
>>
>>>>
>>>>
>>>> - Both Elliotte's and Clay's questions below are important. If someone
>>>> familiar with the code could comment on: For either the main trunk, or
>>>> a temporary working branch for integration:
>>>>
>>>> -- What JVM's will this code compile on? Version/Vendors?
>>>>
>>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>>> sources should run on other JVMs as well.
>>>
>>>>
>>>> -- What JVM's will this code run on? Version/Vendors?
>>>>
>>>
>>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
>>> Sun JVM. But as there is no Sun JVM specific codem these sources
>>> should work on other JVMs without modification ( we have to try it
>>> out though :-) ).
>>
>>
>>
>> Right. This hasn't been tried but i don't see any reason why it
>> shouldn't work on any other JVM as there isn't any Sun JVM specific code.
>>
>> In other mail i have suggested that active Xerces/Xalan committers can
>> try this before committin on main truck as the plan is to put the code
>> on branch first. I proposed JAXP 1.3 APIs to be committed on
>> xml-commons main trunk but i am totally fine with creating a branch
>> first to test
>> the compatibility with other JVM.
>>
>> Neeraj
>>
>>>
>>>
>>>>
>>>> We need to *clearly* document which versions this stuff works on, and
>>>> should conditionally compile or something if it won't compile on at
>>>> least 1.3
>>>
>>>
>>>
>>> Right now we face compilation problems in couple of file with J2SE
>>> 1.3, but these should be worked around though. We can atleast have a
>>> switch to achieve the requirement of compiling on J2SE 1.3.
>>>
>>>> (since we still have a lot of older JDK version users here).
>>>>
>>>> My knee-jerk reaction is also to hope that it will compile & run on
>>>> both recent Sun and IBM JVMs at least before we put this on the main
>>>> trunk: we should really try to be JVM-vendor agnostic.
>>>
>>>
>>>
>>>
>>> I agree.
>>>
>>> Regards
>>> -Ramesh
>>>
>>>> (anyone still
>>>> working on kaffe? 8-)
>>>>
>>>
>>>
>>>>
>>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>>
>>>>
>>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>>
>>>>>
>>>>>> Are these APIs and implementation thereof independent of Java 1.5?
>>>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> environment?
>>>>>
>>>>>> If not, could they be backported to work in such environments?
>>>>>>
>>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>>> http://www.cafeconleche.org/books/xian3/
>>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>>> ref%3Dnosim
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>>
>>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>>> non-Sun implementation of Java...)?
>>>>>
>>>>> Web Maestro Clay
>>>>>
>>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>>> Sun! Love your logo!
>>>>> --
>>>>> Clay Leeds - <cl...@medata.com>
>>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> =====
>>>> - Shane
>>>>
>>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by David Crossley <cr...@apache.org>.
(I notice that some individuals got dropped from the
original posting. Are they on the *.apache mailing lists?)
Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow.
> What is the general procedure ? Is there any formality that needs to be
> completed first ?
Others have mentioned the legal side, so my comments
are about code and community issues.
> What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I am an xml-commons committer and user of this stuff
in Apache Cocoon and Apache Forrest. So i am looking
forward to more people working at Xml-commons to
provide reliability.
One thing that we must have this time around, is a
version number on the xml-apis.jar filename. [1]
I suppose that is an Xml-commons "build" issue.
By the way, that build system is seriously in need
of improvement, but it gets us by.
You would have noticed that there is very little
activity with the xml-commons CVS, so it would be
fine to work on trunk.
At some stage soon, we need to move xml-commons to SVN.
Hopefully that will not disrupt progress.
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
I am a little confused about your planned procedure.
Are you suggesting to add a copy of the core code
to Xerces/Xalan then moving it to Xml-commons later?
It worries me that we end up with copies.
On related matters, there is past discussion, e.g.
[1] http://marc.theaimsgroup.com/?t=106739445900002
--
David Crossley
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Joseph Kesselman <ke...@us.ibm.com>.
I'm probably confused. On the other hand, I doubt I'm the only one who's
confused.
If the Xerces folks say 1.2 is the minimal requirement, I'll take their
word for it. (Most of the folks I know who moved to 1.2 also moved quickly
to 1.3, but most of the useful API changes happened in 1.2 so that's a
reasonable support level.)
As far as Xalan is concerned: We've discussed it often, and I think the
most recent consensus was that it was finally time to stop worrying about
1.1, but I didn't remember a decision to abandon 1.1 actually being made...
and I can't find a statement to that effect on the website. (The XSLTC
support does say that its compiler supports 1.1.8 only at runtime, not
compile time, but...) So as far as I know, Xalan itself is still officially
1.1.8-compatable.... though I don't know whether anyone has tested that in
the past year.
I believe Xalan currently uses JAXP 1.2, so we'll need to make sure it's
compatable with JAXP 1.3...
Again, I'm focusing on Xalan just because that's the other pie I've had my
fingers in; what this really flags is that Apache as a whole should reach
some consensus on what level of JDK APIs is pre-req'd, and every project
should be (a) compatable with that and later JDKs, and (b) clearly
documenting if it's supporting anything earlier.
Nothing wrong with code evolution, as long as the whole eco(de)system stays
balanced...
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Elliotte Harold <el...@metalab.unc.edu>.
Joseph Kesselman wrote:
>
>
>
> Note: While Xerces reached a consensus to move to JDK 1.3 as its earliest
> supported version, I'm not sure Xalan ever did so, nor am I certain about
> other Apache code. If this donation does make 1.2 or 1.3 a hard prereq, it
> might be a good idea to check with Apache as a whole before adopting it.
>
Is that true? I thought Xerces had reached a consensus to move to 1.2,
not 1.3. And I'm pretty sure Xalan has required 1.2 for some time now.
--
Elliotte Rusty Harold elharo@metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/ref%3Dnosim
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Joe,
Consensus hasn't been reached to move to JDK 1.3 in Xerces. We have never
discussed this with the community. We did vote to move up to JDK 1.2 and
Xerces has required it since Xerces 2.6.2.
Thanks.
Joseph Kesselman <ke...@us.ibm.com> wrote on 10/13/2004 11:07:56 AM:
>
> Note: While Xerces reached a consensus to move to JDK 1.3 as its
earliest
> supported version, I'm not sure Xalan ever did so, nor am I certain
about
> other Apache code. If this donation does make 1.2 or 1.3 a hard prereq,
it
> might be a good idea to check with Apache as a whole before adopting it.
>
> (This is not an objection, just an observation that coordination may be
> needed.)
>
> ______________________________________
> Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
> "The world changed profoundly and unpredictably the day Tim Berners Lee
> got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Joseph Kesselman <ke...@us.ibm.com>.
Note: While Xerces reached a consensus to move to JDK 1.3 as its earliest
supported version, I'm not sure Xalan ever did so, nor am I certain about
other Apache code. If this donation does make 1.2 or 1.3 a hard prereq, it
might be a good idea to check with Apache as a whole before adopting it.
(This is not an objection, just an observation that coordination may be
needed.)
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by sterling <ss...@thelinks.com>.
How would client side browsers that did not have or allow java be
impacted?
On Wed, 13 Oct 2004, Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow.
> What is the general procedure ? Is there any formality that needs to be
> completed first ? What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
>
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
>
> Thanks,
> Neeraj
>
>
> Neeraj Bajaj wrote:
>
> >
> >
> > Ramesh Mandava wrote:
> >
> >>>
> >>>
> >>> - Both Elliotte's and Clay's questions below are important. If someone
> >>> familiar with the code could comment on: For either the main trunk, or
> >>> a temporary working branch for integration:
> >>>
> >>> -- What JVM's will this code compile on? Version/Vendors?
> >>>
> >> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
> >> sources should run on other JVMs as well.
> >>
> >>>
> >>> -- What JVM's will this code run on? Version/Vendors?
> >>>
> >>
> >> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
> >> Sun JVM. But as there is no Sun JVM specific codem these sources
> >> should work on other JVMs without modification ( we have to try it
> >> out though :-) ).
> >
> >
> > Right. This hasn't been tried but i don't see any reason why it
> > shouldn't work on any other JVM as there isn't any Sun JVM specific code.
> >
> > In other mail i have suggested that active Xerces/Xalan committers can
> > try this before committin on main truck as the plan is to put the code
> > on branch first. I proposed JAXP 1.3 APIs to be committed on
> > xml-commons main trunk but i am totally fine with creating a branch
> > first to test
> > the compatibility with other JVM.
> >
> > Neeraj
> >
> >>
> >>
> >>>
> >>> We need to *clearly* document which versions this stuff works on, and
> >>> should conditionally compile or something if it won't compile on at
> >>> least 1.3
> >>
> >>
> >> Right now we face compilation problems in couple of file with J2SE
> >> 1.3, but these should be worked around though. We can atleast have a
> >> switch to achieve the requirement of compiling on J2SE 1.3.
> >>
> >>> (since we still have a lot of older JDK version users here).
> >>>
> >>> My knee-jerk reaction is also to hope that it will compile & run on
> >>> both recent Sun and IBM JVMs at least before we put this on the main
> >>> trunk: we should really try to be JVM-vendor agnostic.
> >>
> >>
> >>
> >> I agree.
> >>
> >> Regards
> >> -Ramesh
> >>
> >>> (anyone still
> >>> working on kaffe? 8-)
> >>>
> >>
> >>
> >>>
> >>> --- Clay Leeds <cl...@medata.com> wrote:
> >>>
> >>>
> >>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
> >>>>
> >>>>
> >>>>> Are these APIs and implementation thereof independent of Java 1.5?
> >>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
> >>>>>
> >>>>
> >>>>
> >>>> environment?
> >>>>
> >>>>> If not, could they be backported to work in such environments?
> >>>>>
> >>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
> >>>>> XML in a Nutshell 3rd Edition Just Published!
> >>>>> http://www.cafeconleche.org/books/xian3/
> >>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
> >>>>> ref%3Dnosim
> >>>>>
> >>>>
> >>>>
> >>>> Forgive me if this is covered under Mr. Harold's question, but:
> >>>>
> >>>> Would this also be portable to IBM Java 1.30 (and any other
> >>>> non-Sun implementation of Java...)?
> >>>>
> >>>> Web Maestro Clay
> >>>>
> >>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
> >>>> Sun! Love your logo!
> >>>> --
> >>>> Clay Leeds - <cl...@medata.com>
> >>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
> >>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>> =====
> >>> - Shane
> >>>
> >>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >>> For additional commands, e-mail: xalan-dev-help@xml.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
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> > For additional commands, e-mail: general-help@xml.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by ramesh mandava <Ra...@Sun.COM>.
Henry Zongaro wrote:
> Hi, Neeraj,
>
> Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/14/2004 07:53:26 AM:
>
>>Michael Glavassevich wrote:
>>
>>>Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>>>
>>>>
>>>>Hello All,
>>>>
>>>>I was wondering when can we start merging the JAXP 1.3 sources ?
>
> Merging
>
>>>>the code in branch/review/testing/committing to main trunk
>>>>would take time so at least from my side i would like to see this work
>
>
>>>>started as early as possible say from tomorrow.
>>>>
>>>>What is the general procedure ? Is there any formality that needs to
>
> be
>
>>>>completed first ? What is the opinion of
>>>>(Xml-commons/Xerces/Xalan) committers ?
>>>
>>>I'm interested in getting started on this so tomorrow sounds good to
>
> me.
>
>>>Formally, that's a +1 from me.
>>
>>It would be good to see response from Xalan committers too.
>
>
> Sorry for not chiming in sooner - I've been heavily occupied by other
> work.
>
> Speaking as a Xalan-J committer and an occasional contributor to
> xml-commons, I'll give this a +1. I'd like to see this work get underway
> very soon.
+1 from me too. I can help in getting the JAXP 1.3 sources into Xalan
branch.
Regards
-Ramesh
>
> Thanks,
>
> Henry
> ------------------------------------------------------------------
> Henry Zongaro Xalan development
> IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
> mailto:zongaro@ca.ibm.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by ramesh mandava <Ra...@Sun.COM>.
Henry Zongaro wrote:
> Hi, Neeraj,
>
> Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/14/2004 07:53:26 AM:
>
>>Michael Glavassevich wrote:
>>
>>>Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>>>
>>>>
>>>>Hello All,
>>>>
>>>>I was wondering when can we start merging the JAXP 1.3 sources ?
>
> Merging
>
>>>>the code in branch/review/testing/committing to main trunk
>>>>would take time so at least from my side i would like to see this work
>
>
>>>>started as early as possible say from tomorrow.
>>>>
>>>>What is the general procedure ? Is there any formality that needs to
>
> be
>
>>>>completed first ? What is the opinion of
>>>>(Xml-commons/Xerces/Xalan) committers ?
>>>
>>>I'm interested in getting started on this so tomorrow sounds good to
>
> me.
>
>>>Formally, that's a +1 from me.
>>
>>It would be good to see response from Xalan committers too.
>
>
> Sorry for not chiming in sooner - I've been heavily occupied by other
> work.
>
> Speaking as a Xalan-J committer and an occasional contributor to
> xml-commons, I'll give this a +1. I'd like to see this work get underway
> very soon.
+1 from me too. I can help in getting the JAXP 1.3 sources into Xalan
branch.
Regards
-Ramesh
>
> Thanks,
>
> Henry
> ------------------------------------------------------------------
> Henry Zongaro Xalan development
> IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
> mailto:zongaro@ca.ibm.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by ramesh mandava <Ra...@Sun.COM>.
Henry Zongaro wrote:
> Hi, Neeraj,
>
> Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/14/2004 07:53:26 AM:
>
>>Michael Glavassevich wrote:
>>
>>>Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>>>
>>>>
>>>>Hello All,
>>>>
>>>>I was wondering when can we start merging the JAXP 1.3 sources ?
>
> Merging
>
>>>>the code in branch/review/testing/committing to main trunk
>>>>would take time so at least from my side i would like to see this work
>
>
>>>>started as early as possible say from tomorrow.
>>>>
>>>>What is the general procedure ? Is there any formality that needs to
>
> be
>
>>>>completed first ? What is the opinion of
>>>>(Xml-commons/Xerces/Xalan) committers ?
>>>
>>>I'm interested in getting started on this so tomorrow sounds good to
>
> me.
>
>>>Formally, that's a +1 from me.
>>
>>It would be good to see response from Xalan committers too.
>
>
> Sorry for not chiming in sooner - I've been heavily occupied by other
> work.
>
> Speaking as a Xalan-J committer and an occasional contributor to
> xml-commons, I'll give this a +1. I'd like to see this work get underway
> very soon.
+1 from me too. I can help in getting the JAXP 1.3 sources into Xalan
branch.
Regards
-Ramesh
>
> Thanks,
>
> Henry
> ------------------------------------------------------------------
> Henry Zongaro Xalan development
> IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
> mailto:zongaro@ca.ibm.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by ramesh mandava <Ra...@Sun.COM>.
Henry Zongaro wrote:
> Hi, Neeraj,
>
> Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/14/2004 07:53:26 AM:
>
>>Michael Glavassevich wrote:
>>
>>>Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>>>
>>>>
>>>>Hello All,
>>>>
>>>>I was wondering when can we start merging the JAXP 1.3 sources ?
>
> Merging
>
>>>>the code in branch/review/testing/committing to main trunk
>>>>would take time so at least from my side i would like to see this work
>
>
>>>>started as early as possible say from tomorrow.
>>>>
>>>>What is the general procedure ? Is there any formality that needs to
>
> be
>
>>>>completed first ? What is the opinion of
>>>>(Xml-commons/Xerces/Xalan) committers ?
>>>
>>>I'm interested in getting started on this so tomorrow sounds good to
>
> me.
>
>>>Formally, that's a +1 from me.
>>
>>It would be good to see response from Xalan committers too.
>
>
> Sorry for not chiming in sooner - I've been heavily occupied by other
> work.
>
> Speaking as a Xalan-J committer and an occasional contributor to
> xml-commons, I'll give this a +1. I'd like to see this work get underway
> very soon.
+1 from me too. I can help in getting the JAXP 1.3 sources into Xalan
branch.
Regards
-Ramesh
>
> Thanks,
>
> Henry
> ------------------------------------------------------------------
> Henry Zongaro Xalan development
> IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
> mailto:zongaro@ca.ibm.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by ramesh mandava <Ra...@Sun.COM>.
Henry Zongaro wrote:
> Hi, Neeraj,
>
> Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/14/2004 07:53:26 AM:
>
>>Michael Glavassevich wrote:
>>
>>>Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>>>
>>>>
>>>>Hello All,
>>>>
>>>>I was wondering when can we start merging the JAXP 1.3 sources ?
>
> Merging
>
>>>>the code in branch/review/testing/committing to main trunk
>>>>would take time so at least from my side i would like to see this work
>
>
>>>>started as early as possible say from tomorrow.
>>>>
>>>>What is the general procedure ? Is there any formality that needs to
>
> be
>
>>>>completed first ? What is the opinion of
>>>>(Xml-commons/Xerces/Xalan) committers ?
>>>
>>>I'm interested in getting started on this so tomorrow sounds good to
>
> me.
>
>>>Formally, that's a +1 from me.
>>
>>It would be good to see response from Xalan committers too.
>
>
> Sorry for not chiming in sooner - I've been heavily occupied by other
> work.
>
> Speaking as a Xalan-J committer and an occasional contributor to
> xml-commons, I'll give this a +1. I'd like to see this work get underway
> very soon.
+1 from me too. I can help in getting the JAXP 1.3 sources into Xalan
branch.
Regards
-Ramesh
>
> Thanks,
>
> Henry
> ------------------------------------------------------------------
> Henry Zongaro Xalan development
> IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
> mailto:zongaro@ca.ibm.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Henry Zongaro <zo...@ca.ibm.com>.
Hi, Neeraj,
Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/14/2004 07:53:26 AM:
> Michael Glavassevich wrote:
>> Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>>>
>>>
>>> Hello All,
>>>
>>> I was wondering when can we start merging the JAXP 1.3 sources ?
Merging
>>> the code in branch/review/testing/committing to main trunk
>>> would take time so at least from my side i would like to see this work
>>> started as early as possible say from tomorrow.
>>>
>>> What is the general procedure ? Is there any formality that needs to
be
>>> completed first ? What is the opinion of
>>> (Xml-commons/Xerces/Xalan) committers ?
>>
>> I'm interested in getting started on this so tomorrow sounds good to
me.
>> Formally, that's a +1 from me.
> It would be good to see response from Xalan committers too.
Sorry for not chiming in sooner - I've been heavily occupied by other
work.
Speaking as a Xalan-J committer and an occasional contributor to
xml-commons, I'll give this a +1. I'd like to see this work get underway
very soon.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:zongaro@ca.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Henry Zongaro <zo...@ca.ibm.com>.
Hi, Neeraj,
Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/14/2004 07:53:26 AM:
> Michael Glavassevich wrote:
>> Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>>>
>>>
>>> Hello All,
>>>
>>> I was wondering when can we start merging the JAXP 1.3 sources ?
Merging
>>> the code in branch/review/testing/committing to main trunk
>>> would take time so at least from my side i would like to see this work
>>> started as early as possible say from tomorrow.
>>>
>>> What is the general procedure ? Is there any formality that needs to
be
>>> completed first ? What is the opinion of
>>> (Xml-commons/Xerces/Xalan) committers ?
>>
>> I'm interested in getting started on this so tomorrow sounds good to
me.
>> Formally, that's a +1 from me.
> It would be good to see response from Xalan committers too.
Sorry for not chiming in sooner - I've been heavily occupied by other
work.
Speaking as a Xalan-J committer and an occasional contributor to
xml-commons, I'll give this a +1. I'd like to see this work get underway
very soon.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:zongaro@ca.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Henry Zongaro <zo...@ca.ibm.com>.
Hi, Neeraj,
Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/14/2004 07:53:26 AM:
> Michael Glavassevich wrote:
>> Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>>>
>>>
>>> Hello All,
>>>
>>> I was wondering when can we start merging the JAXP 1.3 sources ?
Merging
>>> the code in branch/review/testing/committing to main trunk
>>> would take time so at least from my side i would like to see this work
>>> started as early as possible say from tomorrow.
>>>
>>> What is the general procedure ? Is there any formality that needs to
be
>>> completed first ? What is the opinion of
>>> (Xml-commons/Xerces/Xalan) committers ?
>>
>> I'm interested in getting started on this so tomorrow sounds good to
me.
>> Formally, that's a +1 from me.
> It would be good to see response from Xalan committers too.
Sorry for not chiming in sooner - I've been heavily occupied by other
work.
Speaking as a Xalan-J committer and an occasional contributor to
xml-commons, I'll give this a +1. I'd like to see this work get underway
very soon.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:zongaro@ca.ibm.com
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Henry Zongaro <zo...@ca.ibm.com>.
Hi, Neeraj,
Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/14/2004 07:53:26 AM:
> Michael Glavassevich wrote:
>> Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>>>
>>>
>>> Hello All,
>>>
>>> I was wondering when can we start merging the JAXP 1.3 sources ?
Merging
>>> the code in branch/review/testing/committing to main trunk
>>> would take time so at least from my side i would like to see this work
>>> started as early as possible say from tomorrow.
>>>
>>> What is the general procedure ? Is there any formality that needs to
be
>>> completed first ? What is the opinion of
>>> (Xml-commons/Xerces/Xalan) committers ?
>>
>> I'm interested in getting started on this so tomorrow sounds good to
me.
>> Formally, that's a +1 from me.
> It would be good to see response from Xalan committers too.
Sorry for not chiming in sooner - I've been heavily occupied by other
work.
Speaking as a Xalan-J committer and an occasional contributor to
xml-commons, I'll give this a +1. I'd like to see this work get underway
very soon.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:zongaro@ca.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Henry Zongaro <zo...@ca.ibm.com>.
Hi, Neeraj,
Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/14/2004 07:53:26 AM:
> Michael Glavassevich wrote:
>> Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>>>
>>>
>>> Hello All,
>>>
>>> I was wondering when can we start merging the JAXP 1.3 sources ?
Merging
>>> the code in branch/review/testing/committing to main trunk
>>> would take time so at least from my side i would like to see this work
>>> started as early as possible say from tomorrow.
>>>
>>> What is the general procedure ? Is there any formality that needs to
be
>>> completed first ? What is the opinion of
>>> (Xml-commons/Xerces/Xalan) committers ?
>>
>> I'm interested in getting started on this so tomorrow sounds good to
me.
>> Formally, that's a +1 from me.
> It would be good to see response from Xalan committers too.
Sorry for not chiming in sooner - I've been heavily occupied by other
work.
Speaking as a Xalan-J committer and an occasional contributor to
xml-commons, I'll give this a +1. I'd like to see this work get underway
very soon.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:zongaro@ca.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Michael Glavassevich wrote:
>Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>
>
>
>>Hello All,
>>
>>I was wondering when can we start merging the JAXP 1.3 sources ? Merging
>>
>>
>
>
>
>>the code in branch/review/testing/committing to main trunk
>>would take time so at least from my side i would like to see this work
>>started as early as possible say from tomorrow.
>>
>>What is the general procedure ? Is there any formality that needs to be
>>completed first ? What is the opinion of
>>(Xml-commons/Xerces/Xalan) committers ?
>>
>>
>
>I'm interested in getting started on this so tomorrow sounds good to me.
>Formally, that's a +1 from me.
>
It would be good to see response from Xalan committers too.
>
>
>
>>As the sources would be put in a branch so it won't affect normal
>>development but it would be good if we can restrict
>>large chunk of changes to the main trunk and fix only critical changes.
>>It would help merging the changes back to main
>>trunk. What do others think ?
>>
>>
>
>I think that's a good idea. We should merge the RI code into the main
>trunk in stages. One of the first things I'd like to see on the Xerces
>main trunk is an update of xml-apis.jar to JAXP 1.3, so we can clean-up
>the hacks currently there for SAX 2.0.2 and DOM Level 3.
>
>
I agree.
Thanks,
Neeraj
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Michael Glavassevich wrote:
>Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>
>
>
>>Hello All,
>>
>>I was wondering when can we start merging the JAXP 1.3 sources ? Merging
>>
>>
>
>
>
>>the code in branch/review/testing/committing to main trunk
>>would take time so at least from my side i would like to see this work
>>started as early as possible say from tomorrow.
>>
>>What is the general procedure ? Is there any formality that needs to be
>>completed first ? What is the opinion of
>>(Xml-commons/Xerces/Xalan) committers ?
>>
>>
>
>I'm interested in getting started on this so tomorrow sounds good to me.
>Formally, that's a +1 from me.
>
It would be good to see response from Xalan committers too.
>
>
>
>>As the sources would be put in a branch so it won't affect normal
>>development but it would be good if we can restrict
>>large chunk of changes to the main trunk and fix only critical changes.
>>It would help merging the changes back to main
>>trunk. What do others think ?
>>
>>
>
>I think that's a good idea. We should merge the RI code into the main
>trunk in stages. One of the first things I'd like to see on the Xerces
>main trunk is an update of xml-apis.jar to JAXP 1.3, so we can clean-up
>the hacks currently there for SAX 2.0.2 and DOM Level 3.
>
>
I agree.
Thanks,
Neeraj
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Michael Glavassevich wrote:
>Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>
>
>
>>Hello All,
>>
>>I was wondering when can we start merging the JAXP 1.3 sources ? Merging
>>
>>
>
>
>
>>the code in branch/review/testing/committing to main trunk
>>would take time so at least from my side i would like to see this work
>>started as early as possible say from tomorrow.
>>
>>What is the general procedure ? Is there any formality that needs to be
>>completed first ? What is the opinion of
>>(Xml-commons/Xerces/Xalan) committers ?
>>
>>
>
>I'm interested in getting started on this so tomorrow sounds good to me.
>Formally, that's a +1 from me.
>
It would be good to see response from Xalan committers too.
>
>
>
>>As the sources would be put in a branch so it won't affect normal
>>development but it would be good if we can restrict
>>large chunk of changes to the main trunk and fix only critical changes.
>>It would help merging the changes back to main
>>trunk. What do others think ?
>>
>>
>
>I think that's a good idea. We should merge the RI code into the main
>trunk in stages. One of the first things I'd like to see on the Xerces
>main trunk is an update of xml-apis.jar to JAXP 1.3, so we can clean-up
>the hacks currently there for SAX 2.0.2 and DOM Level 3.
>
>
I agree.
Thanks,
Neeraj
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Michael Glavassevich wrote:
>Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
>
>
>
>>Hello All,
>>
>>I was wondering when can we start merging the JAXP 1.3 sources ? Merging
>>
>>
>
>
>
>>the code in branch/review/testing/committing to main trunk
>>would take time so at least from my side i would like to see this work
>>started as early as possible say from tomorrow.
>>
>>What is the general procedure ? Is there any formality that needs to be
>>completed first ? What is the opinion of
>>(Xml-commons/Xerces/Xalan) committers ?
>>
>>
>
>I'm interested in getting started on this so tomorrow sounds good to me.
>Formally, that's a +1 from me.
>
It would be good to see response from Xalan committers too.
>
>
>
>>As the sources would be put in a branch so it won't affect normal
>>development but it would be good if we can restrict
>>large chunk of changes to the main trunk and fix only critical changes.
>>It would help merging the changes back to main
>>trunk. What do others think ?
>>
>>
>
>I think that's a good idea. We should merge the RI code into the main
>trunk in stages. One of the first things I'd like to see on the Xerces
>main trunk is an update of xml-apis.jar to JAXP 1.3, so we can clean-up
>the hacks currently there for SAX 2.0.2 and DOM Level 3.
>
>
I agree.
Thanks,
Neeraj
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow.
>
> What is the general procedure ? Is there any formality that needs to be
> completed first ? What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I'm interested in getting started on this so tomorrow sounds good to me.
Formally, that's a +1 from me.
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
I think that's a good idea. We should merge the RI code into the main
trunk in stages. One of the first things I'd like to see on the Xerces
main trunk is an update of xml-apis.jar to JAXP 1.3, so we can clean-up
the hacks currently there for SAX 2.0.2 and DOM Level 3.
> Thanks,
> Neeraj
Thanks
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow.
>
> What is the general procedure ? Is there any formality that needs to be
> completed first ? What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I'm interested in getting started on this so tomorrow sounds good to me.
Formally, that's a +1 from me.
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
I think that's a good idea. We should merge the RI code into the main
trunk in stages. One of the first things I'd like to see on the Xerces
main trunk is an update of xml-apis.jar to JAXP 1.3, so we can clean-up
the hacks currently there for SAX 2.0.2 and DOM Level 3.
> Thanks,
> Neeraj
Thanks
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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by sterling <ss...@thelinks.com>.
How would client side browsers that did not have or allow java be
impacted?
On Wed, 13 Oct 2004, Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow.
> What is the general procedure ? Is there any formality that needs to be
> completed first ? What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
>
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
>
> Thanks,
> Neeraj
>
>
> Neeraj Bajaj wrote:
>
> >
> >
> > Ramesh Mandava wrote:
> >
> >>>
> >>>
> >>> - Both Elliotte's and Clay's questions below are important. If someone
> >>> familiar with the code could comment on: For either the main trunk, or
> >>> a temporary working branch for integration:
> >>>
> >>> -- What JVM's will this code compile on? Version/Vendors?
> >>>
> >> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
> >> sources should run on other JVMs as well.
> >>
> >>>
> >>> -- What JVM's will this code run on? Version/Vendors?
> >>>
> >>
> >> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
> >> Sun JVM. But as there is no Sun JVM specific codem these sources
> >> should work on other JVMs without modification ( we have to try it
> >> out though :-) ).
> >
> >
> > Right. This hasn't been tried but i don't see any reason why it
> > shouldn't work on any other JVM as there isn't any Sun JVM specific code.
> >
> > In other mail i have suggested that active Xerces/Xalan committers can
> > try this before committin on main truck as the plan is to put the code
> > on branch first. I proposed JAXP 1.3 APIs to be committed on
> > xml-commons main trunk but i am totally fine with creating a branch
> > first to test
> > the compatibility with other JVM.
> >
> > Neeraj
> >
> >>
> >>
> >>>
> >>> We need to *clearly* document which versions this stuff works on, and
> >>> should conditionally compile or something if it won't compile on at
> >>> least 1.3
> >>
> >>
> >> Right now we face compilation problems in couple of file with J2SE
> >> 1.3, but these should be worked around though. We can atleast have a
> >> switch to achieve the requirement of compiling on J2SE 1.3.
> >>
> >>> (since we still have a lot of older JDK version users here).
> >>>
> >>> My knee-jerk reaction is also to hope that it will compile & run on
> >>> both recent Sun and IBM JVMs at least before we put this on the main
> >>> trunk: we should really try to be JVM-vendor agnostic.
> >>
> >>
> >>
> >> I agree.
> >>
> >> Regards
> >> -Ramesh
> >>
> >>> (anyone still
> >>> working on kaffe? 8-)
> >>>
> >>
> >>
> >>>
> >>> --- Clay Leeds <cl...@medata.com> wrote:
> >>>
> >>>
> >>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
> >>>>
> >>>>
> >>>>> Are these APIs and implementation thereof independent of Java 1.5?
> >>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
> >>>>>
> >>>>
> >>>>
> >>>> environment?
> >>>>
> >>>>> If not, could they be backported to work in such environments?
> >>>>>
> >>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
> >>>>> XML in a Nutshell 3rd Edition Just Published!
> >>>>> http://www.cafeconleche.org/books/xian3/
> >>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
> >>>>> ref%3Dnosim
> >>>>>
> >>>>
> >>>>
> >>>> Forgive me if this is covered under Mr. Harold's question, but:
> >>>>
> >>>> Would this also be portable to IBM Java 1.30 (and any other
> >>>> non-Sun implementation of Java...)?
> >>>>
> >>>> Web Maestro Clay
> >>>>
> >>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
> >>>> Sun! Love your logo!
> >>>> --
> >>>> Clay Leeds - <cl...@medata.com>
> >>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
> >>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>> =====
> >>> - Shane
> >>>
> >>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >>> For additional commands, e-mail: xalan-dev-help@xml.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
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> > For additional commands, e-mail: general-help@xml.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow.
>
> What is the general procedure ? Is there any formality that needs to be
> completed first ? What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I'm interested in getting started on this so tomorrow sounds good to me.
Formally, that's a +1 from me.
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
I think that's a good idea. We should merge the RI code into the main
trunk in stages. One of the first things I'd like to see on the Xerces
main trunk is an update of xml-apis.jar to JAXP 1.3, so we can clean-up
the hacks currently there for SAX 2.0.2 and DOM Level 3.
> Thanks,
> Neeraj
Thanks
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-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Neeraj Bajaj <Ne...@sun.com> wrote on 10/13/2004 10:11:00 AM:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow.
>
> What is the general procedure ? Is there any formality that needs to be
> completed first ? What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
I'm interested in getting started on this so tomorrow sounds good to me.
Formally, that's a +1 from me.
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
I think that's a good idea. We should merge the RI code into the main
trunk in stages. One of the first things I'd like to see on the Xerces
main trunk is an update of xml-apis.jar to JAXP 1.3, so we can clean-up
the hacks currently there for SAX 2.0.2 and DOM Level 3.
> Thanks,
> Neeraj
Thanks
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by sterling <ss...@thelinks.com>.
How would client side browsers that did not have or allow java be
impacted?
On Wed, 13 Oct 2004, Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> started as early as possible say from tomorrow.
> What is the general procedure ? Is there any formality that needs to be
> completed first ? What is the opinion of
> (Xml-commons/Xerces/Xalan) committers ?
>
> As the sources would be put in a branch so it won't affect normal
> development but it would be good if we can restrict
> large chunk of changes to the main trunk and fix only critical changes.
> It would help merging the changes back to main
> trunk. What do others think ?
>
> Thanks,
> Neeraj
>
>
> Neeraj Bajaj wrote:
>
> >
> >
> > Ramesh Mandava wrote:
> >
> >>>
> >>>
> >>> - Both Elliotte's and Clay's questions below are important. If someone
> >>> familiar with the code could comment on: For either the main trunk, or
> >>> a temporary working branch for integration:
> >>>
> >>> -- What JVM's will this code compile on? Version/Vendors?
> >>>
> >> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
> >> sources should run on other JVMs as well.
> >>
> >>>
> >>> -- What JVM's will this code run on? Version/Vendors?
> >>>
> >>
> >> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
> >> Sun JVM. But as there is no Sun JVM specific codem these sources
> >> should work on other JVMs without modification ( we have to try it
> >> out though :-) ).
> >
> >
> > Right. This hasn't been tried but i don't see any reason why it
> > shouldn't work on any other JVM as there isn't any Sun JVM specific code.
> >
> > In other mail i have suggested that active Xerces/Xalan committers can
> > try this before committin on main truck as the plan is to put the code
> > on branch first. I proposed JAXP 1.3 APIs to be committed on
> > xml-commons main trunk but i am totally fine with creating a branch
> > first to test
> > the compatibility with other JVM.
> >
> > Neeraj
> >
> >>
> >>
> >>>
> >>> We need to *clearly* document which versions this stuff works on, and
> >>> should conditionally compile or something if it won't compile on at
> >>> least 1.3
> >>
> >>
> >> Right now we face compilation problems in couple of file with J2SE
> >> 1.3, but these should be worked around though. We can atleast have a
> >> switch to achieve the requirement of compiling on J2SE 1.3.
> >>
> >>> (since we still have a lot of older JDK version users here).
> >>>
> >>> My knee-jerk reaction is also to hope that it will compile & run on
> >>> both recent Sun and IBM JVMs at least before we put this on the main
> >>> trunk: we should really try to be JVM-vendor agnostic.
> >>
> >>
> >>
> >> I agree.
> >>
> >> Regards
> >> -Ramesh
> >>
> >>> (anyone still
> >>> working on kaffe? 8-)
> >>>
> >>
> >>
> >>>
> >>> --- Clay Leeds <cl...@medata.com> wrote:
> >>>
> >>>
> >>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
> >>>>
> >>>>
> >>>>> Are these APIs and implementation thereof independent of Java 1.5?
> >>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
> >>>>>
> >>>>
> >>>>
> >>>> environment?
> >>>>
> >>>>> If not, could they be backported to work in such environments?
> >>>>>
> >>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
> >>>>> XML in a Nutshell 3rd Edition Just Published!
> >>>>> http://www.cafeconleche.org/books/xian3/
> >>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
> >>>>> ref%3Dnosim
> >>>>>
> >>>>
> >>>>
> >>>> Forgive me if this is covered under Mr. Harold's question, but:
> >>>>
> >>>> Would this also be portable to IBM Java 1.30 (and any other
> >>>> non-Sun implementation of Java...)?
> >>>>
> >>>> Web Maestro Clay
> >>>>
> >>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
> >>>> Sun! Love your logo!
> >>>> --
> >>>> Clay Leeds - <cl...@medata.com>
> >>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
> >>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>> =====
> >>> - Shane
> >>>
> >>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> >>> For additional commands, e-mail: xalan-dev-help@xml.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
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> > For additional commands, e-mail: general-help@xml.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
I was wondering when can we start merging the JAXP 1.3 sources ? Merging
the code in branch/review/testing/committing to main trunk
would take time so at least from my side i would like to see this work
started as early as possible say from tomorrow.
What is the general procedure ? Is there any formality that needs to be
completed first ? What is the opinion of
(Xml-commons/Xerces/Xalan) committers ?
As the sources would be put in a branch so it won't affect normal
development but it would be good if we can restrict
large chunk of changes to the main trunk and fix only critical changes.
It would help merging the changes back to main
trunk. What do others think ?
Thanks,
Neeraj
Neeraj Bajaj wrote:
>
>
> Ramesh Mandava wrote:
>
>>>
>>>
>>> - Both Elliotte's and Clay's questions below are important. If someone
>>> familiar with the code could comment on: For either the main trunk, or
>>> a temporary working branch for integration:
>>>
>>> -- What JVM's will this code compile on? Version/Vendors?
>>>
>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>> sources should run on other JVMs as well.
>>
>>>
>>> -- What JVM's will this code run on? Version/Vendors?
>>>
>>
>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
>> Sun JVM. But as there is no Sun JVM specific codem these sources
>> should work on other JVMs without modification ( we have to try it
>> out though :-) ).
>
>
> Right. This hasn't been tried but i don't see any reason why it
> shouldn't work on any other JVM as there isn't any Sun JVM specific code.
>
> In other mail i have suggested that active Xerces/Xalan committers can
> try this before committin on main truck as the plan is to put the code
> on branch first. I proposed JAXP 1.3 APIs to be committed on
> xml-commons main trunk but i am totally fine with creating a branch
> first to test
> the compatibility with other JVM.
>
> Neeraj
>
>>
>>
>>>
>>> We need to *clearly* document which versions this stuff works on, and
>>> should conditionally compile or something if it won't compile on at
>>> least 1.3
>>
>>
>> Right now we face compilation problems in couple of file with J2SE
>> 1.3, but these should be worked around though. We can atleast have a
>> switch to achieve the requirement of compiling on J2SE 1.3.
>>
>>> (since we still have a lot of older JDK version users here).
>>>
>>> My knee-jerk reaction is also to hope that it will compile & run on
>>> both recent Sun and IBM JVMs at least before we put this on the main
>>> trunk: we should really try to be JVM-vendor agnostic.
>>
>>
>>
>> I agree.
>>
>> Regards
>> -Ramesh
>>
>>> (anyone still
>>> working on kaffe? 8-)
>>>
>>
>>
>>>
>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>
>>>
>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>
>>>>
>>>>> Are these APIs and implementation thereof independent of Java 1.5?
>>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>>
>>>>
>>>>
>>>> environment?
>>>>
>>>>> If not, could they be backported to work in such environments?
>>>>>
>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>> http://www.cafeconleche.org/books/xian3/
>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>> ref%3Dnosim
>>>>>
>>>>
>>>>
>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>
>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>> non-Sun implementation of Java...)?
>>>>
>>>> Web Maestro Clay
>>>>
>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>> Sun! Love your logo!
>>>> --
>>>> Clay Leeds - <cl...@medata.com>
>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>
>>>
>>>
>>>
>>>
>>> =====
>>> - Shane
>>>
>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Hello All,
I was wondering when can we start merging the JAXP 1.3 sources ? Merging
the code in branch/review/testing/committing to main trunk
would take time so at least from my side i would like to see this work
started as early as possible say from tomorrow.
What is the general procedure ? Is there any formality that needs to be
completed first ? What is the opinion of
(Xml-commons/Xerces/Xalan) committers ?
As the sources would be put in a branch so it won't affect normal
development but it would be good if we can restrict
large chunk of changes to the main trunk and fix only critical changes.
It would help merging the changes back to main
trunk. What do others think ?
Thanks,
Neeraj
Neeraj Bajaj wrote:
>
>
> Ramesh Mandava wrote:
>
>>>
>>>
>>> - Both Elliotte's and Clay's questions below are important. If someone
>>> familiar with the code could comment on: For either the main trunk, or
>>> a temporary working branch for integration:
>>>
>>> -- What JVM's will this code compile on? Version/Vendors?
>>>
>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>> sources should run on other JVMs as well.
>>
>>>
>>> -- What JVM's will this code run on? Version/Vendors?
>>>
>>
>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
>> Sun JVM. But as there is no Sun JVM specific codem these sources
>> should work on other JVMs without modification ( we have to try it
>> out though :-) ).
>
>
> Right. This hasn't been tried but i don't see any reason why it
> shouldn't work on any other JVM as there isn't any Sun JVM specific code.
>
> In other mail i have suggested that active Xerces/Xalan committers can
> try this before committin on main truck as the plan is to put the code
> on branch first. I proposed JAXP 1.3 APIs to be committed on
> xml-commons main trunk but i am totally fine with creating a branch
> first to test
> the compatibility with other JVM.
>
> Neeraj
>
>>
>>
>>>
>>> We need to *clearly* document which versions this stuff works on, and
>>> should conditionally compile or something if it won't compile on at
>>> least 1.3
>>
>>
>> Right now we face compilation problems in couple of file with J2SE
>> 1.3, but these should be worked around though. We can atleast have a
>> switch to achieve the requirement of compiling on J2SE 1.3.
>>
>>> (since we still have a lot of older JDK version users here).
>>>
>>> My knee-jerk reaction is also to hope that it will compile & run on
>>> both recent Sun and IBM JVMs at least before we put this on the main
>>> trunk: we should really try to be JVM-vendor agnostic.
>>
>>
>>
>> I agree.
>>
>> Regards
>> -Ramesh
>>
>>> (anyone still
>>> working on kaffe? 8-)
>>>
>>
>>
>>>
>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>
>>>
>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>
>>>>
>>>>> Are these APIs and implementation thereof independent of Java 1.5?
>>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>>
>>>>
>>>>
>>>> environment?
>>>>
>>>>> If not, could they be backported to work in such environments?
>>>>>
>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>> http://www.cafeconleche.org/books/xian3/
>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>> ref%3Dnosim
>>>>>
>>>>
>>>>
>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>
>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>> non-Sun implementation of Java...)?
>>>>
>>>> Web Maestro Clay
>>>>
>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>> Sun! Love your logo!
>>>> --
>>>> Clay Leeds - <cl...@medata.com>
>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>
>>>
>>>
>>>
>>>
>>> =====
>>> - Shane
>>>
>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@sun.com>.
Hello All,
I was wondering when can we start merging the JAXP 1.3 sources ? Merging
the code in branch/review/testing/committing to main trunk
would take time so at least from my side i would like to see this work
started as early as possible say from tomorrow.
What is the general procedure ? Is there any formality that needs to be
completed first ? What is the opinion of
(Xml-commons/Xerces/Xalan) committers ?
As the sources would be put in a branch so it won't affect normal
development but it would be good if we can restrict
large chunk of changes to the main trunk and fix only critical changes.
It would help merging the changes back to main
trunk. What do others think ?
Thanks,
Neeraj
Neeraj Bajaj wrote:
>
>
> Ramesh Mandava wrote:
>
>>>
>>>
>>> - Both Elliotte's and Clay's questions below are important. If someone
>>> familiar with the code could comment on: For either the main trunk, or
>>> a temporary working branch for integration:
>>>
>>> -- What JVM's will this code compile on? Version/Vendors?
>>>
>> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
>> sources should run on other JVMs as well.
>>
>>>
>>> -- What JVM's will this code run on? Version/Vendors?
>>>
>>
>> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
>> Sun JVM. But as there is no Sun JVM specific codem these sources
>> should work on other JVMs without modification ( we have to try it
>> out though :-) ).
>
>
> Right. This hasn't been tried but i don't see any reason why it
> shouldn't work on any other JVM as there isn't any Sun JVM specific code.
>
> In other mail i have suggested that active Xerces/Xalan committers can
> try this before committin on main truck as the plan is to put the code
> on branch first. I proposed JAXP 1.3 APIs to be committed on
> xml-commons main trunk but i am totally fine with creating a branch
> first to test
> the compatibility with other JVM.
>
> Neeraj
>
>>
>>
>>>
>>> We need to *clearly* document which versions this stuff works on, and
>>> should conditionally compile or something if it won't compile on at
>>> least 1.3
>>
>>
>> Right now we face compilation problems in couple of file with J2SE
>> 1.3, but these should be worked around though. We can atleast have a
>> switch to achieve the requirement of compiling on J2SE 1.3.
>>
>>> (since we still have a lot of older JDK version users here).
>>>
>>> My knee-jerk reaction is also to hope that it will compile & run on
>>> both recent Sun and IBM JVMs at least before we put this on the main
>>> trunk: we should really try to be JVM-vendor agnostic.
>>
>>
>>
>> I agree.
>>
>> Regards
>> -Ramesh
>>
>>> (anyone still
>>> working on kaffe? 8-)
>>>
>>
>>
>>>
>>> --- Clay Leeds <cl...@medata.com> wrote:
>>>
>>>
>>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>>
>>>>
>>>>> Are these APIs and implementation thereof independent of Java 1.5?
>>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>>
>>>>
>>>>
>>>> environment?
>>>>
>>>>> If not, could they be backported to work in such environments?
>>>>>
>>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>>> XML in a Nutshell 3rd Edition Just Published!
>>>>> http://www.cafeconleche.org/books/xian3/
>>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>>> ref%3Dnosim
>>>>>
>>>>
>>>>
>>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>>
>>>> Would this also be portable to IBM Java 1.30 (and any other
>>>> non-Sun implementation of Java...)?
>>>>
>>>> Web Maestro Clay
>>>>
>>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>>> Sun! Love your logo!
>>>> --
>>>> Clay Leeds - <cl...@medata.com>
>>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>>
>>>
>>>
>>>
>>>
>>> =====
>>> - Shane
>>>
>>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>>> For additional commands, e-mail: xalan-dev-help@xml.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
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ramesh Mandava wrote:
>>
>>
>> - Both Elliotte's and Clay's questions below are important. If someone
>> familiar with the code could comment on: For either the main trunk, or
>> a temporary working branch for integration:
>>
>> -- What JVM's will this code compile on? Version/Vendors?
>>
> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
> sources should run on other JVMs as well.
>
>>
>> -- What JVM's will this code run on? Version/Vendors?
>>
>
> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
> Sun JVM. But as there is no Sun JVM specific codem these sources
> should work on other JVMs without modification ( we have to try it out
> though :-) ).
Right. This hasn't been tried but i don't see any reason why it
shouldn't work on any other JVM as there isn't any Sun JVM specific code.
In other mail i have suggested that active Xerces/Xalan committers can
try this before committin on main truck as the plan is to put the code
on branch first. I proposed JAXP 1.3 APIs to be committed on xml-commons
main trunk but i am totally fine with creating a branch first to test
the compatibility with other JVM.
Neeraj
>
>
>>
>> We need to *clearly* document which versions this stuff works on, and
>> should conditionally compile or something if it won't compile on at
>> least 1.3
>
> Right now we face compilation problems in couple of file with J2SE
> 1.3, but these should be worked around though. We can atleast have a
> switch to achieve the requirement of compiling on J2SE 1.3.
>
>> (since we still have a lot of older JDK version users here).
>>
>> My knee-jerk reaction is also to hope that it will compile & run on
>> both recent Sun and IBM JVMs at least before we put this on the main
>> trunk: we should really try to be JVM-vendor agnostic.
>
>
> I agree.
>
> Regards
> -Ramesh
>
>> (anyone still
>> working on kaffe? 8-)
>>
>
>
>>
>> --- Clay Leeds <cl...@medata.com> wrote:
>>
>>
>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>
>>>
>>>> Are these APIs and implementation thereof independent of Java 1.5?
>>>>
>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>
>>>
>>> environment?
>>>
>>>> If not, could they be backported to work in such environments?
>>>>
>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>> XML in a Nutshell 3rd Edition Just Published!
>>>> http://www.cafeconleche.org/books/xian3/
>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>> ref%3Dnosim
>>>>
>>>
>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>
>>> Would this also be portable to IBM Java 1.30 (and any other non-Sun
>>> implementation of Java...)?
>>>
>>> Web Maestro Clay
>>>
>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>> Sun! Love your logo!
>>> --
>>> Clay Leeds - <cl...@medata.com>
>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>
>>
>>
>>
>> =====
>> - Shane
>>
>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>> For additional commands, e-mail: xalan-dev-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ramesh Mandava wrote:
>>
>>
>> - Both Elliotte's and Clay's questions below are important. If someone
>> familiar with the code could comment on: For either the main trunk, or
>> a temporary working branch for integration:
>>
>> -- What JVM's will this code compile on? Version/Vendors?
>>
> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
> sources should run on other JVMs as well.
>
>>
>> -- What JVM's will this code run on? Version/Vendors?
>>
>
> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
> Sun JVM. But as there is no Sun JVM specific codem these sources
> should work on other JVMs without modification ( we have to try it out
> though :-) ).
Right. This hasn't been tried but i don't see any reason why it
shouldn't work on any other JVM as there isn't any Sun JVM specific code.
In other mail i have suggested that active Xerces/Xalan committers can
try this before committin on main truck as the plan is to put the code
on branch first. I proposed JAXP 1.3 APIs to be committed on xml-commons
main trunk but i am totally fine with creating a branch first to test
the compatibility with other JVM.
Neeraj
>
>
>>
>> We need to *clearly* document which versions this stuff works on, and
>> should conditionally compile or something if it won't compile on at
>> least 1.3
>
> Right now we face compilation problems in couple of file with J2SE
> 1.3, but these should be worked around though. We can atleast have a
> switch to achieve the requirement of compiling on J2SE 1.3.
>
>> (since we still have a lot of older JDK version users here).
>>
>> My knee-jerk reaction is also to hope that it will compile & run on
>> both recent Sun and IBM JVMs at least before we put this on the main
>> trunk: we should really try to be JVM-vendor agnostic.
>
>
> I agree.
>
> Regards
> -Ramesh
>
>> (anyone still
>> working on kaffe? 8-)
>>
>
>
>>
>> --- Clay Leeds <cl...@medata.com> wrote:
>>
>>
>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>
>>>
>>>> Are these APIs and implementation thereof independent of Java 1.5?
>>>>
>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>
>>>
>>> environment?
>>>
>>>> If not, could they be backported to work in such environments?
>>>>
>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>> XML in a Nutshell 3rd Edition Just Published!
>>>> http://www.cafeconleche.org/books/xian3/
>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>> ref%3Dnosim
>>>>
>>>
>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>
>>> Would this also be portable to IBM Java 1.30 (and any other non-Sun
>>> implementation of Java...)?
>>>
>>> Web Maestro Clay
>>>
>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>> Sun! Love your logo!
>>> --
>>> Clay Leeds - <cl...@medata.com>
>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>
>>
>>
>>
>> =====
>> - Shane
>>
>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>> For additional commands, e-mail: xalan-dev-help@xml.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Ramesh Mandava wrote:
>>
>>
>> - Both Elliotte's and Clay's questions below are important. If someone
>> familiar with the code could comment on: For either the main trunk, or
>> a temporary working branch for integration:
>>
>> -- What JVM's will this code compile on? Version/Vendors?
>>
> J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
> sources should run on other JVMs as well.
>
>>
>> -- What JVM's will this code run on? Version/Vendors?
>>
>
> J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on
> Sun JVM. But as there is no Sun JVM specific codem these sources
> should work on other JVMs without modification ( we have to try it out
> though :-) ).
Right. This hasn't been tried but i don't see any reason why it
shouldn't work on any other JVM as there isn't any Sun JVM specific code.
In other mail i have suggested that active Xerces/Xalan committers can
try this before committin on main truck as the plan is to put the code
on branch first. I proposed JAXP 1.3 APIs to be committed on xml-commons
main trunk but i am totally fine with creating a branch first to test
the compatibility with other JVM.
Neeraj
>
>
>>
>> We need to *clearly* document which versions this stuff works on, and
>> should conditionally compile or something if it won't compile on at
>> least 1.3
>
> Right now we face compilation problems in couple of file with J2SE
> 1.3, but these should be worked around though. We can atleast have a
> switch to achieve the requirement of compiling on J2SE 1.3.
>
>> (since we still have a lot of older JDK version users here).
>>
>> My knee-jerk reaction is also to hope that it will compile & run on
>> both recent Sun and IBM JVMs at least before we put this on the main
>> trunk: we should really try to be JVM-vendor agnostic.
>
>
> I agree.
>
> Regards
> -Ramesh
>
>> (anyone still
>> working on kaffe? 8-)
>>
>
>
>>
>> --- Clay Leeds <cl...@medata.com> wrote:
>>
>>
>>> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>>
>>>
>>>> Are these APIs and implementation thereof independent of Java 1.5?
>>>>
>>>> i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>>
>>>
>>> environment?
>>>
>>>> If not, could they be backported to work in such environments?
>>>>
>>>> -- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>> XML in a Nutshell 3rd Edition Just Published!
>>>> http://www.cafeconleche.org/books/xian3/
>>>> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>> ref%3Dnosim
>>>>
>>>
>>> Forgive me if this is covered under Mr. Harold's question, but:
>>>
>>> Would this also be portable to IBM Java 1.30 (and any other non-Sun
>>> implementation of Java...)?
>>>
>>> Web Maestro Clay
>>>
>>> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>> Sun! Love your logo!
>>> --
>>> Clay Leeds - <cl...@medata.com>
>>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>>
>>
>>
>>
>> =====
>> - Shane
>>
>> <eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>> For additional commands, e-mail: xalan-dev-help@xml.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
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Ramesh Mandava <Ra...@Sun.COM>.
Hi Shane:
>A couple of comments:
>- Please cc: commons-dev@xml.apache.org, since xml-commons is the
>actual repository that holds the JAXP code.
>
>- Yay! Great progress all, both Xerces/Xalan folks for coordinating,
>and Sun folks for getting the process unstuck. 8-)
>
>- Both Elliotte's and Clay's questions below are important. If someone
>familiar with the code could comment on: For either the main trunk, or
>a temporary working branch for integration:
>
>-- What JVM's will this code compile on? Version/Vendors?
>
J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
sources should run on other JVMs as well.
>
>-- What JVM's will this code run on? Version/Vendors?
>
J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on Sun
JVM. But as there is no Sun JVM specific codem these sources should
work on other JVMs without modification ( we have to try it out though
:-) ).
>
>We need to *clearly* document which versions this stuff works on, and
>should conditionally compile or something if it won't compile on at
>least 1.3
>
Right now we face compilation problems in couple of file with J2SE 1.3,
but these should be worked around though. We can atleast have a switch
to achieve the requirement of compiling on J2SE 1.3.
>(since we still have a lot of older JDK version users here).
>
>My knee-jerk reaction is also to hope that it will compile & run on
>both recent Sun and IBM JVMs at least before we put this on the main
>trunk: we should really try to be JVM-vendor agnostic.
>
I agree.
Regards
-Ramesh
> (anyone still
>working on kaffe? 8-)
>
>
>--- Clay Leeds <cl...@medata.com> wrote:
>
>
>>On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>
>>
>>>Are these APIs and implementation thereof independent of Java 1.5?
>>>
>>>
>>>i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>
>>>
>>environment?
>>
>>
>>>If not, could they be backported to work in such environments?
>>>
>>>-- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>XML in a Nutshell 3rd Edition Just Published!
>>>http://www.cafeconleche.org/books/xian3/
>>>http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>ref%3Dnosim
>>>
>>>
>>Forgive me if this is covered under Mr. Harold's question, but:
>>
>>Would this also be portable to IBM Java 1.30 (and any other non-Sun
>>implementation of Java...)?
>>
>>Web Maestro Clay
>>
>>p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>Sun!
>>Love your logo!
>>--
>>Clay Leeds - <cl...@medata.com>
>>Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>
>>
>
>
>=====
>- Shane
>
><eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Ramesh Mandava <Ra...@Sun.COM>.
Hi Shane:
>A couple of comments:
>- Please cc: commons-dev@xml.apache.org, since xml-commons is the
>actual repository that holds the JAXP code.
>
>- Yay! Great progress all, both Xerces/Xalan folks for coordinating,
>and Sun folks for getting the process unstuck. 8-)
>
>- Both Elliotte's and Clay's questions below are important. If someone
>familiar with the code could comment on: For either the main trunk, or
>a temporary working branch for integration:
>
>-- What JVM's will this code compile on? Version/Vendors?
>
J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
sources should run on other JVMs as well.
>
>-- What JVM's will this code run on? Version/Vendors?
>
J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on Sun
JVM. But as there is no Sun JVM specific codem these sources should
work on other JVMs without modification ( we have to try it out though
:-) ).
>
>We need to *clearly* document which versions this stuff works on, and
>should conditionally compile or something if it won't compile on at
>least 1.3
>
Right now we face compilation problems in couple of file with J2SE 1.3,
but these should be worked around though. We can atleast have a switch
to achieve the requirement of compiling on J2SE 1.3.
>(since we still have a lot of older JDK version users here).
>
>My knee-jerk reaction is also to hope that it will compile & run on
>both recent Sun and IBM JVMs at least before we put this on the main
>trunk: we should really try to be JVM-vendor agnostic.
>
I agree.
Regards
-Ramesh
> (anyone still
>working on kaffe? 8-)
>
>
>--- Clay Leeds <cl...@medata.com> wrote:
>
>
>>On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>
>>
>>>Are these APIs and implementation thereof independent of Java 1.5?
>>>
>>>
>>>i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>
>>>
>>environment?
>>
>>
>>>If not, could they be backported to work in such environments?
>>>
>>>-- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>XML in a Nutshell 3rd Edition Just Published!
>>>http://www.cafeconleche.org/books/xian3/
>>>http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>ref%3Dnosim
>>>
>>>
>>Forgive me if this is covered under Mr. Harold's question, but:
>>
>>Would this also be portable to IBM Java 1.30 (and any other non-Sun
>>implementation of Java...)?
>>
>>Web Maestro Clay
>>
>>p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>Sun!
>>Love your logo!
>>--
>>Clay Leeds - <cl...@medata.com>
>>Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>
>>
>
>
>=====
>- Shane
>
><eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.apache.org
>
>
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Dalibor Topic <ro...@kaffe.org>.
Shane Curcuru wrote:
> A couple of comments:
> My knee-jerk reaction is also to hope that it will compile & run on
> both recent Sun and IBM JVMs at least before we put this on the main
> trunk: we should really try to be JVM-vendor agnostic. (anyone still
> working on kaffe? 8-)
Oh yes! :)
cheers,
dalibor topic
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Ramesh Mandava <Ra...@Sun.COM>.
Hi Shane:
>A couple of comments:
>- Please cc: commons-dev@xml.apache.org, since xml-commons is the
>actual repository that holds the JAXP code.
>
>- Yay! Great progress all, both Xerces/Xalan folks for coordinating,
>and Sun folks for getting the process unstuck. 8-)
>
>- Both Elliotte's and Clay's questions below are important. If someone
>familiar with the code could comment on: For either the main trunk, or
>a temporary working branch for integration:
>
>-- What JVM's will this code compile on? Version/Vendors?
>
J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
sources should run on other JVMs as well.
>
>-- What JVM's will this code run on? Version/Vendors?
>
J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on Sun
JVM. But as there is no Sun JVM specific codem these sources should
work on other JVMs without modification ( we have to try it out though
:-) ).
>
>We need to *clearly* document which versions this stuff works on, and
>should conditionally compile or something if it won't compile on at
>least 1.3
>
Right now we face compilation problems in couple of file with J2SE 1.3,
but these should be worked around though. We can atleast have a switch
to achieve the requirement of compiling on J2SE 1.3.
>(since we still have a lot of older JDK version users here).
>
>My knee-jerk reaction is also to hope that it will compile & run on
>both recent Sun and IBM JVMs at least before we put this on the main
>trunk: we should really try to be JVM-vendor agnostic.
>
I agree.
Regards
-Ramesh
> (anyone still
>working on kaffe? 8-)
>
>
>--- Clay Leeds <cl...@medata.com> wrote:
>
>
>>On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>
>>
>>>Are these APIs and implementation thereof independent of Java 1.5?
>>>
>>>
>>>i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>
>>>
>>environment?
>>
>>
>>>If not, could they be backported to work in such environments?
>>>
>>>-- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>XML in a Nutshell 3rd Edition Just Published!
>>>http://www.cafeconleche.org/books/xian3/
>>>http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>ref%3Dnosim
>>>
>>>
>>Forgive me if this is covered under Mr. Harold's question, but:
>>
>>Would this also be portable to IBM Java 1.30 (and any other non-Sun
>>implementation of Java...)?
>>
>>Web Maestro Clay
>>
>>p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>Sun!
>>Love your logo!
>>--
>>Clay Leeds - <cl...@medata.com>
>>Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>
>>
>
>
>=====
>- Shane
>
><eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Dalibor Topic <ro...@kaffe.org>.
Shane Curcuru wrote:
> A couple of comments:
> My knee-jerk reaction is also to hope that it will compile & run on
> both recent Sun and IBM JVMs at least before we put this on the main
> trunk: we should really try to be JVM-vendor agnostic. (anyone still
> working on kaffe? 8-)
Oh yes! :)
cheers,
dalibor topic
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Dalibor Topic <ro...@kaffe.org>.
Shane Curcuru wrote:
> A couple of comments:
> My knee-jerk reaction is also to hope that it will compile & run on
> both recent Sun and IBM JVMs at least before we put this on the main
> trunk: we should really try to be JVM-vendor agnostic. (anyone still
> working on kaffe? 8-)
Oh yes! :)
cheers,
dalibor topic
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Ramesh Mandava <Ra...@Sun.COM>.
Hi Shane:
>A couple of comments:
>- Please cc: commons-dev@xml.apache.org, since xml-commons is the
>actual repository that holds the JAXP code.
>
>- Yay! Great progress all, both Xerces/Xalan folks for coordinating,
>and Sun folks for getting the process unstuck. 8-)
>
>- Both Elliotte's and Clay's questions below are important. If someone
>familiar with the code could comment on: For either the main trunk, or
>a temporary working branch for integration:
>
>-- What JVM's will this code compile on? Version/Vendors?
>
J2SE 1.4.x, J2SE 5.0 . We tried this on Sun JDKs but the same
sources should run on other JVMs as well.
>
>-- What JVM's will this code run on? Version/Vendors?
>
J2SE 1.3.x, J2SE 1.4.x, J2SE 5.0. Again we qualified the sources on Sun
JVM. But as there is no Sun JVM specific codem these sources should
work on other JVMs without modification ( we have to try it out though
:-) ).
>
>We need to *clearly* document which versions this stuff works on, and
>should conditionally compile or something if it won't compile on at
>least 1.3
>
Right now we face compilation problems in couple of file with J2SE 1.3,
but these should be worked around though. We can atleast have a switch
to achieve the requirement of compiling on J2SE 1.3.
>(since we still have a lot of older JDK version users here).
>
>My knee-jerk reaction is also to hope that it will compile & run on
>both recent Sun and IBM JVMs at least before we put this on the main
>trunk: we should really try to be JVM-vendor agnostic.
>
I agree.
Regards
-Ramesh
> (anyone still
>working on kaffe? 8-)
>
>
>--- Clay Leeds <cl...@medata.com> wrote:
>
>
>>On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
>>
>>
>>>Are these APIs and implementation thereof independent of Java 1.5?
>>>
>>>
>>>i.e. can they be compiled and used in a Java 1.2/1.3/1.4
>>>
>>>
>>environment?
>>
>>
>>>If not, could they be backported to work in such environments?
>>>
>>>-- Elliotte Rusty Harold elharo@metalab.unc.edu
>>>XML in a Nutshell 3rd Edition Just Published!
>>>http://www.cafeconleche.org/books/xian3/
>>>http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
>>>ref%3Dnosim
>>>
>>>
>>Forgive me if this is covered under Mr. Harold's question, but:
>>
>>Would this also be portable to IBM Java 1.30 (and any other non-Sun
>>implementation of Java...)?
>>
>>Web Maestro Clay
>>
>>p.s. I'm not trying to look a gift-horse in the mouth--Thank you
>>Sun!
>>Love your logo!
>>--
>>Clay Leeds - <cl...@medata.com>
>>Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>>PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>
>>
>
>
>=====
>- Shane
>
><eof .sig="http://apachecon.com/ November in Vegas, baby!" />
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xalan-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Shane Curcuru <sh...@yahoo.com>.
A couple of comments:
- Please cc: commons-dev@xml.apache.org, since xml-commons is the
actual repository that holds the JAXP code.
- Yay! Great progress all, both Xerces/Xalan folks for coordinating,
and Sun folks for getting the process unstuck. 8-)
- Both Elliotte's and Clay's questions below are important. If someone
familiar with the code could comment on: For either the main trunk, or
a temporary working branch for integration:
-- What JVM's will this code compile on? Version/Vendors?
-- What JVM's will this code run on? Version/Vendors?
We need to *clearly* document which versions this stuff works on, and
should conditionally compile or something if it won't compile on at
least 1.3 (since we still have a lot of older JDK version users here).
My knee-jerk reaction is also to hope that it will compile & run on
both recent Sun and IBM JVMs at least before we put this on the main
trunk: we should really try to be JVM-vendor agnostic. (anyone still
working on kaffe? 8-)
--- Clay Leeds <cl...@medata.com> wrote:
> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
> > Are these APIs and implementation thereof independent of Java 1.5?
>
> > i.e. can they be compiled and used in a Java 1.2/1.3/1.4
> environment?
> > If not, could they be backported to work in such environments?
> >
> > -- Elliotte Rusty Harold elharo@metalab.unc.edu
> > XML in a Nutshell 3rd Edition Just Published!
> > http://www.cafeconleche.org/books/xian3/
> > http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
> > ref%3Dnosim
>
> Forgive me if this is covered under Mr. Harold's question, but:
>
> Would this also be portable to IBM Java 1.30 (and any other non-Sun
> implementation of Java...)?
>
> Web Maestro Clay
>
> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
> Sun!
> Love your logo!
> --
> Clay Leeds - <cl...@medata.com>
> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
=====
- Shane
<eof .sig="http://apachecon.com/ November in Vegas, baby!" />
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Shane Curcuru <sh...@yahoo.com>.
A couple of comments:
- Please cc: commons-dev@xml.apache.org, since xml-commons is the
actual repository that holds the JAXP code.
- Yay! Great progress all, both Xerces/Xalan folks for coordinating,
and Sun folks for getting the process unstuck. 8-)
- Both Elliotte's and Clay's questions below are important. If someone
familiar with the code could comment on: For either the main trunk, or
a temporary working branch for integration:
-- What JVM's will this code compile on? Version/Vendors?
-- What JVM's will this code run on? Version/Vendors?
We need to *clearly* document which versions this stuff works on, and
should conditionally compile or something if it won't compile on at
least 1.3 (since we still have a lot of older JDK version users here).
My knee-jerk reaction is also to hope that it will compile & run on
both recent Sun and IBM JVMs at least before we put this on the main
trunk: we should really try to be JVM-vendor agnostic. (anyone still
working on kaffe? 8-)
--- Clay Leeds <cl...@medata.com> wrote:
> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
> > Are these APIs and implementation thereof independent of Java 1.5?
>
> > i.e. can they be compiled and used in a Java 1.2/1.3/1.4
> environment?
> > If not, could they be backported to work in such environments?
> >
> > -- Elliotte Rusty Harold elharo@metalab.unc.edu
> > XML in a Nutshell 3rd Edition Just Published!
> > http://www.cafeconleche.org/books/xian3/
> > http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
> > ref%3Dnosim
>
> Forgive me if this is covered under Mr. Harold's question, but:
>
> Would this also be portable to IBM Java 1.30 (and any other non-Sun
> implementation of Java...)?
>
> Web Maestro Clay
>
> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
> Sun!
> Love your logo!
> --
> Clay Leeds - <cl...@medata.com>
> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
=====
- Shane
<eof .sig="http://apachecon.com/ November in Vegas, baby!" />
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Shane Curcuru <sh...@yahoo.com>.
A couple of comments:
- Please cc: commons-dev@xml.apache.org, since xml-commons is the
actual repository that holds the JAXP code.
- Yay! Great progress all, both Xerces/Xalan folks for coordinating,
and Sun folks for getting the process unstuck. 8-)
- Both Elliotte's and Clay's questions below are important. If someone
familiar with the code could comment on: For either the main trunk, or
a temporary working branch for integration:
-- What JVM's will this code compile on? Version/Vendors?
-- What JVM's will this code run on? Version/Vendors?
We need to *clearly* document which versions this stuff works on, and
should conditionally compile or something if it won't compile on at
least 1.3 (since we still have a lot of older JDK version users here).
My knee-jerk reaction is also to hope that it will compile & run on
both recent Sun and IBM JVMs at least before we put this on the main
trunk: we should really try to be JVM-vendor agnostic. (anyone still
working on kaffe? 8-)
--- Clay Leeds <cl...@medata.com> wrote:
> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
> > Are these APIs and implementation thereof independent of Java 1.5?
>
> > i.e. can they be compiled and used in a Java 1.2/1.3/1.4
> environment?
> > If not, could they be backported to work in such environments?
> >
> > -- Elliotte Rusty Harold elharo@metalab.unc.edu
> > XML in a Nutshell 3rd Edition Just Published!
> > http://www.cafeconleche.org/books/xian3/
> > http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
> > ref%3Dnosim
>
> Forgive me if this is covered under Mr. Harold's question, but:
>
> Would this also be portable to IBM Java 1.30 (and any other non-Sun
> implementation of Java...)?
>
> Web Maestro Clay
>
> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
> Sun!
> Love your logo!
> --
> Clay Leeds - <cl...@medata.com>
> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
=====
- Shane
<eof .sig="http://apachecon.com/ November in Vegas, baby!" />
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Shane Curcuru <sh...@yahoo.com>.
A couple of comments:
- Please cc: commons-dev@xml.apache.org, since xml-commons is the
actual repository that holds the JAXP code.
- Yay! Great progress all, both Xerces/Xalan folks for coordinating,
and Sun folks for getting the process unstuck. 8-)
- Both Elliotte's and Clay's questions below are important. If someone
familiar with the code could comment on: For either the main trunk, or
a temporary working branch for integration:
-- What JVM's will this code compile on? Version/Vendors?
-- What JVM's will this code run on? Version/Vendors?
We need to *clearly* document which versions this stuff works on, and
should conditionally compile or something if it won't compile on at
least 1.3 (since we still have a lot of older JDK version users here).
My knee-jerk reaction is also to hope that it will compile & run on
both recent Sun and IBM JVMs at least before we put this on the main
trunk: we should really try to be JVM-vendor agnostic. (anyone still
working on kaffe? 8-)
--- Clay Leeds <cl...@medata.com> wrote:
> On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
> > Are these APIs and implementation thereof independent of Java 1.5?
>
> > i.e. can they be compiled and used in a Java 1.2/1.3/1.4
> environment?
> > If not, could they be backported to work in such environments?
> >
> > -- Elliotte Rusty Harold elharo@metalab.unc.edu
> > XML in a Nutshell 3rd Edition Just Published!
> > http://www.cafeconleche.org/books/xian3/
> > http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
> > ref%3Dnosim
>
> Forgive me if this is covered under Mr. Harold's question, but:
>
> Would this also be portable to IBM Java 1.30 (and any other non-Sun
> implementation of Java...)?
>
> Web Maestro Clay
>
> p.s. I'm not trying to look a gift-horse in the mouth--Thank you
> Sun!
> Love your logo!
> --
> Clay Leeds - <cl...@medata.com>
> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
=====
- Shane
<eof .sig="http://apachecon.com/ November in Vegas, baby!" />
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Clay Leeds <cl...@medata.com>.
On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
> Are these APIs and implementation thereof independent of Java 1.5?
> i.e. can they be compiled and used in a Java 1.2/1.3/1.4 environment?
> If not, could they be backported to work in such environments?
>
> -- Elliotte Rusty Harold elharo@metalab.unc.edu
> XML in a Nutshell 3rd Edition Just Published!
> http://www.cafeconleche.org/books/xian3/
> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
> ref%3Dnosim
Forgive me if this is covered under Mr. Harold's question, but:
Would this also be portable to IBM Java 1.30 (and any other non-Sun
implementation of Java...)?
Web Maestro Clay
p.s. I'm not trying to look a gift-horse in the mouth--Thank you Sun!
Love your logo!
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Ramesh Mandava <Ra...@Sun.COM>.
Hi Elliotte:
> Are these APIs and implementation thereof independent of Java 1.5?
> i.e. can they be compiled and used in a Java 1.2/1.3/1.4 environment?
> If not, could they be backported to work in such environments?
>
JAXP 1.3 API and RI sources
-Can be compiled with J2SE 1.4 , J2SE 5.0
- Run on J2SE 1.3, J2SE 1.4, J2SE 5.0
- JAXP 1.3 TCK qualify these sources on J2SE 1.3, J2SE 1.4 and J2SE 5.0
Base JDK requirement for JAXP 1.3 is J2SE 1.3
Regards
-Ramesh
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Clay Leeds <cl...@medata.com>.
On Oct 12, 2004, at 5:12 AM, Elliotte Harold wrote:
> Are these APIs and implementation thereof independent of Java 1.5?
> i.e. can they be compiled and used in a Java 1.2/1.3/1.4 environment?
> If not, could they be backported to work in such environments?
>
> -- Elliotte Rusty Harold elharo@metalab.unc.edu
> XML in a Nutshell 3rd Edition Just Published!
> http://www.cafeconleche.org/books/xian3/
> http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/
> ref%3Dnosim
Forgive me if this is covered under Mr. Harold's question, but:
Would this also be portable to IBM Java 1.30 (and any other non-Sun
implementation of Java...)?
Web Maestro Clay
p.s. I'm not trying to look a gift-horse in the mouth--Thank you Sun!
Love your logo!
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Ramesh Mandava <Ra...@Sun.COM>.
Hi Elliotte:
> Are these APIs and implementation thereof independent of Java 1.5?
> i.e. can they be compiled and used in a Java 1.2/1.3/1.4 environment?
> If not, could they be backported to work in such environments?
>
JAXP 1.3 API and RI sources
-Can be compiled with J2SE 1.4 , J2SE 5.0
- Run on J2SE 1.3, J2SE 1.4, J2SE 5.0
- JAXP 1.3 TCK qualify these sources on J2SE 1.3, J2SE 1.4 and J2SE 5.0
Base JDK requirement for JAXP 1.3 is J2SE 1.3
Regards
-Ramesh
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Elliotte Harold <el...@metalab.unc.edu>.
Are these APIs and implementation thereof independent of Java 1.5? i.e.
can they be compiled and used in a Java 1.2/1.3/1.4 environment? If not,
could they be backported to work in such environments?
--
Elliotte Rusty Harold elharo@metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/ref%3Dnosim
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Elliotte Harold <el...@metalab.unc.edu>.
Are these APIs and implementation thereof independent of Java 1.5? i.e.
can they be compiled and used in a Java 1.2/1.3/1.4 environment? If not,
could they be backported to work in such environments?
--
Elliotte Rusty Harold elharo@metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/ref%3Dnosim
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Elliotte Harold <el...@metalab.unc.edu>.
Are these APIs and implementation thereof independent of Java 1.5? i.e.
can they be compiled and used in a Java 1.2/1.3/1.4 environment? If not,
could they be backported to work in such environments?
--
Elliotte Rusty Harold elharo@metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/ref%3Dnosim
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Elliotte Harold <el...@metalab.unc.edu>.
Are these APIs and implementation thereof independent of Java 1.5? i.e.
can they be compiled and used in a Java 1.2/1.3/1.4 environment? If not,
could they be backported to work in such environments?
--
Elliotte Rusty Harold elharo@metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/ref%3Dnosim
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Elliotte Harold <el...@metalab.unc.edu>.
Are these APIs and implementation thereof independent of Java 1.5? i.e.
can they be compiled and used in a Java 1.2/1.3/1.4 environment? If not,
could they be backported to work in such environments?
--
Elliotte Rusty Harold elharo@metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN%3D0596007647/cafeaulaitA/ref%3Dnosim
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Michael Glavassevich wrote:
>Hello Neeraj,
>
>I think this is a good plan for merging the JAXP 1.3 changes into Xerces.
>There's been quite a bit of progress on the XInclude implementation in
>CVS, particularly in the last two months, so I imagine it's quite
>different than it's state in the RI. Initially putting the RI on a
>separate branch and then merging onto the main trunk sounds like the right
>way to move forward.
>
>
Thanks Michael. I also see that merging Xinclude would require little
extra effort than merging
other components.
Regarding donation and merge of the sources, there have
been couple of questions
which i believe have been answered and there are other questions like
compiling code on other
JVM vendors which we (active Xerces/Xalan committers) can work out while
working on the branch
before committing on main trunk.
Regards,
Neeraj
>Thanks.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/12/2004 08:02:14 AM:
>
>
>
>>JAXP 1.3 RI: (Implementation components that should be part of Xerces)
>>
>>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes
>>into that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes
>>to the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>
>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
>
>
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Michael Glavassevich wrote:
>Hello Neeraj,
>
>I think this is a good plan for merging the JAXP 1.3 changes into Xerces.
>There's been quite a bit of progress on the XInclude implementation in
>CVS, particularly in the last two months, so I imagine it's quite
>different than it's state in the RI. Initially putting the RI on a
>separate branch and then merging onto the main trunk sounds like the right
>way to move forward.
>
>
Thanks Michael. I also see that merging Xinclude would require little
extra effort than merging
other components.
Regarding donation and merge of the sources, there have
been couple of questions
which i believe have been answered and there are other questions like
compiling code on other
JVM vendors which we (active Xerces/Xalan committers) can work out while
working on the branch
before committing on main trunk.
Regards,
Neeraj
>Thanks.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/12/2004 08:02:14 AM:
>
>
>
>>JAXP 1.3 RI: (Implementation components that should be part of Xerces)
>>
>>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes
>>into that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes
>>to the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>
>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
>
>
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Neeraj Bajaj <Ne...@Sun.COM>.
Michael Glavassevich wrote:
>Hello Neeraj,
>
>I think this is a good plan for merging the JAXP 1.3 changes into Xerces.
>There's been quite a bit of progress on the XInclude implementation in
>CVS, particularly in the last two months, so I imagine it's quite
>different than it's state in the RI. Initially putting the RI on a
>separate branch and then merging onto the main trunk sounds like the right
>way to move forward.
>
>
Thanks Michael. I also see that merging Xinclude would require little
extra effort than merging
other components.
Regarding donation and merge of the sources, there have
been couple of questions
which i believe have been answered and there are other questions like
compiling code on other
JVM vendors which we (active Xerces/Xalan committers) can work out while
working on the branch
before committing on main trunk.
Regards,
Neeraj
>Thanks.
>
>Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/12/2004 08:02:14 AM:
>
>
>
>>JAXP 1.3 RI: (Implementation components that should be part of Xerces)
>>
>>
>>JAXP 1.3 RI contains the implementation of following packages
>>
>>javax.xml.datatype
>>javax.xml.validation
>>javax.xml.parsers ( reset(), xinclude, etc.)
>>
>>which should reside at Xerces.
>>
>>I propose that we create a branch, and merge JAXP 1.3 RI changes
>>into that branch. This will help
>>other Xerces active committers to have a chance to look at it before
>>these changes being finally
>>committed to main trunk. This process would require merging changes
>>to the branch and then committing
>>changes to main trunk, i seek help of active Xerces committers.
>>
>>
>
>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
>
>
>
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hello Neeraj,
I think this is a good plan for merging the JAXP 1.3 changes into Xerces.
There's been quite a bit of progress on the XInclude implementation in
CVS, particularly in the last two months, so I imagine it's quite
different than it's state in the RI. Initially putting the RI on a
separate branch and then merging onto the main trunk sounds like the right
way to move forward.
Thanks.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/12/2004 08:02:14 AM:
> JAXP 1.3 RI: (Implementation components that should be part of Xerces)
>
>
> JAXP 1.3 RI contains the implementation of following packages
>
> javax.xml.datatype
> javax.xml.validation
> javax.xml.parsers ( reset(), xinclude, etc.)
>
> which should reside at Xerces.
>
> I propose that we create a branch, and merge JAXP 1.3 RI changes
> into that branch. This will help
> other Xerces active committers to have a chance to look at it before
> these changes being finally
> committed to main trunk. This process would require merging changes
> to the branch and then committing
> changes to main trunk, i seek help of active Xerces committers.
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
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hello Neeraj,
I think this is a good plan for merging the JAXP 1.3 changes into Xerces.
There's been quite a bit of progress on the XInclude implementation in
CVS, particularly in the last two months, so I imagine it's quite
different than it's state in the RI. Initially putting the RI on a
separate branch and then merging onto the main trunk sounds like the right
way to move forward.
Thanks.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/12/2004 08:02:14 AM:
> JAXP 1.3 RI: (Implementation components that should be part of Xerces)
>
>
> JAXP 1.3 RI contains the implementation of following packages
>
> javax.xml.datatype
> javax.xml.validation
> javax.xml.parsers ( reset(), xinclude, etc.)
>
> which should reside at Xerces.
>
> I propose that we create a branch, and merge JAXP 1.3 RI changes
> into that branch. This will help
> other Xerces active committers to have a chance to look at it before
> these changes being finally
> committed to main trunk. This process would require merging changes
> to the branch and then committing
> changes to main trunk, i seek help of active Xerces committers.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Donation of JAXP 1.3 Sources to Apache
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hello Neeraj,
I think this is a good plan for merging the JAXP 1.3 changes into Xerces.
There's been quite a bit of progress on the XInclude implementation in
CVS, particularly in the last two months, so I imagine it's quite
different than it's state in the RI. Initially putting the RI on a
separate branch and then merging onto the main trunk sounds like the right
way to move forward.
Thanks.
Neeraj Bajaj <Ne...@Sun.COM> wrote on 10/12/2004 08:02:14 AM:
> JAXP 1.3 RI: (Implementation components that should be part of Xerces)
>
>
> JAXP 1.3 RI contains the implementation of following packages
>
> javax.xml.datatype
> javax.xml.validation
> javax.xml.parsers ( reset(), xinclude, etc.)
>
> which should reside at Xerces.
>
> I propose that we create a branch, and merge JAXP 1.3 RI changes
> into that branch. This will help
> other Xerces active committers to have a chance to look at it before
> these changes being finally
> committed to main trunk. This process would require merging changes
> to the branch and then committing
> changes to main trunk, i seek help of active Xerces committers.
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-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org