March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMICROCONT-159) Multiple components

by Scott M Stark (JIRA)

Multiple components -------------------- Key: JBMICROCONT-159 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-159 Project: JBoss MicroContainer Issue Type: Bug Components: Deployment Affects Versions: JBossMC_2_0_0 Beta3 Reporter: Scott M Stark There is a problem with how component deployments are handled. When a DeploymentUnit contains multiple sources of component metadata (a jar with a META-INF/*-beans.xml,*-service.xml for example), duplicate processing of components is occuring. This is due to the AbstractComponentDeployer.deployComponents query for the component metadata: protected void deployComponents(DeploymentUnit unit) throws DeploymentException { if (compVisitor == null) return; Set<? extends C> components = unit.getAllMetaData(componentType); for (C component : components) compVisitor.deploy(unit, component); } The DeploymentUnit.getAllMetaData(componentType) for the current DeploymentComponentContext looks to its parent for metadata. This combined with the recursive processing in the MainDeployerImpl.commitDeploy: private void commitDeploy(Deployer deployer, DeploymentContext context, Set<DeploymentContext> components) throws DeploymentException { DeploymentContext[] theComponents = null; if (components != null && components.isEmpty() == false) theComponents = components.toArray(new DeploymentContext[components.size()]); DeploymentUnit unit = context.getDeploymentUnit(); deployer.commitDeploy(unit); try { if (theComponents != null) { for (int i = 0; i < theComponents.length; ++i) { try { Set<DeploymentContext> componentComponents = theComponents[i].getComponents(); commitDeploy(deployer, theComponents[i], componentComponents); } catch (DeploymentException e) { // Unwind the previous components for (int j = i-1; j >=0; --j) prepareUndeploy(deployer, theComponents[j], true); throw e; } } } } catch (DeploymentException e) { prepareUndeploy(deployer, context, false); throw e; } } Results in a structure like: DU(some.jar) + CDC(Bean1) + CDC(ServiceBean2) + CDC(Bean2) + CDC(ServiceBean2) + CDC(ServiceBean1) + CDC(ServiceBean2) + CDC(ServiceBean2) The service deployer components are being recursively added to the kernel components and duplicate install errors result. See the org.jboss.test.deployers.deployer.test.MultipleComponentTypeUnitTestCase -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4199) Up the default

by Scott M Stark (JIRA)

Up the default --------------- Key: JBAS-4199 URL: http://jira.jboss.com/jira/browse/JBAS-4199 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 A request to up the default memory settings to: JAVA_OPTS="-Xms512m -Xmx1024m -Dsun.rmi.dgc.client.gcInterval=3600000 - Dsun.rmi.dgc.server.gcInterval=3600000 -XX:PermSize=256m -XX:MaxPermSize=512m" has been made. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-707) PojoCache to aspectize JDom classes

by Ben Wang (JIRA)

PojoCache to aspectize JDom classes ----------------------------------- Key: JBCACHE-707 URL: http://jira.jboss.com/jira/browse/JBCACHE-707 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: POJOCache This is suggested by Bela during a customer visit. Idea is the customer is using JDom internally to store the documents such as mail, fax, email, parcel, and the like. However, for clustering purpose, each single update on document element would require replication of the whole document. Not a very efficient process. If PojoCache can aspectize JDom classes then fine-grained replication can be done transparently. -- 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, 7 months

3
13
0 / 0

[JBoss JIRA] Created: (JBCACHE-726) PojoCache to replicate static field variable

by Ben Wang (JIRA)

PojoCache to replicate static field variable -------------------------------------------- Key: JBCACHE-726 URL: http://jira.jboss.com/jira/browse/JBCACHE-726 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Priority: Minor Fix For: POJOCache There may be use cases that staic field variable is not final nor constant. In this case, can we replicate that field? The problem is static variable is global scoped, so where should we store it under? Maybe a separate area for global space, but this will break BR, btw. -- 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, 7 months

2
11
0 / 0

[JBoss JIRA] Created: (JBCACHE-727) PojoCache to create an impl for Iterator interface

by Ben Wang (JIRA)

PojoCache to create an impl for Iterator interface -------------------------------------------------- Key: JBCACHE-727 URL: http://jira.jboss.com/jira/browse/JBCACHE-727 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: POJOCache Currently we have proxy impl for Collection classes and the iterator is implemented as inner class. We may need a default Iterator impl as well so when user is doing like, setIterator(Iterator it) we can replace it with our own (such that we can intercept it). -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-732) PojoCache introduces @NonTransient annotation

by Ben Wang (JIRA)

PojoCache introduces @NonTransient annotation --------------------------------------------- Key: JBCACHE-732 URL: http://jira.jboss.com/jira/browse/JBCACHE-732 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: POJOCache We need to introduce a @NonTransient annotation to override the transient modifier. -- 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, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-737) PojoCache to handle Java array

by Ben Wang (JIRA)

PojoCache to handle Java array ------------------------------ Key: JBCACHE-737 URL: http://jira.jboss.com/jira/browse/JBCACHE-737 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: POJOCache Currently we depend on JBoss Aop to handle interception. However, it currently doesn't handle Java array, e.g., pojo[]. We will need this at least to do corase-grained replication. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-756) log.debug calls are unprotected

by Dave Caruana (JIRA)

log.debug calls are unprotected ------------------------------- Key: JBPM-756 URL: http://jira.jboss.com/jira/browse/JBPM-756 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Environment: Window XP, Java 5 Reporter: Dave Caruana Assigned To: Tom Baeyens Within org.jbpm.context.exe.VariableContainer there are calls to log.debug. In particular: line 156: log.debug("create variable '"+name+"' in '"+this+"' with value '"+value+"'"); line 160: log.debug("update variable '"+name+"' in '"+this+"' to value '"+value+"'"); However, they are unprotected i.e. the method is called even if debug logging is not switched on. This is not too much of a problem if the variable value is of a primitive type, but sometimes, values can be complex (including their toString()). "if (log.isDebugEnabled())" statements are missing. -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-723) Eclipse plugin detects error inconsistently and without location information

by Scott Reed (JIRA)

Eclipse plugin detects error inconsistently and without location information ---------------------------------------------------------------------------- Key: JBRULES-723 URL: http://jira.jboss.com/jira/browse/JBRULES-723 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 3.0.5 Environment: JRE 1.5_10, Eclipse 3.2, Windows 2000 Reporter: Scott Reed Assigned To: Mark Proctor The Eclipse plugin is tagging the DRL file in Package Explorer with an error and the Problem tab shows an error in the DRL file, location unknown. However, there is no error shown in the editor and the rules seems to run without any problem. If I edit the DRL by adding white space the error description will change. Once it was ExceptionInInitializer, once it was just blank, once it was complaining about an unknown function and displaying text from log message, and now it is NPE. In all cases no error is displayed in the editor and the rules run without an error. I will load a screen shot. -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-770) PojoCache to support non-serializable and no-aspectized POJO

by Ben Wang (JIRA)

PojoCache to support non-serializable and no-aspectized POJO ------------------------------------------------------------ Key: JBCACHE-770 URL: http://jira.jboss.com/jira/browse/JBCACHE-770 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Priority: Minor Fix For: PojoCache Currently in 2.0, we have to drop the support for the non-serializable and non-aspectized POJO, that is, a POJO that is neither implements Serializable or instrumented. -- 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, 7 months

2
3
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 March 2007