On Tue, 13 Nov 2001 20:07, Ulrich Mayring wrote:
> Peter Donald wrote:
> > oh. I may have a solution for that in a week or two ;)
> >
> > What you may want to do is declare a dependency via Optional Package
> > mechanism. See
> > http://java.sun.com/j2se/1.3/docs/guide/extensions/versioning.html
> >
> > Then the container should find required dependencies from a central
> > repository.
>
> Oops, saw this message too late. Yes, something like that would be cool.
> Currently I'm leaning towards putting the jar in the central lib
> directory of Avalon, rather than in every .sar application's lib
> directory. IMHO a central lib-repository with some mechanisms to use it
> has been on top of my Java-wishlist for a long time.
Okay I went and implemented it yesterday afternoon. So now the jars that
contain blocks can declare dependencies on external libraries aka "Optional
Packages". I have tested it a fair bit in one of my own apps and all seems
good.
However it is completely undocumented at this stage. I probably wont get a
chance to document till later in the week .. maybe thursday. Till then you
can read the above link and if thats not enough you can look at the
simpleserver demo in cornerstone. This shows a simple usage of the
Optional Packages/extensions code.
Anyways I will write up proper docs sometime later if thats not enough. The
central repository is located at ${phoenix.home}/ext. The only thing that is
unimplemented (and it will stay unimplemented for security reasons) is the
Implementation-URL: attribute by which you could auotmatically download
packages. Other than that we should be good to go.
--
Cheers,
Pete
*-----------------------------------------------------*
| For those who refuse to understand, no explanation |
| will ever suffice. For those who refuse to believe, |
| no evidence will ever suffice. |
*-----------------------------------------------------*
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
