On Jul 25, 2005, at 2:13 PM, Marcus Brito wrote:
Kevin Menard <kmenard <at> servprise.com> writes:
What do you propose should happen when two JARs set the same
Tapestry-
Component-Library value?
Hmm, that would be tricky. How about loading only the first one
found, and issue
warnings about any duplicate namespaces?
This would most certainly cause confusion.
A second option would be to detect this
situation *before* loading any library, and loudly complain about
it (i.e.,
throw an exception) if there are duplicate namespaces.
This would result in a case where two component libs cannot be used
unless the two authors coordinate on who uses what namespace. Even
if it was configurable, you'd lose the "works out-of-the-box" feature.
I think a convention for namespace claiming would be more
appropriate, although I'm not sure what that convention would be.
--
Kevin
