What is an optimal configuration for a cluster to avoid shutting down the grid every time domain objects change?
Given a domain object DailyPrice with an interface Price in domain.jar and a function reading the domain object using its interface: This works but requires the cluster to be shut down: Scenario 1: domain.jar on system CLASSPATH, cluster shut down, domain.jar copied into locator/cluster_config/cluster, cluster restart Results: Geode deploys the domain.jar and everything works fine. Cost: Need to shut down rather than simply undeploy/ deploy. Scenario 2: domain.jar on system CLASSPATH, cluster stays up, AND domain.jar undeploy/ deploy Results: com.company.domain.DailyPrice cannot be cast to com.company.domain.Price Scenario 3: domain.jar on gfsh start server —classpath=domain.jar AND domain.jar undeploy/ deploy Results: com.company.domain.DailyPrice cannot be cast to com.company.domain.Price Scenario 4: No classpath AND domain.jar undeploy/ deploy Results: com.company.domain.DailyPrice cannot be cast to com.company.domain.Price Scenario 5: no classpath, cluster shut down, domain.jar copied into locator/cluster_config/cluster, cluster restart Results: com.company.domain.DailyPrice cannot be cast to com.company.domain.Price Is there a way to avoid the class path conflict and avoid bouncing the cluster? Thanks, Wes
