July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1644) Make drools imply null checks before trying to read a value

by Alex McCarrier (JIRA)

Make drools imply null checks before trying to read a value ----------------------------------------------------------- Key: JBRULES-1644 URL: http://jira.jboss.com/jira/browse/JBRULES-1644 Project: JBoss Drools Issue Type: Feature Request Components: Drl Parser/Builder Affects Versions: 4.0.6 Environment: all Reporter: Alex McCarrier Assigned To: Mark Proctor Priority: Minor Fix For: FUTURE Not sure if this is MVEL or drools itself, but it would be nice if it would do null checks on fields for you rather than having the rule author do it. Example, when doing something like: when Object(value1.value2 == something) before attempting to read value2 it makes sure value1 is not null, and if value1 is null than rather than throwing an error like it does currently, just consider the rule as not matching. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-5426) Define JCA SPI

by Jesper Pedersen (JIRA)

Define JCA SPI -------------- Key: JBAS-5426 URL: http://jira.jboss.com/jira/browse/JBAS-5426 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Reporter: Jesper Pedersen Assigned To: Jesper Pedersen Fix For: JBossAS-5.0.0.CR1 We need to define a SPI for the JCA layer in order to better separate clients (f.ex. EJB3) of JCA from the actual implementation. The SPI will live in the jboss-integration module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBBUILD-430) Look into bug with maven plugin manager.

by Paul Gier (JIRA)

Look into bug with maven plugin manager. ---------------------------------------- Key: JBBUILD-430 URL: http://jira.jboss.com/jira/browse/JBBUILD-430 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2007 There seems to be a bug in maven in the plugin resolution when there are different versions of plugins available in different repositories. A maven bug should be submitted, and the issue should be patched. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work

by Juergen Zimmermann (JIRA)

5.0.0CR1: EJB refs across EARs don't work ----------------------------------------- Key: EJBTHREE-1434 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1434 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 5.0.0.CR1 Environment: JBoss 5.0.0.CR1, JDK 6u10beta Reporter: Juergen Zimmermann I'm having 2 different EARs and stateless session beans of the 2nd EAR are referencing stateless session beans of the 1st ear. It worked fine with 4.2.2 I'll attach a stripped down testcase: * src.zip: source of projects for Eclipse w/ JBoss Tools * hska.ear.zip: exploded EAR 1 (and zipped for transferring) * testHska.ear.zip: exploded EAR 1 (and zipped for transferring) src.zip: * hska is the 1st EAR project * hskaEJB contains the ejb module for hska * testHska is the EAR project for the 2nd EAR * testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB * testHskaClient is an application client module for testHska using JUnit -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1429) SFSB replication soak testing

by Brian Stansberry (JIRA)

SFSB replication soak testing ----------------------------- Key: EJBTHREE-1429 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1429 Project: EJB 3.0 Issue Type: Task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 5.0.0.CR2 Long running tests of SFSB replication under heavy load. Should include: 1) Letting a significant percentage of sessions passivate and later activate. 2) Letting a significant percentage of sessions expire due to time out. 3) Invalidating remaining sessions after a while (i.e. don't use any sessions for the life of test; all get used and replaced after a while). 4) Perhaps, a low (say 1/1000) probability of failover. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

5
12
0 / 0

[JBoss JIRA] Created: (JBRULES-842) Extract/index rule fact info on save

by Michael Neale (JIRA)

Extract/index rule fact info on save ------------------------------------ Key: JBRULES-842 URL: http://jira.jboss.com/jira/browse/JBRULES-842 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-836) DSL expression browser

by Michael Neale (JIRA)

DSL expression browser ---------------------- Key: JBRULES-836 URL: http://jira.jboss.com/jira/browse/JBRULES-836 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5345) New instance of resources injected on every onMessage MDB call

by Dok Tora (JIRA)

New instance of resources injected on every onMessage MDB call -------------------------------------------------------------- Key: JBAS-5345 URL: http://jira.jboss.com/jira/browse/JBAS-5345 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.0.5.GA Environment: Java version: 1.5.0_13,Apple Computer, Inc. OS-System: Mac OS X 10.4.11,i386 Reporter: Dok Tora Assigned To: Adrian Brock Priority: Critical A new instance of an injected bean is created every time the onMessage() method of an MDB is called. Details with sample code modifications to EJBTrailBlazer for reproduction can be found here: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132331 Problem was replicated in 4.0.5.GA, 4.2.1 and 4.2.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

5
11
0 / 0

[JBoss JIRA] Created: (JBAS-3816) Wildcard handling in "org.jboss.metadata.MethodAttributes.patternMatches()" isn't correct (or documentation problem)

by Anders Welen (JIRA)

Wildcard handling in "org.jboss.metadata.MethodAttributes.patternMatches()" isn't correct (or documentation problem) -------------------------------------------------------------------------------------------------------------------- Key: JBAS-3816 URL: http://jira.jboss.com/jira/browse/JBAS-3816 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: Anders Welen Priority: Minor Attachments: JBossBug.tgz The method "patternMatches" in "org.jboss.metadata.MethodAttributes" just stops at the first wildcard ("*") found and assumes that match is ok. Either this is a bug or the documentation ("http://docs.jboss.com/jbossas/guides/j2eeguide/r2/en/html_single/#d0e11084") should be changed and clearly inform that the wildcard must be the last character. If you specify for example "*get*" than all methods will be matched.... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-4078) DeploymentManager.getAvailableModules() returns null

by Libor Kotouc (JIRA)

DeploymentManager.getAvailableModules() returns null ---------------------------------------------------- Key: JBAS-4078 URL: http://jira.jboss.com/jira/browse/JBAS-4078 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta2 Environment: JBoss 5.0.0.beta2 trunk build 20070206, JDK 1.5.0_08 Reporter: Libor Kotouc Assigned To: Dimitris Andreadis Priority: Critical This issue blocks an integration of JBoss AS 5 into NetBeans IDE. Steps to reproduce the behavior: 1. create a simple web application and copy the .war file into the deploy directory (I used the 'default' server) 2. start JBoss server (./run.sh) 3. run the following code from a J2SE application (I added JBoss jars to the classpath): public class Main { public static void main(String[] args) { try { javax.enterprise.deploy.spi.factories.DeploymentFactory df = new org.jboss.deployment.spi.factories.DeploymentFactoryImpl(); javax.enterprise.deploy.spi.DeploymentManager dm; dm = df.getDeploymentManager("http://org.jboss.deployment/jsr88", null, null); javax.enterprise.deploy.spi.Target[] targets = dm.getTargets(); javax.enterprise.deploy.spi.TargetModuleID[] modules; modules = dm.getAvailableModules(javax.enterprise.deploy.shared.ModuleType.WAR, targets); System.out.println(targets.length + " " + targets[0]); System.out.println(modules); } catch (javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException ex) { } catch (javax.enterprise.deploy.spi.exceptions.TargetException ex) { } } } The output of System.out.println statements is: 1 org.jboss.deployment.spi.JMXTarget@161d36b null I expect the module representing the web application, but null is returned. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

4
5
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 July 2008