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
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 h
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
c
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-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,
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
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
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 <[EMAIL PROTECTED]> wrote on 04/05/2005 06:48:30 AM:
> Ok I just finishe
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
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 th
[EMAIL PROTECTED], xerces-j-dev@xml.apache.org, Eduardo
Pelegri-Llopart <[EMAIL PROTECTED]>,
general@incubator.apache.org, general@xml.apache.org, Janet Breuer
<[EMAIL PROTECTED]>, Jeff Suttor <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject
Re: Donation of JAXP 1.3 Sources to Apache
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
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.
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
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
- The following addresses had permanent fatal errors -
(reason: 552 ZIP attachments are not accepted here.)
What should i do now ? Is there a way to upload s
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
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
d to
xerces-j-dev
To
"Geir Magnusson Jr." <[EMAIL PROTECTED]>
cc
general@incubator.apache.org, Eduardo Pelegri-Llopart
<[EMAIL PROTECTED]>, Jeff Suttor <[EMAIL PROTECTED]>,
general@xml.apache.org, xalan-dev@xml.apache.org,
[EMAIL PROTECTED], [EMAIL PROTECTED], xerces-j-
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
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 sign
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 sta
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 act
El mar, 19-10-2004 a las 11:40 -0700, Justin Erenkrantz escribiÃ:
> --On Tuesday, October 19, 2004 1:56 PM -0400 Neil Graham <[EMAIL PROTECTED]>
> wrote:
>
> > I'd also be curious to know what proportion of Apache projects have
> > migrated to SVN so far? There would be a significantly higher am
--On Tuesday, October 19, 2004 1:56 PM -0400 Neil Graham <[EMAIL PROTECTED]>
wrote:
I'd also be curious to know what proportion of Apache projects have
migrated to SVN so far? There would be a significantly higher amount of
churn caused to the community by an SVN migration than was caused by our
On Wednesday 20 October 2004 01:56, Neil Graham wrote:
> I'd also be curious to know what proportion of Apache projects have
> migrated to SVN so far?
http://svn.apache.org/repos/asf/
Is the current complete set of projects migrated, some larger than others.
Niclas
--
+--//
Hi David,
>
> So would this be an appropriate time to move the
> xml-commons repository to SVN?
Well, I don't know about you, but I generally prefer to ease my way into
new software tools, rather than dive right into advanced usage. So,
speaking for myself, I'd prefer to wait for a period of
Henry Zongaro wrote:
Hi, Neeraj,
Neeraj Bajaj <[EMAIL PROTECTED]> wrote on 10/14/2004 07:53:26 AM:
Michael Glavassevich wrote:
Neeraj Bajaj <[EMAIL PROTECTED]> wrote on 10/13/2004 10:11:00 AM:
Hello All,
I was wondering when can we start merging the JAXP 1.3 sources ?
Merging
the code in branch/
Hi, Neeraj,
Neeraj Bajaj <[EMAIL PROTECTED]> wrote on 10/14/2004 07:53:26 AM:
> Michael Glavassevich wrote:
>> Neeraj Bajaj <[EMAIL PROTECTED]> wrote on 10/13/2004 10:11:00 AM:
>>>
>>>
>>> Hello All,
>>>
>>> I was wondering when can we start merging the JAXP 1.3 sources ?
Merging
>>> the code
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 int
Neeraj Bajaj wrote:
>
> I checked on this one, This work involves legal and is being worked with
> legal now.
> I guess this process would take some time so wanted to update the
> community about the status.
So would this be an appropriate time to move the
xml-commons repository to SVN?
--
Da
Geir Magnusson Jr. wrote:
I worked on the some of the legal aspects with Eduardo, so going to
jump in here.
On Oct 13, 2004, at 3:59 PM, Berin Lautenbach wrote:
Neeraj Bajaj wrote:
Hello All,
I was wondering when can we start merging the JAXP 1.3 sources ?
Merging the code in branch/review/te
Sarah McNamara wrote:
> David Crossley wrote:
> >One thing that we must have this time around, is a
> >version number on the xml-apis.jar filename. [1]
> >I suppose that is an Xml-commons "build" issue.
> >By the way, that build system is seriously in need
> >of improvement, but it gets us by.
>
>
Hi all,
Berin Lautenbach <[EMAIL PROTECTED]> wrote on 10/13/2004 06:59:22
PM:
> I'm assuming that this is something that XML-Commons/Xerces/Xalan wish
> to do?
Here's a +1 from someone who's committed to Xerces-J and xml-commons. If
either project didn't want to move up to the latest standa
Sarah McNamara dijo:
> I agree we need a mechanism to identify different versions of an
> xml-apis.jar, but would prefer to see a versioning scheme worked out such
> that we can incorporate a Version class in the jar, version information in
> the jar's manifest, and a release distribution package (
-0 to including version number in the xml-apis.jar filename, unless
someone can show it will actually make sense to most people. Hmmm. But
what about including a versioned name, only for use by other projects that
already include their whole mess of dependent jars in their default
installs?
David Crossley wrote:
>One thing that we must have this time around, is a
>version number on the xml-apis.jar filename. [1]
>I suppose that is an Xml-commons "build" issue.
>By the way, that build system is seriously in need
>of improvement, but it gets us by.
A version number 'on' the jar fil
I dropped most of the Cc because this part is now an
issue for XML-Commons and the XML PMC.
Neeraj Bajaj wrote:
> David Crossley wrote:
> > One thing that we must have this time around, is a
> > version number on the xml-apis.jar filename. [1]
> > I suppose that is an Xml-commons "build" issue.
>
Berin,
Judging from yours, Geir's and David's messages, this sounds like mostly a
matter of clearing the IP (use the template), but is otherwise eagerly
awaited by a community already working with its precursor.
As for where it goes, I think that can be left to the community working with
the code
I worked on the some of the legal aspects with Eduardo, so going to
jump in here.
On Oct 13, 2004, at 3:59 PM, Berin Lautenbach wrote:
Neeraj Bajaj wrote:
Hello All,
I was wondering when can we start merging the JAXP 1.3 sources ?
Merging the code in branch/review/testing/committing to main tr
Neeraj Bajaj wrote:
Hello All,
I was wondering when can we start merging the JAXP 1.3 sources ? Merging
the code in branch/review/testing/committing to main trunk
would take time so at least from my side i would like to see this work
started as early as possible say from tomorrow. What is the ge
Michael Glavassevich wrote:
Neeraj Bajaj <[EMAIL PROTECTED]> wrote on 10/13/2004 10:11:00 AM:
Hello All,
I was wondering when can we start merging the JAXP 1.3 sources ? Merging
the code in branch/review/testing/committing to main trunk
would take time so
David Crossley wrote:
One thing that we must have this time around, is a
version number on the xml-apis.jar filename. [1]
I suppose that is an Xml-commons "build" issue.
By the way, that build system is seriously in need
of improvement,
This is something i can work with you when upgr
Berin Lautenbach wrote:
Neeraj Bajaj wrote:
Hello All,
I was wondering when can we start merging the JAXP 1.3 sources ?
Merging the code in branch/review/testing/committing to main trunk
would take time so at least from my side i would like to see this
work started as early as possible say from
(I notice that some individuals got dropped from the
original posting. Are they on the *.apache mailing lists?)
Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take
Neeraj Bajaj <[EMAIL PROTECTED]> wrote on 10/13/2004 10:11:00 AM:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at least from my side i would like to see this work
> st
How would client side browsers that did not have or allow java be
impacted?
On Wed, 13 Oct 2004, Neeraj Bajaj wrote:
> Hello All,
>
> I was wondering when can we start merging the JAXP 1.3 sources ? Merging
> the code in branch/review/testing/committing to main trunk
> would take time so at
Hello All,
I was wondering when can we start merging the JAXP 1.3 sources ? Merging
the code in branch/review/testing/committing to main trunk
would take time so at least from my side i would like to see this work
started as early as possible say from tomorrow.
What is the general procedure ? I
Ramesh Mandava wrote:
- Both Elliotte's and Clay's questions below are important. If someone
familiar with the code could comment on: For either the main trunk, or
a temporary working branch for integration:
-- What JVM's will this code compile on? Version/Vendors?
J2SE 1.4.x, J2SE 5.0 . We
Hi Shane:
A couple of comments:
- Please cc: [EMAIL PROTECTED], since xml-commons is the
actual repository that holds the JAXP code.
- Yay! Great progress all, both Xerces/Xalan folks for coordinating,
and Sun folks for getting the process unstuck. 8-)
- Both Elliotte's and Clay's questions below
Shane Curcuru wrote:
A couple of comments:
My knee-jerk reaction is also to hope that it will compile & run on
both recent Sun and IBM JVMs at least before we put this on the main
trunk: we should really try to be JVM-vendor agnostic. (anyone still
working on kaffe? 8-)
Oh yes! :)
cheers,
dalibo
The bottom line for the APIs is "yes for this case, but don't assume it
will necessarily continue to be so". For our specific implementation,
it certainly works for J2SE 1.4, but don't know about 1.3 and below.
Some more details on the API situation. JAXP is bundled in J2SE and in
J2EE. There
A couple of comments:
- Please cc: [EMAIL PROTECTED], since xml-commons is the
actual repository that holds the JAXP code.
- Yay! Great progress all, both Xerces/Xalan folks for coordinating,
and Sun folks for getting the process unstuck. 8-)
- Both Elliotte's and Clay's questions below are imp
52 matches
Mail list logo
