[JBoss JIRA] (DROOLS-5149) Able to specify a releaseId with KieHelper
by Toshiya Kobayashi (Jira)
Toshiya Kobayashi created DROOLS-5149:
-----------------------------------------
Summary: Able to specify a releaseId with KieHelper
Key: DROOLS-5149
URL: https://issues.redhat.com/browse/DROOLS-5149
Project: Drools
Issue Type: Enhancement
Components: core engine
Affects Versions: 7.34.0.Final
Reporter: Toshiya Kobayashi
Assignee: Toshiya Kobayashi
KieHelper builds a KieModule with a default releaseId org.default:artifact:1.0.0 and we cannot change it. It could be an issue when testing with multithread.
This JIRA is to add a method to specify a releaseId.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13216) /openapi throws 406 when Accept header is sufficiently complex
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13216?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13216:
--------------------------------
Description:
When accessing /openapi endpoint via Chrome, the following Accept header is sent:
Accept : text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
This should return a yaml document, as \*/\* is acceptable, though lower priority than, say, text/html.
This currently returns a 406 error.
was:
When accessing /openapi endpoint via Chrome, the following Accept header is sent:
Accept : text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
This should return a yaml document, as */* is acceptable, though lower priority than, say, text/html.
This currently returns a 406 error.
> /openapi throws 406 when Accept header is sufficiently complex
> --------------------------------------------------------------
>
> Key: WFLY-13216
> URL: https://issues.redhat.com/browse/WFLY-13216
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenAPI
> Affects Versions: 19.0.0.Beta3
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Blocker
>
> When accessing /openapi endpoint via Chrome, the following Accept header is sent:
> Accept : text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
> This should return a yaml document, as \*/\* is acceptable, though lower priority than, say, text/html.
> This currently returns a 406 error.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-5148) [DMN Designer] Copy/Paste is not working
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-5148?page=com.atlassian.jira.plug... ]
Guilherme Gomes updated DROOLS-5148:
------------------------------------
Description:
Ctrl + C / Ctrl + V is not working on DMN editor. When users try to copy and paste a node, the name and the boxed expression are not copied:
!demo.gif|width=600!
h5. Acceptance criteria
The copy/paste feature must work for text annotations, BKMs, decisions, Inputs, knowledge sources, and decision services.
was:
Ctrl + C / Ctrl + V is not working on DMN editor. When users try to copy and paste a node, the name and the boxed expression are not copied:
!demo.gif|width=600!
h5. Acceptance criteria
The copy/paste
> [DMN Designer] Copy/Paste is not working
> ----------------------------------------
>
> Key: DROOLS-5148
> URL: https://issues.redhat.com/browse/DROOLS-5148
> Project: Drools
> Issue Type: Bug
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: demo.gif
>
>
> Ctrl + C / Ctrl + V is not working on DMN editor. When users try to copy and paste a node, the name and the boxed expression are not copied:
> !demo.gif|width=600!
> h5. Acceptance criteria
> The copy/paste feature must work for text annotations, BKMs, decisions, Inputs, knowledge sources, and decision services.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-5148) [DMN Designer] Copy/Paste is not working
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-5148?page=com.atlassian.jira.plug... ]
Guilherme Gomes updated DROOLS-5148:
------------------------------------
Description:
Ctrl + C / Ctrl + V is not working on DMN editor. When users try to copy and paste a node, the name and the boxed expression are not copied:
!demo.gif|width=600!
h5. Acceptance criteria
The copy/paste
was:
Ctrl + C / Ctrl + V is not working on DMN editor. When users try to copy and paste a node, the name and the boxed expression are not copied:
!demo.gif|width=600!
> [DMN Designer] Copy/Paste is not working
> ----------------------------------------
>
> Key: DROOLS-5148
> URL: https://issues.redhat.com/browse/DROOLS-5148
> Project: Drools
> Issue Type: Bug
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: demo.gif
>
>
> Ctrl + C / Ctrl + V is not working on DMN editor. When users try to copy and paste a node, the name and the boxed expression are not copied:
> !demo.gif|width=600!
> h5. Acceptance criteria
> The copy/paste
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-5148) [DMN Designer] Copy/Paste is not working
by Guilherme Gomes (Jira)
Guilherme Gomes created DROOLS-5148:
---------------------------------------
Summary: [DMN Designer] Copy/Paste is not working
Key: DROOLS-5148
URL: https://issues.redhat.com/browse/DROOLS-5148
Project: Drools
Issue Type: Bug
Reporter: Guilherme Gomes
Assignee: Guilherme Gomes
Attachments: demo.gif
Ctrl + C / Ctrl + V is not working on DMN editor. When users try to copy and paste a node, the name and the boxed expression are not copied:
!demo.gif|width=600!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13221) Remove package-schema cruft from wildfly-feature-pack-build.xml files
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13221?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13221:
------------------------------------
Description:
The various wildfly-feature-pack-build.xml files include 'package-schemas' elements. AIUI the children of those elements only need to refer to maven groupId for which that specific feature pack provides artifacts with schemas. It does not need to include groupIds for artifacts from other f-ps that the f-p depends on. The WF galleon plugin itself combines those.
So the task is
1) to clean out cruft, i.e. elements that are related to artifacts from other feature packs. Helps clarify the expected use of these files.
2) Perhaps in the verifier tests for servlet-dist, ee-dist, dist add verification of the presence of 1 schema from each relevant maven groupId. Guard against schemas suddenly not getting picked up.
was:
The various wildfly-feature-pack-build.xml files include 'package-schemas' elements. AIUI the children of those elements only need to refer to maven groupId for which that specific feature pack provides artifacts with schemas. It does not need to include schemas from other f-ps that the f-p depends on; the WF galleon plugin itself combines those.
So the task is
1) to clean out cruft, i.e. elements that are related to artifacts from other feature packs. Helps clarify the expected use of these files.
2) Perhaps in the verifier tests for servlet-dist, ee-dist, dist add verification of the presence of 1 schema from each relevant maven groupId. Guard against schemas suddenly not getting picked up.
> Remove package-schema cruft from wildfly-feature-pack-build.xml files
> ---------------------------------------------------------------------
>
> Key: WFLY-13221
> URL: https://issues.redhat.com/browse/WFLY-13221
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: Brian Stansberry
> Assignee: Yeray Borges Santana
> Priority: Minor
>
> The various wildfly-feature-pack-build.xml files include 'package-schemas' elements. AIUI the children of those elements only need to refer to maven groupId for which that specific feature pack provides artifacts with schemas. It does not need to include groupIds for artifacts from other f-ps that the f-p depends on. The WF galleon plugin itself combines those.
> So the task is
> 1) to clean out cruft, i.e. elements that are related to artifacts from other feature packs. Helps clarify the expected use of these files.
> 2) Perhaps in the verifier tests for servlet-dist, ee-dist, dist add verification of the presence of 1 schema from each relevant maven groupId. Guard against schemas suddenly not getting picked up.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months