Bug 1075588 - CDI portlet throws an exception during deployment
Summary: CDI portlet throws an exception during deployment
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: DR02
: 6.2.0
Assignee: Nobody
QA Contact: Tomas Kyjovsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-12 12:29 UTC by Petr Mensik
Modified: 2025-02-10 03:35 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:35:20 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
CDI portlet (14.64 KB, application/zip)
2014-03-12 12:29 UTC, Petr Mensik 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GTNPORTAL-3426 0 Major Resolved CDI portlet throws an exception during deployment 2015-06-16 06:55:52 UTC

Internal Links: 1082651

Description Petr Mensik 2014-03-12 12:29:40 UTC 
Created attachment 873512 [details]
CDI portlet

Any CDI portlet will currently this exception during deployment

ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."cdi-jsf-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-jsf-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service

You can find full stack trace here - http://pastebin.com/b8WYRrhy

I am also enclosing one CDI portlet for easy reproduction.
Comment 3 Peter Palaga 2014-03-21 15:07:30 UTC 
https://github.com/gatein/gatein-portal/pull/805 was merged in upstream.
Comment 5 Petr Mensik 2014-05-13 12:56:02 UTC 
I confirm that this issue has been fixed in ER02.
Comment 9 Red Hat Bugzilla 2025-02-10 03:35:20 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.