[jboss-jira] [JBoss JIRA] (WFLY-5012) Recent infinispan model changes break client compatibility

Heiko Braun (JIRA) issues at jboss.org
Mon Jul 27 09:32:03 EDT 2015


    [ https://issues.jboss.org/browse/WFLY-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093075#comment-13093075 ] 

Heiko Braun commented on WFLY-5012:
-----------------------------------

Another related problem: The alias resources are shown by default in :read-children-types

{noformat}
[domain at localhost:9990 /] /profile=full/subsystem=infinispan/cache-container=*/invalidation-cache=web:read-children-types
{
    "outcome" => "success",
    "result" => [
        "binary-keyed-jdbc-store",
        "component",
        "eviction",
        "expiration",
        "file-store",
        "locking",
        "mixed-keyed-jdbc-store",
        "remote-store",
        "store",
        "string-keyed-jdbc-store",
        "transaction"
    ]
}
{noformat}

but they are excluded from :read-resource-description 

{noformat}
[domain at localhost:9990 /] /profile=full/subsystem=infinispan/cache-container=*/invalidation-cache=web:read-resource-description
 [...]

 "children" => {
                "store" => {
                    "description" => "A persistent store for a cache.",
                    "model-description" => undefined
                },
                "component" => {
                    "description" => "A configuration component of a cache.",
                    "model-description" => undefined
                }
            }


{noformat}

> Recent infinispan model changes break client compatibility
> ----------------------------------------------------------
>
>                 Key: WFLY-5012
>                 URL: https://issues.jboss.org/browse/WFLY-5012
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Brian Stansberry
>            Priority: Blocker
>
> Formlery we could request the ../eviction=EVICTION resource. I assume that with the resource name change a transformer kicks that redirects the request to the ../component" => "eviction resource. The response header however contains the wrong address, which prevents clients to correlate the request with the response. In HAL this breaks the access control mechanism.
> {noformat}
> [domain at localhost:9990 /] /profile=full/subsystem=infinispan/cache-container=*/invalidation-cache=*/eviction=EVICTION:read-resource-description
> {
>     "outcome" => "success",
>     "result" => [{
>         "address" => [
>             ("profile" => "full"),
>             ("subsystem" => "infinispan"),
>             ("cache-container" => "*"),
>             ("invalidation-cache" => "*"),
>             ("component" => "eviction")
>         ],
>         "outcome" => "success",
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the jboss-jira mailing list