Chapter 4. Migrating from 1.1 M2

Note: If you previously installed Spring .xsd files to your VS.NET installation directory, remove them manually, and copy over the new ones, which have the -1.1.xsd suffix.

The names of the section handlers to register custom schemas has changed, from ConfigParsersSectionHandler to NamespaceParsersSectionHandler.

The target namespaces have changed, the 'directory' named /schema/ has been removed. For example, the target schema changed from http://www.springframework.net/schema/tx to http://www.springframework.net/tx.

A typical declaration to use custom schemas within your configuration file looks like this

<objects xmlns='http://www.springframework.net'
         xmlns:db="http://www.springframework.net/database"
         xmlns:tx="http://www.springframework.net/tx"
         xmlns:aop="http://www.springframework.net/aop">

The class XmlParserRegistry was renamed to NamespaceParserRegistry.

Renamed Spring.Validation.ValidationConfigParser to Spring.Validation.Config.ValidationNamespaceParser

Renamed from DatabaseConfigParser to DatabaseNamespaceParser

Renamed/Moved Remoting.RemotingConfigParser to Remoting.Config.RemotingNamespaceParser

<configuration>

  <configSections>
    <sectionGroup name="spring">
      <section name="parsers" type="Spring.Context.Support.NamespaceParsersSectionHandler, Spring.Core"/>         
     </sectionGroup>
  </configSections>

  <spring>
    <parsers> 
      <parser type="Spring.Aop.Config.AopNamespaceParser, Spring.Aop" /> 
      <parser type="Spring.Data.Config.DatabaseNamespaceParser, Spring.Data" /> 
      <parser type="Spring.Transaction.Config.TxNamespaceParser, Spring.Data" /> 
    </parsers> 
  </spring>

NamespaceParserRegistry.RegisterParser(typeof(AopNamespaceParser));
NamespaceParserRegistry.RegisterParser(typeof(DatabaseNamespaceParser));
NamespaceParserRegistry.RegisterParser(typeof(TxNamespaceParser));