Berin Loritsch wrote:

Stephen McConnell wrote:

Berin Loritsch wrote:

Stephen McConnell wrote:

Berin Loritsch wrote:


IT IS NOT A TECHNICAL PROBLEM!





Good. We don't have a problem. End of thread. Steve.




Technical problems are not the only kind of problem this community needs to address.

The thread is not over.

Please respond to the points I made.



Sorry - why should I respond to a non-technical issue?


Ok, nevermind. Skrew your users and keep them guessing about what Avalon really is. Keep it up, let Avalon go into relative obscurity mainly because they have lost touch with one of the main reasons for being--people who use and support the project.

After all, you can't play nice, so why play?

Berin,
out of all the people taking part in this mudsling, you are IMNSHO the person who try the hardest to make it into a Personal issue.


I kindly ask you to cool down a bit and try to view the technical issues at hand, not whether you like Stephen or not (which we all know already).

Where is the technical problem between AF v4.1.5 and v4.2?

1. No change in the AF code itself.

2. A Specification Clarification that 4.2 components can declare the Life cycle artifacts in their constructor, instead of the phased population. Containers that does not support this feature, will not be considered 4.2 compatible.

3. All 4.1.x components will work in 4.1.x and 4.2 compliant containers.

4. Avalon is saying to its users; "Framework is NOT enough to declare a compatible component contract. Containers SHOULD go beyond Framework, and Avalon is providing the tools." You are free to use or ignore this recommendation.

5. The roadmap will be pointing to an Avalon 5, which will REQUIRE containers to support a water tight component contract, and not free to introduce incompatibilities in the component-side contract, but free to add extensions elsewhere. Hence the introduction of a "Facility" concept in Merlin to make the distinction clear.


Cheers Niclas

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



Reply via email to