April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1453) boss.seam.Component) - Exception calling component @Destroy method: repository

by Joseph Bonello (JIRA)

boss.seam.Component) - Exception calling component @Destroy method: repository ------------------------------------------------------------------------------ Key: JBRULES-1453 URL: http://jira.jboss.com/jira/browse/JBRULES-1453 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.4 Environment: Windows XP SP2, JDK 1.6, Sun Application Server 9u1 Reporter: Joseph Bonello rg.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1966:org.jboss.seam.Component) - instantiating Seam component: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1387:org.jboss.seam.Component) - initializing new instance of: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1404:org.jboss.seam.Component) - done initializing: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1966:org.jboss.seam.Component) - instantiating Seam component: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1387:org.jboss.seam.Component) - initializing new instance of: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1404:org.jboss.seam.Component) - done initializing: org.jboss.seam.core.events org.jboss.seam.core.Events - 2008-02-07 08:59:20,453 () DEBUG (Events.java:60:org.jboss.seam.core.Events) - Processing event:org.jboss.seam.preDestroy.repository org.jboss.seam.Component - 2008-02-07 08:59:20,453 () WARN (Component.java:1340:org.jboss.seam.Component) - Exception calling component @Destroy method: repository java.lang.IllegalArgumentException: method not found: close for component: repository at org.jboss.seam.Component.callComponentMethod(Component.java:2105) at org.jboss.seam.Component.callDestroyMethod(Component.java:2018) at org.jboss.seam.Component.destroy(Component.java:1336) at org.jboss.seam.contexts.Contexts.destroy(Contexts.java:251) at org.jboss.seam.contexts.Contexts.flushAndDestroyContexts(Contexts.java:394) at org.jboss.seam.contexts.ServletLifecycle.endRequest(ServletLifecycle.java:60) at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:49) at org.jboss.seam.web.ContextFilter.doFilter(ContextFilter.java:37) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:216) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844) at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287) at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252) at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75) Caused by: java.lang.NoSuchMethodException: org.drools.brms.server.repository.RulesRepositoryManager_$$_javassist_2.close() at java.lang.Class.getMethod(Class.java:1605) at org.jboss.seam.Component.callComponentMethod(Component.java:2084) ... 32 more org.jboss.seam.contexts.Contexts - 2008-02-07 08:59:20,453 () DEBUG (Contexts.java:244:org.jboss.seam.contexts.Contexts) - destroying: org.jboss.seam.transaction.transaction org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1966:org.jboss.seam.Component) - instantiating Seam component: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1387:org.jboss.seam.Component) - initializing new instance of: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1404:org.jboss.seam.Component) - done initializing: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1966:org.jboss.seam.Component) - instantiating Seam component: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1387:org.jboss.seam.Component) - initializing new instance of: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1404:org.jboss.seam.Component) - done initializing: org.jboss.seam.core.events org.jboss.seam.core.Events - 2008-02-07 08:59:20,453 () DEBUG (Events.java:60:org.jboss.seam.core.Events) - Processing event:org.jboss.seam.preDestroy.org.jboss.seam.transaction.transaction org.jboss.seam.contexts.Contexts - 2008-02-07 08:59:20,453 () DEBUG (Contexts.java:244:org.jboss.seam.contexts.Contexts) - destroying: org.jboss.seam.core.manager org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1966:org.jboss.seam.Component) - instantiating Seam component: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1387:org.jboss.seam.Component) - initializing new instance of: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1404:org.jboss.seam.Component) - done initializing: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1966:org.jboss.seam.Component) - instantiating Seam component: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1387:org.jboss.seam.Component) - initializing new instance of: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1404:org.jboss.seam.Component) - done initializing: org.jboss.seam.core.events -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBFORUMS-164) lastPostDate must be persisted in database

by Ryszard Kozmik (JIRA)

lastPostDate must be persisted in database ------------------------------------------ Key: JBFORUMS-164 URL: http://jira.jboss.com/jira/browse/JBFORUMS-164 Project: JBoss Forums Issue Type: Task Components: Forum Model Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Blocker Fix For: 1.1.0 Alpha Forums are not efficient mainly because of this very big problem of their module and database schema. There is no place to keep lastPostDates so they have to be generated each time what takes big amounts of time as those are very timetaking sql queries. This is main performance killer at this point. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBFORUMS-249) Make Forums compatible with Portal URLMapper

by Ryszard Kozmik (JIRA)

Make Forums compatible with Portal URLMapper -------------------------------------------- Key: JBFORUMS-249 URL: http://jira.jboss.com/jira/browse/JBFORUMS-249 Project: JBoss Forums Issue Type: Task Components: Forum Enhancements, Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC It is now impossible to overwrite url parameter names of Forums by Portal URLMapper and it should be. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBFORUMS-260) Integrate WYSIWYG editor for posting.

by Ryszard Kozmik (JIRA)

Integrate WYSIWYG editor for posting. ------------------------------------- Key: JBFORUMS-260 URL: http://jira.jboss.com/jira/browse/JBFORUMS-260 Project: JBoss Forums Issue Type: Task Components: Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.1.0 Alpha To make Forums look better and be more usable, it should have WYSIWYG editor for posting. e.g. tinyMCE -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-140) Caching

by Ryszard Kozmik (JIRA)

Caching ------- Key: JBFORUMS-140 URL: http://jira.jboss.com/jira/browse/JBFORUMS-140 Project: JBoss Forums Issue Type: Task Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.0 Beta JBoss Forums model have to have caching enabled and configured. Secondary level cache and sql statements caching for Hibernate must be configured and properly used by queries. -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1390) Add support to streams

by Edson Tirelli (JIRA)

Add support to streams ---------------------- Key: JBRULES-1390 URL: http://jira.jboss.com/jira/browse/JBRULES-1390 Project: JBoss Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Edson Tirelli Assigned To: Edson Tirelli -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1554) "not in" used with "or" is not thread safe

by Jan Boboli (JIRA)

"not in" used with "or" is not thread safe ------------------------------------------ Key: JBRULES-1554 URL: http://jira.jboss.com/jira/browse/JBRULES-1554 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 4.0.5 Reporter: Jan Boboli Assigned To: Mark Proctor Priority: Blocker "not in" used with "or" is not thread safe. following construct causes ClassCastExeption when executed in parallel by different threads : when: $validateOrderIn : ValidateOrderIn( ) Sim( $sim : sim ) ( __sims( sim == $sim, $status : status not in ( "n", "o", "p") ) ) or ( __sims( sim == $sim, $status : status not in ("r", "l", "m" ) ) ) then ... -- 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, 6 months

3
14
0 / 0

[JBoss JIRA] Created: (JBRULES-1023) Typing the parameter to be replace by DSL/DRL replacement

by christian bastin (JIRA)

Typing the parameter to be replace by DSL/DRL replacement --------------------------------------------------------- Key: JBRULES-1023 URL: http://jira.jboss.com/jira/browse/JBRULES-1023 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: christian bastin Assigned To: Mark Proctor We have a very long DSL including more 150 différent lines (wich could be very similar). We have no posibility to be sure of the replacement operarted by the parsing. We often dicover problem that force us to move the order of the lines in the DSL. This is an simple example of what I think could be improved. If you have a DSL test {code} is {value} this could replace this 2 rules in the DRL rule "Rule-1" when test 10 is 10 then > System.out.println("test 1 OK"); end rule "Rule-1" when test 10 + 10 is 10 then > System.out.println("test 1 OK"); end I would like the ability to type the parameter of my DSL, for example with regular expression. test {code|[0-9]+} is {value|[0-9]+} so the only rule available for replacement should be the first rule ("Rule-1"). The other rule would not find a replacement and should be implemented in the DSL. -- 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, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1331) Implement CEP/ESP support into Drools

by Edson Tirelli (JIRA)

Implement CEP/ESP support into Drools ------------------------------------- Key: JBRULES-1331 URL: http://jira.jboss.com/jira/browse/JBRULES-1331 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 4.1.0 This is the parent ticket for CEP/ESP support development -- 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, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBRULES-380) Create some decision table examples

by william hayhurst (JIRA)

Create some decision table examples ----------------------------------- Key: JBRULES-380 URL: http://jira.jboss.com/jira/browse/JBRULES-380 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Decision tables, Documentation Affects Versions: 3.0 Reporter: william hayhurst Assigned To: Mark Proctor Attachments: barbarian.xls As per IRC, some more fleshed out examples of decision tables in action. -- 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, 6 months

5
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2008