Re: Fortress: strange behavior

[Mu Mike]

god ,that is not a design anymore, it is an almost finished project
well,at least I learned something: my services are not specific enough, 
they should be divided into more speicific ones.
and thanks

From: "hammett" <[EMAIL PROTECTED]>
Reply-To: "Avalon framework users" <[EMAIL PROTECTED]>
To: "Avalon framework users" <[EMAIL PROTECTED]>
Subject: Re: Fortress: strange behavior
Date: Fri, 16 Jan 2004 00:36:38 -0300
----- Original Message -----
From: "Mu Mike" <[EMAIL PROTECTED]>
> dont you think this is too strict?

If you down_cast your interface to an implementation why do you need 
Avalon
anyway? The interface represents a service, and your client should no be
aware - or care - about its implementation. From time to time the
implementation can be changed and your clients would broke if you use in 
the
way you proposed.

> every implementaion of a Service must have all its public methods 
declared
> in the interface,and if you happen to need to add a public method to a
> specific implemetation class, you must declare it in the Interface,and
> since other implementations may need not use that method, you will have 
to
> have an abstract class also,just such a right rule.

Maybe you have a not well design application. Try to search for holes in 
the
services contracts, not in Avalon.

regards,
hammett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
与联机的朋友进行交流，请使用 MSN Messenger:  http://messenger.msn.com/cn  

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