InfoQ Homepage Presentations Introduction to Spring.NET for Java Developers
Introduction to Spring.NET for Java Developers
01:26:00
Summary
Mark Pollack and Stephen Bohlen discuss Spring.NET, comparing it with Spring for Java, explaining how Java-.NET interoperability works, what tools are available and .NET features such as LINQ and MVC.
Bio
Dr. Mark Pollack has been a core Spring developer since 2003 and founder of Spring.NET. He has been a developer and architect of apps in the financial market. Mark is a Microsoft MVP. Stephen Bohlen is the Technical Lead and Community Evangelist for the Spring.NET Framework. Stephen is also an active contributor to several other .NET Open-Source Software projects including NHibernate, NDbUnit.
About the conference
SpringOne 2GX is a collocated event covering the entire Spring ecosystem and Groovy/Grails technologies. SpringOne 2GX is a one-of-a-kind conference for application developers, solution architects, web operations and IT teams who develop, deploy and manage business applications. This is the most important Java event of 2010, especially for anyone using Spring technologies, Groovy & Grails, or Tomcat. Whether you're building and running mission-critical business applications or designing the next killer cloud application, SpringOne 2GX will keep you up to date with the latest enterprise technology.
Apr 15, 2011
-
Related Sponsored Content
-
Related Sponsor
/filters:no_upscale()/sponsorship/topic/d7295235-717e-4e53-b057-e8f2b20f7838/MicrosoftLogoRSB-1650524400057.png)
Community comments
Growth in spring.net
by gaurav saxena,
Spring and Spring.NET
by Steve Whatmore,
Growth in spring.net
by gaurav saxena,
Your message is awaiting moderation. Thank you for participating in the discussion.
Good to know the amount of work done in Spring.net.
But waiting for a good book on spring.net.
Spring and Spring.NET
by Steve Whatmore,
Your message is awaiting moderation. Thank you for participating in the discussion.
We are a small ISV in the financial services industry that produces a native solution (Java and .NET platforms) using the produces the following stacks
Java .NET
---- ----
Spring Spring.NET
Hibernate nHibernate
ExtJS ExtJS
ANT nANT
jUnit nUnit
The individual projects are actually structured so that we actually share many components (i.e. ExtJS screens) by linking the two projects via SVN externals. This way we only develop certain components once and share across the platforms.
We have found that the similarities of the platforms and architecture, actually allowed us to create one logical architecture that was implemented natively on both platforms. Due to the similarities we actually have one development team supporting both platforms, regardless of whether those developers originally started as a C# developer or a Java developer.
This would not have been possible IMHO with the Spring framework.
Good job
PS: I do have a number of "WHY?" moments (i.e. syntax of configuration files being different, certain API(s) being different) but am happy nonetheless.