[JBoss JIRA] (WFLY-11195) Module dependency on org.jboss.as.xts from org.jboss.xts should be optional.
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11195?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11195:
------------------------------------
Description:
The org.jboss.xts module depends on org.jboss.as.xts. It does to allow the WildflyTransactionClientTxBridgeIntegrationHandler class to be found after the XTS subsystem's XTSHandlerDeploymentProcessor wires it's name into the deployment.
But if there is no xts subsystem, then there's no XTSHandlerDeploymentProcessor and thus there's no wiring of the class name nor any need to load the class.
So, this dependency is optional and should be marked as such.
The reason this is important is that we currently have this dependency chain:
org.jboss.as.transactions/org.jboss.narayana.compensations/org.jboss.xts/org.jboss.as.xts/org.jboss.as.webservices.server.integration
And org.jboss.as.transactions is used from quite a lot of places. And that means this org.jboss.xts dependency brings the whole WS stack into a lot of places. Making this link optional will allow Galleon to optimize that away.
was:
The org.jboss.xts module depends on org.jboss.as.xts. It does so to allow the WildflyTransactionClientTxBridgeIntegrationHandler class can be found after the XTS subsystem's XTSHandlerDeploymentProcessor wires it's name into the deployment.
But if there is no xts subsystem, then there's no XTSHandlerDeploymentProcessor and thus there's no wiring of the class name nor any need to load the class.
So, this dependency is optional and should be marked as such.
The reason this is important is that we currently have this dependency chain:
org.jboss.as.transactions/org.jboss.narayana.compensations/org.jboss.xts/org.jboss.as.xts/org.jboss.as.webservices.server.integration
And org.jboss.as.transactions is used from quite a lot of places. And that means this org.jboss.xts dependency brings the whole WS stack into a lot of places. Making this link optional will allow Galleon to optimize that away.
> Module dependency on org.jboss.as.xts from org.jboss.xts should be optional.
> ----------------------------------------------------------------------------
>
> Key: WFLY-11195
> URL: https://issues.jboss.org/browse/WFLY-11195
> Project: WildFly
> Issue Type: Enhancement
> Components: XTS
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> The org.jboss.xts module depends on org.jboss.as.xts. It does to allow the WildflyTransactionClientTxBridgeIntegrationHandler class to be found after the XTS subsystem's XTSHandlerDeploymentProcessor wires it's name into the deployment.
> But if there is no xts subsystem, then there's no XTSHandlerDeploymentProcessor and thus there's no wiring of the class name nor any need to load the class.
> So, this dependency is optional and should be marked as such.
> The reason this is important is that we currently have this dependency chain:
> org.jboss.as.transactions/org.jboss.narayana.compensations/org.jboss.xts/org.jboss.as.xts/org.jboss.as.webservices.server.integration
> And org.jboss.as.transactions is used from quite a lot of places. And that means this org.jboss.xts dependency brings the whole WS stack into a lot of places. Making this link optional will allow Galleon to optimize that away.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11195) Module dependency on org.jboss.as.xts from org.jboss.xts should be optional.
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-11195:
---------------------------------------
Summary: Module dependency on org.jboss.as.xts from org.jboss.xts should be optional.
Key: WFLY-11195
URL: https://issues.jboss.org/browse/WFLY-11195
Project: WildFly
Issue Type: Enhancement
Components: XTS
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The org.jboss.xts module depends on org.jboss.as.xts. It does so to allow the WildflyTransactionClientTxBridgeIntegrationHandler class can be found after the XTS subsystem's XTSHandlerDeploymentProcessor wires it's name into the deployment.
But if there is no xts subsystem, then there's no XTSHandlerDeploymentProcessor and thus there's no wiring of the class name nor any need to load the class.
So, this dependency is optional and should be marked as such.
The reason this is important is that we currently have this dependency chain:
org.jboss.as.transactions/org.jboss.narayana.compensations/org.jboss.xts/org.jboss.as.xts/org.jboss.as.webservices.server.integration
And org.jboss.as.transactions is used from quite a lot of places. And that means this org.jboss.xts dependency brings the whole WS stack into a lot of places. Making this link optional will allow Galleon to optimize that away.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFCORE-4172) Add support for TLS 1.3
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/WFCORE-4172?page=com.atlassian.jira.plugi... ]
Farah Juma moved EAP7-1137 to WFCORE-4172:
------------------------------------------
Project: WildFly Core (was: EAP 7 Planning Pilot)
Key: WFCORE-4172 (was: EAP7-1137)
Issue Type: Feature Request (was: Requirement)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0)
Component/s: Security
(was: Security)
Jirban PT Pre-Checked (PC): (was: TODO)
Target Release: (was: 7.3.0.GA)
Jirban PT Community Docs (CD): (was: TODO)
Jirban PT Product Docs (PD): (was: New)
Jirban PT Test Dev (TD): (was: TODO)
Jirban PT Docs Analysis (DA): (was: TODO)
Jirban PT Test Plan (TP): (was: TODO)
Jirban PT Analysis Document (AD): (was: TODO)
> Add support for TLS 1.3
> -----------------------
>
> Key: WFCORE-4172
> URL: https://issues.jboss.org/browse/WFCORE-4172
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Farah Juma
> Assignee: Farah Juma
> Priority: Major
> Labels: eap-7.2.0-deferred
>
> It presently appears as though TLS 1.3 support could be available from Java 11.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3151) [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3151?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3151:
-------------------------------------
[~bdellasc] Here's a pic of the GDT, which has 4 colors.
!GDT.png|thumbnail!
> [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-3151
> URL: https://issues.jboss.org/browse/DROOLS-3151
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.13.0.Final
> Reporter: Edson Tirelli
> Assignee: Michael Anstis
> Priority: Major
> Labels: VisualDesign, drools-tools
> Attachments: GDT.png, dtable-column-colours.png
>
>
> [~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns.
> {quote}
> this is way too subtle, to be honest... can we get colours that are a bit more distinguishable?
> {quote}
> See the attached screenshot.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11194) NPE removing a pooled-connection-factory
by Claudio Miranda (Jira)
Claudio Miranda created WFLY-11194:
--------------------------------------
Summary: NPE removing a pooled-connection-factory
Key: WFLY-11194
URL: https://issues.jboss.org/browse/WFLY-11194
Project: WildFly
Issue Type: Bug
Components: JMS
Reporter: Claudio Miranda
Assignee: Jeff Mesnil
There is a NullPointerException when try to remove a pooled-connection-factory
{code}
/subsystem=messaging-activemq/in-vm-connector=invm1:add(server-id=123)
/subsystem=messaging-activemq/pooled-connection-factory=pool3:add(connectors=[invm1],entries=[foo])
/subsystem=messaging-activemq/pooled-connection-factory=pool3:remove()
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException",
"rolled-back" => true
}
{code}
{code}
15:46:19,661 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("remove") failed - address: ([
("subsystem" => "messaging-activemq"),
("pooled-connection-factory" => "pool3")
]): java.lang.NullPointerException
at org.wildfly.extension.messaging.activemq.jms.JMSServices.getPooledConnectionFactoryBaseServiceName(JMSServices.java:64)
at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryRemove.performRuntime(PooledConnectionFactoryRemove.java:56)
at org.jboss.as.controller.AbstractRemoveStepHandler$1.execute(AbstractRemoveStepHandler.java:84)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1411)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423)
at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3152) [DMN Designer] Context Expression can not be saved
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3152?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3152:
----------------------------------------
Sorry [~tari_manga] but your _fix_ for DROOLS-3116 has caused this regression.
The problem is that we need [this|https://github.com/kiegroup/kie-wb-common/commit/ba5aefec948af9f1167...] to ensure there is an expression on a {{ContextEntry}} (and other cases) when the file is saved. However we want to be able to differentiate [here|https://github.com/kiegroup/kie-wb-common/commit/ba5aefec948af9f1167...] between the mock {{LiteralExpression}} added in the foregoing (i.e. really there was a {{null}} expression) and a {{LiteralExpression}} that has an empty value.
Trisotech manage this in the follow way:
1) {{null}} Expression (i.e. empty {{ContextEntry}})
{{<dmn11:literalExpression/>}} (No *ID*)
2) Empty (no text, {{null text}}) {{LiteralExpression}}
{{<dmn11:literalExpression id="_6e353f23-efd5-4ee7-98e6-3593c7152555"/>}} (Has *ID*)
3) Empty String ({{""}}) {{LiteralExpression}}
{code}
<dmn11:literalExpression id="_8d494cba-437c-46d6-ab72-7d5a743335f0">
<dmn11:text>""</dmn11:text>
</dmn11:literalExpression>
{code}
> [DMN Designer] Context Expression can not be saved
> --------------------------------------------------
>
> Key: DROOLS-3152
> URL: https://issues.jboss.org/browse/DROOLS-3152
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Matteo Mortari
> Priority: Blocker
> Labels: drools-tools
> Attachments: Screenshot from 2018-10-16 15-03-23.png, error.log
>
>
> User can not save DMN diagram if it contains a decision node with *Context* as top level expression.
> Spotted during DROOLS-3109 review, however not 100% sure it is the root cause.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3151) [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3151?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3151:
-------------------------------------
[~bdellasc] In the event that you can help with this I pulled out some key points from channel chats that might be helpful in providing CSS RGB values (#RRGGBB style) for DMN Decision Tables (and possibly Simulation Testing GIVEN and EXPECTED blocks).
Goals:
- clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type - row number column, description column etc and for Sim Test: GIVEN columns and EXPECTED columns - and possibly a third "general" type for row number, description etc
- need cell/column background (and header background, if you like - I can have different colours for the cell background and header background) for 2 (or 3) different types of column. IDK if that's any clearer but like you can have "striped odd/even rows" think we need something similar for columns (but not striped as such)
> [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-3151
> URL: https://issues.jboss.org/browse/DROOLS-3151
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.13.0.Final
> Reporter: Edson Tirelli
> Assignee: Michael Anstis
> Priority: Major
> Labels: VisualDesign, drools-tools
> Attachments: dtable-column-colours.png
>
>
> [~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns.
> {quote}
> this is way too subtle, to be honest... can we get colours that are a bit more distinguishable?
> {quote}
> See the attached screenshot.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3152) [DMN Designer] Context Expression can not be saved
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3152?page=com.atlassian.jira.plugi... ]
Michael Anstis reassigned DROOLS-3152:
--------------------------------------
Assignee: Matteo Mortari (was: Michael Anstis)
> [DMN Designer] Context Expression can not be saved
> --------------------------------------------------
>
> Key: DROOLS-3152
> URL: https://issues.jboss.org/browse/DROOLS-3152
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Matteo Mortari
> Priority: Blocker
> Labels: drools-tools
> Attachments: Screenshot from 2018-10-16 15-03-23.png, error.log
>
>
> User can not save DMN diagram if it contains a decision node with *Context* as top level expression.
> Spotted during DROOLS-3109 review, however not 100% sure it is the root cause.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months