November 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1687) Eclipse based decision table editor

by Michael Neale (JIRA)

Eclipse based decision table editor ----------------------------------- Key: JBRULES-1687 URL: https://jira.jboss.org/jira/browse/JBRULES-1687 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Affects Versions: 4.0.7 Reporter: Michael Neale Assignee: John Graham Fix For: FUTURE We have a few options for this: 1) Edit the guided decision table format (using the same model the web editor uses) 2) Provide an editor that can edit a subset of XLS formatted decision tables 3) Some other format which is unique to this editor... (may be column based rather then row based for instance). In all cases, drl is generated. Each approach has pros/cons, need to investigate some options and come up with some estimate on difficulty. -- 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

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-266) Allow for declarative domain configuration

by Ales Justin (JIRA)

Allow for declarative domain configuration ------------------------------------------ Key: JBDEPLOY-266 URL: https://jira.jboss.org/browse/JBDEPLOY-266 Project: JBoss Deployers Issue Type: Feature Request Components: classloading Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.2.0.Beta1 We should allow for more fine-grained classloading domain configuration. Use JBCL ClassLoadingDomainMetaData for the metadata model. -- 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

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8105) Integrate HornetQ XA Recovery into jbossts out of the box.

by Clebert Suconic (JIRA)

Integrate HornetQ XA Recovery into jbossts out of the box. ---------------------------------------------------------- Key: JBAS-8105 URL: https://jira.jboss.org/browse/JBAS-8105 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 6.0.0.M3 Reporter: Clebert Suconic Assignee: Clebert Suconic Fix For: 6.0.0.M4 as documented on http://hornetq.sourceforge.net/docs/hornetq-2.1.0.Final/user-manual/en/ht... -- 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

15 years, 2 months

6
9
0 / 0

[JBoss JIRA] Created: (JBCL-129) Implement missing features suggested by the OSGi Spec

by Adrian Brock (JIRA)

Implement missing features suggested by the OSGi Spec ----------------------------------------------------- Key: JBCL-129 URL: https://jira.jboss.org/jira/browse/JBCL-129 Project: JBoss ClassLoader Issue Type: Feature Request Components: Modules Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossCL.2.0.9.GA , JBossCL.2.2.0.Alpha See the subtasks for this ongoing work. -- 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

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCL-176) Allow for declarative domain configuration

by Ales Justin (JIRA)

Allow for declarative domain configuration ------------------------------------------ Key: JBCL-176 URL: https://jira.jboss.org/browse/JBCL-176 Project: JBoss ClassLoader Issue Type: Feature Request Components: ClassLoaderSystem, MetaData Reporter: Ales Justin Assignee: Ales Justin Fix For: JBossCL.2.2.0.Beta1 We should allow for more fine-grained CL domain configuration. e.g. jboss-cl-domain.xml or <parent-policy> inside jboss-classloading.xml -- 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

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCL-131) Add a notion of on demand resolution

by Adrian Brock (JIRA)

Add a notion of on demand resolution ------------------------------------ Key: JBCL-131 URL: https://jira.jboss.org/jira/browse/JBCL-131 Project: JBoss ClassLoader Issue Type: Sub-task Components: Dependencies Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossCL.2.0.9.GA , JBossCL.2.2.0.Alpha OSGi has a notion where a dependent classloader/bundle is not rcreated/resolved until somebody wants to import one of its exports. -- 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

15 years, 2 months

3
18
0 / 0

[JBoss JIRA] Created: (JBRULES-2796) NullPointerException in FromNode.destroyCreatedHandles

by Tommy Odom (JIRA)

NullPointerException in FromNode.destroyCreatedHandles ------------------------------------------------------ Key: JBRULES-2796 URL: https://jira.jboss.org/browse/JBRULES-2796 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Reporter: Tommy Odom Assignee: Mark Proctor I received this NullPointerException after upgrading to drools 5.1.1. The NullPointerException is being thrown when the rule executes "update($build);" where $build is set in the LHS from a Build in working memory. I'm not sure if the bug is that matches may be null and a null check needs to be added or if something else is going on causing the tuple to not be found. Caused by: java.lang.NullPointerException at org.drools.reteoo.FromNode.destroyCreatedHandles(FromNode.java:336) at org.drools.reteoo.FromNode.retractLeftTuple(FromNode.java:326) at org.drools.reteoo.CompositeLeftTupleSinkAdapter.doPropagateRetractLeftTuple(CompositeLeftTupleSinkAdapter.java:238) at org.drools.reteoo.CompositeLeftTupleSinkAdapter.propagateRetractRightTuple(CompositeLeftTupleSinkAdapter.java:155) at org.drools.reteoo.JoinNode.retractRightTuple(JoinNode.java:151) at org.drools.reteoo.ModifyPreviousTuples.retractTuples(ModifyPreviousTuples.java:126) at org.drools.reteoo.EntryPointNode.modifyObject(EntryPointNode.java:176) at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1442) at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1349) at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:183) at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:196) at buildSchedulerV2.Rule_Combine_Builds_0.defaultConsequence(Rule_Combine_Builds_0.java:36) at buildSchedulerV2.Rule_Combine_Builds_0DefaultConsequenceInvoker.evaluate(Rule_Combine_Builds_0DefaultConsequenceInvoker.java:49) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:917) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-7909) AOPClassLoaderDeployer breaks OSGi integration

by Thomas Diesler (JIRA)

AOPClassLoaderDeployer breaks OSGi integration ---------------------------------------------- Key: JBAS-7909 URL: https://jira.jboss.org/jira/browse/JBAS-7909 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: AOP Reporter: Thomas Diesler Assignee: Kabir Khan Fix For: JBossAS-6.0.0.M3 11:11:21,726 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to ClassLoader: name=vfs:///home/tdiesler/svn/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/osgi/org.osgi.compendium.jar state=Describe mode=Manual requiredState=ClassLoader: org.jboss.deployers.spi.DeploymentException: Error during deploy: vfs:///home/tdiesler/svn/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/osgi/org.osgi.compendium.jar at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) Caused by: java.lang.IllegalStateException: Have ClassLoaderDomain@12078a{NOT_USED_PLACEHOLDER} but no classloader domain at org.jboss.aop.asintegration.jboss5.AOPVFSClassLoaderDomainRegistry.validateInitMaps(AOPVFSClassLoaderDomainRegistry.java:85) at org.jboss.classpool.plugins.jbosscl.VFSClassLoaderDomainRegistry.initMapsForModule(VFSClassLoaderDomainRegistry.java:119) at org.jboss.classpool.plugins.jbosscl.RegisterModuleCallback.registerModule(RegisterModuleCallback.java:87) at org.jboss.classpool.plugins.jbosscl.JBossClDelegatingClassPoolFactory.create(JBossClDelegatingClassPoolFactory.java:83) at org.jboss.classpool.plugins.jbosscl.JBossClDelegatingClassPoolFactory.create(JBossClDelegatingClassPoolFactory.java:50) at org.jboss.aop.asintegration.jboss5.JBoss5Integration.create(JBoss5Integration.java:157) at org.jboss.classpool.scoped.ScopedClassPoolRepositoryImpl.createScopedClassPool(ScopedClassPoolRepositoryImpl.java:93) at org.jboss.classpool.scoped.ScopedClassPoolRepositoryImpl.registerClassLoader(ScopedClassPoolRepositoryImpl.java:125) at org.jboss.classpool.spi.ClassPoolRepository.registerClassLoader(ClassPoolRepository.java:138) at org.jboss.aop.AspectManager.registerClassLoader(AspectManager.java:846) at org.jboss.aop.asintegration.jboss5.VFSClassLoaderScopingPolicy.registerClassLoader(VFSClassLoaderScopingPolicy.java:46) at org.jboss.aop.asintegration.jboss5.AOPClassLoaderInitializer.registerLoaders(AOPClassLoaderInitializer.java:84) at org.jboss.aop.asintegration.jboss5.AOPClassLoaderInitializer.initializeForUnit(AOPClassLoaderInitializer.java:41) at org.jboss.aop.asintegration.jboss5.AOPClassLoaderDeployer.internalDeploy(AOPClassLoaderDeployer.java:65) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) -- 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

15 years, 2 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-8536) Cannot connect to JSR160 with IPv6

by Thomas Diesler (JIRA)

Cannot connect to JSR160 with IPv6 ---------------------------------- Key: JBAS-8536 URL: https://jira.jboss.org/browse/JBAS-8536 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Management services Reporter: Thomas Diesler Assignee: Dimitris Andreadis Fix For: 7.0.0.M2 jconsole cannot connect using a connection URL when server runs with IPv6 on Fedora13 -- 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

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8657) Provide an installer for AS7

by Thomas Diesler (JIRA)

Provide an installer for AS7 ---------------------------- Key: JBAS-8657 URL: https://jira.jboss.org/browse/JBAS-8657 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Installer Reporter: Thomas Diesler Assignee: Amit Bhayani Brian says I don't see commented out config as a solution. First, at this point, when the file is re-written following an update, comments are lost. That may change, but in general using the file as documentation is fragile. Second, if we added commented out sections for all the various options different subsystems may want to expose, we'll soon have a 1,00 line file full of confusing stuff. I think we're going to need a mix of things to solve this: 1) Ship a few different canned configs files for the most common profiles, with the user able to select which they want via a command line switch. 2) An "examples" dir in the dist where some less common choices can be highlighted. 3) Most importantly, an installer application where users can easily tell us what subsystems they want in their profile. This is the most important part; #1 is mostly to provide a very easy out-of-the-box experience. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
5
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 November 2010