EDIT

isRemoting is no longer based on a bean in the application context, but
the type of cdm source

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...

setting application configuration and boolean remoting flag (bean) in hibernate proxy classes to differentiate local and remoting

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

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