For some reason, I can't find an archive of our original discussion
("multiple component jars" - Sept 28, 2005 -
[email protected]). So I'll post a summary to this thread.
As previously discussed by:
- Alexander Jesse
- Martin Marinschek
- Mike Kienenberger
- Ed Burns
- Craig McClanahan
- Andrew Robinson
You have to be able to declare dependencies both ways on a 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"
In the jar's MANIFEST.MF file, create two new attributes, similar to
the standard jar "Class-Path:" attribute. These as-of-yet-unnamed
attributes would represent the two relationships above.
For those jars that don't specify a dependency order, JSF would fall
back to the behavior described in Issue #:121 (loading alphabetical by
file name)
I owe Ed an apology as I was the one that suggested it should fall
back to the above alphabetic behavior in the original thread, so I
don't have any basis for complaining about implementing it that way
other than a bad memory and an argumentative personality :)
So I'm changing my -1 to a +1 -- something needs to be in place as a
default ordering, and that's the best candidate to date. No reason
why that step can't happen sooner rather than later.
I'm going to add the contents of this message as a comment to issue
121 so it doesn't get lost again. I'll let it sit out here for
comment for a day first (or whenever the discussion reaches a lull) in
case anything needs to be corrected or updated.
-Mike
