Re: JDOM 2.x additional features

Benjamin Graf <[email protected]> Fri, 13 Apr 2012 09:15:03 +0200
Newsgroups gmane.comp.java.jdom.general
Message-ID <[email protected]>
Hi Rolf,

well, for business reasons the most interesting features are Android support for
mobile apps and "full" Saxon support for enterprise applications.

Have you ever look on Apache ServiceMix? They package jdom as an OSGi bundle for
years. (https://github.com/apache/servicemix4-bundles/tree/trunk/jdom-1.1.2)

The idea with the resolver sounds cool, but at the moment I see no much use
cases for usage with jdom in "normal" environments. Together with mobile support
(Android) in unstable network environments I think it should make sense.
Probably something for the contrib subproject?

Best regards
Benjamin

On 12.04.2012 20:46, Rolf Lear wrote:
> Hi again everyone.
>
> I am scheduling some additional features to put in the 'roadmap' for JDOM.
> I am already working on some, but I want to get some feedback and
> suggestions too.
>
> 'On the side' I have started the 'Resolver' project. This is hosted on
> github: https://github.com/rolfl/Resolver This project comes directly from
> the JDOM work because I did much of my JDOM work on the train, without an
> internet connection, and I needed to 'resolve' XSD and other resources from
> the web. If the Resolver project gets some interest, I am sure it would
> make some sense to at least consider moving it in to JDOM.
>
> I have been playing with a new Android tablet, and messing with the
> Android dev kit. I think it would be useful to come up with at minimum a
> 'statement' indicating Android support. If JDOM operates on Android it
> would be good to indicate what works, what's needed to make it work, what
> does not work, etc. Something similar to the Java5 page for JDOM:
> https://github.com/hunterhacker/jdom/wiki/JDOM2-Using-Java5
>
> Other items that I am not yet working on are:
>
> XPath 2.0 support
> Saxon 'native' integration - integrate with Saxon at a lower level and
> perhaps make it possible (by just including a saxon jar) to use Saxon for
> both XSLT and XPath.
> OSGi - investigate it, and find out whether JDOM could be a part of that
> model.
>
>
> Finally, there are a whole bunch of things I am not aware of that should
> be happening.... What should JDOM 2.x be doing for you?
>
> Rolf
> _______________________________________________
> To control your jdom-interest membership:
> http://www.jdom.org/mailman/options/jdom-interest/[email protected]

_______________________________________________
To control your jdom-interest membership:
http://www.jdom.org/mailman/options/jdom-interest/[email protected]
signature.asc (application/pgp-signature, 552 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAwAGBQJPh9J3AAoJEFIsy9OLZs8CEzsH/jcFZAxPHwV1+750pQaiA4IY
qwk4p8Udz5UNMxExO5qcsB36HTc0TI1Dd2opNmoU3JxSmEtyfRAD1lbLxTKhGJDD
BHRjreYzSK0kqAOalFWwW2GOfq8FTT6D1YOE9xnf4xRS5UQlsJHftoe7fnquilhv
m7z5jlr/bIx+wzwO/quGqZmAHzAs8vPzlo5QcbhcDKn0pVHCV8AcdshaMmA9+WMs
P2JSOrWmj0w5XJVjaj6an7wcoCFn3UxZTmQX8mJ2YlArX7HO3sXHbAeQBinZiG4x
HkkjW2XpDcuRJL+Bg71lA5i3hcU/odvD7iWBRAQYlaPXzNVe2VI1SMGHtB4twAU=
=lU6i
-----END PGP SIGNATURE-----