[JBoss JIRA] (DROOLS-3018) [DMN Designer] Data Types - Constraints - None option component
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3018?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3018:
--------------------------------
Description:
- When "None" is selected in the _Base Component_, no constraint must be set in the Data Type and no element should be loaded in the _Base Component_.
h2. Acceptance test
h3. Manage Custom Data Type dialog
- When *none* constraint selected, other input elements for constraints are hidden
- When *none* constraint selected, other input elements for constraints are disabled
h3. Output Data Type select box
- When *none* constraint selected, other input elements for constraints are hidden
- When *none* constraint selected, other input elements for constraints are disabled
was:- When "None" is selected in the _Base Component_, no constraint must be set in the Data Type and no element should be loaded in the _Base Component_.
> [DMN Designer] Data Types - Constraints - None option component
> ---------------------------------------------------------------
>
> Key: DROOLS-3018
> URL: https://issues.jboss.org/browse/DROOLS-3018
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: edit-decision.png
>
>
> - When "None" is selected in the _Base Component_, no constraint must be set in the Data Type and no element should be loaded in the _Base Component_.
> h2. Acceptance test
> h3. Manage Custom Data Type dialog
> - When *none* constraint selected, other input elements for constraints are hidden
> - When *none* constraint selected, other input elements for constraints are disabled
> h3. Output Data Type select box
> - When *none* constraint selected, other input elements for constraints are hidden
> - When *none* constraint selected, other input elements for constraints are disabled
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (WFLY-11072) domain="undefined" in JSESSIONIDSSO
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created WFLY-11072:
-------------------------------------
Summary: domain="undefined" in JSESSIONIDSSO
Key: WFLY-11072
URL: https://issues.jboss.org/browse/WFLY-11072
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 14.0.0.Final
Reporter: Hisanobu Okuda
Assignee: Stuart Douglas
When SSO is enabled and the domain is undefined, the JSESSIONIDSSO cookie has a invalid domain="undefined" as follows:
{code}
Set-Cookie: JSESSIONIDSSO=H_xYotFv_g4dUibKUXxkK5zaFx-IESzIHHDvmeEW; path=/; domain=undefined
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (WFLY-11071) domain="undefined" in JSESSIONIDSSO
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created WFLY-11071:
-------------------------------------
Summary: domain="undefined" in JSESSIONIDSSO
Key: WFLY-11071
URL: https://issues.jboss.org/browse/WFLY-11071
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 14.0.0.Final
Reporter: Hisanobu Okuda
Assignee: Stuart Douglas
When SSO is enabled and the domain is undefined, the JSESSIONIDSSO cookie has a invalid domain="undefined" as follows:
{code}
Set-Cookie: JSESSIONIDSSO=H_xYotFv_g4dUibKUXxkK5zaFx-IESzIHHDvmeEW; path=/; domain=undefined
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (WFLY-10638) Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-10638?page=com.atlassian.jira.plugin... ]
Paul Ferraro commented on WFLY-10638:
-------------------------------------
[~smarlow] It means we should remove the <transaction/> configuration from our default hibernate cache configuration.
> Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-10638
> URL: https://issues.jboss.org/browse/WFLY-10638
> Project: WildFly
> Issue Type: Task
> Components: Clustering, JPA / Hibernate
> Affects Versions: 13.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
>
> Currently, during deployment of ORM 5.3.* applications, the following warning is logged in the server console, four times per persistence unit. It should not appear at all.
> {quote}
> HHH025030: Transactional caches are not supported. The configuration option will be ignored; please unset.
> {quote}
> The warning comes from ORM 5.3 integration code org.infinispan.hibernate.cache.v53.InfinispanRegionFactory#unsetTransactions.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (WFLY-10638) Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-10638?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-10638:
-------------------------------------
[~rvansa] what does the "Transactional caches are not supported" warning mean for WildFly users?
Should WildFly users that deploy applications using an Infinispan second level cache, make a persistence.xml configuration change to address this warning?
> Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-10638
> URL: https://issues.jboss.org/browse/WFLY-10638
> Project: WildFly
> Issue Type: Task
> Components: Clustering, JPA / Hibernate
> Affects Versions: 13.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
>
> Currently, during deployment of ORM 5.3.* applications, the following warning is logged in the server console, four times per persistence unit. It should not appear at all.
> {quote}
> HHH025030: Transactional caches are not supported. The configuration option will be ignored; please unset.
> {quote}
> The warning comes from ORM 5.3 integration code org.infinispan.hibernate.cache.v53.InfinispanRegionFactory#unsetTransactions.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (WFLY-11070) Fix JSR77 subsystem use of ModelController
by Brian Stansberry (JIRA)
Brian Stansberry created WFLY-11070:
---------------------------------------
Summary: Fix JSR77 subsystem use of ModelController
Key: WFLY-11070
URL: https://issues.jboss.org/browse/WFLY-11070
Project: WildFly
Issue Type: Bug
Components: Management
Reporter: Brian Stansberry
Assignee: Jeff Mesnil
Priority: Minor
The ModelReader class is getting a direct reference to a ModelController and invoking execute on it. At this point I think this is the only such use of ModelController outside the management kernel. If it can use ModelControllerClientFactory to get a local client that would be better. I haven't thought hard but don't believe it should be a SuperUser client as this code is used to service end user requests.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months