Hi Romain, I'm working on the OSGi compatibility of Ignite. I appreciate your input.
I'm thinking about the situation you describe and I wonder if you're exporting Ignite as an OSGi service which is then consumed from other bundles. Under this situation, it would be quite easy to reproduce the behaviour you describe if Ignite is not resolving classes via the TCCL. Need to dig deeper into that. Off the top of my head, there are two alternatives to solve it: 1. Use the TCCL for marshalling/unmarshalling (if not already used) – we gotta be wary of possible regressions. 2. Create a special OSGi header Ignite-Export-Package so that bundles containing DTOs can expose packages to Ignite's marshallers. Regards, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Mon, Nov 2, 2015 at 9:56 AM, Gilles, Romain <romain.gil...@misys.com> wrote: > Hi all, > > I'm really interested in this issue: > https://issues.apache.org/jira/browse/IGNITE-1270 . We some stuff to make > it work in our osgi environment. The main issue for us now is the > serialization. I think it you will have to rework the OptimizedMarshaller > or any other marshaller that works with object that come from outside your > class space. > > We have try kryo that works. Kryo provide an extension point in order to > resolve the classes: > https://github.com/EsotericSoftware/kryo/blob/master/src/com/esotericsoftware/kryo/ClassResolver.java > . With this extension we are able to solve the problem of external classes. > The only issue with kryo is that some classes need a certain care in the > serialization process and therefore a specialized serializer. > > So I would like to know from the community what do think of changing the > way the optimized marshaller works or introducing the support of yet > another marshaller based on a kryo like technology? > > > Thanks in advance, > > > Best regards, > > > Romain. > > > PS: I'm ready to help in the both cases. > "Misys" is the trade name of the Misys group of companies. This email and > any attachments have been scanned for known viruses using multiple > scanners. This email message is intended for the named recipient only. It > may be privileged and/or confidential. If you are not the named recipient > of this email please notify us immediately and do not copy it or use it for > any purpose, nor disclose its contents to any other person. This email does > not constitute the commencement of legal relations between you and Misys. > Please refer to the executed contract between you and the relevant member > of the Misys group for the identity of the contracting party with which you > are dealing. >
