[JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container "eventually required" rather than required.
12:25 p.m.
Richard Achmatowicz created AS7-3488:
----------------------------------------
Summary: Make default-cache attribute of cache-container "eventually
required" rather than required.
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you
create the cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So
under that covers, the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:25 p.m.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz updated AS7-3488:
-------------------------------------
Description:
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
was:
Can we remove the restriction that default-cache must be set when you
create the cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So
under that covers, the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
Make default-cache attribute of cache-container "eventually
required" rather than required.
-------------------------------------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:27 p.m.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3488:
------------------------------------------
Paul and I discussed the issue and here is one possible solution.
The cache-container=*:add() operation executes in two parts: the MODEL stage followed by
the RUNTIME stage. At the moment, the default-cache is a required attribute in both stages
and it is flagged as such in its AttributeDefinition. If we leave the attribute definition
as is, don't make it required in the MODEL stage, and make it required in the RUNTIME
stage, then we have these outcomes:
- the default-cache attribute will still be marked required in the description for users
to see
- if someone tries to execute a cache-container=*:add() command in isolation and does not
pass a default-cache attribute, it will fail because the RUNTIME stage requires it
- if someone executes a cache-container=*:add() command in a batch of commands, and that
batch contains a command to set the default-cache attribute, then the operation will not
fail, as by the time the MODEL stage completes, the attribute will be set
This is a one line change and it would seem to provide a workaround for what you want.
One other point: the cache-container resource does not have a start operation - when we
perform add, the cache container is configured, and installed as a service in ON_DEMAND
mode. It is only when the an application requests use of the cache container that
CacheContainerService.start() is called. The section of docs you referenced and which I
wrote are out of date. My apologies.
Make default-cache attribute of cache-container "eventually
required" rather than required.
-------------------------------------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:33 p.m.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3488:
------------------------------------------
I've made changes to CacheContainerAdd:
- in populatModel(), don't make default-cache a required attribute:
{noformat}
target.get(ModelKeys.DEFAULT_CACHE).set(source.get(ModelKeys.DEFAULT_CACHE));
{noformat}
- in performRuntime(), get the value of the default cache as follows:
{noformat}
String defaultCache = DEFAULT_CACHE.resolveModelAttribute(context, model).asString();
{noformat}
Testing with the CLI:
{noformat}
[nrla@lenovo bin]$ ./jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or
'help' for the list of supported commands.
[disconnected /] connect
[standalone@localhost:9999 /] /subsystem=infinispan/cache-container=fred:add()
{
"outcome" => "failed",
"failure-description" => "JBAS014746: default-cache may not be
null",
"rolled-back" => true
}
[standalone@localhost:9999 /] batch
[standalone@localhost:9999 / #] /subsystem=infinispan/cache-container=fred:add()
#1 /subsystem=infinispan/cache-container=fred:add()
[standalone@localhost:9999 / #]
/subsystem=infinispan/cache-container=fred:write-attribute(name=default-cache,value=wilma)
#2
/subsystem=infinispan/cache-container=fred:write-attribute(name=default-cache,value=wilma)
[standalone@localhost:9999 / #] list-batch
#1 /subsystem=infinispan/cache-container=fred:add()
#2
/subsystem=infinispan/cache-container=fred:write-attribute(name=default-cache,value=wilma)
[standalone@localhost:9999 / #] run-batch
The batch executed successfully.
{noformat}
So, if we execute the operation in isolation with no default-cache, it fails; if we
execute it in the context of a batch and supply the default-cache at some point in the
batch, if passes.
Make default-cache attribute of cache-container "eventually
required" rather than required.
-------------------------------------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:35 p.m.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3488:
------------------------------------------
I'm going to keep there caches in a topic branch for the time being. If this solution
is acceptable, let me know and i'll set up the pull request.
Make default-cache attribute of cache-container "eventually
required" rather than required.
-------------------------------------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:12 p.m.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on AS7-3488:
-----------------------------------
That doesn't make sense to me. At this point "wilma" is not a valid cache
name. Why is that better than leaving default-cache undefined?
Make default-cache attribute of cache-container "eventually
required" rather than required.
-------------------------------------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:36 p.m.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on AS7-3488:
-----------------------------------
Also, relying on batch mode is awkward from a usability standpoint.
Can't we solve the chicken and egg problem?
What if you add a required "default-cache-type" parameter to the add operation?
Then the add operation would just create a cache for the default-cache. The user would
probably need to go back and configure the new cache. But at least you would always
maintain a valid configuration.
So this would execute successfully:
{noformat}/subsystem=infinispan/cache-container=fred:add(default-cache=wilma,default-cache-type=LOCAL){noformat}
And read-resource would immediately look like this:
{noformat}/subsystem=infinispan/cache-container=fred/:read-resource(recursive=true,proxies=false,include-runtime=false,include-defaults=true)
{
"outcome" => "success",
"result" => {
"aliases" => undefined,
"default-cache" => "wilma",
"distributed-cache" => undefined,
"eviction-executor" => undefined,
"invalidation-cache" => undefined,
"jndi-name" => undefined,
"listener-executor" => undefined,
"replicated-cache" => undefined,
"replication-queue-executor" => undefined,
"start" => undefined,
"transport" => undefined,
"local-cache" => {"wilma" => {
"batching" => false,
"cache-mode" => "LOCAL",
"eviction" => undefined,
"expiration" => undefined,
"file-store" => undefined,
"jdbc-store" => undefined,
"locking" => undefined,
"name" => "wilma",
"remote-store" => undefined,
"store" => undefined,
"transaction" => undefined
}}
},
"response-headers" => {"process-state" =>
"reload-required"}
}{noformat}
Make default-cache attribute of cache-container "eventually
required" rather than required.
-------------------------------------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:40 p.m.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3488:
------------------------------------------
It's better in that you can now defer setting the default-cache name to some time
later in the batch and not when you perform the add command. But it still needs to be
there for the command to succeed. If we made default-cache undefined, the command could
succeed even though default-cache was left undefined.
If the fact that default-cache still does not correspond to an actual cache is the
problem, then we can add in a check to fail the operation if such a cache definition is
not present.
Make default-cache attribute of cache-container "eventually
required" rather than required.
-------------------------------------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:20 p.m.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on AS7-3488:
-----------------------------------
It's impossible for the cache to be present. You can't create the cache until you
create the cache container.
Is my proposed solution workable?
Make default-cache attribute of cache-container "eventually
required" rather than required.
-------------------------------------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:35 p.m.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3488:
------------------------------------------
As per the conf call, we decided to:
- do not make default-cache a required attribute
- if the attribute is not set during cacheContainerAdd, then set it when adding the first
cache (to the name of the first cache); the user can then override the value as and when
required
- consider throwing an exception during cache container start() to notify the user that
the default cache has not been set to a valid value
Make default-cache attribute of cache-container "eventually
required" rather than required.
-------------------------------------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:03 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz updated AS7-3488:
-------------------------------------
Summary: Make default-cache attribute of cache-container not required. (was: Make
default-cache attribute of cache-container "eventually required" rather than
required.)
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:09 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3488:
------------------------------------------
After discussion with Paul, we have only removed the restriction that default-cache be a
required attribute.
There are two remaining issues to deal with which are postponed to a later pull request:
- dealing with side effects of not defining a default cache
(DefaultEmbeddedCacheManager.getCache() and the fact that aliases for default cache will
not be available
- allowing changing of default-cache without reload-required state to be entered
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:45 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-3488:
---------------------------------------
Was this completed?
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.0.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:53 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz resolved AS7-3488.
--------------------------------------
Fix Version/s: 7.1.1.Final
(was: 7.1.0.Final)
Resolution: Done
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.1.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:53 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3488:
------------------------------------------
no - its a relatively complicated piece of work. Rescheduling for 7.1.1.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.1.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:09 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz reopened AS7-3488:
--------------------------------------
Mistakenly closed this issue, when I wanted to change the fix for version.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.1.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:57 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-3488:
------------------------------
Fix Version/s: 7.1.2.Final
(was: 7.1.1.Final)
This issue is being relocated to 7.1.2 so that 7.1.1 only contains criticals, blockers,
and EAP LA issues (which are probably not yet at the right status, or need an extra triage
pass).
If these issues are completed in a 7.1.1 timeframe please change the fix version. Although
if you forget I will bulk correct.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:02 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3488 at 3/5/12 8:02 PM:
------------------------------------------------------------------
Note to myself:
Looking at the code, if default-cache is not defined as a cache-container attribute, then
(briefly):
- CacheContainerAdd will create an EmbeddedCacheManagerConfigurationService with a
defaultCache value of null
- DefaultEmbeddedCacheManager, which is an AbstractDelegatingCacheManager, will have a
defaultCache value of null
- when we call DefaultEmbeddedCacheManager.getCache(), rather than returning the cache
corresponding to cache name defaultCache, it will return the cache corresponding to cache
name null, which is __default.
Thus, leaving default-cache undefined may cause no exception to be thrown, but the
application gets the DefaultCacheManager's default cache, which is __default. The
settings for the default cache will have been specified in the <default> section of
the cache manager configuration (as opposed to the <global> section.
So, if the subsystem does not set the default-cache for a cache container, it will get a
default cache none the less - but perhaps not the one desired.
was (Author: rachmato):
Note to nmyself:
Looking at the code, if default-cache is not defined as a cache-container attribute, then
(briefly):
- CacheContainerAdd will create an EmbeddedCacheManagerConfigurationService with a
defaultCache value of null
- DefaultEmbeddedCacheManager, which is an AbstractDelegatingCacheManager, will have a
defaultCache value of null
- when we call DefaultEmbeddedCacheManager.getCache(), rather than returning the cache
corresponding to cache name defaultCache, it will return the cache corresponding to cache
name null, which is __default.
Thus, leaving default-cache undefined may cause no exception to be thrown, but the
application gets the DefaultCacheManager's default cache, which is __default. The
settings for the default cache will have been specified in the <default> section of
the cache manager configuration (as opposed to the <global> section.
So, if the subsystem does not set the default-cache for a cache container, it will get a
default cache node the less - but perhaps not the one desired.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:02 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3488:
------------------------------------------
Note to nmyself:
Looking at the code, if default-cache is not defined as a cache-container attribute, then
(briefly):
- CacheContainerAdd will create an EmbeddedCacheManagerConfigurationService with a
defaultCache value of null
- DefaultEmbeddedCacheManager, which is an AbstractDelegatingCacheManager, will have a
defaultCache value of null
- when we call DefaultEmbeddedCacheManager.getCache(), rather than returning the cache
corresponding to cache name defaultCache, it will return the cache corresponding to cache
name null, which is __default.
Thus, leaving default-cache undefined may cause no exception to be thrown, but the
application gets the DefaultCacheManager's default cache, which is __default. The
settings for the default cache will have been specified in the <default> section of
the cache manager configuration (as opposed to the <global> section.
So, if the subsystem does not set the default-cache for a cache container, it will get a
default cache node the less - but perhaps not the one desired.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:18 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3488:
------------------------------------------
Note to myself:
Changing the default cache value should require some degree of restart: if we are in a
cluster with several cache-using app instances using the default cache, we change the
default cache and then a new member joins, the caches used will become out of sync.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:18 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3488 at 3/5/12 8:17 PM:
------------------------------------------------------------------
Note to myself:
Changing the default cache value should require some degree of restart: if we are in a
cluster with several cache-using app instances using the default cache, we change the
default cache and then a new member joins with no intervening restart, the caches used
will become out of sync.
was (Author: rachmato):
Note to myself:
Changing the default cache value should require some degree of restart: if we are in a
cluster with several cache-using app instances using the default cache, we change the
default cache and then a new member joins, the caches used will become out of sync.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:29 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3488 at 3/5/12 8:29 PM:
------------------------------------------------------------------
Note to myself:
Changing the default cache value should require some degree of restart: if we are in a
cluster with several cache-using app instances using the default cache, we change the
default cache and then a new member joins with no intervening restart, the caches used
will become out of sync.
Given the options for restarts (no-services, all-services, jvm, resource-services), rather
than restart all services in the system, we need only restart the services associated with
that cache container (i.e. restart-required => resource-services):
EmbeddedCacheManagerConfigurationService, DefaultEmbeddedCacheManagerService. This entails
shutting them down and then starting with the revised configuration.
was (Author: rachmato):
Note to myself:
Changing the default cache value should require some degree of restart: if we are in a
cluster with several cache-using app instances using the default cache, we change the
default cache and then a new member joins with no intervening restart, the caches used
will become out of sync.
Given the options for restarts (no-services, all-services, jvm, resource-services), rather
than restart all services in the system, we need only restart the services associated with
that cache container: EmbeddedCacheManagerConfigurationService,
DefaultEmbeddedCacheManagerService. This entails shutting them down and then starting with
the revised configuration.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:29 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3488 at 3/5/12 8:28 PM:
------------------------------------------------------------------
Note to myself:
Changing the default cache value should require some degree of restart: if we are in a
cluster with several cache-using app instances using the default cache, we change the
default cache and then a new member joins with no intervening restart, the caches used
will become out of sync.
Given the options for restarts (no-services, all-services, jvm, resource-services), rather
than restart all services in the system, we need only restart the services associated with
that cache container: EmbeddedCacheManagerConfigurationService,
DefaultEmbeddedCacheManagerService. This entails shutting them down and then starting with
the revised configuration.
was (Author: rachmato):
Note to myself:
Changing the default cache value should require some degree of restart: if we are in a
cluster with several cache-using app instances using the default cache, we change the
default cache and then a new member joins with no intervening restart, the caches used
will become out of sync.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:51 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3488 at 3/5/12 8:50 PM:
------------------------------------------------------------------
Note to myself:
Looking at the code, if default-cache is not defined as a cache-container attribute, then
(briefly):
- CacheContainerAdd will create an EmbeddedCacheManagerConfigurationService with a
defaultCache value of null
- DefaultEmbeddedCacheManager, which is an AbstractDelegatingCacheManager, will have a
defaultCache value of null
- when we call DefaultEmbeddedCacheManager.getCache(), rather than returning the cache
corresponding to cache name defaultCache, it will return the cache corresponding to cache
name null, which will correspond to the default cache of DefaultCacheManager, which is
__default.
Thus, leaving default-cache undefined may cause no exception to be thrown, but the
application gets the DefaultCacheManager's default cache, which is __default. The
settings for the default cache will have been specified in the <default> section of
the cache manager configuration (as opposed to the <global> section.
So, if the subsystem does not set the default-cache for a cache container, it will get a
default cache none the less - but perhaps not the one desired.
was (Author: rachmato):
Note to myself:
Looking at the code, if default-cache is not defined as a cache-container attribute, then
(briefly):
- CacheContainerAdd will create an EmbeddedCacheManagerConfigurationService with a
defaultCache value of null
- DefaultEmbeddedCacheManager, which is an AbstractDelegatingCacheManager, will have a
defaultCache value of null
- when we call DefaultEmbeddedCacheManager.getCache(), rather than returning the cache
corresponding to cache name defaultCache, it will return the cache corresponding to cache
name null, which is __default.
Thus, leaving default-cache undefined may cause no exception to be thrown, but the
application gets the DefaultCacheManager's default cache, which is __default. The
settings for the default cache will have been specified in the <default> section of
the cache manager configuration (as opposed to the <global> section.
So, if the subsystem does not set the default-cache for a cache container, it will get a
default cache none the less - but perhaps not the one desired.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:51 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3488 at 3/5/12 8:51 PM:
------------------------------------------------------------------
Note to myself:
Looking at the code, if default-cache is not defined as a cache-container attribute, then
(briefly):
- CacheContainerAdd will create an EmbeddedCacheManagerConfigurationService with a
defaultCache value of null
- DefaultEmbeddedCacheManager, which is an AbstractDelegatingCacheManager, will have a
defaultCache value of null
- when we call DefaultEmbeddedCacheManager.getCache(), rather than returning the cache
corresponding to cache name defaultCache, it will return the cache corresponding to cache
name null, which is __default.
Thus, leaving default-cache undefined may cause no exception to be thrown, but the
application gets the DefaultCacheManager's default cache, which is __default. The
settings for the default cache will have been specified in the <default> section of
the cache manager configuration (as opposed to the <global> section.
So, if the subsystem does not set the default-cache for a cache container, it will get a
default cache none the less - but perhaps not the one desired.
was (Author: rachmato):
Note to myself:
Looking at the code, if default-cache is not defined as a cache-container attribute, then
(briefly):
- CacheContainerAdd will create an EmbeddedCacheManagerConfigurationService with a
defaultCache value of null
- DefaultEmbeddedCacheManager, which is an AbstractDelegatingCacheManager, will have a
defaultCache value of null
- when we call DefaultEmbeddedCacheManager.getCache(), rather than returning the cache
corresponding to cache name defaultCache, it will return the cache corresponding to cache
name null, which will correspond to the default cache of DefaultCacheManager, which is
__default.
Thus, leaving default-cache undefined may cause no exception to be thrown, but the
application gets the DefaultCacheManager's default cache, which is __default. The
settings for the default cache will have been specified in the <default> section of
the cache manager configuration (as opposed to the <global> section.
So, if the subsystem does not set the default-cache for a cache container, it will get a
default cache none the less - but perhaps not the one desired.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:57 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3488 at 3/5/12 8:56 PM:
------------------------------------------------------------------
Note to myself:
Changing the default cache value should require some degree of restart: if we are in a
cluster with several cache-using app instances using the default cache, we change the
default cache and then a new member joins with no intervening restart, the caches used
will become out of sync.
Given the options for restarts (no-services, all-services, jvm, resource-services), rather
than restart all services in the system, we need only restart the services associated with
that cache container (i.e. restart-required => resource-services):
EmbeddedCacheManagerConfigurationService, DefaultEmbeddedCacheManagerService. This entails
shutting them down and then starting with the revised configuration.
The DEFAULT_CACHE attribute access flags are currently set to RESTART_ALL_SERVICES,
meaning that we need to perform a /:reload operation, but not a full JVM restart.
was (Author: rachmato):
Note to myself:
Changing the default cache value should require some degree of restart: if we are in a
cluster with several cache-using app instances using the default cache, we change the
default cache and then a new member joins with no intervening restart, the caches used
will become out of sync.
Given the options for restarts (no-services, all-services, jvm, resource-services), rather
than restart all services in the system, we need only restart the services associated with
that cache container (i.e. restart-required => resource-services):
EmbeddedCacheManagerConfigurationService, DefaultEmbeddedCacheManagerService. This entails
shutting them down and then starting with the revised configuration.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:16 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3488:
------------------------------------------
Note to myself:
Also, when we actually create the cache which has the same name as the default cache
attribute, two aliases are defined:
- CacheConfigurationService.getServiceName(container, null)
- CacheService.getServiceName(container, null)
which would be used when the default cache is looked up via the ServiceRegistry.
These aliases would need to be added when the attribute was updated.
It doesn't look as though you can add aliases to an already installed service from the
ServiceController, so it may mean removing the service and then reinstalling it.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:49 p.m.
New subject: [JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container not required.
[
https://issues.jboss.org/browse/AS7-3488?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry resolved AS7-3488.
-----------------------------------
Resolution: Done
AFAICT, this is done. If there's further work here, please open a separate JIRA for
7.2 for the remaining bits.
Make default-cache attribute of cache-container not required.
-------------------------------------------------------------
Key: AS7-3488
URL: https://issues.jboss.org/browse/AS7-3488
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.2.Final (EAP)
Can we remove the restriction that default-cache must be set when you create the
cache-container? That way, I can just make it so the UI
forces them to set that value before calling the start operation. So under that covers,
the console does this:
{noformat}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute
-->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable
resource and sets them via write-attribute -->
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack,
value=udp)
/subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout,
value=100)
<!-- When user is ready to start the cache-container, prompt for default-cache if not
set. -->
<!-- Then do these two as a batch -->
/subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y)
/subsystem=infinispan/cache-container=X:start(mode=on-demand)
{noformat}
Any thoughts on this? The answer has great implications on the UI design.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4629
days inactive
4730
days old
27 comments
4 participants
participants (4)
-
Brian Stansberry (JIRA) -
Jason Greene (JIRA)
-
Richard Achmatowicz (JIRA)
-
Stan Silvert (JIRA)