December 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2927) WS provide/consume tools have typo in java.endorsed.dirs definition

by Rostislav Svoboda (Created) (JIRA)

WS provide/consume tools have typo in java.endorsed.dirs definition ------------------------------------------------------------------- Key: AS7-2927 URL: https://issues.jboss.org/browse/AS7-2927 Project: Application Server 7 Issue Type: Feature Request Components: Web Services Affects Versions: 7.1.0.Beta1 Reporter: Rostislav Svoboda Assignee: Rostislav Svoboda Fix For: 7.1.0.CR1 WS provide/consume tools has typo in java.endorsed.dirs definition Affected files: wsprovide.sh wsprovide.bat wsconsume.sh -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] (AS7-2928) CLONE - WS provide/consume tools have typo in java.endorsed.dirs definition

by Rostislav Svoboda (Created) (JIRA)

CLONE - WS provide/consume tools have typo in java.endorsed.dirs definition --------------------------------------------------------------------------- Key: AS7-2928 URL: https://issues.jboss.org/browse/AS7-2928 Project: Application Server 7 Issue Type: Feature Request Components: Web Services Affects Versions: 7.1.0.Beta1 Reporter: Rostislav Svoboda Assignee: Rostislav Svoboda Fix For: 7.1.0.CR1 WS provide/consume tools has typo in java.endorsed.dirs definition Affected files: wsprovide.sh wsprovide.bat wsconsume.sh change $JBOSS_HOME/modules/com/sun/xml/bin/main to $JBOSS_HOME/modules/com/sun/xml/bind/main ( bin --> bind ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2521) Deploying RichFaces application causes Critical error during deployment

by Juraj Huska (Created) (JIRA)

Deploying RichFaces application causes Critical error during deployment ----------------------------------------------------------------------- Key: AS7-2521 URL: https://issues.jboss.org/browse/AS7-2521 Project: Application Server 7 Issue Type: Bug Components: Deployment, JSF Affects Versions: 7.1.0.Beta1 Environment: AS: jboss-as-7.1.0.Alpha2-SNAPSHOT application deployed: richfaces-showcase-4.1.0.20111101-M4-jbas7.war Reporter: Juraj Huska Assignee: Thomas Diesler I have tried to deploy richfaces-showcase application to the AS, which I have downloaded from https://ci.jboss.org/jenkins/view/JBoss%20AS/job/JBoss-AS-7.0.x/. During deployment I am encountering error with this stacktrace: {code} 18:24:36,699 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-5) Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:376) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:225) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3845) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:81) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] Caused by: java.lang.UnsupportedOperationException at javax.faces.context.FacesContext.getExceptionHandler(FacesContext.java:280) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.event.ExceptionQueuedEventContext.getListenersForEventClass(ExceptionQueuedEventContext.java:262) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2077) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:286) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:244) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:293) [jboss-as-weld-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:302) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) [jboss-as-weld-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:601) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:370) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] ... 9 more 18:24:36,701 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:292) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3845) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:81) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] Caused by: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:376) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:225) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] ... 8 more Caused by: java.lang.UnsupportedOperationException at javax.faces.context.FacesContext.getExceptionHandler(FacesContext.java:280) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.event.ExceptionQueuedEventContext.getListenersForEventClass(ExceptionQueuedEventContext.java:262) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2077) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:286) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:244) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:293) [jboss-as-weld-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:302) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) [jboss-as-weld-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:601) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:370) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] ... 9 more 18:24:36,703 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart 18:24:36,703 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/showcase] startup failed due to previous errors 18:24:36,704 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-5) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:957) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:316) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:126) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:328) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3489) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3994) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3912) [jbossweb-7.0.2.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:81) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] 18:24:36,707 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./showcase: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./showcase: failed to start context at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:86) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] 18:24:36,911 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "richfaces-showcase-4.1.0.20111014-M3-jbas7.war" was rolled back with failure message {"Failed services" => {"jboss.web.deployment.default-host./showcase" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./showcase: failed to start context"}} 18:24:36,912 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) Service status report Services which failed to start: service jboss.web.deployment.default-host./showcase: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./showcase: failed to start context 18:24:36,915 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Failed services" => {"jboss.web.deployment.default-host./showcase" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./showcase: failed to start context"}}}} {code} The deployment is failing approximately 4 times from total of 5 times, I mean I am able to deploy that application, but randomly this error is thrown. The mentioned application is released in jboss staging repository, or can be cloned from https://github.com/richfaces/showcase -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
6
0 / 0

[JBoss JIRA] (AS7-2860) Provider general EE descriptor validation

by Thomas Diesler (Created) (JIRA)

Provider general EE descriptor validation ----------------------------------------- Key: AS7-2860 URL: https://issues.jboss.org/browse/AS7-2860 Project: Application Server 7 Issue Type: Task Components: Server Reporter: Thomas Diesler Assignee: Thomas Diesler -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] (AS7-2925) resource adapters subsystem have to marshal also defaults it set

by Stefano Maestri (Created) (JIRA)

resource adapters subsystem have to marshal also defaults it set ---------------------------------------------------------------- Key: AS7-2925 URL: https://issues.jboss.org/browse/AS7-2925 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.Beta1 Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2917) Upgrade Resteasy to 2.3.0.GA

by Bill Burke (Created) (JIRA)

Upgrade Resteasy to 2.3.0.GA ---------------------------- Key: AS7-2917 URL: https://issues.jboss.org/browse/AS7-2917 Project: Application Server 7 Issue Type: Task Reporter: Bill Burke There have a been a bunch of bug fixes since 2.2.3, so an upgrade is desirable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] (AS7-2418) Looking up BeanManager from JNDI doesn't work in ServletRequestListener.requestInitialized()

by Christian Kaltepoth (Created) (JIRA)

Looking up BeanManager from JNDI doesn't work in ServletRequestListener.requestInitialized() -------------------------------------------------------------------------------------------- Key: AS7-2418 URL: https://issues.jboss.org/browse/AS7-2418 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Affects Versions: 7.0.2.Final Reporter: Christian Kaltepoth Assignee: Stuart Douglas Looking up BeanManager from JNDI doesn't work if the lookup is done from ServletRequestListener.requestInitialized(). You can reproduce this issue by simply adding this class to CDI WAR application deployed to AS 7.0.2.Final: {code} @WebListener @WebFilter(urlPatterns = "/*") public class TestListener implements ServletRequestListener, Filter { @Override public void init(FilterConfig config) throws ServletException { lookupBeanManager("Filter.init()"); } @Override public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException { lookupBeanManager("filter.doFilter()"); chain.doFilter(request, response); } @Override public void destroy() { } @Override public void requestInitialized(ServletRequestEvent event) { lookupBeanManager("ServletRequestListener.requestInitialized()"); } @Override public void requestDestroyed(ServletRequestEvent arg0) { } private void lookupBeanManager(String calledFrom) { try { InitialContext ic = new InitialContext(); Object beanManager = ic.lookup("java:comp/BeanManager"); System.out.println(calledFrom + ": Lookup SUCCESS"); } catch (NamingException e) { System.out.println(calledFrom + ": Lookup FAILED"); } } } {code} You will see that the lookup works fine for the Filter methods {{initFilter}} and {{doFilter}}, but not for {{requestInitialized}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
4
0 / 0

[JBoss JIRA] Created: (JBAS-8679) Add xml comment support to the domain model

by Jason Greene (JIRA)

Add xml comment support to the domain model ------------------------------------------- Key: JBAS-8679 URL: https://jira.jboss.org/browse/JBAS-8679 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jason Greene Fix For: 7.0.0.Beta1 For usability reasons, we should attach an xml comment to the nearest AbstractModelElement, so that they can be recreated when the model is altered. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-8140) Standard JTS-based configuration

by Brian Stansberry (JIRA)

Standard JTS-based configuration -------------------------------- Key: JBAS-8140 URL: https://jira.jboss.org/browse/JBAS-8140 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> Would like to have a configuration with JBossTM JTS implementation >> already installed and optimized for servers that need distributed >> transactions. Proper transaction management is an advanced topic for >> JBoss admins and having Redhat's expertise already configured on a >> server is very reassuring. -- 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

14 years, 7 months

5
8
0 / 0

[JBoss JIRA] (AS7-2920) Change the ObjectName domain for the exposed management model to jboss.as

by Brian Stansberry (Created) (JIRA)

Change the ObjectName domain for the exposed management model to jboss.as ------------------------------------------------------------------------- Key: AS7-2920 URL: https://issues.jboss.org/browse/AS7-2920 Project: Application Server 7 Issue Type: Task Components: Domain Management, JMX Affects Versions: 7.1.0.Beta1 Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker Fix For: 7.1.0.CR1 The mbeans representing the JBoss AS management model resources are in their own JMX domain. Currently it is named jboss.model, which is too generic. Per discussion with Jason we want it to be jboss.as. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
1
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 2011