forked from spring-projects/spring-net
-
Notifications
You must be signed in to change notification settings - Fork 0
/
BreakingChanges.txt
132 lines (80 loc) · 5.53 KB
/
BreakingChanges.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
Changes (1.3.2 to 2.0)
========================
1. Default transaction isolation level is now IsolationLevel.Unspecified instead of old IsolationLevel.ReadUncommitted
- You need to update your configuration to set the isolation level where old ReadUncommitted was expected, see Spring documentation's Transaction Management chapter
2. Protected fields were changed to private. Access is now allowed via public/protected property member.
3. Most of members marked as Obsolete before 2.0 release were removed.
4. DbProvider automatically sets BindByName to true for Oracle's ODP.NET OracleCommand instances when created
Changes (1.3.1 to 1.3.2)
========================
Spring.Data
1. Changed AbstractPlatformTransactionManager to set default Transaction Synchronizcation to TransactionSynchronization.NeverChange from TransactionSynchronizationState.Never. Use the setter 'TransactionSynchonization' to change. This was changed so as to avoid an issue with NHibernate Open Session In View functionality and some nested declarative transaction management settings. See https://jira.springsource.org/browse/SPRNET-1438 for more details.
Note: This functionality is an advanced feature of Spring, so if you are using it, you probably know all about it, otherwise you can safely ignore this message.
Changes (1.3 RC1 to 1.3 GA or greater)
========================
Spring.Data
-----------
1. The namespace for MultiDelegatingDbProvider was changed from Spring.Data to Spring.Data.Common as that is consistent with all the other implementations of IDbProvider.
Changes (1.2.0 to 1.3 or greater)
========================
Spring.Core
-----------
1. within an ValidationGroup element (<v:group>,<v:exclusive>,..), nested validator elements now must occur after any
<v:message>, <v:action> or <v:property> elements. The following was allowed previously, but now will raise a schema
validation error:
<v:group ..>
<v:validator ...>
<v:action ...>
change this to
<v:group ..>
<v:action ...>
<v:validator ...>
2. XmlReaderContext constructor now requires an IObjectDefinitionFactory to be specified. Thus XmlReaderContext.ObjectDefinitionFactory
is read only now.
3. Changes to the Apache NMS API, which was not yet a public release when included in Spring 1.2.0 made breaking API changes.
On NmsTemlate,
1) The property 'byte Priority' was changed to 'MsgPriority Priority'
2) The property 'bool Persistent' is no longer part of the NMS API but is still supported in a backward compatible
manner by Spring by translation to standard MsgDeliveryMode enumeration values of Persistent and NonPersistent.
A new property MsgDelivery has been added. The class, CachedMessageProducer, which is unlikely to be use by
end users, was directly upgraded to the latest API without any backwards compatibility support.
4. AbstractApplicationContext.CaseSensitive renamed to AbstractApplicationContext.IsCaseSensitive
5. Spring.Validation: Base class BaseValidator changed to BaseSimpleValidator for single validators as compared to group validators
which now commonly derive from BaseGroupValidator instead of ValidatorGroup
6. IVariableSource implementations now must also implement CanResolveVariable(string variableName) and may throw exceptions in
ResolveVariable() in case the variable cannot resolved by this particular variable source.
In order to distinguish between an existing variable having a null value and a non-existing variable, variable sources
need to be changed to this new contract.
7. a) Signature of CollectionUtils.Contains(ICollection collection, object element) changed to CollectionUtils.Contains(IEnumerable collection, object element)
b) returns 'null' in case of collection==null instead of throwing an exception
8. dropped Spring.Expressions.DateLiteralNode
Spring.Aop
----------
1. AbstractAutoProxyCreator.FindEligibleAdvisors(Type) changed to
AbstractAutoProxyCreator.FindEligibleAdvisors(Type, Name)
2. It is not possible to change a ProxyFactoryObject's product configuration at runtime
if IsSingleton==true since factory object singleton products get cached now.
Changes (1.2 RC1 to 1.2.0 or greater)
=====================================
none
Changes (1.1.2 to 1.2 RC1 or greater)
=====================================
Spring.Core
-----------
1. ContextRegistry.GetContext(string name) now throws an exception if no context has been registered under that name instead of returning null.
2. Removed getter property of IApplicationContext in IApplicationContextAware
3. Removed getter property of IResourceLoader in IResourceLoaderAware
4. AbstractBinding.IsValid property changed to method AbstractBinding.IsValid( IValidationErrors )
Spring.Data
-----------
1. The provider name System.Data.SqlServerCe is now aliased to SqlServerCe-3.5.1 (was SqlServerCe-3.1)
2. Removed setter property RollbackOnly on ITransactionStatus, now use the method SetRollbackOnly() to 'doom' a transaction to always rollback.
Spring.Services
---------------
1. Removed WebServiceProxyFactory.ClientProtocolType property (obsolete)
2. WebServiceExporter generates WebServiceBinding attribute with WSI basic profile 1.1 by default.
Spring.Web
----------
1. Moved Spring.Web.Support.ISharedStateAware to Spring.Objects.ISharedStateAware
2. Dropped IProcess support
3. IHttpHandler instance dependencies won't be injected until PreRequestHandlerExecute stage (to support "session"-scoped deps)