MANIFEST.MF : New apache http client packages added CdmServerInfo : changed name and added inner class for cdm instance httpInvokerServiceClients : added new services remotingApplicationContext : refactor for cache package
ICdmEntitySessionManager, CdmEntitySessionManager, MockCdmEntitySessionManager : removed cdm entity session access methods CdmServiceInterceptorException, CdmServiceRequestExecutor, TermServiceRequestExecutor : New executor classes to be used to execute intercept remote service requests starting with the term service...
moving all source files from the remoting project to the cdmlib project
clean up
remotingApplicationContext : now using the cachers from cdmlib CdmServiceCacher : added unimplemented method
CdmServiceCacher : Added class to load / cache CDM entities using services remotingApplicationContext : updated cacher bean config httpInvokerServiceClients : removed unnecessary loading of remote config CdmServiceCacherTest : added cacher test
remotingApplicationContext : added CdmCacher as bean to be initialised META-INF/MANIFEST.MF, .classpath, lib/ehcache-core-2.4.3.jar, lib/ehcache-core-2.6.9.jar: replaced ehcache-core-2.4.3 with ehcache-core-2.6.9 for the CdmCacher. It seems that even though hibernate-ehcache-4.1.10.Final is embedded with ehcache-core-2.4.3, it is compatible with ehcache-core-2.6.9 according to http://architects.dzone.com/articles/hibernate-4-and-ehcache-higher.
.classpath : added test resources in classpath CdmPersistentRemoteSourceTest : added new tests for remote source connection CdmRemoteSourceBase : added code to connect to the target database (before initialising the full application context) to retrieve metadata...
isRemoting is no longer based on a bean in the application context, but the type of cdm source
CdmApplicationRemoteConfiguration : removed spring bean name hack, since we now have a new controller CdmApplicationRemoteController : new Controller class to handle remoting AbstractLazyInitializer / AbstractPersistentCollection : added missing methods to check if proxy object is initialized...
setting application configuration and boolean remoting flag (bean) in hibernate proxy classes to differentiate local and remoting
RemoteLazyLoadingTest : Creating application configuration programmatically AbstractPersistentCollection, AbstractLazyInitializer : Copied aspect code here CdmApplicationRemoteConfiguration : overriding datasource since it is not required in remoting remotingApplicationContext : added autowiring config
CdmApplicationRemoteConfiguration : added GeoService and @Component bean name remotingApplicationContext : exclude CdmApplicationDefaultConfiguration from comp scan remoting_services_security : cosmetic httpInvokerServiceClients : added editGeoService config.properties : corrected context path...
reverting cdm application / controller refactoring and simply extending the CdmApplicationRemoteConfiguration class by throwing UnsupportedOperationException for methods that are not supported by remoting
changed package name to be consistent with cdmlib remotingApplicationContext.xml : cleaning up component scan
erging from remoting-1.0 branch