[JBoss JIRA] (WFLY-13588) Messaging should not expose its subsystem module to deployments
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13588?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13588:
--------------------------------
Description:
The messaging-activemq subsystem exposes its subsystem module to the deployment classloader. According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection. This is a very bad idea, as the deployment can then access all of the subsystem internals (including its dependents).
The correct way to do this is to create a separate module containing the CDI extension and its dependents and only expose this module to deployments.
was:
The messaging-activemq subsystem exposes its subsystem module to the deployment classloader. According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection. This is a very bad idea, as the deployment can then access all of the subsystem internals.
The correct way to do this is to create a separate module containing the CDI extension and its dependents and only expose this module to deployments.
> Messaging should not expose its subsystem module to deployments
> ---------------------------------------------------------------
>
> Key: WFLY-13588
> URL: https://issues.redhat.com/browse/WFLY-13588
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 20.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> The messaging-activemq subsystem exposes its subsystem module to the deployment classloader. According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection. This is a very bad idea, as the deployment can then access all of the subsystem internals (including its dependents).
> The correct way to do this is to create a separate module containing the CDI extension and its dependents and only expose this module to deployments.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13588) Messaging should not expose its subsystem module to deployments
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13588?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13588:
--------------------------------
Description:
The messaging-activemq subsystem exposes its subsystem module to the deployment classloader. According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection. This is a very bad idea, as the deployment can then access all of the subsystem internals (including its dependents).
The correct way to do this is to create a separate module containing userspace classes, including the CDI extension and its dependents. Only this module should ever be exposed to deployments.
was:
The messaging-activemq subsystem exposes its subsystem module to the deployment classloader. According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection. This is a very bad idea, as the deployment can then access all of the subsystem internals (including its dependents).
The correct way to do this is to create a separate module containing the CDI extension and its dependents and only expose this module to deployments.
> Messaging should not expose its subsystem module to deployments
> ---------------------------------------------------------------
>
> Key: WFLY-13588
> URL: https://issues.redhat.com/browse/WFLY-13588
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 20.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> The messaging-activemq subsystem exposes its subsystem module to the deployment classloader. According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection. This is a very bad idea, as the deployment can then access all of the subsystem internals (including its dependents).
> The correct way to do this is to create a separate module containing userspace classes, including the CDI extension and its dependents. Only this module should ever be exposed to deployments.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13588) Messaging should not expose its subsystem module to deployments
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13588?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13588:
--------------------------------
Description:
The messaging-activemq subsystem exposes its subsystem module to the deployment classloader. According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection. This is a very bad idea, as the deployment can then access all of the subsystem internals.
The correct way to do this is to create a separate module containing the CDI extension and its dependents and only expose this module to deployments.
was:
The messaging-activemq subsystem exposes its subsystem module to the deployment classloader. According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection.
The correct way to do this is to create a separate module containing the CDI extension and its dependents and only expose this module to deployments.
> Messaging should not expose its subsystem module to deployments
> ---------------------------------------------------------------
>
> Key: WFLY-13588
> URL: https://issues.redhat.com/browse/WFLY-13588
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 20.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> The messaging-activemq subsystem exposes its subsystem module to the deployment classloader. According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection. This is a very bad idea, as the deployment can then access all of the subsystem internals.
> The correct way to do this is to create a separate module containing the CDI extension and its dependents and only expose this module to deployments.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13588) Messaging should not expose its subsystem module to deployments
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13588?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13588:
--------------------------------
Description:
The messaging-activemq subsystem exposes its subsystem module to the deployment classloader. According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection.
The correct way to do this is to create a separate module containing the CDI extension and its dependents and only expose this module to deployments.
was:The messaging-activemq subsystem exposes its subsystem module to the deployment classloader. According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection. However, this is unnecessary, since the subsystem already has a DUP that registers the portable extension via the WeldCapability.
> Messaging should not expose its subsystem module to deployments
> ---------------------------------------------------------------
>
> Key: WFLY-13588
> URL: https://issues.redhat.com/browse/WFLY-13588
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 20.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> The messaging-activemq subsystem exposes its subsystem module to the deployment classloader. According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection.
> The correct way to do this is to create a separate module containing the CDI extension and its dependents and only expose this module to deployments.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13599) Admin console will not open - I added users
by Charles Herrick (Jira)
[ https://issues.redhat.com/browse/WFLY-13599?page=com.atlassian.jira.plugi... ]
Charles Herrick updated WFLY-13599:
-----------------------------------
Description:
Wildfly 18.0.1 final and Wildfly 20.0 final installed.
add-user.bat executed for admin and one other user.
Kie-server 7.38 war deployed to deployments. start server.
Admin console will not display. Error says "you have not yet added users".
Used: add-user -a -u admin -p **** -ro admin,kie-server,rest-all,kiemgmt
Got: Updated user 'admin' to file 'C:\Redhat\Wildfly18\standalone\configuration\application-users.properties'
Updated user 'admin' to file 'C:\Redhat\Wildfly18\domain\configuration\application-users.properties'
Updated user 'admin' with groups admin,kie-server,rest-all,kiemgmt to file 'C:\Redhat\Wildfly18\standalone\configuration\application-roles.properties'
Updated user 'admin' with groups admin,kie-server,rest-all,kiemgmt to file 'C:\Redhat\Wildfly18\domain\configuration\application-roles.properties'
Please help me get the admin console up.
was:
Wildfly 18.0.1 final and Wildfly 20.0 final installed.
add-user.bat executed for admin and one other user.
Kie-server 7.38 war deployed to deployments. start server.
Admin console will not display. Error says "you have not yet added users".
Used: add-user -a -u herrick -p **** -ro admin,kie-server,rest-all,kiemgmt
Got: Updated user 'admin' to file 'C:\Redhat\Wildfly18\standalone\configuration\application-users.properties'
Updated user 'admin' to file 'C:\Redhat\Wildfly18\domain\configuration\application-users.properties'
Updated user 'admin' with groups admin,kie-server,rest-all,kiemgmt to file 'C:\Redhat\Wildfly18\standalone\configuration\application-roles.properties'
Updated user 'admin' with groups admin,kie-server,rest-all,kiemgmt to file 'C:\Redhat\Wildfly18\domain\configuration\application-roles.properties'
Please help me get the admin console up.
> Admin console will not open - I added users
> -------------------------------------------
>
> Key: WFLY-13599
> URL: https://issues.redhat.com/browse/WFLY-13599
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 18.0.1.Final, 20.0.0.Final
> Reporter: Charles Herrick
> Assignee: Harald Pehl
> Priority: Major
>
> Wildfly 18.0.1 final and Wildfly 20.0 final installed.
> add-user.bat executed for admin and one other user.
> Kie-server 7.38 war deployed to deployments. start server.
> Admin console will not display. Error says "you have not yet added users".
> Used: add-user -a -u admin -p **** -ro admin,kie-server,rest-all,kiemgmt
> Got: Updated user 'admin' to file 'C:\Redhat\Wildfly18\standalone\configuration\application-users.properties'
> Updated user 'admin' to file 'C:\Redhat\Wildfly18\domain\configuration\application-users.properties'
> Updated user 'admin' with groups admin,kie-server,rest-all,kiemgmt to file 'C:\Redhat\Wildfly18\standalone\configuration\application-roles.properties'
> Updated user 'admin' with groups admin,kie-server,rest-all,kiemgmt to file 'C:\Redhat\Wildfly18\domain\configuration\application-roles.properties'
>
> Please help me get the admin console up.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13599) Admin console will not open - I added users
by Charles Herrick (Jira)
[ https://issues.redhat.com/browse/WFLY-13599?page=com.atlassian.jira.plugi... ]
Charles Herrick updated WFLY-13599:
-----------------------------------
Description:
Wildfly 18.0.1 final and Wildfly 20.0 final installed.
add-user.bat executed for admin and one other user.
Kie-server 7.38 war deployed to deployments. start server.
Admin console will not display. Error says "you have not yet added users".
Used: add-user -a -u herrick -p **** -ro admin,kie-server,rest-all,kiemgmt
Got: Updated user 'admin' to file 'C:\Redhat\Wildfly18\standalone\configuration\application-users.properties'
Updated user 'admin' to file 'C:\Redhat\Wildfly18\domain\configuration\application-users.properties'
Updated user 'admin' with groups admin,kie-server,rest-all,kiemgmt to file 'C:\Redhat\Wildfly18\standalone\configuration\application-roles.properties'
Updated user 'admin' with groups admin,kie-server,rest-all,kiemgmt to file 'C:\Redhat\Wildfly18\domain\configuration\application-roles.properties'
Please help me get the admin console up.
was:
Wildfly 18.0.1 final and Wildfly 20.0 final installed.
add-user.bat executed for admin and one other user.
Kie-server 7.38 war deployed to deployments. start server.
Admin console will not display. Error says "you have not yet added users".
Used: add-user -a -u admin -p admin -ro password! ,kie-server,rest-all,kiemgmt
Please help me get the admin console up.
> Admin console will not open - I added users
> -------------------------------------------
>
> Key: WFLY-13599
> URL: https://issues.redhat.com/browse/WFLY-13599
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 18.0.1.Final, 20.0.0.Final
> Reporter: Charles Herrick
> Assignee: Harald Pehl
> Priority: Major
>
> Wildfly 18.0.1 final and Wildfly 20.0 final installed.
> add-user.bat executed for admin and one other user.
> Kie-server 7.38 war deployed to deployments. start server.
> Admin console will not display. Error says "you have not yet added users".
> Used: add-user -a -u herrick -p **** -ro admin,kie-server,rest-all,kiemgmt
> Got: Updated user 'admin' to file 'C:\Redhat\Wildfly18\standalone\configuration\application-users.properties'
> Updated user 'admin' to file 'C:\Redhat\Wildfly18\domain\configuration\application-users.properties'
> Updated user 'admin' with groups admin,kie-server,rest-all,kiemgmt to file 'C:\Redhat\Wildfly18\standalone\configuration\application-roles.properties'
> Updated user 'admin' with groups admin,kie-server,rest-all,kiemgmt to file 'C:\Redhat\Wildfly18\domain\configuration\application-roles.properties'
>
> Please help me get the admin console up.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13599) Admin console will not open - I added users
by Charles Herrick (Jira)
Charles Herrick created WFLY-13599:
--------------------------------------
Summary: Admin console will not open - I added users
Key: WFLY-13599
URL: https://issues.redhat.com/browse/WFLY-13599
Project: WildFly
Issue Type: Bug
Components: Web Console
Affects Versions: 20.0.0.Final, 18.0.1.Final
Reporter: Charles Herrick
Assignee: Harald Pehl
Wildfly 18.0.1 final and Wildfly 20.0 final installed.
add-user.bat executed for admin and one other user.
Kie-server 7.38 war deployed to deployments. start server.
Admin console will not display. Error says "you have not yet added users".
Used: add-user -a -u admin -p admin -ro password! ,kie-server,rest-all,kiemgmt
Please help me get the admin console up.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5442) Key navigation failure in Descision table
by Anna Dupliak (Jira)
Anna Dupliak created DROOLS-5442:
------------------------------------
Summary: Key navigation failure in Descision table
Key: DROOLS-5442
URL: https://issues.redhat.com/browse/DROOLS-5442
Project: Drools
Issue Type: Bug
Components: Guided Decision Table Editor
Affects Versions: 7.39.0.Final
Reporter: Anna Dupliak
Assignee: Toni Rikkola
Attachments: arrow.webm, image-2020-06-18-15-04-15-605.png, image-2020-06-18-15-06-26-220.png
When user navigates among columns from Description to any other - he need to push right arrow key twice to skip a hidden column introduced recently for decision tables.
!image-2020-06-18-15-04-15-605.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5442) Key navigation failure in Descision table
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5442?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5442:
---------------------------------
Steps to Reproduce:
# Go for *guided decision* assert
# Create a row in the decision table
# Add a column in the decision table
# Press *Shift+Home* to navigate to the home (leftmost cell of the table)
# Navigate to the first fact value (second column)
Expect: First cell after description cell is highlighted
Actual description is highlighted
See [^arrow.webm]
was:
# Go for *guided decision* assert
# Create a row in the decision table
# Add a column in the decision table
# Press *Shift+Home* to navigate to the home (leftmost cell of the table)
# Navigate to the first fact value (second column)
Expect: First cell after description cell is highlighted
Actual description is highlighted
> Key navigation failure in Descision table
> -----------------------------------------
>
> Key: DROOLS-5442
> URL: https://issues.redhat.com/browse/DROOLS-5442
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.39.0.Final
> Reporter: Anna Dupliak
> Assignee: Toni Rikkola
> Priority: Major
> Labels: decision_table
> Attachments: arrow.webm, image-2020-06-18-15-04-15-605.png, image-2020-06-18-15-06-26-220.png
>
>
> When user navigates among columns from Description to any other - he need to push right arrow key twice to skip a hidden column introduced recently for decision tables.
> !image-2020-06-18-15-04-15-605.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13598) Hard coded dependencies from resource adapters to legacy security sercvies.
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13598?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFLY-13598:
-----------------------------------------
[~maeste] FYI - I am just having a look into this one now to see if it is something simple. Overall we still seem reliant on some services provided by the legacy security subsystem.
> Hard coded dependencies from resource adapters to legacy security sercvies.
> ---------------------------------------------------------------------------
>
> Key: WFLY-13598
> URL: https://issues.redhat.com/browse/WFLY-13598
> Project: WildFly
> Issue Type: Bug
> Components: JCA, Security
> Affects Versions: 20.0.0.Final
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> A resource adapter defined similar to:
>
> {code:xml}
> <resource-adapters>
> <resource-adapter id="myrar.rar">
> <archive>
> myrar.rar
> </archive>
> <connection-definitions>
> <connection-definition class-name="org.wildfly.test.MyRar" pool-name="connection-definition"/>
> </connection-definitions>
> </resource-adapter>
> </resource-adapters>
> {code}
> Leads to an error:
> {code}
> 13:48:11,932 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "resource-adapters"),
> ("resource-adapter" => "myrar.rar"),
> ("connection-definitions" => "connection-definition")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.security.subject-factory",
> "jboss.security.simple-security-manager"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.resourceadapters.ra.\"myrar.rar\".connection-definition is missing [jboss.security.simple-security-manager, jboss.security.subject-factory]"]
> }
> {code}
> Resources should not depend on legacy security by default as it may not be there.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years