-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ClassNotFound in CacheProviderImpl when using 3.12 #1
Comments
@bpaskin-ibm I had added the You would need to build from that branch to make it work. IIRC it was not working fully and also note that it is for an old version of Hazelcast (3.8). |
Hi, thanks for the info. I am receiving an error on the mvn build. It would seem that the Hazelcast-client-protocol 1.3 snapshot is missing from the sonatype.
Thanks, Brian |
I guess you could try client protocol version 1.3.0, I don't remember I have needed any changes to the client protocol for it to work. |
Hi, I am just running maven with the POM provided. I did try others and it fails in various parts. |
Hi @bpaskin-ibm , Just out of curiosity, what is your use case with hazelcast-dynacache integration and where do you plan to use it? |
Hi, a customer is moving from tWAS to Liberty and was using the distributed Object Cache in tWAS, which is not available in Liberty. They do not want to change their code, so they were looking for a way to do it with a third party library. This is were Hazelcast comes in with this feature. I don't know the statistics of usage, but it is an important app for the customer. Thanks Brian |
Thanks for the info. We will be looking into the issue. Can we talk about this in detail on a call or in email? I would like to understand the details of the integration. |
@bpaskin-ibm; as a workaround, you can use the The issue with the |
Fixed by #2, where |
When pulling down the latest Hazelcast bundle and compiling some of the classes of been changed or removed. The 'CacheProviderImpl' class imports
com.hazelcast.client.osgi.HazelcastClientOSGiService
, but that would seem to have been moved tocom.hazelcast.osgi.HazelcastOSGiService
or removed. Updating the class to reflect this causes another issue with the configuration:Incompatible types: com.hazelcast.client.config.ClientConfig cannot be converted to com.hazelcast.config.Config
on the linehazelcastClientInstance = hazelcastClientOSGIService.newHazelcastInstance(config);'
I have not looked into the config issue yet, but I suspect it is not the exact same or has changed.
Brian
The text was updated successfully, but these errors were encountered: