#5031 Update remoting code to be compatible with new common service collection calls
AbstractPersistentCollection : fixed loading of collection
MockCdmEntitySessionManager, MockCdmEntitySession, ICdmEntitySessionManager, ICdmEntitySession, CdmEntitySessionManager,
CdmEntitySession : added new load method with choice to update client object graph...
ICachedCommonService, CachedCommonServiceImpl : moved class to service package
CdmApplicationRemoteConfiguration, AbstractPersistentCollection, AbstractLazyInitializer : refactored package of CachedCommonService
CdmServiceRequestExecutor : added code for intercepting all services and loading returned objects into current session...
refactoring due to change in cache package name
moving all source files from the remoting project to the cdmlib project
moving code to remoting project
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
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
erging from remoting-1.0 branch