[JBoss JIRA] (GTNPORTAL-3107) NullPointerException during Portlet Deployment when there is no <display-name> in web.xml
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3107?page=com.atlassian.jira.pl... ]
Work on GTNPORTAL-3107 stopped by Vu Viet Phuong.
> NullPointerException during Portlet Deployment when there is no <display-name> in web.xml
> -----------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3107
> URL: https://issues.jboss.org/browse/GTNPORTAL-3107
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Vu Viet Phuong
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> I am not sure if this is a bug or feature. Anyway, GateIn does not like WARs which do not have {{<display-name>}} in their {{web.xml}}. I guess the portal should be able to work around the non-availabbility of an explicit <display-name> through working with the default one?
> Steps to reproduce:
> * Take any quickstart from https://github.com/gatein/gatein-portal-quickstart, e.g. simplest-hello-world-portlet
> * remove {{<display-name>}} from {{web.xml}}
> * Compile & deploy
> * Expected: The portal should swallow the portlet app without any error.
> * Current: The portal throws this NPE
> {code}
> [0m[31m09:20:11,195 ERROR [org.exoplatform.web.application.javascript.JavascriptConfigDeployer] (ServerService Thread Pool -- 93) An error occurs while registering 'Javascript in gatein-resources.xml' from the context 'null': java.lang.IllegalArgumentException: The context name cannot be null
> at org.exoplatform.container.definition.PortalContainerConfig.getPortalContainerNames(PortalContainerConfig.java:502) [exo.kernel.container-2.4.3-GA-redhat-1.jar:2.4.3-GA-redhat-1]
> at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:474) [exo.kernel.container-2.4.3-GA-redhat-1.jar:2.4.3-GA-redhat-1]
> at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.add(JavascriptConfigDeployer.java:96) [exo.portal.component.web.resources-3.6.0.Beta02-redhat-1.jar:3.6.0.Beta02-redhat-1]
> at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.onEvent(JavascriptConfigDeployer.java:71) [exo.portal.component.web.resources-3.6.0.Beta02-redhat-1.jar:3.6.0.Beta02-redhat-1]
> at org.gatein.wci.ServletContainer.safeFireEvent(ServletContainer.java:319) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer.fireEvent(ServletContainer.java:338) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer.access$400(ServletContainer.java:56) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer$RegistrationImpl.registerWebApp(ServletContainer.java:462) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.jboss.JB7ServletContainerContext.start(JB7ServletContainerContext.java:369) [wci-jboss7-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.jboss.JB7ServletContainerContext.lifecycleEvent(JB7ServletContainerContext.java:223) [wci-jboss7-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3772) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_19]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_19]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_19]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_19]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (GTNPORTAL-3107) NullPointerException during Portlet Deployment when there is no <display-name> in web.xml
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3107?page=com.atlassian.jira.pl... ]
Vu Viet Phuong commented on GTNPORTAL-3107:
-------------------------------------------
The problem is: Kernel project use servletContext.getServletContextName() --> but this method return "null" if there is no <display-name> in web.xml
- So we may update GateIn document : any WebApp that is portal container's dependencies must declare <display-name> (in this case, the webapp container gatein-resouces.xml)
- Or we need to improve Kernel to use other value (maybe context path) when servlet context name is null. I've create a jira for this https://jira.exoplatform.org/browse/KER-264
> NullPointerException during Portlet Deployment when there is no <display-name> in web.xml
> -----------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3107
> URL: https://issues.jboss.org/browse/GTNPORTAL-3107
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Vu Viet Phuong
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> I am not sure if this is a bug or feature. Anyway, GateIn does not like WARs which do not have {{<display-name>}} in their {{web.xml}}. I guess the portal should be able to work around the non-availabbility of an explicit <display-name> through working with the default one?
> Steps to reproduce:
> * Take any quickstart from https://github.com/gatein/gatein-portal-quickstart, e.g. simplest-hello-world-portlet
> * remove {{<display-name>}} from {{web.xml}}
> * Compile & deploy
> * Expected: The portal should swallow the portlet app without any error.
> * Current: The portal throws this NPE
> {code}
> [0m[31m09:20:11,195 ERROR [org.exoplatform.web.application.javascript.JavascriptConfigDeployer] (ServerService Thread Pool -- 93) An error occurs while registering 'Javascript in gatein-resources.xml' from the context 'null': java.lang.IllegalArgumentException: The context name cannot be null
> at org.exoplatform.container.definition.PortalContainerConfig.getPortalContainerNames(PortalContainerConfig.java:502) [exo.kernel.container-2.4.3-GA-redhat-1.jar:2.4.3-GA-redhat-1]
> at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:474) [exo.kernel.container-2.4.3-GA-redhat-1.jar:2.4.3-GA-redhat-1]
> at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.add(JavascriptConfigDeployer.java:96) [exo.portal.component.web.resources-3.6.0.Beta02-redhat-1.jar:3.6.0.Beta02-redhat-1]
> at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.onEvent(JavascriptConfigDeployer.java:71) [exo.portal.component.web.resources-3.6.0.Beta02-redhat-1.jar:3.6.0.Beta02-redhat-1]
> at org.gatein.wci.ServletContainer.safeFireEvent(ServletContainer.java:319) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer.fireEvent(ServletContainer.java:338) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer.access$400(ServletContainer.java:56) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer$RegistrationImpl.registerWebApp(ServletContainer.java:462) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.jboss.JB7ServletContainerContext.start(JB7ServletContainerContext.java:369) [wci-jboss7-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.jboss.JB7ServletContainerContext.lifecycleEvent(JB7ServletContainerContext.java:223) [wci-jboss7-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3772) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_19]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_19]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_19]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_19]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (GTNPORTAL-3226) Composite CSS file of portlet in portals is not build properly
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3226?focusedWorklogId=12429745&... ]
Trong Tran logged work on GTNPORTAL-3226:
-----------------------------------------
Author: Trong Tran
Created on: 17/Sep/13 11:50 PM
Start Date: 17/Sep/13 11:50 PM
Worklog Time Spent: 30 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 1 hour)
Time Spent: 30 minutes
Worklog Id: (was: 12429745)
> Composite CSS file of portlet in portals is not build properly
> --------------------------------------------------------------
>
> Key: GTNPORTAL-3226
> URL: https://issues.jboss.org/browse/GTNPORTAL-3226
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Son Tran
> Assignee: Son Tran
> Priority: Minor
> Labels: backlogs
> Original Estimate: 1 hour
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> Group CSS of portlets in portal in 1 composite file.
> Currently, GateIn has already provided this machanism, but it is missing portlets that are not in the first UIPortal child level
> The problem is in: UIPortalApplication#getPortalPortletSkins method. It only find the portlets in 1 level descendants
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (GTNPORTAL-3226) Composite CSS file of portlet in portals is not build properly
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3226?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3226:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 3.7.0.Final
Resolution: Done
> Composite CSS file of portlet in portals is not build properly
> --------------------------------------------------------------
>
> Key: GTNPORTAL-3226
> URL: https://issues.jboss.org/browse/GTNPORTAL-3226
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Son Tran
> Assignee: Son Tran
> Priority: Minor
> Labels: backlogs
> Fix For: 3.7.0.Final
>
> Original Estimate: 1 hour
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> Group CSS of portlets in portal in 1 composite file.
> Currently, GateIn has already provided this machanism, but it is missing portlets that are not in the first UIPortal child level
> The problem is in: UIPortalApplication#getPortalPortletSkins method. It only find the portlets in 1 level descendants
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (GTNPORTAL-3225) Height and width of Portlets are not affected after setting
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3225?focusedWorklogId=12429744&... ]
Trong Tran logged work on GTNPORTAL-3225:
-----------------------------------------
Author: Trong Tran
Created on: 17/Sep/13 11:45 PM
Start Date: 17/Sep/13 11:45 PM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 1 hour)
Time Spent: 1 hour
Worklog Id: (was: 12429744)
> Height and width of Portlets are not affected after setting
> -----------------------------------------------------------
>
> Key: GTNPORTAL-3225
> URL: https://issues.jboss.org/browse/GTNPORTAL-3225
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Son Tran
> Assignee: Son Tran
> Priority: Minor
> Labels: backlogs
> Fix For: 3.7.0.Final
>
> Original Estimate: 1 hour
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> Height and width of Portlets are not affected after setting
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (GTNPORTAL-3107) NullPointerException during Portlet Deployment when there is no <display-name> in web.xml
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3107?page=com.atlassian.jira.pl... ]
Vu Viet Phuong reassigned GTNPORTAL-3107:
-----------------------------------------
Assignee: Vu Viet Phuong
> NullPointerException during Portlet Deployment when there is no <display-name> in web.xml
> -----------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3107
> URL: https://issues.jboss.org/browse/GTNPORTAL-3107
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Vu Viet Phuong
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> I am not sure if this is a bug or feature. Anyway, GateIn does not like WARs which do not have {{<display-name>}} in their {{web.xml}}. I guess the portal should be able to work around the non-availabbility of an explicit <display-name> through working with the default one?
> Steps to reproduce:
> * Take any quickstart from https://github.com/gatein/gatein-portal-quickstart, e.g. simplest-hello-world-portlet
> * remove {{<display-name>}} from {{web.xml}}
> * Compile & deploy
> * Expected: The portal should swallow the portlet app without any error.
> * Current: The portal throws this NPE
> {code}
> [0m[31m09:20:11,195 ERROR [org.exoplatform.web.application.javascript.JavascriptConfigDeployer] (ServerService Thread Pool -- 93) An error occurs while registering 'Javascript in gatein-resources.xml' from the context 'null': java.lang.IllegalArgumentException: The context name cannot be null
> at org.exoplatform.container.definition.PortalContainerConfig.getPortalContainerNames(PortalContainerConfig.java:502) [exo.kernel.container-2.4.3-GA-redhat-1.jar:2.4.3-GA-redhat-1]
> at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:474) [exo.kernel.container-2.4.3-GA-redhat-1.jar:2.4.3-GA-redhat-1]
> at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.add(JavascriptConfigDeployer.java:96) [exo.portal.component.web.resources-3.6.0.Beta02-redhat-1.jar:3.6.0.Beta02-redhat-1]
> at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.onEvent(JavascriptConfigDeployer.java:71) [exo.portal.component.web.resources-3.6.0.Beta02-redhat-1.jar:3.6.0.Beta02-redhat-1]
> at org.gatein.wci.ServletContainer.safeFireEvent(ServletContainer.java:319) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer.fireEvent(ServletContainer.java:338) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer.access$400(ServletContainer.java:56) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer$RegistrationImpl.registerWebApp(ServletContainer.java:462) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.jboss.JB7ServletContainerContext.start(JB7ServletContainerContext.java:369) [wci-jboss7-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.jboss.JB7ServletContainerContext.lifecycleEvent(JB7ServletContainerContext.java:223) [wci-jboss7-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3772) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_19]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_19]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_19]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_19]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (GTNPORTAL-3107) NullPointerException during Portlet Deployment when there is no <display-name> in web.xml
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3107?page=com.atlassian.jira.pl... ]
Work on GTNPORTAL-3107 started by Vu Viet Phuong.
> NullPointerException during Portlet Deployment when there is no <display-name> in web.xml
> -----------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3107
> URL: https://issues.jboss.org/browse/GTNPORTAL-3107
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Vu Viet Phuong
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> I am not sure if this is a bug or feature. Anyway, GateIn does not like WARs which do not have {{<display-name>}} in their {{web.xml}}. I guess the portal should be able to work around the non-availabbility of an explicit <display-name> through working with the default one?
> Steps to reproduce:
> * Take any quickstart from https://github.com/gatein/gatein-portal-quickstart, e.g. simplest-hello-world-portlet
> * remove {{<display-name>}} from {{web.xml}}
> * Compile & deploy
> * Expected: The portal should swallow the portlet app without any error.
> * Current: The portal throws this NPE
> {code}
> [0m[31m09:20:11,195 ERROR [org.exoplatform.web.application.javascript.JavascriptConfigDeployer] (ServerService Thread Pool -- 93) An error occurs while registering 'Javascript in gatein-resources.xml' from the context 'null': java.lang.IllegalArgumentException: The context name cannot be null
> at org.exoplatform.container.definition.PortalContainerConfig.getPortalContainerNames(PortalContainerConfig.java:502) [exo.kernel.container-2.4.3-GA-redhat-1.jar:2.4.3-GA-redhat-1]
> at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:474) [exo.kernel.container-2.4.3-GA-redhat-1.jar:2.4.3-GA-redhat-1]
> at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.add(JavascriptConfigDeployer.java:96) [exo.portal.component.web.resources-3.6.0.Beta02-redhat-1.jar:3.6.0.Beta02-redhat-1]
> at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.onEvent(JavascriptConfigDeployer.java:71) [exo.portal.component.web.resources-3.6.0.Beta02-redhat-1.jar:3.6.0.Beta02-redhat-1]
> at org.gatein.wci.ServletContainer.safeFireEvent(ServletContainer.java:319) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer.fireEvent(ServletContainer.java:338) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer.access$400(ServletContainer.java:56) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer$RegistrationImpl.registerWebApp(ServletContainer.java:462) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.jboss.JB7ServletContainerContext.start(JB7ServletContainerContext.java:369) [wci-jboss7-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.jboss.JB7ServletContainerContext.lifecycleEvent(JB7ServletContainerContext.java:223) [wci-jboss7-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3772) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_19]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_19]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_19]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_19]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months