April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1124) CMS needs to allow admins to make pages as live w/o editing the page

by Alex Pinkin (JIRA)

CMS needs to allow admins to make pages as live w/o editing the page -------------------------------------------------------------------- Key: JBPORTAL-1124 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1124 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Reporter: Alex Pinkin Assigned To: Roy Russo To make pages live today, you have to edit the page, and that action creates a new version. Users need to be able to make particular versions of a file live without creating a new version. -- 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, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-4053) EJB TimerService createTimer swallows underlying exception

by Jim Moran (JIRA)

EJB TimerService createTimer swallows underlying exception ---------------------------------------------------------- Key: JBAS-4053 URL: http://jira.jboss.com/jira/browse/JBAS-4053 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2, EJB3 Affects Versions: JBossAS-4.0.5.GA Reporter: Jim Moran Assigned To: Scott M Stark javax.ejb.TimerService.createTimer implementation, org.jboss.ejb.txtimer.TimerServiceImpl.createTimer does not throw EJBException for "system-level failure" as per spec but rather just returns null and logs an error for any Exception. >From TimerServerImpl.createTimer: catch (Exception e) { log.error("Cannot create txtimer", e); return null; } -- 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, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-4185) Clean up jboss messaging 1.2.0.GA issues

by Scott M Stark (JIRA)

Clean up jboss messaging 1.2.0.GA issues ---------------------------------------- Key: JBAS-4185 URL: http://jira.jboss.com/jira/browse/JBAS-4185 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMS service, Test Suite Reporter: Scott M Stark Assigned To: Ovidiu Feodorov Fix For: JBossAS-5.0.0.Beta2 There are many failures and broken jms tests that need cleanup to validate the jboss messaging integration. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-339) Remove thread for handling of merge views in Multiplexer once we have out-of-band messages

by Bela Ban (JIRA)

Remove thread for handling of merge views in Multiplexer once we have out-of-band messages ------------------------------------------------------------------------------------------ Key: JGRP-339 URL: http://jira.jboss.com/jira/browse/JGRP-339 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 There is no need then to use a separate thread -- 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, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-107) Make AbstractParsingDeployer namespace aware

by Thomas Diesler (JIRA)

Make AbstractParsingDeployer namespace aware -------------------------------------------- Key: JBMICROCONT-107 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-107 Project: JBoss MicroContainer Issue Type: Feature Request Components: Deployment Reporter: Thomas Diesler Currently the parsing deployers work of the metadata filename (i.e. application-client.xml) only This deployer should look at the namespaceURI of the root element to see if it should process the dd. Note, jboss dds have a doctype.publicId instead of a namespaceURI. -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-4379) MC beans deployed twice because of jacc service

by Thomas Diesler (JIRA)

MC beans deployed twice because of jacc service ----------------------------------------------- Key: JBAS-4379 URL: http://jira.jboss.com/jira/browse/JBAS-4379 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR1 The latest jboss.sar contains MC bean definitions as well as a war [tdiesler@tddell build]$ jar -tf ../integration-jboss50/output/lib/jbossws50.sar | sort jbossws-context.war jbossws-core.jar META-INF/ META-INF/jbossws-beans.xml META-INF/MANIFEST.MF META-INF/standard-jaxrpc-client-config.xml META-INF/standard-jaxrpc-endpoint-config.xml META-INF/standard-jaxws-client-config.xml META-INF/standard-jaxws-endpoint-config.xml policy.jar wsdl4j.jar xmlsec.jar It seams that because of the JACC service the bean definitions are deployed twice 12:55:04,409 ERROR [BeanMetaDataDeployer] Error during deployment: jboss:id=jbossws.sar,service=jacc org.jboss.deployers.spi.DeploymentException: Error deploying: KernelLocator at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:71) at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:42) at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:56) at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:170) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:592) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:603) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:603) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:476) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:406) -- 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, 10 months

3
5
0 / 0

[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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-451) Disabling a network interface and subsequent re-enabling it (on Windows) doesn't merge

by Bela Ban (JIRA)

Disabling a network interface and subsequent re-enabling it (on Windows) doesn't merge -------------------------------------------------------------------------------------- Key: JGRP-451 URL: http://jira.jboss.com/jira/browse/JGRP-451 Project: JGroups Issue Type: Feature Request Affects Versions: 2.5 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 - Run 2 Draw instances: 1 cluster of 2 - Disable the interface (on Windows). [Need to check whether ifcfg down eth0 causes the same issue] - 2 clusters of 1 each - Re-enable the interface: members don't merge as sending on the interface always fails -- 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, 10 months

1
3
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, 10 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, 10 months

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