You are viewing a plain text version of this content. The canonical link for it is here.

Posted to j-dev@xerces.apache.org by Neeraj Bajaj <Ne...@Sun.COM> on 2005/03/31 18:09:11 UTC

Re: Donation of JAXP 1.3 Sources to Apache

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: 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/

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

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

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: 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,

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 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

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 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...@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...@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: 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: 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@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

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