spring.net

4 Responses to “spring.net”

1. Luke Flemmer Says:
   August 22nd, 2005 at 11:54 am

   dan points out this was previously mentioned on this fine blog…

   while we’re broadly on the subject of interception, is it just me or does the .net interception option suck? so, if i’m prepared to derive from ContextBoundObject, i can get arbitrary method interception, but otherwise i’m outta luck (short of some gnarly IL fixup?) forcing derivation in a language that doesn’t support multiple inheritance doesn’t seem like a great option. none of the articles i have found on interception even seem to consider that a drawback…

2. Damien Morton Says:
   August 22nd, 2005 at 1:16 pm

   Deriving from CBO does indeed suck. Ive come across articles which explained why they made that decision, though I cant seem to find a reference now.

   I imagine its possible to create equivalent functionality using classloader interception techniques, some code generation, and judicious use of a few coding rules.

3. Daniel Chait Says:
   August 22nd, 2005 at 1:28 pm

   That’s what Spring Framework solves.

   From the Spring.Net Documentation :

   “The Spring.Services library let you expose any “normal” object (meaning an object that does not inherit from a special service base class) as an enterprise (COM+) service or remoting object. .NET Web services get additional configuration flexibility with support for depedency injection and overriding of attribute metadata. Windows Service intergration is also provided.”

4. Luke Flemmer Says:
   August 22nd, 2005 at 2:36 pm

   that’s not how i read it; are you sure?