February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-714) Guvnor/BRMS removing multi-line for-loop innards

by Daniel Daniel (JIRA)

Daniel Daniel created DROOLS-714: ------------------------------------ Summary: Guvnor/BRMS removing multi-line for-loop innards Key: DROOLS-714 URL: https://issues.jboss.org/browse/DROOLS-714 Project: Drools Issue Type: Bug Reporter: Daniel Daniel Assignee: Mark Proctor Priority: Minor rule "Load all bundles" agenda-group "LoadBundles" salience 900 when $bundle : Bundle(processed == false) then $bundle.setProcessed(true); update($bundle); ScheduleDescriptor descriptor = ScheduleModule.parseSchedule($bundle); for (Days dd : descriptor.getDays()) { insert(dd); } end For this example above, when I save the freeform DRL, close, and open the rule, it deletes my "insert(dd);" line. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1249) preparedStatementCacheHitCount / preparedStatementCacheMissCount should be long

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1249: -------------------------------------- Summary: preparedStatementCacheHitCount / preparedStatementCacheMissCount should be long Key: JBJCA-1249 URL: https://issues.jboss.org/browse/JBJCA-1249 Project: IronJacamar Issue Type: Task Components: JDBC Affects Versions: 1.2.2.Final, 1.1.9.Final, 1.0.30.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.10.Final, 1.2.3.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1248) rar-info: XATransaction resource adapters should use a security domain for recovery

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1248: -------------------------------------- Summary: rar-info: XATransaction resource adapters should use a security domain for recovery Key: JBJCA-1248 URL: https://issues.jboss.org/browse/JBJCA-1248 Project: IronJacamar Issue Type: Task Components: AS Reporter: Jesper Pedersen Assignee: Johnathon Lee Fix For: 1.2.3.Final Currently {noformat} <recovery> <recover-credential> <user-name>blah</> <password>blah</> </> </> {noformat} is used -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4354) EJBs can't inherit a JDK8 default method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4354?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4354: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1193109, https://bugzilla.redhat.com/show_bug.cgi?id=1193119 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1193109) > EJBs can't inherit a JDK8 default method > ---------------------------------------- > > Key: WFLY-4354 > URL: https://issues.jboss.org/browse/WFLY-4354 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Jan Martiska > Assignee: David Lloyd > > If an EJB bean inherits a default method from an interface and doesn't override it, attempt to call this method fails with: > {noformat} > org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4354) EJBs can't inherit a JDK8 default method

by Jan Martiska (JIRA)

Jan Martiska created WFLY-4354: ---------------------------------- Summary: EJBs can't inherit a JDK8 default method Key: WFLY-4354 URL: https://issues.jboss.org/browse/WFLY-4354 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 9.0.0.Alpha1 Reporter: Jan Martiska Assignee: David Lloyd If an EJB bean inherits a default method from an interface and doesn't override it, attempt to call this method fails with: {noformat} org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit) {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4354) EJBs can't inherit a JDK8 default method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4354?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4354: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1193109 > EJBs can't inherit a JDK8 default method > ---------------------------------------- > > Key: WFLY-4354 > URL: https://issues.jboss.org/browse/WFLY-4354 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Jan Martiska > Assignee: David Lloyd > > If an EJB bean inherits a default method from an interface and doesn't override it, attempt to call this method fails with: > {noformat} > org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-713) Guvnor/BRMS not converting freeform DRL val == $var + 1 correctly

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-713?page=com.atlassian.jira.plugin... ] Michael Anstis resolved DROOLS-713. ----------------------------------- Resolution: Done > Guvnor/BRMS not converting freeform DRL val == $var + 1 correctly > ----------------------------------------------------------------- > > Key: DROOLS-713 > URL: https://issues.jboss.org/browse/DROOLS-713 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR4 > Reporter: Daniel Daniel > Assignee: Michael Anstis > Priority: Minor > > Here is a shorter version of my rule: > rule "X" > agenda-group "MyGroup" > salience 900 > when > $bundle : MyClass($protocolSequence : protocolSequence) > eval($protocolSequence != null) > $followupBundle : MyClass(protocolSequence == $protocolSequence + 1) > then > ... > end > When I save in BRMS's UI, it shows the "protocolSequence == $protocolSequence + 1" condition incorrectly. > It just shows [protocolSequence] [equal to] [Choose...] > And the Choose... dropdown gives me the names of my variables. > The source tab shows the correct DRL at least. So it is probably just a cosmetic issue, but it does mean I can only modify the rule using freeform DRL, which is not good for when I hand it over to the business users. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-713) Guvnor/BRMS not converting freeform DRL val == $var + 1 correctly

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-713?page=com.atlassian.jira.plugin... ] Michael Anstis commented on DROOLS-713: --------------------------------------- *drools/drools-workbench-models* (master) http://github.com/droolsjbpm/drools/commit/cf143ffbe (6.2.x) http://github.com/droolsjbpm/drools/commit/fe1c49b00 > Guvnor/BRMS not converting freeform DRL val == $var + 1 correctly > ----------------------------------------------------------------- > > Key: DROOLS-713 > URL: https://issues.jboss.org/browse/DROOLS-713 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR4 > Reporter: Daniel Daniel > Assignee: Michael Anstis > Priority: Minor > > Here is a shorter version of my rule: > rule "X" > agenda-group "MyGroup" > salience 900 > when > $bundle : MyClass($protocolSequence : protocolSequence) > eval($protocolSequence != null) > $followupBundle : MyClass(protocolSequence == $protocolSequence + 1) > then > ... > end > When I save in BRMS's UI, it shows the "protocolSequence == $protocolSequence + 1" condition incorrectly. > It just shows [protocolSequence] [equal to] [Choose...] > And the Choose... dropdown gives me the names of my variables. > The source tab shows the correct DRL at least. So it is probably just a cosmetic issue, but it does mean I can only modify the rule using freeform DRL, which is not good for when I hand it over to the business users. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4313) Clean-up tests which use Kerberos in the WildFly testsuite

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4313?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4313: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1189141|https://bugzilla.redhat.com/show_bug.cgi?id=1189141] from POST to MODIFIED > Clean-up tests which use Kerberos in the WildFly testsuite > ---------------------------------------------------------- > > Key: WFLY-4313 > URL: https://issues.jboss.org/browse/WFLY-4313 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > Clean up Kerberos tests and add an unified logic for skipping Kerberos test configurations which proved to be unstable/buggy. By a configuration here is meant combination of Java vendor, version and IP stack. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4353) Incompliant CDI behavior since WFLY-4185

by Arcadiy Ivanov (JIRA)

[ https://issues.jboss.org/browse/WFLY-4353?page=com.atlassian.jira.plugin.... ] Arcadiy Ivanov updated WFLY-4353: --------------------------------- Description: WFLY-4185/WFLY-4350 introduced an ability to specify producers in Servlet listeners and other non-EJB Java-EE components. This behavior is not compliant per CDI-spec, as discussed in WELD-1872. Specifically, "Servlet listeners are not considered beans (even though they support injection and interception)." Therefore, no producers should be registered on servlet listeners to ensure portable compliant behavior. However, pre-WFLY-4185 behavior is also not acceptable, since no warnings or errors are produced in response to encountering the producers in components that should have none and such components are ignored silently. Therefore, I propose: # Revert WFLY-4185 # Add ## at a minimum, warning-level log messages when encountering managed bean annotations for non-bean components; or ## fail the deployment for strict compliance with the spec when encountering managed bean annotations for non-bean components was: WFLY-4185/WFLY-4350 introduced an ability to specify producers in Servlet listeners and other non-EJB Java-EE components. This behavior is not compliant per CDI-spec, as discussed in WELD-1872. Specifically, "Servlet listeners are not considered beans (even though they support injection and interception)." Therefore, no producers should be registered on servlet listeners to ensure portable compliant behavior. However, current behavior is also not acceptable, since no warnings or errors are produced in response to encountering the producers in components that should have none. Therefore, I propose: # Revert WFLY-4185 # Add ## at a minimum, warning-level log messages when encountering managed bean annotations for non-bean components; or ## fail the deployment for strict compliance with the spec when encountering managed bean annotations for non-bean components > Incompliant CDI behavior since WFLY-4185 > ---------------------------------------- > > Key: WFLY-4353 > URL: https://issues.jboss.org/browse/WFLY-4353 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: Arcadiy Ivanov > Assignee: Stuart Douglas > Priority: Minor > > WFLY-4185/WFLY-4350 introduced an ability to specify producers in Servlet listeners and other non-EJB Java-EE components. > This behavior is not compliant per CDI-spec, as discussed in WELD-1872. > Specifically, "Servlet listeners are not considered beans (even though they support injection and interception)." Therefore, no producers should be registered on servlet listeners to ensure portable compliant behavior. > However, pre-WFLY-4185 behavior is also not acceptable, since no warnings or errors are produced in response to encountering the producers in components that should have none and such components are ignored silently. > Therefore, I propose: > # Revert WFLY-4185 > # Add > ## at a minimum, warning-level log messages when encountering managed bean annotations for non-bean components; or > ## fail the deployment for strict compliance with the spec when encountering managed bean annotations for non-bean components -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 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 February 2015