Hi Gordon, Entity Java classes are not needed in .NET client classpath. Can you give an example when that does not work for you?
As for services, unfortunately, there is a limitation on Java side, Service class should be available on all nodes [1] [2]. Thanks, Pavel [1] https://apacheignite.readme.io/docs/service-grid [2] https://issues.apache.org/jira/browse/IGNITE-975 On Thu, Oct 26, 2017 at 9:51 AM, Gordon Reid (Nine Mile) < [email protected]> wrote: > Hi Igniters, > > > > We are running Ignite 2.2.0, we have a .NET client (runs in ignite client > mode) and Java servers. We call Ignite Services running on the Java side, > from the .NET client. We also access our memory grid entities from the .NET > client. Currently it seems we need to package our java server jar, publish > it to nuget, and then import this on the .NET side. If we don’t have the > entity and service classes available on the .NET side’s Java classpath then > we cannot communicate from the .NET side to the Java side. We are using the > binary marshaller and simple name mapper. > > > > Is there any way around this requirement? It is quite a hassle creating > this tight binary coupling between our .NET client and Java server. > > > > Thanks, > > Gordon. > > > > > > This email and any attachments are proprietary & confidential and are > intended solely for the use of the individuals to whom it is addressed. Any > views or opinions expressed are solely for those of the author and do not > necessarily reflect those of Nine Mile Financial Pty. Limited. If you have > received this email in error, please let us know immediately by reply email > and delete from your system. Nine Mile Financial Pty. Limited. ABN: 346 > 1349 0252 >
