RE: [aus-dotnet] System.ComponentModel - Passing information back to Parent Forms

[Nick Lothian]

> 
> What I'm not too sure about is whether Spring or another IoC 
> framework 
> will be widely taken up by the .NET community for now - I don't work 
> with many organisations dealing with .NET that are concerned with 
> complex domain modeling and how objects are wired together.  The 
> emphasis is often just on consuming the FCL and extending it's 
> infrastructure in the creation of a propriety reusable 
> services framework.
> 
> Coming from Java, do you see any difference in the communities?
> 

Yes, it is very different in the Java world. The reasons for that are
probably more philisopical than technical.

I think IoC is most often used in Java systems as a way of interfacing
components, and less frequently in domain modelling.

In the Java world there is a focus on keeping things as open as possible so
that one part/layer/component of the system can be substituted for another
very easily, no matter how unrealistic it is that this would ever occur. 

Seriously - there are at least 5 major web presentation frameworks (Struts,
Webwork, Spring, JSF & Tapestry), and at least 4 major data access
strategies (Plain JDBC, Entity Beans, Hibernate & JDO), and many people try
to write business code that can be used from any of the presentation layers
and can use any of the data access strategies. 

This can make for very flexible systems, but it also makes them very complex
- especially since generally Java based configuration/deployment tools are
very primative compared to the Microsoft tooling.

IoC allows developers to implement a system like this relativly easily and
(using a framework like Spring) to keep the configuration at least somewhat
managable.

It is also very useful in Domain Modelling when used with the stronger
refactoring tools that are available for Java (ie, Eclipse & IDEA). Once
you've done a fair bit of refactoring you quickly realize that the
relationships between objects are more difficult to rearrange than the rest
of the code. IoC acts as a complement to refactoring tools by automating the
relationships between objects.

There's also a much bigger acceptance in Java in using things from "some
weird open source project someone  found on the web", as opposed to the
general approach in the .NET world of doing it like Microsoft does. This
probably made the IoC containers take of quicker than in the .NET world.

I'd suspect that the stronger refactoring support in VS2005 might encourage
people to look at IoC for domain modelling. I don't really see a requirement
for it at the system component level, since in .NET there is usually only
one realisitic alternative at each layer in the system.

Nick
_________________
You are a part of the Australian "dotnet" mailing list.
To unsubscribe send "unsubscribe dotnet" or to re-subscribe send "subscribe dotnet Your Name" in the body of the email to: imailsrv@xxxxxxxxxxx
List managed by: http://www.stanski.com