dom4j-1_4_orbeon.jar

What has been changed in the OPS dom4j-1_4_orbeon.jar?

We're suffering from a few problems from dom4j-1.4 - memory leaks while
redeploying (apparently a known problem before 1.6 versions), and the
emedding of un-repackaged of a very old version of jaxen. So I want to
use the 1.6.1 jar, but the _orbeon suffix makes me uneasy as to what
OPS-specific changes I might be losing.

Adrian



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Adrian,

This is quite a shame to admit, but this must be the only JAR in OPS for
which I can't find the source (the source for all modified JARs is
usually under orbeon/tools, BTW). However, I don't think much has
changed from the original 1.4, but this JAR is now so old that we can't
be sure exactly :-(

I would try to go ahead and give 1.6.1 a try. Please be sure to report
any success or issues you may have.

-Erik

Adrian Baker wrote:
> What has been changed in the OPS dom4j-1_4_orbeon.jar?
>
> We're suffering from a few problems from dom4j-1.4 - memory leaks while
> redeploying (apparently a known problem before 1.6 versions), and the
> emedding of un-repackaged of a very old version of jaxen. So I want to
> use the 1.6.1 jar, but the _orbeon suffix makes me uneasy as to what
> OPS-specific changes I might be losing.
>
> Adrian

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

The OPS XForms engine runs fine under dom4j-1.6.1 in combination with jaxen-1.1-beta-9 (I wouldn't try with the very old beta 1 jaxen that OPS currently ships with). Given the problems 1.4 has caused us, I'd suggest it's worth upgrading. I don't have any complex XPL logic to test with the new version however.

Regarding your local change, might it be related to this note under the 1.5 beta 1 release? (http://www.dom4j.org/status.html):

    Fixed some bugs in BackedList (contributed by Alessandro Vernet).

Adrian


Erik Bruchez wrote:

Adrian,

This is quite a shame to admit, but this must be the only JAR in OPS for which I can't find the source (the source for all modified JARs is usually under orbeon/tools, BTW). However, I don't think much has changed from the original 1.4, but this JAR is now so old that we can't be sure exactly :-(

I would try to go ahead and give 1.6.1 a try. Please be sure to report any success or issues you may have.

-Erik

Adrian Baker wrote:

What has been changed in the OPS dom4j-1_4_orbeon.jar?

We're suffering from a few problems from dom4j-1.4 - memory leaks while redeploying (apparently a known problem before 1.6 versions), and the emedding of un-repackaged of a very old version of jaxen. So I want to use the 1.6.1 jar, but the _orbeon suffix makes me uneasy as to what OPS-specific changes I might be losing.

Adrian

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

On 5/1/06, Adrian Baker <[hidden email]> wrote:
>  Regarding your local change, might it be related to this note under the 1.5
> beta 1 release? (http://www.dom4j.org/status.html):
>
>      Fixed some bugs in BackedList (contributed by Alessandro Vernet).

That rings a bell :). So it's good to see that at least some of the
chances we did (and maybe all of them) made their way into a released
version. What you suggests seems reasonable so we are planning to
upgrade to dom4j 1.6.1 and Jaxen 1.1 beta 9 next week and we'll see
how it goes.

Alex
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Adrian Baker wrote:
> The OPS XForms engine runs fine under dom4j-1.6.1 in combination with
> jaxen-1.1-beta-9 (I wouldn't try with the very old beta 1 jaxen that OPS
> currently ships with). Given the problems 1.4 has caused us, I'd suggest
> it's worth upgrading. I don't have any complex XPL logic to test with
> the new version however.

FYI the latest nightly builds now use the latest dom4j and Jaxen. This
caused a couple of issues that I have fixed, in particular the fact that
Jaxen now correctly returns namespace nodes with "node()".

One project for OPS would be to move completely away from Jaxen and use
the Saxon XPath engine everywhere.

-Erik

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws