[infinispan-dev] Quick fix for ISPN-7710

[Adrian Nistor]

Yup. That's exactly what I'm proposing. But today I stopped working on 
it because of some PR reviewing for the release. I hope to restart it 
and have a PoC by tomorrow.

On 06/15/2017 04:06 PM, Sanne Grinovero wrote:
> On 15 June 2017 at 10:05, Adrian Nistor <anistor at redhat.com> wrote:
>> Hi Galder,
>>
>> this fix is acceptable for now as it quickly enables users to use
>> CompatibilityProtoStreamMarshaller (provided by Infinispan), but in the
>> long run we would want users to be able to specify a custom marshaller
>> class that comes from a user supplied module or even a deployment - the
>> general case.
>>
>> With the introduction of encoders and deprecation of compat mode we
>> still have the same class loading issue in the general case. So I
>> propose to refine a bit our approach and instead of specifying just a
>> class name we should use a naming schema like "moduleId:slot:className",
>> giving users the ability to specify a class that comes from a different
>> module or deployment. I'm currently experimenting with this. I'll come
>> back with results soon.
> Great idea!
> Can you also figure out how to identify loading something from the
> user deployment ?
> Maybe we could apply a simple convention, as in when the module
> identification is missing then we look into TCCL, while when it's
> provided we look for the specific module (exclusively) ?
>
> Thanks,
> Sanne
>
>> There are also other code bits that need to be deployed in the server
>> ASAP: protostream entity marshallers, lucene analyzers. I'm thinking
>> these could all benefit from the same solution.
>>
>> Btw, what is the relation between ISPN-7814 and ISPN-7710 ?
>>
>> Adrian
>>
>> On 06/14/2017 06:35 PM, Galder Zamarreño wrote:
>>> Hi all,
>>>
>>> I'm seeing more and more people trying to do stuff like I did in [1] WRT to running server tasks in server.
>>>
>>> One of the blockers is [2]. I know we have transcoding coming up but I wondered if we could implement the quick hack of referencing remote-query.server module from root org.infinispan module.
>>>
>>> So, in essence, adding the following to org/infinispan/main/module.xml:
>>>
>>>         <module name="org.infinispan.remote-query.server" optional="true"/>
>>>
>>> Once ISPN-7710 is in place, along with ISPN-7814, users can run the demos in [1] without a custom server build.
>>>
>>> Cheers,
>>>
>>> [1] https://github.com/infinispan-demos/swiss-transport-datagrid
>>> [2] https://issues.jboss.org/browse/ISPN-7710
>>> --
>>> Galder Zamarreño
>>> Infinispan, Red Hat
>>>
>>>
>>> _______________________________________________
>>> infinispan-dev mailing list
>>> infinispan-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev