struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric D Nielsen <niels...@MIT.EDU>
Subject Exploring actionPackage-based configuration issues
Date Wed, 26 Sep 2007 17:59:15 GMT
I've been using Struts 2 for a few weeks now and am finding a few areas that
don't seem to posses the same clarity/utilty as most of the framework.  I'm
interested in seeing if I can come up with a patch to address these areas.

The first thing that's been bothering me is the lack of a clean way to link
auto-detected actions via actionPackages with an XWork package, without
resorting to lots of repetition of @ParentPackage.

I submitted a JIRA issue:
https://issues.apache.org/struts/browse/WW-2205
my writeup includes a few thoughts on what a solution might look like.  I would
be happy to expand upon them here or in follow-up comments there.

Realized after the fact that its highly redundant with
https://issues.apache.org/struts/browse/WW-2016

though the latter frames it as a documentation issue, while I feel there is also
a code issue.  The comments on 2016 seem to indicate a very non-inutitive
solution that I would feel is probably a bug that should be replaced with some
other solution.  (Ie @ParentPackage annotation "bleeds" through to affect other
classes)

I'm planning to start poking around the source tonight.  However, I've seen a
lot of references to annotation cleanup/plugin, but without seeing what's been
planned.  Searching through the open JIRA issues hasn't offered much insight
either.  I don't want to re-implement something that someone is already working
on, etc.

Thanks

Eric

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message