[JBoss JIRA] (ISPN-9628) infinispan-commons MANIFEST doesn not include Multi-Release entry
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-9628:
-------------------------------------
Summary: infinispan-commons MANIFEST doesn not include Multi-Release entry
Key: ISPN-9628
URL: https://issues.jboss.org/browse/ISPN-9628
Project: Infinispan
Issue Type: Bug
Components: Build
Affects Versions: 9.3.3.Final, 9.4.0.Final
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 9.4.1.Final, 9.3.4.Final
The Multi-Release:true entry is present in infinispan-commons test-jar but not in the main jar.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (ISPN-8981) Generate Hot Rod parser automatically
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-8981?page=com.atlassian.jira.plugin.... ]
Diego Lovison closed ISPN-8981.
-------------------------------
> Generate Hot Rod parser automatically
> -------------------------------------
>
> Key: ISPN-8981
> URL: https://issues.jboss.org/browse/ISPN-8981
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 9.2.0.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Priority: Major
> Fix For: 9.4.0.Alpha1, 9.4.0.CR3
>
>
> This JIRA has two objectives:
> 1. reduce number of allocated objects
> 2. improve the parsing on server side to avoid chains of lambda mappings
> Manual parsing of Hot Rod protocol, invoking recursive methods that return {{Optional}}s or {{Optional<Optional<...>}}s seems to generate a lot of garbage. A better approach would be a finite state automaton that would read the byte stream and invoke callbacks.
> Such automaton can be generated from a high-level grammar as part of the build process.
> Along with these changes we can remove the {{Response}} abstraction and write responses directly as {{ByteBuf}}s.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months