September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1198) NoClassDefFoundError when using str[endsWith] on a field that matches an imported class name

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1198?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-1198: ----------------------------------- Attachment: screenshot-fixed-650CR2andmaster.png > NoClassDefFoundError when using str[endsWith] on a field that matches an imported class name > -------------------------------------------------------------------------------------------- > > Key: DROOLS-1198 > URL: https://issues.jboss.org/browse/DROOLS-1198 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.4.0.Final > Reporter: Chris Austin > Assignee: Mario Fusco > Priority: Minor > Fix For: 7.0.0.Beta2 > > Attachments: DROOLS-1198-unabletoreproduce.zip, screenshot-640Final.png, screenshot-fixed-650CR2andmaster.png, screenshot-linux.png, screenshot-Mac.png > > > This error was triggered when accessing the user field with str[endsWith] when user is null: > java.lang.NoClassDefFoundError: mssp/io/model/user (wrong name: mssp/io/model/User) > Condition that triggers the error: > $a : Alert(user!=null, user str[endsWith] "$") > This does not trigger the error: > $a : Alert(user!=null, user matches ".+\\$") > If I remove the import for the User class the error will not be triggered. As a workaround I've switched to using matches instead of str[endsWith], but I'd prefer to switch back. > I did not experience this issue in 6.3.0-Final, so it appears to be a regression in 6.4.0-Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1198) NoClassDefFoundError when using str[endsWith] on a field that matches an imported class name

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1198?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-1198: ----------------------------------- Attachment: screenshot-640Final.png > NoClassDefFoundError when using str[endsWith] on a field that matches an imported class name > -------------------------------------------------------------------------------------------- > > Key: DROOLS-1198 > URL: https://issues.jboss.org/browse/DROOLS-1198 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.4.0.Final > Reporter: Chris Austin > Assignee: Mario Fusco > Priority: Minor > Fix For: 7.0.0.Beta2 > > Attachments: DROOLS-1198-unabletoreproduce.zip, screenshot-640Final.png, screenshot-linux.png, screenshot-Mac.png > > > This error was triggered when accessing the user field with str[endsWith] when user is null: > java.lang.NoClassDefFoundError: mssp/io/model/user (wrong name: mssp/io/model/User) > Condition that triggers the error: > $a : Alert(user!=null, user str[endsWith] "$") > This does not trigger the error: > $a : Alert(user!=null, user matches ".+\\$") > If I remove the import for the User class the error will not be triggered. As a workaround I've switched to using matches instead of str[endsWith], but I'd prefer to switch back. > I did not experience this issue in 6.3.0-Final, so it appears to be a regression in 6.4.0-Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7219) Wrong description of missing target-name in simple-permission-mapper

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7219?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7219: ----------------------------- Component/s: Security > Wrong description of missing target-name in simple-permission-mapper > -------------------------------------------------------------------- > > Key: WFLY-7219 > URL: https://issues.jboss.org/browse/WFLY-7219 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Jan Kalina > > In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7219) Wrong description of missing target-name in simple-permission-mapper

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7219?page=com.atlassian.jira.plugin.... ] Jan Kalina moved ELY-631 to WFLY-7219: -------------------------------------- Project: WildFly (was: WildFly Elytron) Key: WFLY-7219 (was: ELY-631) Affects Version/s: (was: 1.1.0.Beta9) > Wrong description of missing target-name in simple-permission-mapper > -------------------------------------------------------------------- > > Key: WFLY-7219 > URL: https://issues.jboss.org/browse/WFLY-7219 > Project: WildFly > Issue Type: Bug > Reporter: Ondrej Lukas > Assignee: Jan Kalina > > In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1333) Add protection in DsXmlDeployer to prevent from loading xml resource

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1333?page=com.atlassian.jira.plugin... ] Stefano Maestri reassigned JBJCA-1333: -------------------------------------- Assignee: Stefano Maestri > Add protection in DsXmlDeployer to prevent from loading xml resource > -------------------------------------------------------------------- > > Key: JBJCA-1333 > URL: https://issues.jboss.org/browse/JBJCA-1333 > Project: IronJacamar > Issue Type: Enhancement > Components: Deployer > Affects Versions: 1.2.7.Final > Reporter: COLLIGNON Thomas > Assignee: Stefano Maestri > Priority: Minor > Fix For: 1.2.8.Final > > > If we place a datasource.xml in a jar file, the class DsXmlDeployer will fail with "URI not hierarchical error", because it doesn't handle jar file. > The goal of this issue is prevent for loading jar file in DsXmlDeployer. > The second goal is to provide ability of overring DsXmlDeployer in custom deployer who extends this class. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1333) Add protection in DsXmlDeployer to prevent from loading xml resource

by COLLIGNON Thomas (JIRA)

COLLIGNON Thomas created JBJCA-1333: --------------------------------------- Summary: Add protection in DsXmlDeployer to prevent from loading xml resource Key: JBJCA-1333 URL: https://issues.jboss.org/browse/JBJCA-1333 Project: IronJacamar Issue Type: Enhancement Components: Deployer Affects Versions: 1.2.7.Final Reporter: COLLIGNON Thomas Priority: Minor Fix For: 1.2.8.Final If we place a datasource.xml in a jar file, the class DsXmlDeployer will fail with "URI not hierarchical error", because it doesn't handle jar file. The goal of this issue is prevent for loading jar file in DsXmlDeployer. The second goal is to provide ability of overring DsXmlDeployer in custom deployer who extends this class. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1331) Use connection-url to get database connection when connection properties for datasource-class is empty

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1331?page=com.atlassian.jira.plugin... ] Lin Gao resolved JBJCA-1331. ---------------------------- Resolution: Done > Use connection-url to get database connection when connection properties for datasource-class is empty > ------------------------------------------------------------------------------------------------------ > > Key: JBJCA-1331 > URL: https://issues.jboss.org/browse/JBJCA-1331 > Project: IronJacamar > Issue Type: Task > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.4.Final, 1.2.7.Final > Reporter: Lin Gao > Assignee: Lin Gao > Fix For: WildFly/IronJacamar 1.3.5.Final, 1.2.8.Final > > > Fixes of JBJCA-1312 will fail the old configuration where the connection-url is used. > In the compatibility point of view, we should try to use {{connection-url}} & {{driver-class}} to get the database connection if the connection properties are empty && datasource-class != null. A warning message should be printed to encourage users to use DataSource for database connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1331) Use connection-url to get database connection when connection properties for datasource-class is empty

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1331?page=com.atlassian.jira.plugin... ] Lin Gao updated JBJCA-1331: --------------------------- Fix Version/s: WildFly/IronJacamar 1.3.5.Final 1.2.8.Final Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/575, https://github.com/ironjacamar/ironjacamar/pull/577 (was: https://github.com/ironjacamar/ironjacamar/pull/575) Affects Version/s: 1.2.7.Final > Use connection-url to get database connection when connection properties for datasource-class is empty > ------------------------------------------------------------------------------------------------------ > > Key: JBJCA-1331 > URL: https://issues.jboss.org/browse/JBJCA-1331 > Project: IronJacamar > Issue Type: Task > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.4.Final, 1.2.7.Final > Reporter: Lin Gao > Assignee: Lin Gao > Fix For: WildFly/IronJacamar 1.3.5.Final, 1.2.8.Final > > > Fixes of JBJCA-1312 will fail the old configuration where the connection-url is used. > In the compatibility point of view, we should try to use {{connection-url}} & {{driver-class}} to get the database connection if the connection properties are empty && datasource-class != null. A warning message should be printed to encourage users to use DataSource for database connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-631) Wrong description of missing target-name in simple-permission-mapper

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-631?page=com.atlassian.jira.plugin.sy... ] Jan Kalina edited comment on ELY-631 at 9/26/16 10:53 AM: ---------------------------------------------------------- The problem is: * Subsystem does not know if Permission should have a name (depends on class name) * The Permission doesnt know anything about subsystem attributes (like target-name) Ideas: * Catch IllegalArgumentException in subsystem and if message/attribute match "name" (Permission param), rewrite to "target-name" (attribute in subsystem) ** Problem: IllegalArgumentException has the error message only, only whole error message comparison possible now... was (Author: honza889): The problem is: * Subsystem does not know if Permission should have a name (depends on class name) * The Permission doesnt know anything about subsystem attributes (like target-name) Ideas: * Catch IllegalArgumentException in subsystem and if message/attribute match "name" (Permission param), rewrite to "target-name" (attribute in subsystem) * Problem: IllegalArgumentException has the error message only, only whole error message comparison possible now... > Wrong description of missing target-name in simple-permission-mapper > -------------------------------------------------------------------- > > Key: ELY-631 > URL: https://issues.jboss.org/browse/ELY-631 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta9 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > > In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-631) Wrong description of missing target-name in simple-permission-mapper

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-631?page=com.atlassian.jira.plugin.sy... ] Jan Kalina edited comment on ELY-631 at 9/26/16 10:52 AM: ---------------------------------------------------------- The problem is: * Subsystem does not know if Permission should have a name (depends on class name) * The Permission doesnt know anything about subsystem attributes (like target-name) Ideas: * Catch IllegalArgumentException in subsystem and if message/attribute match "name" (Permission param), rewrite to "target-name" (attribute in subsystem) * Problem: IllegalArgumentException has the error message only, only whole error message comparison possible now... was (Author: honza889): The problem is: * Subsystem does not know if Permission should have a name (depends on class name) * The Permission doesnt know anything about subsystem attributes (like target-name) Ideas: * Catch IllegalArgumentException in subsystem and if message/attribute match "name" (Permission param), rewrite to "target-name" (attribute in subsystem) ? > Wrong description of missing target-name in simple-permission-mapper > -------------------------------------------------------------------- > > Key: ELY-631 > URL: https://issues.jboss.org/browse/ELY-631 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta9 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > > In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2016