August 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2031) Enhancements to spreadsheet based testing tool

by Michael Neale (JIRA)

Enhancements to spreadsheet based testing tool ---------------------------------------------- Key: JBRULES-2031 URL: https://jira.jboss.org/jira/browse/JBRULES-2031 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-testing Reporter: Michael Neale Assignee: Michael Neale Fix For: FUTURE As mentioned by Ansgar in blog comments: http://blog.athico.com/2009/03/new-testing-tool.html Hi, we're using Drools to perform mortgage scoring. For testing, we developed a somewhat similar, but already more sophisticated testing framework. Currently, our test set comprises of roughly 800 test scenarios/test cases. Similarities: * also uses spreadsheet tables to define test cases. * each column resembles a test case * leftmost column used to name elements of input facts or define expected conditions (see below) Differences: * concept of "expected values" not expressed as mere values, but as drools conditions which are expected to hold after rules all under test finished execution. These conditions are automagically converted into a drools query which is run against the working memory after rule execution. Enhancements: * conditions support simple text replacement, like a macro preprocessor. Wildcards in drools condition can be replaced by test case-specific text * allows skipping of certain condition checks on a per-test-case basis * event logging of the drools working memory embedded into fit output file for failed checks. visibility of log can be toggled using html-embedded javascript. allows for simple copy/paste into "audit view" window in eclipse. This eases debugging rules a lot! * possibility to define a subset of rules contained in a *.drl file to be tested Open issues: * Syntax of initial facts specification is probably a bit cumbersome. We're using a self-brewed language to do this. Already thought of replacing this by MVEL, but not done yet. For us, the current solution works ok. * Up to now, requires explicit import of all used Java classes. This is rather a limitation of drools - we did not manage to get package imports in *.drl files to work. Could probably be solved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1311) rovide the ability to view sever logs through the web interface

by Heiko Braun (JIRA)

rovide the ability to view sever logs through the web interface --------------------------------------------------------------- Key: AS7-1311 URL: https://issues.jboss.org/browse/AS7-1311 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
7
0 / 0

[JBoss JIRA] Created: (JBRULES-3155) Bug with default properties in KnowledgeStoreServiceImpl

by Pavel Sknar (JIRA)

Bug with default properties in KnowledgeStoreServiceImpl -------------------------------------------------------- Key: JBRULES-3155 URL: https://issues.jboss.org/browse/JBRULES-3155 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.Final Reporter: Pavel Sknar Assignee: Mark Proctor Priority: Critical Method setDefaultImplementations() set default properties in configProps (class KnowledgeStoreServiceImpl). mergeConfig() execute after specific properties loaded to configuration. This overlaps specific properties. [17:08] <pavlz> hi [17:09] <pavlz> I have bug for you [17:09] <Rikkola> :( [17:10] <pavlz> Problem with KnowledgeStoreServiceImpl [17:10] <pavlz> in org.drools.persistence.jpa [17:12] <pavlz> default properties merged first in config (in ChainedProperties: this.props.add( 0, properties )) [17:14] <pavlz> and this overlaps specific properties [17:15] <pavlz> drools.commandService, drools.timerService and else [17:15] <pavlz> I have this bug in 5.2.0.Final [17:23] <conan> pavlz: do you have a fix? [17:25] <pavlz> No, I see this now [17:27] <pavlz> but I think: need to create in ChainedProperties new method "setDefaultProperties" [17:29] <pavlz> and in SessionConfiguration too, to use this method in KnowledgeStoreServiceImpl.mergeConfig() [17:30] <pavlz> then default properties loaded later [17:31] <Rikkola> pavlz: best to make a jira about it [17:31] <Rikkola> https://issues.jboss.org/browse/JBRULES [17:31] <pavlz> ok -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

5
19
0 / 0

[JBoss JIRA] Created: (AS7-1038) Add http to https redirect capability to http-interface

by Darran Lofthouse (JIRA)

Add http to https redirect capability to http-interface ------------------------------------------------------- Key: AS7-1038 URL: https://issues.jboss.org/browse/AS7-1038 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (AS7-1461) prepared statement is getting closed prematurely

by Scott Marlow (JIRA)

prepared statement is getting closed prematurely ------------------------------------------------ Key: AS7-1461 URL: https://issues.jboss.org/browse/AS7-1461 Project: Application Server 7 Issue Type: Feature Request Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

6
11
0 / 0

[JBoss JIRA] Created: (JBAS-9416) EJB3 SFSB performace problem: parallel calls are sequenced

by Radim Hanus (JIRA)

EJB3 SFSB performace problem: parallel calls are sequenced ---------------------------------------------------------- Key: JBAS-9416 URL: https://issues.jboss.org/browse/JBAS-9416 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Reporter: Radim Hanus When a client looks up more SFSB of given type in dedicated threads and subsequently calls business methods then such calls are always sequenced. Works fine in jboss-5.1.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

9
26
0 / 0

[JBoss JIRA] Created: (AS7-1581) tomcatAuthentication attribute on the AJP connector

by Brett Prucha (JIRA)

tomcatAuthentication attribute on the AJP connector --------------------------------------------------- Key: AS7-1581 URL: https://issues.jboss.org/browse/AS7-1581 Project: Application Server 7 Issue Type: Feature Request Components: Server Affects Versions: 7.0.0.Final Environment: Windows Server 2003 32 bit, IIS 6, tomcat connector 1.2.28 used as an extension Reporter: Brett Prucha Assignee: Jason Greene Priority: Minor In JBoss 5.1.0 I could set the tomcatAuthentication attribute of the AJP connector to false to allow IIS to handle the authentication and pass that along to JBoss. I'm wanting to upgrade to JBoss 7 but unable to set this attribute in version 7.0.0 final to make this work. This attribute is descibed in the tomcat documentation at http://tomcat.apache.org/tomcat-7.0-doc/config/ajp.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

6
8
0 / 0

[JBoss JIRA] Created: (JBAS-9245) Passivation of a @Stateful session bean with an @Inject'ed @Stateless session bean fails with not-serializable error.

by Felix Ullrich (JIRA)

Passivation of a @Stateful session bean with an @Inject'ed @Stateless session bean fails with not-serializable error. --------------------------------------------------------------------------------------------------------------------- Key: JBAS-9245 URL: https://issues.jboss.org/browse/JBAS-9245 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 6.0.0.Final Reporter: Felix Ullrich Assignee: Carlo de Wolf I've the same problem described in this issue https://issues.jboss.org/browse/JBAS-8384 Could you please resolve it (maybe in 6.1.0) and dont just close it. Thank you -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-9433) JBoss-6.1.0-SNAPSHOT - Adding @WebService causes EJBException "Named query not found"

by Ralf Battenfeld (JIRA)

JBoss-6.1.0-SNAPSHOT - Adding @WebService causes EJBException "Named query not found" ------------------------------------------------------------------------------------- Key: JBAS-9433 URL: https://issues.jboss.org/browse/JBAS-9433 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 6.0.0.Final Environment: Windows Vista 32-bit, JDK 1.6.0_21-b07 Reporter: Ralf Battenfeld Assignee: Carlo de Wolf Attachments: TestNamedQueryException.zip We faced an issue when a webservice annotation is added to a session bean and there are two persistence units defined. All of them are in the same ejb module defined and packed in an ear. The behaviour is not predictable, some times it works but most of the times, not. Without the @Webservice annotation, we don't have deployment issues. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9391) EJB3.1 spec 4.8.4: destroying singleton because of error during initialization is not honored

by Pierre Kobylanski (JIRA)

EJB3.1 spec 4.8.4: destroying singleton because of error during initialization is not honored --------------------------------------------------------------------------------------------- Key: JBAS-9391 URL: https://issues.jboss.org/browse/JBAS-9391 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 6.0.0.Final Environment: $ uname -a Linux tumlatum 2.6.38-2-686-bigmem #1 SMP Sun May 8 15:43:39 UTC 2011 i686 GNU/Linux Reporter: Pierre Kobylanski Assignee: Carlo de Wolf ejb 3.1 spec [4.8.4 Singleton Error Handling] says that "Errors occurring during Singleton initialization are considered fatal and must result in the discarding of the Singleton instance." I tried to raise a system exception in the @PostConstruct method of a singleton bean. Logs show the deployment error. But I then can access and call the singleton methods. -- Full paragraph 4.8.4: ----------------------------- Errors occurring during Singleton initialization are considered fatal and must result in the discarding of the Singleton instance. Possible initialization errors include injection failure, a system exception thrown from a PostConstruct method, or the failure of a PostConstruct method container-managed transaction to successfully commit. If a singleton fails to initialize, attempted invocations on the Singleton result in an exception as defined by Section 3.4.3 and Section 3.4.4. ------------------------------------------------------ I tested to raise a system exception (throw new RuntimeException()) in the @PostConstruct method. -- Logs show the error ------------------------------- ERROR [AbstractKernelController] Error installing to Start: name=startup-singleton-initiator:topLevelUnit=ts.ear,unit=testSingletonEjb.jar,bean=counter aliases=[startup-singleton-initiator:bean=counter,topLevelUnit=ts.ear,unit=testSingletonEjb.jar] state=Create: java.lang.RuntimeException: Could not invoke PostConstruct on the newly created bean instance at org.jboss.ejb3.singleton.impl.container.SingletonEJBInstanceManagerImpl.create(SingletonEJBInstanceManagerImpl.java:137) [:1.0.0-alpha-28] ... Caused by: testsingleton.exn.SE // class SE extends RuntimeException{} at testsingleton.ejb.CounterEjb.pc(CounterEjb.java:28) DEPLOYMENTS IN ERROR: Deployment "startup-singleton-initiator:topLevelUnit=ts.ear,unit=testSingletonEjb.jar,bean=counter" is in error due to the following reason(s): testsingleton.exn.SE at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228) [:2.2.0.GA] ------------------------------------------------------ However, it is after that possible to access the singleton through a JNDI lookup and successfully call its methods. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2011