> A small but important note. There have been several attempts to correct
> this issue however that has been opposed with sustained -1s on
> corrections.
I did. I went over the archives a few months ago, and occassionally browse
again. Getting into personalities here isn't going to fix the problem. No
one HERE (and I include the resident Avalon folks) is at fault, and I've no
idea where to find a clue stick for the parties who ARE at fault.
In some ways, this problem with Avalon is a good pain for James. It proves
that we cannot rely upon the Avalon group for a stable API, and if Danny's
goal of portable mailets is to be actualized, we need to mature it into a
more complete and robust specification. One of the biggest items is that an
interface to object repositories needs to be part of the mailet
specification, and mapped to the platform, rather than having to break the
veil.
But all of that is for James v3 and Mailet v2, not NOW.
IMO.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
