[JBoss JIRA] (DROOLS-3952) Can't use "Save" button if data types from another asset left unsaved
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3952?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3952:
--------------------------------
Steps to Reproduce:
# Create two dmn assets
# Open one and create data type, you can see the "Save" button is greyed out
# During editing leave it unsaved and go to another asset
# "Save" button still greyed out and It's not possible to use It
# As a solution you can go back to data type from which you start, edit It and save
was:
# Create two asset
# Open one and create data type, you can see the "Save" button is greyed out
# During editing leave it unsaved and go to another asset
# "Save" button still greyed out and It's not possible to use It
# As a solution you can go back to data type from which you start, edit It and save
> Can't use "Save" button if data types from another asset left unsaved
> ---------------------------------------------------------------------
>
> Key: DROOLS-3952
> URL: https://issues.jboss.org/browse/DROOLS-3952
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.21.0.Final
> Reporter: Yevgeniy Fomin
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> There is a problem with the "Save" button during editing data types and reconnecting to another asset
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12038) Expose the enable1Prefixes configuration on external (pooled) connection factories
by Emmanuel Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-12038?page=com.atlassian.jira.plugin... ]
Emmanuel Hugonnet updated WFLY-12038:
-------------------------------------
Summary: Expose the enable1Prefixes configuration on external (pooled) connection factories (was: Expose the enable1Prefixes configuration on external pooled connection factories)
> Expose the enable1Prefixes configuration on external (pooled) connection factories
> ----------------------------------------------------------------------------------
>
> Key: WFLY-12038
> URL: https://issues.jboss.org/browse/WFLY-12038
> Project: WildFly
> Issue Type: Feature Request
> Components: JMS
> Affects Versions: 16.0.0.Final
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> If we are connecting to a remote AMQ broker of version > 7.2 then we don't have to use the old prefixes for destinations already created on the broker.
> Exposing this property would enable a user to connect to a remote destination (already created on the remote broker) without these prefixes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12038) Expose the enable1Prefixes configuration on external pooled connection factories
by Emmanuel Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-12038?page=com.atlassian.jira.plugin... ]
Emmanuel Hugonnet moved EAP7-1247 to WFLY-12038:
------------------------------------------------
Project: WildFly (was: EAP 7 Planning Pilot)
Key: WFLY-12038 (was: EAP7-1247)
Issue Type: Feature Request (was: Requirement)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0)
Component/s: JMS
(was: JMS)
EAP PT Pre-Checked (PC): (was: TODO)
EAP PT Community Docs (CD): (was: TODO)
EAP PT Product Docs (PD): (was: New)
Affects Version/s: 16.0.0.Final
(was: 7.3.0.CD16)
EAP PT Test Dev (TD): (was: TODO)
EAP PT Docs Analysis (DA): (was: TODO)
EAP PT Test Plan (TP): (was: TODO)
EAP PT Analysis Document (AD): (was: TODO)
> Expose the enable1Prefixes configuration on external pooled connection factories
> --------------------------------------------------------------------------------
>
> Key: WFLY-12038
> URL: https://issues.jboss.org/browse/WFLY-12038
> Project: WildFly
> Issue Type: Feature Request
> Components: JMS
> Affects Versions: 16.0.0.Final
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> If we are connecting to a remote AMQ broker of version > 7.2 then we don't have to use the old prefixes for destinations already created on the broker.
> Exposing this property would enable a user to connect to a remote destination (already created on the remote broker) without these prefixes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months