EDIT

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

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

removing Transient annotation - not required

erging from remoting-1.0 branch

• adding new confugration / controller classes for remoting
• adding aspect and related aop.xml config file
• added aspect and spring remoting jars
• updated manifest , pom and classpath for the new dependencies