Because there has been no reason to update it apparently. On
head jdom should be dropped. I'll update 3.2 to b8.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Colin Sampaleanu wrote:
Is there are particular reason JBoss ships with what
Is there something that replaces JDOM in 4.x?
JDOM can make XML experts out of dummies, and if you're working with
XML-based apps, it's nice to have in the server classpath.
Scott Stark wrote:
... On head jdom should be dropped.
---
dom4j or perhaps even a metadata service. I'm getting
tired of seeing N different sets of xml parser api code
spread throughout core components that should not be
tied to xml.
Tom Coleman wrote:
Is there something that replaces JDOM in 4.x?
JDOM can make XML experts out of dummies, and if
yes the replacment is dom4j. Check it out at
dom4j.org
Regards,
Hiram
--- Tom Coleman [EMAIL PROTECTED] wrote:
Is there something that replaces JDOM in 4.x?
JDOM can make XML experts out of dummies, and if
you're working with
XML-based apps, it's nice to have in the server
Is there are particular reason JBoss ships with what appears to be the
almost 2 year old JDOM b7, instead of the 'current' (about a year old)
b8? I've done a search through the mailing lists and couldn't find any
reference to this.
Upgrading the version in /lib to b8 seems to resolve the
