[JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container "eventually required" rather than required.
by Richard Achmatowicz (JIRA)
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
13 years, 12 months
[JBoss JIRA] (JBRULES-3328) Add an API to allow access to the constraint occurrences of a solution
by David Glassborow (Created) (JIRA)
Add an API to allow access to the constraint occurrences of a solution
----------------------------------------------------------------------
Key: JBRULES-3328
URL: https://issues.jboss.org/browse/JBRULES-3328
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-planner
Affects Versions: FUTURE
Reporter: David Glassborow
Assignee: Mark Proctor
For a given solution, I'd like to show what constraint occurrences are in the working memory, and ideally which occurrences for each planning entity.
This allows end users to understand the schedule, in my experience otherwise they stop trusting the system.
Currently the demo harness uses an internal API to get this information, and I think it maybe getting the wrong WM, the values looked out of step with the solver last time I looked
--
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
13 years, 12 months