January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4217) JDR include system properties, jndi view, deployment module information

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFLY-4217?page=com.atlassian.jira.plugin.... ] Brad Maxwell updated WFLY-4217: ------------------------------- Affects Version/s: 9.0.0.Alpha1 > JDR include system properties, jndi view, deployment module information > ----------------------------------------------------------------------- > > Key: WFLY-4217 > URL: https://issues.jboss.org/browse/WFLY-4217 > Project: WildFly > Issue Type: Enhancement > Components: JDR > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > > JDR include system properties, jndi view, deployment module information -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-674) Rules with bigdecimal comparison not matched for certain values

by Joseph Alex (JIRA)

[ https://issues.jboss.org/browse/DROOLS-674?page=com.atlassian.jira.plugin... ] Joseph Alex edited comment on DROOLS-674 at 1/2/15 11:55 PM: ------------------------------------------------------------- We have a lot of spreadsheets with 100+ rules in each. was (Author: infiniuser): Thanks, we use decision tables. Does it mean each entry has to be suffixed with B manually in the spreadsheet or is there a better way? The variable that's mapped to these values is already defined as a BigDecimal. > Rules with bigdecimal comparison not matched for certain values > --------------------------------------------------------------- > > Key: DROOLS-674 > URL: https://issues.jboss.org/browse/DROOLS-674 > Project: Drools > Issue Type: Bug > Affects Versions: 5.5.0.Final, 6.2.0.CR3 > Reporter: Joseph Alex > Assignee: Mario Fusco > Priority: Minor > Attachments: BigDecimalTestFragment.java > > > For rules which compare BigDecimal inputs against a range considering 2 decimal place precision, match does not happen when the input equals certain upper bounds. Testcase attached. > The rules match when the upper bound is specified with a < condition instead of <= (i.e <70.00 instead of <=69.99) , which seem to indicate value seen by Drools is somewhere between the two. > Envrionment: > Drools : 5.5.0.Final > Java version : Java(TM) SE Runtime Environment (build 1.6.0_21-b06) > OS : CentOS release 6.1 (Final) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-674) Rules with bigdecimal comparison not matched for certain values

by Joseph Alex (JIRA)

[ https://issues.jboss.org/browse/DROOLS-674?page=com.atlassian.jira.plugin... ] Joseph Alex commented on DROOLS-674: ------------------------------------ Thanks, we use decision tables. Does it mean each entry has to be suffixed with B manually in the spreadsheet or is there a better way? The variable that's mapped to these values is already defined as a BigDecimal. > Rules with bigdecimal comparison not matched for certain values > --------------------------------------------------------------- > > Key: DROOLS-674 > URL: https://issues.jboss.org/browse/DROOLS-674 > Project: Drools > Issue Type: Bug > Affects Versions: 5.5.0.Final, 6.2.0.CR3 > Reporter: Joseph Alex > Assignee: Mario Fusco > Priority: Minor > Attachments: BigDecimalTestFragment.java > > > For rules which compare BigDecimal inputs against a range considering 2 decimal place precision, match does not happen when the input equals certain upper bounds. Testcase attached. > The rules match when the upper bound is specified with a < condition instead of <= (i.e <70.00 instead of <=69.99) , which seem to indicate value seen by Drools is somewhere between the two. > Envrionment: > Drools : 5.5.0.Final > Java version : Java(TM) SE Runtime Environment (build 1.6.0_21-b06) > OS : CentOS release 6.1 (Final) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-674) Rules with bigdecimal comparison not matched for certain values

by Joseph Alex (JIRA)

[ https://issues.jboss.org/browse/DROOLS-674?page=com.atlassian.jira.plugin... ] Joseph Alex commented on DROOLS-674: ------------------------------------ Thanks, we use decision tables. Does it mean each entry has to be suffixed with B manually in the spreadsheet or is there a better way? The variable that's mapped to these values is already defined as a BigDecimal. > Rules with bigdecimal comparison not matched for certain values > --------------------------------------------------------------- > > Key: DROOLS-674 > URL: https://issues.jboss.org/browse/DROOLS-674 > Project: Drools > Issue Type: Bug > Affects Versions: 5.5.0.Final, 6.2.0.CR3 > Reporter: Joseph Alex > Assignee: Mario Fusco > Priority: Minor > Attachments: BigDecimalTestFragment.java > > > For rules which compare BigDecimal inputs against a range considering 2 decimal place precision, match does not happen when the input equals certain upper bounds. Testcase attached. > The rules match when the upper bound is specified with a < condition instead of <= (i.e <70.00 instead of <=69.99) , which seem to indicate value seen by Drools is somewhere between the two. > Envrionment: > Drools : 5.5.0.Final > Java version : Java(TM) SE Runtime Environment (build 1.6.0_21-b06) > OS : CentOS release 6.1 (Final) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4217) JDR include system properties, jndi view, deployment module information

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-4217: ---------------------------------- Summary: JDR include system properties, jndi view, deployment module information Key: WFLY-4217 URL: https://issues.jboss.org/browse/WFLY-4217 Project: WildFly Issue Type: Enhancement Components: JDR Reporter: Brad Maxwell Assignee: Brad Maxwell JDR include system properties, jndi view, deployment module information -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1796) Creating a pooled-connection-factory via the CLI requires confusing syntax

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1796?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1796: ----------------------------------------------- Kyle Lape <klape(a)redhat.com> changed the Status of [bug 1178229|https://bugzilla.redhat.com/show_bug.cgi?id=1178229] from NEW to POST > Creating a pooled-connection-factory via the CLI requires confusing syntax > -------------------------------------------------------------------------- > > Key: WFLY-1796 > URL: https://issues.jboss.org/browse/WFLY-1796 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 8.0.0.Alpha3 > Reporter: Justin Bertram > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha4 > > > When creating a pooled-connection factory via the CLI the syntax for the "connector" is confusing. Here is a simple example: > {noformat} > /subsystem=messaging/hornetq-server=default/pooled-connection-factory=my-pooled-connection-factory/:add(connector={"in-vm" => "xyz"}, entries=["java:/MyPooledCF"]) > {noformat} > The "connector" wants a list of name-value pairs, but only the name is taken into consideration. This command results in this XML: > {noformat} > <pooled-connection-factory name="my-pooled-connection-factory"> > <connectors> > <connector-ref connector-name="in-vm"/> > </connectors> > <entries> > <entry name="java:/MyPooledCF"/> > </entries> > </pooled-connection-factory> > {noformat} > The "xyz" is completely unnecessary. > I believe this is because {{org.jboss.as.messaging.jms.ConnectionFactoryAttributes.Common#CONNECTOR}} is defined as a {{org.jboss.as.controller.SimpleMapAttributeDefinition}} and it should probably just be a {{org.jboss.as.controller.PrimitiveListAttributeDefinition}} when used in the pooled-connection-factory. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1796) Creating a pooled-connection-factory via the CLI requires confusing syntax

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1796?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1796: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1178229 > Creating a pooled-connection-factory via the CLI requires confusing syntax > -------------------------------------------------------------------------- > > Key: WFLY-1796 > URL: https://issues.jboss.org/browse/WFLY-1796 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 8.0.0.Alpha3 > Reporter: Justin Bertram > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha4 > > > When creating a pooled-connection factory via the CLI the syntax for the "connector" is confusing. Here is a simple example: > {noformat} > /subsystem=messaging/hornetq-server=default/pooled-connection-factory=my-pooled-connection-factory/:add(connector={"in-vm" => "xyz"}, entries=["java:/MyPooledCF"]) > {noformat} > The "connector" wants a list of name-value pairs, but only the name is taken into consideration. This command results in this XML: > {noformat} > <pooled-connection-factory name="my-pooled-connection-factory"> > <connectors> > <connector-ref connector-name="in-vm"/> > </connectors> > <entries> > <entry name="java:/MyPooledCF"/> > </entries> > </pooled-connection-factory> > {noformat} > The "xyz" is completely unnecessary. > I believe this is because {{org.jboss.as.messaging.jms.ConnectionFactoryAttributes.Common#CONNECTOR}} is defined as a {{org.jboss.as.controller.SimpleMapAttributeDefinition}} and it should probably just be a {{org.jboss.as.controller.PrimitiveListAttributeDefinition}} when used in the pooled-connection-factory. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3865) java:jboss/exported is not available in @PreDestroy methods during shutdown

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3865?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-3865: ----------------------------------- Or you can use a resource-ref to the *component* which binds the name you need. Or you can define a generic name for the required resource and then just bind a dummy value using @Resource or resource-ref for it. > java:jboss/exported is not available in @PreDestroy methods during shutdown > --------------------------------------------------------------------------- > > Key: WFLY-3865 > URL: https://issues.jboss.org/browse/WFLY-3865 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Affects Versions: 8.1.0.Final > Reporter: Kyle Lape > Assignee: Eduardo Martins > > With the following code in a class named e.g. {{JNDIBinderBean.java}} > {code:java} > private static final String name = "java:jboss/exported/JNDIBinderBean"; > private static final String value = "JNDIBinderBean instantiated at " + new Date(); > @PostConstruct > public void start() { > new InitialContext().rebind(name, value); > } > @PreDestroy > public void stop() { > new InitialContext().unbind(name); > } > {code} > When Wildfly shuts down, I get an error saying that the MSC service isn't available: > {noformat} > javax.naming.NamingException: JBAS011836: Could not resolve service > service jboss.naming.context.java.jboss.exported.JNDIBinderBean > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3865) java:jboss/exported is not available in @PreDestroy methods during shutdown

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3865?page=com.atlassian.jira.plugin.... ] David Lloyd edited comment on WFLY-3865 at 1/2/15 3:22 PM: ----------------------------------------------------------- You can also use @Resource and/or env-entry to bind things in a way the container can resolve. This is covered in EE.5.4.1 of the Java EE 7 platform specification. was (Author: dmlloyd): You can also use @Resource and and env-entry to bind things in a way the container can resolve. This is covered in EE.5.4.1.3 of the Java EE 7 platform specification. > java:jboss/exported is not available in @PreDestroy methods during shutdown > --------------------------------------------------------------------------- > > Key: WFLY-3865 > URL: https://issues.jboss.org/browse/WFLY-3865 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Affects Versions: 8.1.0.Final > Reporter: Kyle Lape > Assignee: Eduardo Martins > > With the following code in a class named e.g. {{JNDIBinderBean.java}} > {code:java} > private static final String name = "java:jboss/exported/JNDIBinderBean"; > private static final String value = "JNDIBinderBean instantiated at " + new Date(); > @PostConstruct > public void start() { > new InitialContext().rebind(name, value); > } > @PreDestroy > public void stop() { > new InitialContext().unbind(name); > } > {code} > When Wildfly shuts down, I get an error saying that the MSC service isn't available: > {noformat} > javax.naming.NamingException: JBAS011836: Could not resolve service > service jboss.naming.context.java.jboss.exported.JNDIBinderBean > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3865) java:jboss/exported is not available in @PreDestroy methods during shutdown

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3865?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-3865: ----------------------------------- You can also use @Resource and and env-entry to bind things in a way the container can resolve. This is covered in EE.5.4.1.3 of the Java EE 7 platform specification. > java:jboss/exported is not available in @PreDestroy methods during shutdown > --------------------------------------------------------------------------- > > Key: WFLY-3865 > URL: https://issues.jboss.org/browse/WFLY-3865 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Affects Versions: 8.1.0.Final > Reporter: Kyle Lape > Assignee: Eduardo Martins > > With the following code in a class named e.g. {{JNDIBinderBean.java}} > {code:java} > private static final String name = "java:jboss/exported/JNDIBinderBean"; > private static final String value = "JNDIBinderBean instantiated at " + new Date(); > @PostConstruct > public void start() { > new InitialContext().rebind(name, value); > } > @PreDestroy > public void stop() { > new InitialContext().unbind(name); > } > {code} > When Wildfly shuts down, I get an error saying that the MSC service isn't available: > {noformat} > javax.naming.NamingException: JBAS011836: Could not resolve service > service jboss.naming.context.java.jboss.exported.JNDIBinderBean > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 January 2015