[JBoss JIRA] (ISPN-7425) Enable admins to delete configuration subsections
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7425?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7425:
--------------------------------------
Status: Open (was: New)
> Enable admins to delete configuration subsections
> -------------------------------------------------
>
> Key: ISPN-7425
> URL: https://issues.jboss.org/browse/ISPN-7425
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 9.0.0.Beta2
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.0.CR1
>
>
> We need to add the ability to remove configuration subsections (locking, expiration etc) and make it consistent across configuration screens.
> UI perspective: We could have a delete icon (red cross or trash can etc) in the "panel-title" div of the section that a user is editing. If the user chooses to delete this sections config, then they should be presented with a message screen saying "<section> has not been defined, would you like to define this now?" similar to how we ask users to define container security when they click on the security section. Similarly, if a user loads an existing config with a section undefined, the aforementioned message should be displayed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-7425) Enable admins to delete configuration subsections
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7425?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7425:
--------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/184
> Enable admins to delete configuration subsections
> -------------------------------------------------
>
> Key: ISPN-7425
> URL: https://issues.jboss.org/browse/ISPN-7425
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 9.0.0.Beta2
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.0.CR1
>
>
> We need to add the ability to remove configuration subsections (locking, expiration etc) and make it consistent across configuration screens.
> UI perspective: We could have a delete icon (red cross or trash can etc) in the "panel-title" div of the section that a user is editing. If the user chooses to delete this sections config, then they should be presented with a message screen saying "<section> has not been defined, would you like to define this now?" similar to how we ask users to define container security when they click on the security section. Similarly, if a user loads an existing config with a section undefined, the aforementioned message should be displayed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-6908) Display available JDBC datasources as a dropdown menu
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-6908?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic resolved ISPN-6908.
---------------------------------------
Fix Version/s: 9.0.0.CR1
Resolution: Done
> Display available JDBC datasources as a dropdown menu
> -----------------------------------------------------
>
> Key: ISPN-6908
> URL: https://issues.jboss.org/browse/ISPN-6908
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 9.0.0.Alpha3
> Reporter: Ryan Emerson
> Assignee: Vladimir Blagojevic
> Priority: Minor
> Fix For: 9.0.0.CR1
>
>
> Currently the name of JDBC datasources are entered manually by the user, this should be replaced with a select option that consists of the configured datasources.
> “/profile=clustered/subsystem=datasources/data-source=..."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-7438) Administration console - can't create cache from template with JDBC store
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7438?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7438:
--------------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.0.0.CR1
Resolution: Done
> Administration console - can't create cache from template with JDBC store
> -------------------------------------------------------------------------
>
> Key: ISPN-7438
> URL: https://issues.jboss.org/browse/ISPN-7438
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Beta2
> Reporter: Roman Macor
> Assignee: Ryan Emerson
> Fix For: 9.0.0.CR1
>
> Attachments: domain.xml
>
>
> Start domain with attached configuration (has a distributedCacheAsTemplate template with String key JDBC store) -> cache-container -> add cache -> set distributedCacheAsTemplate and check edit base configuration -> create cache -> create
> Error pop up:
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-2":"WFLYCTL0390: An invalid key 'is-new-node' has been supplied for parameter 'id-column'"}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-7438) Administration console - can't create cache from template with JDBC store
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7438?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7438:
-------------------------------
Status: Open (was: New)
> Administration console - can't create cache from template with JDBC store
> -------------------------------------------------------------------------
>
> Key: ISPN-7438
> URL: https://issues.jboss.org/browse/ISPN-7438
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Beta2
> Reporter: Roman Macor
> Assignee: Ryan Emerson
> Attachments: domain.xml
>
>
> Start domain with attached configuration (has a distributedCacheAsTemplate template with String key JDBC store) -> cache-container -> add cache -> set distributedCacheAsTemplate and check edit base configuration -> create cache -> create
> Error pop up:
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-2":"WFLYCTL0390: An invalid key 'is-new-node' has been supplied for parameter 'id-column'"}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month