April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2683) DroolsSession's initWorkItemManagerFactory method can not work in a OSGi context

by Antoine Toulme (JIRA)

DroolsSession's initWorkItemManagerFactory method can not work in a OSGi context -------------------------------------------------------------------------------- Key: JBRULES-2683 URL: https://jira.jboss.org/browse/JBRULES-2683 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.M1 Reporter: Antoine Toulme Assignee: Mark Proctor Fix For: FUTURE This affects the current trunk. The code in the method does this: String className = this.chainedProperties.getProperty( "drools.workItemManagerFactory", "org.drools.process.instance.impl.DefaultWorkItemManagerFactory" ); [..] clazz = (Class<WorkItemManagerFactory>) Thread.currentThread().getContextClassLoader().loadClass( className ); [..] clazz = (Class<WorkItemManagerFactory>) SessionConfiguration.class.getClassLoader().loadClass( className ); None of this can work for the default factory since drools-core does not depend on drools-flow-core (and creating a dependency would create a cycle). Actually, this won't work for customer code as well, since drools-core won't depend on their bundle. I suggest to use a declarative service to work around this problem, while keeping this type of instantiation around when OSGi is not on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] (AS7-4347) http://localhost:9990/error/index_win.html refers to add-user.sh

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-4347?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved AS7-4347. ----------------------------------- Resolution: Rejected The problem is EAP specific, the AS7 repo still contains the index_win.html that correctly references add-user.bat. > http://localhost:9990/error/index_win.html refers to add-user.sh > ---------------------------------------------------------------- > > Key: AS7-4347 > URL: https://issues.jboss.org/browse/AS7-4347 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.0.Final, 7.1.1.Final > Environment: Windows 7 > Reporter: Burr Sutter > Assignee: Darran Lofthouse > Fix For: 7.1.2.Final > > Attachments: add-user.sh.png > > > Welcome to EAP 6 > Your JBoss Enterprise Application Platform is running. > However you have not yet added any users to be able to access the admin console. > To add a new user execute the add-user.sh script within the bin folder of your EAP 6 installation and enter the requested information. > By default the realm name used by EAP 6 is "ManagementRealm" this is already selected by default. > After you have added the user follow this link to Try Again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-4347) http://localhost:9990/error/index_win.html refers to add-user.sh

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-4347?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on AS7-4347: --------------------------------------- Burr - by selecting both 7.1.0.Final and 7.1.1.Final as the affects versions did you test those versions? Just checked the source of that HTML and it still contains add-user.bat as it should and as it has been since the error page was first added. > http://localhost:9990/error/index_win.html refers to add-user.sh > ---------------------------------------------------------------- > > Key: AS7-4347 > URL: https://issues.jboss.org/browse/AS7-4347 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.0.Final, 7.1.1.Final > Environment: Windows 7 > Reporter: Burr Sutter > Assignee: Darran Lofthouse > Fix For: 7.1.2.Final > > Attachments: add-user.sh.png > > > Welcome to EAP 6 > Your JBoss Enterprise Application Platform is running. > However you have not yet added any users to be able to access the admin console. > To add a new user execute the add-user.sh script within the bin folder of your EAP 6 installation and enter the requested information. > By default the realm name used by EAP 6 is "ManagementRealm" this is already selected by default. > After you have added the user follow this link to Try Again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-677) Setup integration testing

by Geoffrey De Smet (JIRA)

Setup integration testing ------------------------- Key: JBRULES-677 URL: http://jira.jboss.com/jira/browse/JBRULES-677 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Minor based on solver configs -- 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

14 years

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2251) The Solver's score calculation should be reusable without using the Solver itself. The examples should not know the Solver that intimetly and should not use the working memory directly.

by Geoffrey De Smet (JIRA)

The Solver's score calculation should be reusable without using the Solver itself. The examples should not know the Solver that intimetly and should not use the working memory directly. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2251 URL: https://jira.jboss.org/jira/browse/JBRULES-2251 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-solver Affects Versions: 5.0.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet -- 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

14 years

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2884) Drools classpath container allows modification for source and JavaDoc locations

by Masafumi Miura (JIRA)

Drools classpath container allows modification for source and JavaDoc locations -------------------------------------------------------------------------------- Key: JBRULES-2884 URL: https://issues.jboss.org/browse/JBRULES-2884 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-eclipse Reporter: Masafumi Miura Assignee: Mark Proctor The AS, WS and ESB classpath containers allow source and JavaDoc locations to be set via the Properties dialog on each contained jar. The Drools classpath container does not. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2313) Tomcat memery leak with drools 4.0.7 or 5.0.1

by GREFFET Emmanuel (JIRA)

Tomcat memery leak with drools 4.0.7 or 5.0.1 ---------------------------------------------- Key: JBRULES-2313 URL: https://jira.jboss.org/jira/browse/JBRULES-2313 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.0.1.FINAL, 4.0.7 Environment: XP tomcat 5.5.9 Reporter: GREFFET Emmanuel Assignee: Mark Proctor Priority: Critical The memory is never released !!! (never ever ) when à Stop and Start or restart Tomcat. A made this test with a simple Drools call with a simple webapp and i tried with 4.0.7 and 5.0.1 drools version. The problem is the same. We need to stop tomcat process to release memory. Until this stop each Tomcat "Restart" with a drools call, will never release the memory. I made graphic with VisualWM, and we can see this problem ! I made a zip of my simple Eclipse project (webapp + drools) and word file for more information and screen copy of VisualVM. Thanks for help. Emmanuel GREFFET ( FRANCE) -- 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

14 years

3
5
0 / 0

[JBoss JIRA] (JBRULES-3299) Please remove drools-grid-impl from drools-spring

by kenneth westelinck (Created) (JIRA)

Please remove drools-grid-impl from drools-spring ------------------------------------------------- Key: JBRULES-3299 URL: https://issues.jboss.org/browse/JBRULES-3299 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-spring Affects Versions: 5.3.0.Final Environment: all Reporter: kenneth westelinck Assignee: Mark Proctor Attachments: dummy.tar.gz I am referring to the following discussion: http://drools.46999.n3.nabble.com/drools-spring-dependency-on-drools-grid... To solve this, I have performed the following dirty hack: - exclude drools-grid-impl from the dependencies - add necessary interfaces / dummy implementations in own project Attached are the necessary dummy implementations (most are copied from the drools-grid-impl) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

6
6
0 / 0

[JBoss JIRA] (JBRULES-3305) Allow to use any JPA Provider, not just Hibernate (but also OpenJPA, ...)

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3305?page=com.atlassian.jira.plug... ] Geoffrey De Smet reassigned JBRULES-3305: ----------------------------------------- Assignee: Marco Rietveld Marco's work related to JPA 2 and hibernate 4 might or might not enable this. > Allow to use any JPA Provider, not just Hibernate (but also OpenJPA, ...) > ------------------------------------------------------------------------- > > Key: JBRULES-3305 > URL: https://issues.jboss.org/browse/JBRULES-3305 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.3.0.Final > Reporter: Jim Tyrrell > Assignee: Marco Rietveld > > A potential customer has currently been using the BRMS/Govnor and would like the ability to use any JPA provider. They noticed some Hibernate specific annotations and wonder why that would be required/used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2811) Javadocs should aggregate all javadocs of all modules, but should use groups to distinguish them in the overview

by Geoffrey De Smet (JIRA)

Javadocs should aggregate all javadocs of all modules, but should use groups to distinguish them in the overview ---------------------------------------------------------------------------------------------------------------- Key: JBRULES-2811 URL: https://jira.jboss.org/browse/JBRULES-2811 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-api Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Optional Fix For: FUTURE Aggregate: http://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html Groups: http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#gr... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
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 April 2012