October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1254) drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api

by Geoffrey De Smet (JIRA)

drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api ----------------------------------------------------------------------------------------------------------- Key: JBRULES-1254 URL: http://jira.jboss.com/jira/browse/JBRULES-1254 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.1 Reporter: Geoffrey De Smet Assigned To: Mark Proctor Fix For: 4.0.2 log4j and slf4j-log4j12 should be test scoped, because only for the tests they are needed, but users can choose their logging implementation themselves. In examples you'll probably want to make them runtime scoped. slf4j-api is a direct compile time dependency, although currently it's retrieved as a "pseudo transitive dependency" through slf4j-log4j12 which explains why it currently compiles anyway. See drools-repository/pom.xml where I 've commented what I propose to change: <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <scope>test</scope> </dependency> -- 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

16 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-580) no testing tool for the rule base

by Matt Shaw (JIRA)

no testing tool for the rule base --------------------------------- Key: JBRULES-580 URL: http://jira.jboss.com/jira/browse/JBRULES-580 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: Eclipse IDE Reporter: Matt Shaw Assigned To: Mark Proctor At present there is no way of testing rule sets dynamically. I propose to develop an eclipse plugin which parses a rule base and allows the business to create scenarios from the rule base and then dynamically create beans which can than be used to input the data for the scenarios. -- 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

16 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-600) "Otherwise" feature to catch scenarios when no rules fired

by Michael Neale (JIRA)

"Otherwise" feature to catch scenarios when no rules fired ---------------------------------------------------------- Key: JBRULES-600 URL: http://jira.jboss.com/jira/browse/JBRULES-600 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.0.5 Reporter: Michael Neale Assigned To: Michael Neale Fix For: 3.1-m1 Have had a few requests for features when "otherwise" is needed. Basically, in a rule set, when fireAllRules is called, an no "normal" rules activate and fire, rules declared as "otherwise" will then activate, presumably to cater for scenarios that have "fallen through the cracks" in typical business applications. -- 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

16 years, 7 months

4
11
0 / 0

[JBoss JIRA] Created: (JBRULES-666) JCR to SVN integration

by Michael Neale (JIRA)

JCR to SVN integration ---------------------- Key: JBRULES-666 URL: http://jira.jboss.com/jira/browse/JBRULES-666 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

16 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-899) auto import classes from a jar when uploading

by Michael Neale (JIRA)

auto import classes from a jar when uploading --------------------------------------------- Key: JBRULES-899 URL: http://jira.jboss.com/jira/browse/JBRULES-899 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.0.MR2 Reporter: Michael Neale Assigned To: Michael Neale if package header is empty, slap in imports (assuming there is a way to efficiently work them out/guess them). -- 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

16 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-952) Remove repo reference to http://maven.softeu.cz from POMs

by Eric Miles (JIRA)

Remove repo reference to http://maven.softeu.cz from POMs --------------------------------------------------------- Key: JBRULES-952 URL: http://jira.jboss.com/jira/browse/JBRULES-952 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.0.MR3 Environment: Fedora 7, Sun J2SE 1.5.0_12 Reporter: Eric Miles Assigned To: Mark Proctor The reference to a particular repository makes building jbossrules from source a real bear. This is also an issue for someone using jbossrules for the first time as it downloads dependencies, it "hangs" while attempting to download something from this site (maven.softeu.cz). I know there is a workaround for this by either installing the the necessary dependencies in your local repo or in your own remote repo, however this is less than desirable. -- 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

16 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBRULES-1280) Automatically import types into a package config if no config exists

by Michael Neale (JIRA)

Automatically import types into a package config if no config exists -------------------------------------------------------------------- Key: JBRULES-1280 URL: http://jira.jboss.com/jira/browse/JBRULES-1280 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.2 Reporter: Michael Neale Assigned To: Michael Neale Fix For: FUTURE based on what it finds in the jar. -- 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

16 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4515) Quartz scheduler outputs confusable "XX worker threads active" log when shutdown

by Takayoshi Kimura (JIRA)

Quartz scheduler outputs confusable "XX worker threads active" log when shutdown -------------------------------------------------------------------------------- Key: JBAS-4515 URL: http://jira.jboss.com/jira/browse/JBAS-4515 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.2.0.GA Reporter: Takayoshi Kimura Priority: Minor Quartz scheduler always output the following log when shutdown: INFO [org.quartz.simpl.SimpleThreadPool] There are still XX worker threads active. See javadoc runInThread(Runnable) for a possible explanation The thread count XX is not Quartz worker threads. Quarts is using "main" thread group because SimpleThreadPool#isThreadsInheritGroupOfInitializingThread() == true. This is confusing. -- 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

16 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3877) The JMX HtmlAdaptor does not display the exception message

by Lior Shamir (JIRA)

The JMX HtmlAdaptor does not display the exception message ---------------------------------------------------------- Key: JBAS-3877 URL: http://jira.jboss.com/jira/browse/JBAS-3877 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.4.GA Reporter: Lior Shamir Assigned To: Scott M Stark Priority: Minor In JBoss 3.2.x when exception occurred, the HtmlAdaptor display the exception message. In JBoss 4.0.x the HtmlAdaptor display only a generic error message. This is obviously a regression. Can you add the message back? Here is an example: 4.0.4: javax.servlet.ServletException: Failed to invoke operation org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:269) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) root cause javax.management.MBeanException org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180) org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163) org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) org.jboss.mx.server.Invocation.invoke(Invocation.java:86) org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:258) org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:223) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:262) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 3.2.6: javax.servlet.ServletException: Failed to invoke operation org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:248) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:79) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:61) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) root cause MBeanException: com.koko.KOKOException: Invalid type Cause: com.koko.KOKOException: Invalid type org.jboss.mx.server.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:91) org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:64) org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) org.jboss.mx.server.Invocation.invoke(Invocation.java:82) org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197) org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:236) org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:202) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:241) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:79) org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:61) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) -- 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

16 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4749) HTML object tag should be used instead of applet

by Sylvain Avril (JIRA)

HTML object tag should be used instead of applet ------------------------------------------------ Key: JBAS-4749 URL: http://jira.jboss.com/jira/browse/JBAS-4749 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-4.2.2.GA Reporter: Sylvain Avril Assigned To: Darran Lofthouse Priority: Minor The HTML applet tag is deprecated. It can lead to strange behavior. For exemple for my Windows PC, it try to use the 1.3.1 JVM instead of the 1.5.0 which is the default for applets. Some doc could be found here : http://java.sun.com/j2se/1.5.0/docs/guide/plugin/developer_guide/using_ta... -- 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

16 years, 7 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007