EDIT

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

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

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

added more tests for both lazy loading entities and collections

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

added remote collection method checks in addition to local for lists and sets