January 2010 - 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

12 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1642) The <security-domain> tag included in <container-configuration> in the jboss.xml file is ignored

by John Gonon (JIRA)

The <security-domain> tag included in <container-configuration> in the jboss.xml file is ignored ------------------------------------------------------------------------------------------------ Key: EJBTHREE-1642 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1642 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: HEAD Environment: Windows XP JDK 1.6.build10 JBOSS 5.0.0.GA Reporter: John Gonon Priority: Minor The <security-domain> tag included in <container-configuration> in the jboss.xml file is ignored. I have tracked were the problem seems to be (at least as I saw it). In the class "org.jboss.ejb3.security.bridge.SecurityDomainMetaDataBridge" there are those lines: //TODO: How to get the merged meta data? Is the following line correct? if(securityDomain == null) securityDomain = beanMetaData.getJBossMetaData().getSecurityDomain(); I replaced them with: if (securityDomain == null) { JBossMetaData metaData = beanMetaData.getJBossMetaData(); securityDomain = metaData.getContainerConfiguration(beanMetaData.determineConfigurationName()) .getSecurityDomain(); if (securityDomain == null) securityDomain = metaData.getSecurityDomain(); } As I understand it, if no "SecurityDomain" annotation is found, then we finish in this class and we do in order: 1. seek for a security domain in the bean's metadata (I guess it is in the EJB declaration) 2. seek for the one in "jboss-app.xml" I inserted between them some code returning the one comming from the container's configuration I hope this helps ... Best regards, Please keep me informed, I hope to remove my "modified" jar with an official one soon. John -- 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

12 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-6326) InterruptedException on shutdown

by Jeff Yu (JIRA)

InterruptedException on shutdown -------------------------------- Key: JBAS-6326 URL: https://jira.jboss.org/jira/browse/JBAS-6326 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.2.GA Reporter: Jeff Yu Assignee: Jeff Zhang Priority: Minor I see the following exception on shutdown with either default, all, production servers (using all's log4j configuration). I'm not sure it is necessary for users to see. Probably needs to be changed to DEBUG level if really not relevant. 09:07:59,647 WARN [NewMsgsWorker] Interrupted waiting for new msg check java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:474) at EDU.oswego.cs.dl.util.concurrent.Semaphore.acquire(Semaphore.java:108) at EDU.oswego.cs.dl.util.concurrent.SemaphoreControlledChannel.take(SemaphoreControlledChannel.java:131) at org.jboss.resource.adapter.mail.inflow.NewMsgsWorker.run(NewMsgsWorker.java:75) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756) at java.lang.Thread.run(Thread.java:595) -- 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

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-127) SPNEGO Across Cluster

by Darran Lofthouse (JIRA)

SPNEGO Across Cluster --------------------- Key: SECURITY-127 URL: http://jira.jboss.com/jira/browse/SECURITY-127 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Use a distributed cache or re-authenticate at each node? -- 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

12 years, 2 months

1
7
0 / 0

[JBoss JIRA] Created: (SECURITY-140) JBossWS EJB Endpoints Defined With Custom Authenticators

by Darran Lofthouse (JIRA)

JBossWS EJB Endpoints Defined With Custom Authenticators -------------------------------------------------------- Key: SECURITY-140 URL: http://jira.jboss.com/jira/browse/SECURITY-140 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse -- 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

12 years, 2 months

1
7
0 / 0

[JBoss JIRA] Created: (SECURITY-139) JBossWS Client SPNEGO Authentication

by Darran Lofthouse (JIRA)

JBossWS Client SPNEGO Authentication ------------------------------------ Key: SECURITY-139 URL: http://jira.jboss.com/jira/browse/SECURITY-139 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse -- 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

12 years, 2 months

1
7
0 / 0

[JBoss JIRA] Created: (SECURITY-137) Authentication Cache aware of ticket expiration

by Darran Lofthouse (JIRA)

Authentication Cache aware of ticket expiration ----------------------------------------------- Key: SECURITY-137 URL: http://jira.jboss.com/jira/browse/SECURITY-137 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse -- 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

12 years, 2 months

1
7
0 / 0

[JBoss JIRA] Created: (SECURITY-130) Non web invocations to server

by Darran Lofthouse (JIRA)

Non web invocations to server ----------------------------- Key: SECURITY-130 URL: http://jira.jboss.com/jira/browse/SECURITY-130 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Kerberos based SSO can also be made possible for calls over other invokers and can also be used for message integrity and confidentiality. -- 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

12 years, 2 months

1
7
0 / 0

[JBoss JIRA] Created: (SECURITY-128) Same user calling multiple web applications

by Darran Lofthouse (JIRA)

Same user calling multiple web applications ------------------------------------------- Key: SECURITY-128 URL: http://jira.jboss.com/jira/browse/SECURITY-128 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse The same user may be authenticated multiple times. -- 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

12 years, 2 months

2
9
0 / 0

[JBoss JIRA] Created: (SECURITY-131) WS-Kerberos

by Darran Lofthouse (JIRA)

WS-Kerberos ----------- Key: SECURITY-131 URL: http://jira.jboss.com/jira/browse/SECURITY-131 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Both incomming and outbound. -- 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

12 years, 2 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2010