December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBOSGI-4) Deployer changes for OSGi

by Adrian Brock (JIRA)

Deployer changes for OSGi ------------------------- Key: JBOSGI-4 URL: http://jira.jboss.com/jira/browse/JBOSGI-4 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Adrian Brock Assigned To: Adrian Brock This is a holder task for the Deployer changes need to make OSGi work and integrate OSGi bundles with other JBoss deployments (and vice versa). -- 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

18 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-15) Create a concrete subclass of the VFSClassLoaderPolicy that has injectable policy

by Adrian Brock (JIRA)

Create a concrete subclass of the VFSClassLoaderPolicy that has injectable policy --------------------------------------------------------------------------------- Key: JBOSGI-15 URL: http://jira.jboss.com/jira/browse/JBOSGI-15 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Adrian Brock Assigned To: Adrian Brock Once the VFSClassLoader is done JBOSGI-14, we need to create a concrete subclass that allows injectable policy. i.e. setters. This will be used by the both JBossAS and OSGi through the Deployer layer to construct classloaders from the classloading dependencies/rules they define. -- 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

18 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1111) BankBean does not implement its remote interface

by Adrian Brock (JIRA)

BankBean does not implement its remote interface ------------------------------------------------ Key: EJBTHREE-1111 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1111 Project: EJB 3.0 Issue Type: Bug Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: AS 5.0.0.Beta3 The BankBean in the ejb3 testsuite doesn't implement its remote interface as required by spec (section 4.4) -- 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

18 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-189) Make DeploymentContext totally invisible

by Adrian Brock (JIRA)

Make DeploymentContext totally invisible ---------------------------------------- Key: JBMICROCONT-189 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-189 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.GA The DeploymentContext should be totally invisble (possible still exposed for testing/debugging purposes as a deprecated method on the main deployer?) There's still a number of places where it is showing up. See the attached forum thread for a discussion. -- 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

18 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-201) Create a generic describing deployer for dependencies

by Adrian Brock (JIRA)

Create a generic describing deployer for dependencies ----------------------------------------------------- Key: JBMICROCONT-201 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-201 Project: JBoss MicroContainer Issue Type: Sub-task Components: Deployment Reporter: Adrian Brock There should be a generic describing stage deployer that looks at all the metadata and creates dependencies from it, either via an interface implemented by the metadata or a annotation on the metadata describing an adapter/factory. -- 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

18 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-219) Update the microcontainer parsing to use the jbossxb annotations

by Adrian Brock (JIRA)

Update the microcontainer parsing to use the jbossxb annotations ---------------------------------------------------------------- Key: JBMICROCONT-219 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-219 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Affects Versions: JBossMC-2.0.0.Beta6 Reporter: Adrian Brock Assigned To: Ales Justin Fix For: JBossMC-2.0.0.CR1 There is a prototype of using JBossXB annotations to parse the Microcontainer xml here; http://viewvc.jboss.org/cgi-bin/viewvc.cgi/common/jbossxb-builder/trunk/s... This is basically a clone of the MC's xml parsing testsuite and annoations on the metdata from about 5 months ago, so it will be out-of-date wrt to new features since then. This will replace the schema binding initializer code, making jboss-kernel.jar a lot smaller. ;-) Also, there's a version for the javabean parsing from the container project here: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/common/jbossxb-builder/trunk/s... I doubt this has changed since I did it? You probably want to do the javabean one first so you understand what is going on. -- 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

18 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-203) Analyze microcontainer dependencies

by Paul Gier (JIRA)

Analyze microcontainer dependencies ----------------------------------- Key: JBMICROCONT-203 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-203 Project: JBoss MicroContainer Issue Type: Task Components: General Reporter: Paul Gier Assigned To: Paul Gier Fix For: JBossMC-2.0.0.CR1 Using the mvn dependency plugin "mvn dependency:analyze", I noticed that several of the microcontainer modules are using transitive dependencies directly and/or are listing dependencies that aren't used. This dependency tool should be used to clean up these dependencies a bit to make it more clear which ones are required for compilation. -- 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

18 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-207) Factor out container and classloading projects from mc

by Scott M Stark (JIRA)

Factor out container and classloading projects from mc ------------------------------------------------------ Key: JBMICROCONT-207 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-207 Project: JBoss MicroContainer Issue Type: Task Affects Versions: JBossMC-2.0.0.Beta4 Reporter: Scott M Stark Fix For: JBossMC-2.0.0.CR1 There is a circular dependency between aop and mc due to aop depending on the container project. Both the container and classloader projects need to be moved out of the mc. -- 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

18 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-206) The JMXLifecycleCallback should be registering with the ServiceController inside the appserver

by Adrian Brock (JIRA)

The JMXLifecycleCallback should be registering with the ServiceController inside the appserver ---------------------------------------------------------------------------------------------- Key: JBMICROCONT-206 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-206 Project: JBoss MicroContainer Issue Type: Sub-task Components: General Affects Versions: JBossMC-2.0.0.Beta4 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.CR1 The JMXLifecycleCallback needs to be made extensible so that in JBossAS we can do the registration with the ServiceController instead of directly with the MBeanServer. -- 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

18 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-959) Investigate performance delta with MR3 and 3.0.6

by Michael Neale (JIRA)

Investigate performance delta with MR3 and 3.0.6 ------------------------------------------------ Key: JBRULES-959 URL: http://jira.jboss.com/jira/browse/JBRULES-959 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: All Affects Versions: 4.0.0.MR3 Reporter: Michael Neale Assigned To: Michael Neale // Rule execution time test // I give the DRL one fact of class BOBOMessage (made final due to Michael's suggestion) // The "message" member of my BOBOMessage fact contains a random combination of the keywords the rule is designed to match // A random BOBOMessage like that is generated before every execution // MR3's performance: 11:43:01,135 INFO [RuleLoadBean] Average rule execution time in ms: 2.3991 // What is measured: ruleBase = rsl.getGroupRuleBase(group); // That retrieves the RuleBase from the cache StatelessSession session = ruleBase.newStatelessSession(); session.execute(toBeAsserted.get(group.getId()).toArray()); // 3.0.6's performance: 12:09:40,446 INFO [RuleLoadBean] Average rule execution time in ms: 0.7726 // What is measured: ruleBase = rsl.getGroupRuleBase(group); // That retrieves the RuleBase from the cache WorkingMemory wm = ruleBase.newWorkingMemory(); for (Iterator j = toBeAsserted.get(group.getId()).iterator(); j.hasNext();) wm.assertObject(j.next()); wm.fireAllRules(); // The DRL: package com.smsc.mitto.rules import com.smsc.mitto.rules.client.BOBOMessage; import java.lang.String; rule "14" salience 0 activation-group "14" when m : BOBOMessage( message matches ".*BOBO.*") then System.out.println( "BOBO WAS SEEN" ); System.out.println( "BOBO WAS REALLY SEEN, DUDE" ); drools.setFocus( "17" ); end rule "17" salience -20 agenda-group "17" activation-group "17" when m : BOBOMessage( message matches ".*CACA.*") then System.out.println( "CACA WAS SEEN" ); drools.setFocus( "19" ); end rule "19" salience -10 agenda-group "19" activation-group "19" when m : BOBOMessage( message matches ".*BABA.*") then System.out.println( "BABA WAS SEEN" ); drools.setFocus( "21" ); end rule "19false" salience -20 agenda-group "19" activation-group "19" when eval(true) then drools.setFocus( "21" ); end rule "21" salience -20 agenda-group "21" activation-group "21" when m : BOBOMessage( message matches ".*BIBI.*") then System.out.println( "BIBI WAS SEEN" ); drools.setFocus( "23" ); end rule "21false" salience -30 agenda-group "21" activation-group "21" when eval(true) then drools.setFocus( "23" ); end rule "17false" salience -30 agenda-group "17" activation-group "17" when eval(true) then drools.setFocus( "23" ); end rule "23" salience -30 agenda-group "23" activation-group "23" when m : BOBOMessage( message matches ".*POOP.*") then System.out.println( "POOP WAS SEEN" ); drools.setFocus( "25" ); end rule "23false" salience -40 agenda-group "23" activation-group "23" when eval(true) then drools.setFocus( "25" ); end rule "14false" salience -10 agenda-group "14" activation-group "14" when eval(true) then drools.setFocus( "25" ); end rule "25" salience -10 agenda-group "25" activation-group "25" when m : BOBOMessage( message matches ".*SUPER.*") then System.out.println( "SUPER WAS SEEN" ); end -- 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

18 years, 4 months

4
8
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 December 2007