January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-703) HttpHandlers configuration for EJB3 Webservice Endpoints

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-703?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar commented on WFLY-703: ---------------------------------- Support for defining httphandlers in jboss-web.xml was added some time ago. Does this fix this issue? > HttpHandlers configuration for EJB3 Webservice Endpoints > -------------------------------------------------------- > > Key: WFLY-703 > URL: https://issues.jboss.org/browse/WFLY-703 > Project: WildFly > Issue Type: Feature Request > Components: Web Services > Reporter: Sebastian Maurer > Assignee: R Searls > Fix For: Awaiting Volunteers > > > Please add a way to configure handlers for EJB3 endpoints packaged in an ejb-jar. > At the moment there is no option in any of the ejb deployment descriptors and of course it isn't possible to configure valves globally. > The only way to configure handlers is by handlers.conf of ServletExcention at the moment, but this is currently limited to web deployments only. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4219) Use Message Format Patterns for Debug Logging

by Philippe Marschall (JIRA)

Philippe Marschall created WFLY-4219: ---------------------------------------- Summary: Use Message Format Patterns for Debug Logging Key: WFLY-4219 URL: https://issues.jboss.org/browse/WFLY-4219 Project: WildFly Issue Type: Patch Components: EJB Reporter: Philippe Marschall Assignee: David Lloyd Most of the WildFly code uses message format patterns for debug logging in order to avoid unnecessary allocations in normal operation. The EJB3 subsystem client seems to be one of the few places where this is not yet the case and debug messages are always created even if the debug logging is disabled. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4218) Fix EJB3 Compiler Warnings

by Philippe Marschall (JIRA)

Philippe Marschall created WFLY-4218: ---------------------------------------- Summary: Fix EJB3 Compiler Warnings Key: WFLY-4218 URL: https://issues.jboss.org/browse/WFLY-4218 Project: WildFly Issue Type: Patch Components: EJB Reporter: Philippe Marschall Assignee: David Lloyd The EJB3 subsystem contains quite a few compiler warnings that are easy to fix (raw types, unused imports, unused variables, deprecated code). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[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 edited comment on WFLY-4217 at 1/3/15 12:51 AM: ------------------------------------------------------------- Requires this PR to be merged first: https://github.com/wildfly/wildfly/pull/7059 https://issues.jboss.org/browse/WFLY-4168 was (Author: bmaxwell): Requires this PR to be merged first: #7059 https://issues.jboss.org/browse/WFLY-4168 > 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)

9 years, 4 months

1
0
0 / 0

[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)

9 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)

9 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)

9 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)

9 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)

9 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)

9 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2015