[JBoss JIRA] (ISPN-7417) Implement transcoding
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7417?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-7417:
----------------------------------------
When implementing transcoding, server tasks should be able to deal with cache instances exposing POJOs as opposed to byte[]. This is currently doable with compatibility mode but has some issues (e.g. ISPN-7710)
> Implement transcoding
> ---------------------
>
> Key: ISPN-7417
> URL: https://issues.jboss.org/browse/ISPN-7417
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Galder Zamarreño
> Assignee: Gustavo Fernandes
>
> The aim of this JIRA is to implement transcoding so that data of any type can be stored and it can be transformed on the fly, regardless of the endpoint. The work of the JIRA will be split into different subtasks to be able to split the work.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ISPN-7710) CompatibilityProtoStreamMarshaller can't be set in server
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7710?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-7710:
----------------------------------------
The reason why this is useful to do is to be able to run server tasks that rely on caches with non-primitive types.
> CompatibilityProtoStreamMarshaller can't be set in server
> ---------------------------------------------------------
>
> Key: ISPN-7710
> URL: https://issues.jboss.org/browse/ISPN-7710
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.0.0.Final
> Reporter: Galder Zamarreño
>
> Out of the box, it's impossible to set compatibility marshaller to {{org.infinispan.query.remote.CompatibilityProtoStreamMarshaller}} in server because {{org.infinispan.main}} classloader can't access that class.
> As [~dan.berindei] suggested in the mailing list, one way to avoid these kind of issues would be to allow class definitions to have {{slot:module:class}} format so that using the ModularClassResolver any class can be found.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ISPN-7710) CompatibilityProtoStreamMarshaller can't be set in server
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-7710:
--------------------------------------
Summary: CompatibilityProtoStreamMarshaller can't be set in server
Key: ISPN-7710
URL: https://issues.jboss.org/browse/ISPN-7710
Project: Infinispan
Issue Type: Bug
Components: Server
Affects Versions: 9.0.0.Final
Reporter: Galder Zamarreño
Out of the box, it's impossible to set compatibility marshaller to {{org.infinispan.query.remote.CompatibilityProtoStreamMarshaller}} in server because {{org.infinispan.main}} classloader can't access that class.
As [~dan.berindei] suggested in the mailing list, one way to avoid these kind of issues would be to allow class definitions to have {{slot:module:class}} format so that using the ModularClassResolver any class can be found.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ISPN-7709) Generate keystores/truststore during the test phase
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7709?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7709:
----------------------------------
Status: Open (was: New)
> Generate keystores/truststore during the test phase
> ---------------------------------------------------
>
> Key: ISPN-7709
> URL: https://issues.jboss.org/browse/ISPN-7709
> Project: Infinispan
> Issue Type: Bug
> Components: Security, Test Suite - Server
> Affects Versions: 9.0.0.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.1.0.Final
>
>
> The testsuite for both the Hot Rod client and the server include pre-built keystores. This causes a number of issues:
> - they only work with Oracle/OpenJDK and break with IBM JDK
> - there is very little information about how they were produced
> - they have built-in expirations which are causing failures
> By using the maven keytool plugin we can generate the certificates during the test phase. Pros:
> - uses the keytool packaged with the JDK which is being used by the build
> - "documents" the process for generating the certificates and avoids storing binary blobs in version control
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ISPN-7709) Generate keystores/truststore during the test phase
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-7709:
-------------------------------------
Summary: Generate keystores/truststore during the test phase
Key: ISPN-7709
URL: https://issues.jboss.org/browse/ISPN-7709
Project: Infinispan
Issue Type: Bug
Components: Security, Test Suite - Server
Affects Versions: 9.0.0.Final
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 9.1.0.Final
The testsuite for both the Hot Rod client and the server include pre-built keystores. This causes a number of issues:
- they only work with Oracle/OpenJDK and break with IBM JDK
- there is very little information about how they were produced
- they have built-in expirations which are causing failures
By using the maven keytool plugin we can generate the certificates during the test phase. Pros:
- uses the keytool packaged with the JDK which is being used by the build
- "documents" the process for generating the certificates and avoids storing binary blobs in version control
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years