[JBoss JIRA] (DROOLS-4747) DMN Editor: update data type tooltips to include text for the respective action.
by Elizabeth Clayton (Jira)
Elizabeth Clayton created DROOLS-4747:
-----------------------------------------
Summary: DMN Editor: update data type tooltips to include text for the respective action.
Key: DROOLS-4747
URL: https://issues.jboss.org/browse/DROOLS-4747
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Elizabeth Clayton
Assignee: Guilherme Gomes
Update DMN Data type tooltips to include the action that is being referred to along with the shortcut hint. For example: provide the action name in addition to the shortcut: "Edit (Ctrl+E)"; "Add (Ctrl+B)"... versus "Ctrl+E", "Ctrl+B" ...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool
by Elizabeth Clayton (Jira)
Elizabeth Clayton created DROOLS-4746:
-----------------------------------------
Summary: UX for DMN "quick test" tool
Key: DROOLS-4746
URL: https://issues.jboss.org/browse/DROOLS-4746
Project: Drools
Issue Type: Story
Components: DMN Editor
Reporter: Elizabeth Clayton
Assignee: Elizabeth Clayton
As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test.
When the user run the test he can get back the results of the DMN execution.
Moreover, it would be handy to add those input/output to an existing (or new) test scenario.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12733) EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-12733?page=com.atlassian.jira.plugin... ]
Cheng Fang commented on WFLY-12733:
-----------------------------------
[~brian.stansberry] can you comment on the above? Is it recommended to expose certain operations from a component area such as ejb to applications? If so the application will need to programmatically obtain management client and access certain management api to invoke the operation from within the application. Any related docs and examples will also be very helpful.
> EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment
> --------------------------------------------------------------------------------------
>
> Key: WFLY-12733
> URL: https://issues.jboss.org/browse/WFLY-12733
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Reporter: Rhuan Rocha
> Assignee: Cheng Fang
> Priority: Major
>
> The EJB Timer has a way to persist timers in a database using datasources. It is described [here|https://docs.jboss.org/author/display/WFLY10/EJB3+Clustered+Database...]. The database-data-store has an attribute called refresh-interval that define a time in milliseconds to refresh the timers reading the timers from database. Look this sample of configuration.
>
> {code:java}
> <data-stores>
> <file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/>
> <database-data-store name="clustered-store" datasource-jndi-name="java:/jdbc/MyDataSource" partition="timer" refresh-interval="60000" allow-execution="true"/>
> </data-stores>
> {code}
> The RFE is to Wildfly provide a way to force the refresh programmatically.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-259) Delete s2i-producers and s2i-universe project files during image build
by Jan Blizňák (Jira)
[ https://issues.jboss.org/browse/WFWIP-259?page=com.atlassian.jira.plugin.... ]
Jan Blizňák updated WFWIP-259:
------------------------------
Summary: Delete s2i-producers and s2i-universe project files during image build (was: Delete s2i-producers and s2i-universe during image build)
> Delete s2i-producers and s2i-universe project files during image build
> ----------------------------------------------------------------------
>
> Key: WFWIP-259
> URL: https://issues.jboss.org/browse/WFWIP-259
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Jan Blizňák
> Assignee: Jean Francois Denise
> Priority: Minor
>
> These files seem to be not needed after image is built:
> {code:java}
> /opt/jboss/container/wildfly/s2i/galleon/provisioning/jboss-s2i-producers/
> /opt/jboss/container/wildfly/s2i/galleon/provisioning/jboss-s2i-universe/
> {code}
> The artifacts themselves are already installed at galleon-m2-repository so these files ^ can be probably deleted during image build.
> {code:java}
> /opt/jboss/container/wildfly/s2i/galleon/galleon-m2-repository/org/jboss/universe/producer/s2i-producers/1.0.0.Final/
> /opt/jboss/container/wildfly/s2i/galleon/galleon-m2-repository/org/jboss/universe/s2i-universe/1.0.0.Final/
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-259) Delete s2i-producers and s2i-universe during image build
by Jan Blizňák (Jira)
Jan Blizňák created WFWIP-259:
---------------------------------
Summary: Delete s2i-producers and s2i-universe during image build
Key: WFWIP-259
URL: https://issues.jboss.org/browse/WFWIP-259
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Jan Blizňák
Assignee: Jean Francois Denise
These files seem to be not needed after image is built:
{code:java}
/opt/jboss/container/wildfly/s2i/galleon/provisioning/jboss-s2i-producers/
/opt/jboss/container/wildfly/s2i/galleon/provisioning/jboss-s2i-universe/
{code}
The artifacts themselves are already installed at galleon-m2-repository so these files ^ can be probably deleted during image build.
{code:java}
/opt/jboss/container/wildfly/s2i/galleon/galleon-m2-repository/org/jboss/universe/producer/s2i-producers/1.0.0.Final/
/opt/jboss/container/wildfly/s2i/galleon/galleon-m2-repository/org/jboss/universe/s2i-universe/1.0.0.Final/
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months