diff --git a/doc/reference/src/dbprovider.xml b/doc/reference/src/dbprovider.xml index 4cc9ce7d..4611fe7a 100644 --- a/doc/reference/src/dbprovider.xml +++ b/doc/reference/src/dbprovider.xml @@ -108,11 +108,16 @@ - SqlServerCe-3.1 (aliased to - System.Data.SqlServerCe) - Microsoft SQL Server + SqlServerCe-3.1 - Microsoft SQL Server Compact Edition, provider V9.0.242.0 + + SqlServerCe-3.5.1 (aliased to + System.Data.SqlServerCe) - Microsoft SQL Server + Compact Edition, provider V3.5.1.0 + + OleDb-1.1 - OleDb, provider V1.0.5000.0 in framework .NET V1.1 @@ -219,6 +224,11 @@ 15.x + + SybaseAse-AdoNet2 - Sybase ADO.NET 2.0 + provider for ASE 12.x and 15.x + + Odbc-1.1 - ODBC provider V1.0.5000.0 in framework .NET V1.1 diff --git a/doc/reference/src/messaging.xml b/doc/reference/src/messaging.xml index 7be07f6b..8b0a1c13 100644 --- a/doc/reference/src/messaging.xml +++ b/doc/reference/src/messaging.xml @@ -257,7 +257,7 @@ Caching EMS Resources The class - Spring.Messaging.Nms.Connections.CachingConnectionFactory + Spring.Messaging.Nms.Connections.CachingConnectionFactory @@ -290,9 +290,9 @@ Spring.Messaging.Nms.Connections.CachingConnectionFactory extends the functionality of SingleConnectionFactory and adds the - caching of Sessions, MessageProducers, and MessageConsumers. + caching of Sessions, MessageProducers, and MessageConsumers. - The initial cache size is set to 1, use the property + The initial cache size is set to 1, use the property SessionCacheSize to increase the number of cached sessions. Note that the number of actual cached sessions will be more than that number as sessions are cached based on their acknowledgment @@ -302,7 +302,7 @@ MessageProducers and MessageConsumers are cached within their owning session and also take into account the unique properties of the - producers and consumers when caching. + producers and consumers when caching. MessageProducers are cached based on their destination. MessageConsumers are cached @@ -1129,7 +1129,8 @@ namespace MyApp </nms:listener-container> The example above is equivalent to creating two distinct listener - container object definitions and two distinct MessageListenerAdapter object definitions as demonstrated in the section entitled . In addition to the attributes shown above, the listener element may contain several optional ones. The following table describes all available attributes: @@ -1271,7 +1272,7 @@ namespace MyApp connection-factory A reference to the NMS - ConnectionFactory bean (the + ConnectionFactory object (the default object name is 'ConnectionFactory'). @@ -1351,6 +1352,14 @@ namespace MyApp Spring's TimeSpanConverter (e.g. 10s, 10m, 3h, etc) + + + auto-startup + + Set whether to automatically start the listeners after + initialization. Default is true, optionally set to + false. + diff --git a/doc/reference/src/objects.xml b/doc/reference/src/objects.xml index a7c7521f..6f4f866c 100644 --- a/doc/reference/src/objects.xml +++ b/doc/reference/src/objects.xml @@ -5062,6 +5062,17 @@ cfg.PostProcessObjectFactory(factory); </spring> </configuration> + + You can also register custom parser programmatically using the + NamespaceParserRegistry. Here is an example taken from the code used in + the Transactions Quickstart application. + + NamespaceParserRegistry.RegisterParser(typeof(DatabaseNamespaceParser)); +NamespaceParserRegistry.RegisterParser(typeof(TxNamespaceParser)); +NamespaceParserRegistry.RegisterParser(typeof(AopNamespaceParser)); + +IApplicationContext context = + new XmlApplicationContext("assembly://Spring.TxQuickStart.Tests/Spring.TxQuickStart/system-test-local-config.xml"); @@ -5125,7 +5136,7 @@ cfg.PostProcessObjectFactory(factory); the configSecitons section of App.config. The type alias configuration section contains one or more <alias> elements each with a name and a type attribute. Below is an example that registers the alias for - WebServiceExporter + WebServiceExporter <configuration> @@ -5144,7 +5155,7 @@ cfg.PostProcessObjectFactory(factory); </configuration> - For an example showing type aliases for generic types see For an example showing type aliases for generic types see . Another way is to define an object of the type diff --git a/doc/reference/src/overview.xml b/doc/reference/src/overview.xml index 348b0bf0..84b29b21 100644 --- a/doc/reference/src/overview.xml +++ b/doc/reference/src/overview.xml @@ -188,7 +188,7 @@ With the building blocks described above you can use Spring in all sorts of scenarios, from simple stand alone console applications to fully-fledged enterprise applications using Spring's transaction - management functionality and web framework integration. + management functionality and web framework integration. It is important to note that the Spring Framework does not force you to use everything within it; it is not an @@ -198,13 +198,13 @@ access features that Spring offers. The only things you need to do is wire up your business logic using Spring's IoC container and integrate it into your web layer using WebApplicationContext to locate middle tier services - and/or configure your standard ASP.NET pages with depdenency injection. - + and/or configure your standard ASP.NET pages with depdenency + injection. While the Spring framework does not force any particular application architecure it encourages the use of a well layered application architecture with distinct tiers for the presentation, service, data - access, and database. + access, and database. @@ -244,7 +244,13 @@ - A calculator demonstrating remote service abstractions that let you 'export' a plain .NET object (PONO) via .NET Remoting, Web Services, or an EnterpriseService ServiceComponent. Corresponding client side - proxies are also demonstrated. . + proxies are also demonstrated. + + + + WCF - Shows a WCF based + calculator example that configures your WCF service via dependency + injection and apply AOP advice. @@ -283,6 +289,22 @@ included showing how to use the Open-Session In View approach to session management in the web tier. + + + Quartz Quickstart - + Application that shows the use of Quartz.NET integration for + scheduling. + + + + MSMQ - + Application demonstrating MSMQ helper classes. + + + + NMS - Applicatoin + demonstrating NMS helper classes. + diff --git a/doc/reference/src/transaction.xml b/doc/reference/src/transaction.xml index f4929688..f1a00490 100644 --- a/doc/reference/src/transaction.xml +++ b/doc/reference/src/transaction.xml @@ -455,7 +455,13 @@ rollback the transaction programmatically and you are using declarative transaction management, use the utility method - TransactionInterceptor.CurrentTransactionStatus.RollbackOnly = true; + TransactionInterceptor.CurrentTransactionStatus.SetRollbackOnly(); + + + Prior to Spring.NET 1.2 RC1 the API call would be + TransactionInterceptor.CurrentTransactionStatus.RollbackOnly = + true; + Understanding