<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Rolf<br>
<br>
Tested with our code based : <br>
<ul>
<li>all unit-tests passed. </li>
<li>generics works great : <br>
We had long anticipated the time were JDOM would support it and
were already using generics collections, with code such as : <br>
@SuppressWarnings("unchecked"), <br>
List<Element> elmList= elm.getChildren("foo");<br>
I simply had to remove the suppresswarnings everywhere and it
worked like a charm. Great job !</li>
</ul>
I am a little bit confused with the deprecation of method
SAXBuilder.setValidation() <br>
Method is deprecated, but there is still a non deprecated
constructor receiving boolean validate :<br>
This this code compile without warning: <br>
SAXBuilder builder = new
SAXBuilder(org.apache.xerces.parsers.SAXParser.class.getName(),
true);<br>
This code generated warning : <br>
SAXBuilder builder = new
SAXBuilder(org.apache.xerces.parsers.SAXParser.class.getName());<br>
builder.setValidation(true);<br>
<br>
Also note there is a small typo in javadoc for
SAXBuilder.setValidation() : <br>
method provides a means to *me* more specific about validation<br>
I tried to fork the project on github to submit a pull request, but
I am not enough familiar with git yet, and unfortunately do not have
time to dig further for the moment.<br>
<br>
On 14/12/2011 18:43, Rolf wrote:
<blockquote cite="mid:4EE8E035.7020606@tuis.net" type="cite">Hi all.
<br>
<br>
Having just come through a crazy few weeks at 'real' work, and
sorting out a few other 'christmasy', and 'life' issues, I now
have some significant time to throw at JDOM and to make some real
progress. Now is also a good time to summarize and consolidate
where things are.
<br>
<br>
I am also looking for feedback and criticism of the new code. I
know that there have been some people playing with the code:
<a class="moz-txt-link-freetext" href="https://github.com/hunterhacker/jdom/downloads">https://github.com/hunterhacker/jdom/downloads</a> ... how is it
working out for you?
<br>
<br>
If you have not yet had a look, please check out the wiki pages:
<br>
<a class="moz-txt-link-freetext" href="https://github.com/hunterhacker/jdom/wiki/JDOM-2.0">https://github.com/hunterhacker/jdom/wiki/JDOM-2.0</a>
<br>
<br>
The original objectives of the JDOM2 project are close to
complete. To recap:
<br>
<br>
Admin things:
<br>
- move to github,
<br>
- package rename to org.jdom2
<br>
- regression test harness
<br>
- documentation
<br>
<br>
Required things:
<br>
- generics
<br>
- varargs
<br>
- co-variant return types
<br>
- enums
<br>
<br>
Corrective things:
<br>
- XPath factory API
<br>
- many bug fixes
<br>
<br>
Nice things:
<br>
- upgraded XPath
<br>
- upgraded SAX
<br>
- upgraded Filter concept
<br>
- namespaces-in-scope.
<br>
<br>
New things:
<br>
- StAX
<br>
- JDOMConstants
<br>
<br>
<br>
I have tried to keep the wiki pages up to date, for details on all
the major functionality 'drives' in JDOM2 please check out the
JDOM2 Features page:
<a class="moz-txt-link-freetext" href="https://github.com/hunterhacker/jdom/wiki/JDOM2-Features">https://github.com/hunterhacker/jdom/wiki/JDOM2-Features</a>
<br>
<br>
Because the major objectives are essentially complete I want to
bring the code to an 'official' ALPHA type state. I want to
'finalize' the new API's, to start down the road of getting a
final release. I want to put out the 'Alpha' release on Jan 1,
2012. Hopefully it will be a new year resolution I can keep.....
<br>
<br>
JDOM 1.x spent years in 'beta', and I don't want the same thing to
happen with JDOM2. Really, there's not that much that's different,
so it should not be needed, but I think we have a better idea now
of what's important in the JDOM API, so it is not as important to
let the API 'settle' as it is 'played' with in the JDOM2 cycle.
<br>
<br>
In other words, I fully expect any 'alpha' and 'beta' releases to
be short, measured in weeks, not years.
<br>
<br>
It will have to happen at some point, but I don't want to miss
anything out in JDOM2 because JDOM3 is decades away and changing
the JDOM2 API will not be an easy option after it goes in to a
'beta' cycle!
<br>
<br>
This all requires participation and feedback... I need to know
what's working, what needs improvement, what's missing.
<br>
<br>
If you can take the code for a spin... Apply it to your existing
projects. Swap out the jdom 1.x jar you are using, do a
search/replace for 'org.jdom' and replace with 'org.jdom2' and
tell me what breaks....
<br>
<br>
Read this page:
<a class="moz-txt-link-freetext" href="https://github.com/hunterhacker/jdom/wiki/JDOM2--Migration-Issues">https://github.com/hunterhacker/jdom/wiki/JDOM2--Migration-Issues</a>
<br>
<br>
I am putting together a separate mail detailing the changes I
expect to be making in the next week.... and I will want some
feedback on that too.
<br>
<br>
Thanks
<br>
<br>
Rolf
<br>
_______________________________________________
<br>
To control your jdom-interest membership:
<br>
<a class="moz-txt-link-freetext" href="http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com">http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com</a>
<br>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Olivier Jaquemet <a class="moz-txt-link-rfc2396E" href="mailto:olivier.jaquemet@jalios.com"><olivier.jaquemet@jalios.com></a>
Ingénieur R&D Jalios S.A. - <a class="moz-txt-link-freetext" href="http://www.jalios.com/">http://www.jalios.com/</a>
@OlivierJaquemet +33970461480
</pre>
</body>
</html>