On 9/28/05, Martin Marinschek <[EMAIL PROTECTED]> wrote:
Hmm ... a new geek-speak term to learn :-).
Yep, I think you are right. You have to be able to declare dependencies both ways, on a per application (or at least per-JAR) basis:
* "I am dependent on component library FOO, which must be
initialized before I am"
* "If component library BAR is used in this app, make sure that
I am initialized before it is"
Craig
Mike, Craig,
that was a solution I thought about as well.
But what do you do for the case that the user needs to "insert"
himself somewhere in the middle of this whole dependency pi-pa-po?
Hmm ... a new geek-speak term to learn :-).
There was an issue on the MyFaces mailing list were a user needed to
get his phase-listener executed right before a myfaces one.
If we try to solve this whole issue with sequences, we will need to
solve this situation as well, right?
Yep, I think you are right. You have to be able to declare dependencies both ways, on a per application (or at least per-JAR) basis:
* "I am dependent on component library FOO, which must be
initialized before I am"
* "If component library BAR is used in this app, make sure that
I am initialized before it is"
Craig
Now there needs to be a possibility for the user to rewrite the
dependencies! How do you want to do this?
regards,
Martin
On 9/28/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
> Exactly! I was going to use the MANIFEST Class-Path: attribute as an
> example in my last message, but I wasn't sure if it was evaluated for
> any jar other than the original target jar.
>
> On 9/28/05, Craig McClanahan <[EMAIL PROTECTED] > wrote:
> > Some sort of dependency declaration is going to be necessary for solving
> > this problem completely. There's precedent in the way that a JAR file can
> > declare dependencies on other JARs in it's MANIFEST.MF file ... something
> > like that should be explored here as well.
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Trainings in English and German
