April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3414) Segment based unlinking

by Mark Proctor (JIRA)

Mark Proctor created JBRULES-3414: ------------------------------------- Summary: Segment based unlinking Key: JBRULES-3414 URL: https://issues.jboss.org/browse/JBRULES-3414 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (expert) Reporter: Mark Proctor Assignee: Mark Proctor -- 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

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] (JBRULES-3388) KnowledgeAgent custom classloader not working for PKG resources

by Herman Post (JIRA)

Herman Post created JBRULES-3388: ------------------------------------ Summary: KnowledgeAgent custom classloader not working for PKG resources Key: JBRULES-3388 URL: https://issues.jboss.org/browse/JBRULES-3388 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.3.1.Final Environment: Windows 7, Java7-5, JBoss AS7.1 Reporter: Herman Post Assignee: Mark Proctor I believe there may be a bug when trying to use a custom class loader with the KnowledgeAgent and the KnowledgeBuilderConfiguration, and when the ChangeSet is a PKG resource. I have been trying to get the knowledge-agent-classloader sample from the new Drools Cookbook to work with a PKG resource. The sample works fine for a DRL resource, but when I convert it to use my fact jar, and a PKG resource containing my rules, which I downloaded from Guvnor, it throws a ClassNotFoundException for my fact model. If I put my fact model in the classpath, the error goes away and my rules can be added to the KnowledgeAgent and run correctly. Following is the code from the sample that I have converted, and I have attached a zip file with a complete project demonstrating the problem. Also, I can get my rules and fact model to work if I use a DRL ChangeSet.knowledge-agent-classloader.zip URL modelJarURL = getClass().getResource("Patient-1.0.jar"); URLClassLoader customURLClassloader = new URLClassLoader(new URL[] {modelJarURL }); KnowledgeBuilderConfiguration kbuilderConfig = KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration(null, customURLClassloader); KnowledgeBaseConfiguration kbaseConfig = KnowledgeBaseFactory.newKnowledgeBaseConfiguration(null, customURLClassloader); KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase(kbaseConfig); KnowledgeAgentConfiguration aconf = KnowledgeAgentFactory.newKnowledgeAgentConfiguration(); KnowledgeAgent kagent = KnowledgeAgentFactory.newKnowledgeAgent("test", kbase, aconf, kbuilderConfig); // kagent.applyChangeSet(new ClassPathResource("change-set.xml", getClass())); // this goes with model.jar // kagent.applyChangeSet(new ClassPathResource("drl-change-set.xml", getClass())); // this goes with Patient.jar kagent.applyChangeSet(new ClassPathResource("pkg-change-set.xml", getClass())); // this goes with Patient.jar return kagent.getKnowledgeBase(); Following is the stack trace from the error: java.lang.NullPointerException at org.drools.impl.KnowledgeBaseImpl.addKnowledgePackages(KnowledgeBaseImpl.java:148) at org.drools.agent.impl.KnowledgeAgentImpl.addResourcesToKnowledgeBase(KnowledgeAgentImpl.java:1016) at org.drools.agent.impl.KnowledgeAgentImpl.rebuildResources(KnowledgeAgentImpl.java:785) at org.drools.agent.impl.KnowledgeAgentImpl.buildKnowledgeBase(KnowledgeAgentImpl.java:657) at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:190) at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:169) at drools.cookbook.chapter02.KnowledgeAgentClassloaderTest.createKnowledgeBase(KnowledgeAgentClassloaderTest.java:59) at drools.cookbook.chapter02.KnowledgeAgentClassloaderTest.customClassloaderTest(KnowledgeAgentClassloaderTest.java:30) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) I have been having the exact same problem when trying to use a custom class loader with just a KnowldegeBuilder and no KnowledgeAgent. -- 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

13 years, 5 months

3
6
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

13 years, 5 months

1
7
0 / 0

[JBoss JIRA] (JBRULES-3470) publish org.drools.updatesite-*-assembly.zip contents to download.jboss.org so it can be used by end-users and linked from JBoss Central

by Nick Boldt (JIRA)

Nick Boldt created JBRULES-3470: ----------------------------------- Summary: publish org.drools.updatesite-*-assembly.zip contents to download.jboss.org so it can be used by end-users and linked from JBoss Central Key: JBRULES-3470 URL: https://issues.jboss.org/browse/JBRULES-3470 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 5.4.0.CR1, 5.3.1.Final Reporter: Nick Boldt Assignee: Mark Proctor Currently the only ways to get drools/jbpm 5 plugins installed into Eclipse are to: a) download the org.drools.updatesite-*-assembly.zip zip from Nexus, or b) unpack the droolsjbpm-tools-distribution-*.zip linked from http://www.jboss.org/drools/downloads, or c) use the nightly staging site for JBT SOA Tooling http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/ d) use the nightly staging site for JBDS SOA Tooling http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.... Since the JBT site (c) is going away, and (a) and (b) are a relative pain in the butt, we need a new unpacked site, eg., under here: http://download.jboss.org/drools/updates/ or http://download.jboss.org/drools/releases/ -- 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

13 years, 5 months

2
20
0 / 0

[JBoss JIRA] (AS7-3681) JBoss crashes when run with AspectJ java agent

by Jack Lund (JIRA)

Jack Lund created AS7-3681: ------------------------------ Summary: JBoss crashes when run with AspectJ java agent Key: AS7-3681 URL: https://issues.jboss.org/browse/AS7-3681 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.CR1b, 7.0.2.Final Environment: OS X 10.7.2, Ubuntu 11.10 Reporter: Jack Lund Assignee: Jason Greene Priority: Blocker When trying to start JBoss with the AspectJ java agent (-javaagent:/path/aspectjweaver.jar) to enable load-time weaving, JBoss crashes with the following stack trace in the logs: ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/jack/jboss-as-7.1.0.CR1b JAVA: java JAVA_OPTS: -server -javaagent:/home/jack/aspectjweaver.jar -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= WARNING: Failed to load the specified logmodule org.jboss.logmanager:main Exception in thread "main" java.lang.ExceptionInInitializerError at org.jboss.as.server.Main.main(Main.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.jboss.modules.Module.run(Module.java:248) at org.jboss.modules.Main.main(Main.java:313) Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") at org.jboss.logmanager.Logger.getLogger(Logger.java:60) at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42) ... 7 more -- 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

13 years, 5 months

9
14
0 / 0

[JBoss JIRA] (AS7-2152) WSDL URL should be anchor

by Richard Opalka (Created) (JIRA)

WSDL URL should be anchor ------------------------- Key: AS7-2152 URL: https://issues.jboss.org/browse/AS7-2152 Project: Application Server 7 Issue Type: Enhancement Components: Console Reporter: Richard Opalka Assignee: Heiko Braun Fix For: 7.1.0.Beta1 -- 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

13 years, 5 months

4
4
0 / 0

[JBoss JIRA] (AS7-2355) Web Console: Datasources are shown in the deployments list with war files

by Jim Tyrrell (Created) (JIRA)

Web Console: Datasources are shown in the deployments list with war files ------------------------------------------------------------------------- Key: AS7-2355 URL: https://issues.jboss.org/browse/AS7-2355 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun Datasources should have there own special area that enables people to quickly find the settings and values for the JDBC settings. These should not be intermixed with all of the other war/ear/etc files that I have deployed. -- 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

13 years, 5 months

5
10
0 / 0

[JBoss JIRA] (AS7-2091) Manage web deployment information in the console

by David Bosschaert (Created) (JIRA)

Manage web deployment information in the console ------------------------------------------------ Key: AS7-2091 URL: https://issues.jboss.org/browse/AS7-2091 Project: Application Server 7 Issue Type: Sub-task Components: Console Reporter: David Bosschaert Assignee: Heiko Braun /deployment=mydeployment.jar/subsystem=web contains web deployment information which should be made manageable in the console. This should integrate with the overall deployment management views. -- 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

13 years, 5 months

3
3
0 / 0

[JBoss JIRA] (AS7-2315) Click within the Deployments tab in the Administrative Console and drill-down into the war file to see the artifacts

by Blaine Mincey (Created) (JIRA)

Click within the Deployments tab in the Administrative Console and drill-down into the war file to see the artifacts -------------------------------------------------------------------------------------------------------------------- Key: AS7-2315 URL: https://issues.jboss.org/browse/AS7-2315 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: 7.1.0.Alpha1 Reporter: Blaine Mincey Assignee: Heiko Braun Would be nice to be able to be able to click within the Deployments tab in the Administrative Console and either drill-down into the war file to see the artifacts. Potentially also be able to open up the deployed application if a WAR, etc. -- 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

13 years, 5 months

5
8
0 / 0

[JBoss JIRA] (AS7-2339) Web Console: How to add a new server, or clone an existing server

by Jim Tyrrell (Created) (JIRA)

Web Console: How to add a new server, or clone an existing server ----------------------------------------------------------------- Key: AS7-2339 URL: https://issues.jboss.org/browse/AS7-2339 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun No button/UI elements seem to exist for cloning an existing instance and starting it up. Currently had to go into the host.xml file to add new servers. -- 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

13 years, 5 months

5
13
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