Peter Hunsberger pisze: > > I guess part of the debate is whether it is worth defining some > additional method, eg: > > CocoonOutput execute( CocoonInput genericInput) throws ?; > > or > > Object execute( Object genericInput) throws ?; > > I really can't see that the CocoonOuput and CocoonInput are anything > more than marker interfaces and this of course means that more > standard objects have to be wrapped so I think the second version is > preferable. But that certainly doesn't buy you anything as far as > pipeline contracts are concerned for traditional Java. However, I do > think that perhaps this opens up some longer term possibilities for > Aspect oriented inspection across the pipeline so maybe it is actually > worth adding?
You have got a point, it's exactly about this. The problem is (that my code shows) that this kind of thing, looking simple at the beginning results in rather ugly constructs in Java... At least I couldn't make it more concise... -- Best regards, Grzegorz Kossakowski
