[JBoss JIRA] (ISPN-4769) XSD documentation generator does not handle some types (e.g. xs:list)
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-4769:
-------------------------------------
Summary: XSD documentation generator does not handle some types (e.g. xs:list)
Key: ISPN-4769
URL: https://issues.jboss.org/browse/ISPN-4769
Project: Infinispan
Issue Type: Bug
Components: Documentation-Core
Affects Versions: 7.0.0.Beta2
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 7.0.0.CR1
The XSD documentation generator does not handle xs:list simpleTypes and doesn't show documentation for restrictions.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-4763) Create a new status for when put/putIfAbsent/replace return the previous value
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4763?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-4763:
-----------------------------------
Status: Open (was: New)
> Create a new status for when put/putIfAbsent/replace return the previous value
> ------------------------------------------------------------------------------
>
> Key: ISPN-4763
> URL: https://issues.jboss.org/browse/ISPN-4763
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Protocols
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 7.0.0.CR1, 7.0.0.Final
>
>
> With the current protocol way of handling previous, the client needs to track the request's return previous flag value when it needs to decide whether to decode the previous value in the response or it.
> Doing this ties the decoder with the request made. It would be better for the put/putIfAbsent/replace operations to provide a different status code, say 0x04 for when the operation succeeds and the previous value follows. By doing this, the decode has all it needs to decode in the actual response, rather than having to remember what the request flag was.
> This can easily be fixed in Hot Rod 2.0 protocol.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months