Jaxen 1.1.2

[Elliotte Harold]

I am in the process of posting Jaxen 1.1.2 to the web site. This release
rolls up a few small but significant bug fixes from the past year. There
are no API-level changes in this release. If no one notices any
problems, I'll probably announce this more broadly tomorrow.

Going forward, the next step is probably to remove and/or hide all the
deprecated public methods and release that as 1.2. This will be an
API-breaking release, but only in the parts no one is likely to be using
anyway. This will give us a lot more freedom for optimization and
refactoring going forward.

This might also be a good time to consider moving the build system to
Maven 2.0. If anyone feels like a smaller project, there are also a
number of broken links throughout the site that need to be repaired. See
the linkcheck report for details:

http://jaxen.org/linkcheck.html

--
Elliotte Rusty Harold  elharo@...
Refactoring HTML Just Published!
http://www.amazon.com/exec/obidos/ISBN=0321503635/ref=nosim/cafeaulaitA

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Tatu Saloranta]

--- On Wed, 12/3/08, Elliotte Harold <elharo@...> wrote:

> From: Elliotte Harold <elharo@...>
> Subject: [jaxen-dev] Jaxen 1.1.2
> To: dev@...
> Cc: user@...
> Date: Wednesday, December 3, 2008, 8:42 AM
>
> I am in the process of posting Jaxen 1.1.2 to the web site.
> This release rolls up a few small but significant bug fixes
> from the past year. There are no API-level changes in this
> release. If no one notices any problems, I'll probably
> announce this more broadly tomorrow.

Great!

> Going forward, the next step is probably to remove and/or
> hide all the deprecated public methods and release that as
> 1.2. This will be an API-breaking release, but only in the
> parts no one is likely to be using anyway. This will give us
> a lot more freedom for optimization and refactoring going
> forward.

I know it may be early to suggest new things, but one thing that would be nice to see going forward would be possibility to use Jaxen for "streaming xpath": using that subset of xpath that can be resolved without back (prev/parent) references, and without having to materialize an actual xml tree. I don't think Jaxen itself has to add support per se, but there may be some assumptions in modeling that prevent this (I will try to find time to test things out to see if this is true).
A related question is also whether it'd be easy to figure out whether a given expression is "streamable" in this sense. About the only definition of a streamable subset that I have heard of is from XML Schema specification (pointed out by Michael K(, which defines such a subset for expressing some constraints.

My specific use case would be to allow specifying an xpath expression to feed to a streaming parser, and find out which event satisfies it (as in would result in a result node being added corresponding to that event).

-+ Tatu +-



     

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email