Not yet. Just thinking about how I'm going to pull it off.
I'm using Guice for all the injection in JCatapult and we have this same
situation in our Filter. There are a number of Workflow implementations
that need to be called in order such as: JPA (open-session-in-view),
static-resource, security, etc. Right now we are just managing the order
in code. However, as I've been building out the MVC for JCatapult, I've
run into the situation that these workflows are pluggable and still have
a specific order.
I've considered using a dependency graph to figure it out dynamically or
some type of integer based indexing for each Workflow, but these all
seem pretty lame.
-bp
Musachy Barroso wrote:
Do you have an implementation of this already?
musachy
On Mon, Jun 2, 2008 at 1:21 PM, Brian Pontarelli <[EMAIL PROTECTED]> wrote:
Musachy Barroso wrote:
For those of you ignoring the spam on the Convention vote thread :). I
mentioned that the framework should support more than one
UnknownHandler, which would eventually make Convention and Codebehind
compatible, as well as other plugins in the future. The bad side
effect is that some configuration would be needed for the order of
evaluation of the UnknownHandlers, as well as a default(first UH that
can handle the request will be the one used). Comment away.
musachy
This is a large problem that I have been trying to solve for JCatapult. How
do you allow plugins to be dropped in but somehow organize themselves
correctly? The only solution I can think of is to have a configuration
parameter that is a ordered list of named beans to use. If someone is going
to be using both plugins, but will need to set this property by hand. If
they only use one, then XWork can ignore the property because there aren't
multiple UnknownHandlers in the container.
If someone has other cool ideas that don't require configuration, let me
know!
-bp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
