On Friday 19 March 2004 00:39, Berin Loritsch wrote:
> > 3. Service != interface -=-=> The Service carries with it a lot more
> > than the Java interface, incl. the semantics, meta information,
> > documentation, and preferably compliance tests.
>
> Yeah, I was in that camp too. Think about it though. You cannot impose
> semantic meaning without actual code.
On the contrary! Without the semantic meaning, it is not possible to do the
implementation. Otherwise you are "Coding by Coincidence" as someone coined
the expression.
Example;
Please provide a working implementation (I have a client component that uses
several other implementations already) for
public interface GjkhadfUolqwknj
{
float ouihndoubne( String lwwqen, float ppqtrej );
}
For the sake of argument, I have obfuscated the names, since names may carry
implied semantic meaning.
> Therefore, the only time there is
> semantic meaning is when there is code. In this case, the java interface
> and the compliance tests are the only thing with meaning. The meta
> information only gains meaning when the container respects it and acts
> accordingly.
Meta has an enormous importance to bring re-use to the next level. Tools, man,
tools!
> Perhaps I am jaded by the fact that up to now near
> 100% or even 80% re-use has been a pipe dream.
Let's make the Pipe dream become a Reality, even if I am going to die trying.
The potential benefits are too vast to stop trying.
Cheers
Niclas
--
+---------//-------------------+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+------//----------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
