Re: Server side cache configuration only
Hello! 2) Why? These classes will not be accessible by code running on Client. Regards, -- Ilya Kasnacheev пн, 27 янв. 2020 г. в 23:43, Sabar Banks : > Hello Ignite Community, > > My questions are: > > 1) Is it possible to only define cache configurations on the server side, > via xml, and avoid defining caches on the client side? > > 2) Is it possible to only have data bean classes listed in a cache config, > to ONLY exist on the server side physically? I am trying to only have the > bean definitions in one place: server. > > Let me know > > Thanks. > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Server side cache configuration only
Hi! 1) You do not need to have cache configuration on client side, I do that all the time. 2) Do not know Mikael Den 2020-01-27 kl. 21:42, skrev Sabar Banks: Hello Ignite Community, My questions are: 1) Is it possible to only define cache configurations on the server side, via xml, and avoid defining caches on the client side? 2) Is it possible to only have data bean classes listed in a cache config, to ONLY exist on the server side physically? I am trying to only have the bean definitions in one place: server. Let me know Thanks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Server side cache configuration only
Hello Ignite Community, My questions are: 1) Is it possible to only define cache configurations on the server side, via xml, and avoid defining caches on the client side? 2) Is it possible to only have data bean classes listed in a cache config, to ONLY exist on the server side physically? I am trying to only have the bean definitions in one place: server. Let me know Thanks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
