Noel J. Bergman wrote:
>>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.
>
>
I'm not disagreeing.
But to get down to the real "pain" issue - its the dependency on
Cornerstone. Your dependencies at the level of the James implementation
on Framework and Excalibur are ok (at least I had no problems there).
The issues are related to Phonix apps bacause (a) your tied to apps
that are tied to a particular container, which (b) means your dealing
with a small community of users, which (c) means that your not really
getting a lot of value for money. But I emphasis - this is a
Cornerstone/Phoneix issue - not a Avalon Framework or Excalibur issue.
As you said - the implicit Mailet API usage of Cornerstone components
(assuming I understand correctly) is something that needs to be
addressed - I have absolutely no problem with Avalon Framework
depedencies - I tend to float with respect to Excalibur - but lock-in
under Cornerstone is a royal PITA. Isn't it possible to provide Mailet
indepedent interfaces to the services you need, and then provide wrapped
Cornersone components as the service implemetation? This would reduce
your depedencies at at least provide the James community the ability to
migrate without breaking interfaces.
Steve.
>But all of that is for James v3 and Mailet v2, not NOW.
>
p.s.
Maybe some of this implicict Mailet depedencies need to be be address
now - at least at the level of documentation.
SJM
>
>IMO.
>
> --- Noel
>
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
>
>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
