Re: [Heads Up] Deprecation Resolution and Future Concerns

[Leo Simons]

Noel J. Bergman wrote:

What this means is that in addition to providing binary compatibility
with all your users, the deprecation messages from Javac will reflect
Cocoon deprecations.

How does this impact the changes requiring Stephen to convert CM to SM for
James?  Or doesn't it?

it doesn't at all. This change is in the javadocs only, replacing '@deprecated' with '<span style="color: red;"></span>'.

Excalibur Concurrent has been stopped completely, and we are using
Doug Lea's Util.Concurrent library.

Are you exposing util.concurrent, or are you hiding it underneath?

we are not exposing it. We are simply moving some avalon packages which used to use the avalon threadpool implementation (fortress, ECM) to use Doug's threadpool implementation.

What
impact does this have on those of us using your threadpools?

none. The current avalon-excalibur and avalon-cornerstone threadpools are of lower quality than Doug's, apparently (I haven't done much testing myself). Thus we do want to encourage people who use the avalon-produced threadpools to move away from them and refactor to use doug's library. We are still backing the avalon-produced threadpools and they will receive full support.

I am familar with d.l.u.c and JSR 166.  I'm just concerned about short term
migration issues.

If your current application works snappy with the current threadpools, there is nothing to worry about. You don't need to migrate in the short term. Long term, I'm confident a migration path can/shall be provided if neccessary.

cheers!

- Leo



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]