P.S. Sorry about the posting on the vote thread.
There is a good discussion about the three possible solutions with the
bug (http://issues.apache.org/struts/browse/WW-3275). The easiest
(but far from ideal) is to use the solution #2. However, there is a
complete rewrite of PageFilter.java with the new structure, and it
looks a lot of thought went into it. Additionally, they have not only
deprecated PageFilter, but removed the code (pretty aggressive). I
doubt they would do that without reason, so I suspect the migration to
the new code will have to happen sooner than later.
If I had a better understanding of the logic behind the code on the
Sitemesh side, I'd pull together the changes and submit them myself.
If no one has the knowledge of integrating with Sitemesh via the
plugin, I'd be happy to do it. I just figured that someone with a
whole lot more knowledge about the two codebases could easily fix it.
By the way, I will be very happy when the xwork codebase is brought in
under Struts 2. I have tried to check out the project several times
and build, and I always trip on the fact that the xwork artifact is
out of step with Struts 2. You know... Struts will require version
2.X, and the xwork artifact is at a lower version. This wouldn't stop
me from working on the plugin of course, but if I am testing stuff
with the full development builds, I would love to be able to easily
build the source and any changes to test with.
-- Christian Stone
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
