removing tests since they have moved to eu.etaxonomy.taxeditor.remoting
Updated version in config files to 3.3.8-SNAPSHOT
Updated version in config files to 3.3.7
reintegrated redlist branch into trunk
Updated version in config files to 3.3.7-SNAPSHOT
Updated version in config files to 3.3.6
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
updating ehcache to 2.6.9
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.
added sourcepath to all cdm libs
Updated version in config files to 3.3.6-SNAPSHOT
Updated version in config files to 3.3.5
Updated version in config files to 3.3.5-SNAPSHOT
Updated version in config files to 3.3.4
.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...
Updated version in config files to 3.3.4-SNAPSHOT
Updated version in config files to 3.3.3
Updated version in config files to 3.3.3-SNAPSHOT
Updated version in config files to 3.3.2
CdmPersistentRemoteSource : implemented all source methods including save and delete CdmRemoteSourceException : new exception to deal with cdm source errors CdmRemoteSourceBase : added default constructor
CdmApplicationRemoteController : directly loads CdmApplicationRemoteConfiguration bean and sets configuration in hibernate classes CdmApplicationRemoteConfiguration : no longer need the bean name hack due to update in CdmApplicationRemoteController
isRemoting is no longer based on a bean in the application context, but the type of cdm source
cdm.datasources.xml : added test sources settings file CdmRemoteSourceTest, RemoteLazyLoadingTest : updated tests HttpInvokerServicesTest, CdmPersistentRemoteSourceTest, CdmApplicationRemoteControllerTest : new test classes for remoting RemoteApplicationConfigurationTest : no longer a real test, but a super class for remote tests
added new remote package
comments and javadoc
Adding CDM Remote Source set of classes to allow editor to connect to a remote cdmserver
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...
Updated version in config files to 3.3.2-SNAPSHOT
Updated version in config files to 3.3.1
added more tests for both lazy loading entities and collections
adding missing manifest file
setting application configuration and boolean remoting flag (bean) in hibernate proxy classes to differentiate local and remoting
removing unavailable extension eu.etaxonomy.cdm.remote.controller.csv
added remote collection method checks in addition to local for lists and sets
added test class for persistent collections and also a base class for configuringsetting up remote configuration.
added call to remoting with correct check
disabling remoting calls untill further investigation
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
RolesSourceProvider to enable activities by cdm roles and protecting bulkeditors and term editors - #4055 (action enablement adapts to the users granted authorities)
base implementation and configuration for securing the editor - #4055 (action enablement adapts to the users granted authorities)
updaed build properties to include source / resource files when packaging with maven
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
removing aspetcj capability and reverting to default
changed package name to be consistent with cdmlib remotingApplicationContext.xml : cleaning up component scan
removing Transient annotation - not required
erging from remoting-1.0 branch
move ChangeConceptToSynonym business logic from editor operation to service layer
Updated version in config files to 3.3.1-SNAPSHOT
merge-update fixes
merge-update from trunk
Updated version in config files to 3.3.0
updating to latest eclipse rcp indigo jars
undoing last commit
local eclipse version specific dependecy changes
adapting to latest model changes for change of package
Updated version in config files to 3.3.0-SNAPSHOT
reintegrated model changes from branch 3.3-MC-SNAPSHOT
merged trunk into branch