October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4589) Upgrade to JSF RI 1.2_05

by Juergen Zimmermann (JIRA)

Upgrade to JSF RI 1.2_05 ------------------------ Key: JBAS-4589 URL: http://jira.jboss.com/jira/browse/JBAS-4589 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Reporter: Juergen Zimmermann FYI: I ran my testsuite with JSF 1.2_05 RC1 and hadn't any problems. The release notes can be found at https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_05/changelog.html Citation: "Another change which may impact applications is that we've merged all ServletContextListeners into one listener. In 1.2_04, we had three separate listeners. If a container wasn't compliant in invoking listeners defined in a TLD, the developer had to know all three of these. It seemed to have been a mistake to have so many. The only listener to worry about at this point is com.sun.faces.config.ConfigureListener." ConfigureListener is just being used in org/jboss/web/jsf/integration/config/JBossJSFConfigureListener.java So everything looks fine. -- 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

17 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-717) Introduce JBoss-specific replication-only events that actually let you directly write/read the bytestream

by Ben Wang (JIRA)

Introduce JBoss-specific replication-only events that actually let you directly write/read the bytestream --------------------------------------------------------------------------------------------------------- Key: EJBTHREE-717 URL: http://jira.jboss.com/jira/browse/EJBTHREE-717 Project: EJB 3.0 Issue Type: Sub-task Components: Clustering Reporter: Ben Wang Again, per email discussion. Idea is to let user has a fuller control of how replication process should be for sfsb. -- 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

17 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4732) Multihome support: HAJNDI`s HANamingServiceMBean needs a configurable RmiBindAddress (like Naming`s MainMBean)

by Thomas Wenckebach (JIRA)

Multihome support: HAJNDI`s HANamingServiceMBean needs a configurable RmiBindAddress (like Naming`s MainMBean) -------------------------------------------------------------------------------------------------------------- Key: JBAS-4732 URL: http://jira.jboss.com/jira/browse/JBAS-4732 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.0.3 SP1 Reporter: Thomas Wenckebach Assigned To: Brian Stansberry For multihomed servers, it is essential to be able to bind JBoss services to dedicated interfaces (bind address). This requirement is not fulfilled HAJNDI. Affected source files: $JBOSS_SRC/cluster/src/main/org/jboss/ha/jndi/HANamingServiceMBean.java $JBOSS_SRC/cluster/src/main/org/jboss/ha/jndi/HANamingService.java -- 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

17 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-169) Add support for setting the SchemaValidation usage to ObjectModelFactoryDeployer

by Scott M Stark (JIRA)

Add support for setting the SchemaValidation usage to ObjectModelFactoryDeployer -------------------------------------------------------------------------------- Key: JBMICROCONT-169 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-169 Project: JBoss MicroContainer Issue Type: Feature Request Components: Deployment Reporter: Scott M Stark Assigned To: Scott M Stark To address JBAS-4193, the ObjectModelFactoryDeployer needs a flag controlling the Unmarshaller.SchemaValidation behavior. -- 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

17 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JGRP-410) Convert to junit 4 (or testng)

by Bela Ban (JIRA)

Convert to junit 4 (or testng) ------------------------------ Key: JGRP-410 URL: http://jira.jboss.com/jira/browse/JGRP-410 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.x Advantage: use of annotations plus start of channel before *all* tests and tear down afterwards (faster execution of test suite) -- 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

17 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1064) review and update assigned JIRA tasks

by William DeCoste (JIRA)

review and update assigned JIRA tasks ------------------------------------- Key: EJBTHREE-1064 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1064 Project: EJB 3.0 Issue Type: Task Reporter: William DeCoste Assigned To: William DeCoste -- 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

17 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4545) Modification of jsp causes redeploy of war

by Scott M Stark (JIRA)

Modification of jsp causes redeploy of war ------------------------------------------ Key: JBAS-4545 URL: http://jira.jboss.com/jira/browse/JBAS-4545 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 Adding content to a war is resulting in a failed redeploy of the war. [starksm@succubus deploy]$ touch jmx-console.war/tst.jsp 17:23:34,670 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta3 (build: SVNTag=JBoss_5_0_0_Beta3 date=200707111842)] Started in 25s:815ms 17:25:30,753 INFO [TomcatDeployment] undeploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war 17:25:30,840 ERROR [WebAppParsingDeployer] Error during deploy: vfsfile:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ org.jboss.deployers.spi.DeploymentException: Error parsing meta data jmx-console.war/WEB-INF/web.xml at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.vfs.spi.deployer.ObjectModelFactoryDeployer.parse(ObjectModelFactoryDeployer.java:90) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:201) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:177) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:140) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:164) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstall(DeployersImpl.java:657) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstall(DeployersImpl.java:623) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:587) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:304) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1257) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:685) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:813) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:735) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:573) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:374) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:426) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:340) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:287) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:219) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: vfsfile:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/WEB-INF/web.xml@4,46 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:173) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:180) at org.jboss.deployers.vfs.spi.deployer.ObjectModelFactoryDeployer.parse(ObjectModelFactoryDeployer.java:86) ... 28 more Caused by: java.lang.NullPointerException at org.jboss.util.xml.JBossEntityResolver.loadClasspathResource(JBossEntityResolver.java:506) at org.jboss.util.xml.JBossEntityResolver.resolvePublicID(JBossEntityResolver.java:314) at org.jboss.util.xml.JBossEntityResolver.resolveEntity(JBossEntityResolver.java:244) at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:169) ... 30 more 17:25:30,848 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ state=Not Installed mode=Manual requiredState=Parse org.jboss.deployers.spi.DeploymentException: Error parsing meta data jmx-console.war/WEB-INF/web.xml at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.vfs.spi.deployer.ObjectModelFactoryDeployer.parse(ObjectModelFactoryDeployer.java:90) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:201) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:177) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:140) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:164) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstall(DeployersImpl.java:657) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstall(DeployersImpl.java:623) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:587) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:304) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1257) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:685) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:813) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:735) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:573) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:374) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:426) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:340) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:287) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:219) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: vfsfile:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/WEB-INF/web.xml@4,46 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:173) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:180) at org.jboss.deployers.vfs.spi.deployer.ObjectModelFactoryDeployer.parse(ObjectModelFactoryDeployer.java:86) ... 28 more Caused by: java.lang.NullPointerException at org.jboss.util.xml.JBossEntityResolver.loadClasspathResource(JBossEntityResolver.java:506) at org.jboss.util.xml.JBossEntityResolver.resolvePublicID(JBossEntityResolver.java:314) at org.jboss.util.xml.JBossEntityResolver.resolveEntity(JBossEntityResolver.java:244) at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:169) ... 30 more 17:25:30,850 WARN [HDScanner] Failed to process changes org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** CONTEXTS IN ERROR: Name -> Error vfsfile:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ -> java.lang.NullPointerException at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:552) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:379) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:288) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:219) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) -- 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

17 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-4310) Deployed archive is locked in JBoss 5.0 Beta2

by Wolfgang Knauf (JIRA)

Deployed archive is locked in JBoss 5.0 Beta2 --------------------------------------------- Key: JBAS-4310 URL: http://jira.jboss.com/jira/browse/JBAS-4310 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta2 Environment: WinXP64 Sun JDK 1.5.0_11-b03 Reporter: Wolfgang Knauf Deploy an Java5 EAR application by copying it to server\default\deploy\ It will be deployed. Now try to undeploy it by deleting the file => file is in use and cannot be deleted. I verified it with this EAR: http://www.informatik.fh-wiesbaden.de/~knauf/public/Stateless.ear The same problem also occurs if I deploy only the EJB jar file from the sample. -- 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

17 years, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (JBAS-4396) implement support for configuring, controlling and monitoring: Datasources and JMS

by Mark Spritzler (JIRA)

implement support for configuring, controlling and monitoring: Datasources and JMS ---------------------------------------------------------------------------------- Key: JBAS-4396 URL: http://jira.jboss.com/jira/browse/JBAS-4396 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Mark Spritzler Implement support for configuring, controlling and monitoring the following resource types * DataSources o XA o LocalTx o NoTx * JMS Destinations o Queues o Topics -- 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

17 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-116) Validation of paths on case insensative file systems

by Scott M Stark (JIRA)

Validation of paths on case insensative file systems ---------------------------------------------------- Key: JBMICROCONT-116 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-116 Project: JBoss MicroContainer Issue Type: Task Affects Versions: JBossMC_2_0_0 Beta Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC_2_0_0_CR1 Remy brought up the issue of being able to validate whether a given url mapping is valid when case insensative file systems are in use. See the forum reference for the details. We should be able to configure the VFS file context to allow for case sensative finds when the underlying file system is not case sensative. -- 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

17 years, 10 months

4
14
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 October 2007