Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 983112 - a4j:log is not visible in Metamer
Summary: a4j:log is not visible in Metamer
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: PortletBridge
Version: 6.1.0
Hardware: x86_64
OS: Linux
Target Milestone: ER04
: 6.1.0
Assignee: Ken Finnigan
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2013-07-10 14:14 UTC by Petr Mensik
Modified: 2015-07-20 01:00 UTC (History)
4 users (show)

Doc Type: Bug Fix
Doc Text:
Clone Of:
Fedora 18, Firefox 22
Last Closed: 2013-07-22 08:49:20 UTC
Type: Bug

Attachments (Terms of Use)

Description Petr Mensik 2013-07-10 14:14:13 UTC
As stated above, a4j:log is just not visible on the Metamer page with this component. So you can't see logs or set the log level. The non-portal version is working fine. 

Steps to reproduce

1. Deploy Metamer portlet
2. Go to a4j:log, continue to Simple page

Comment 2 Ken Finnigan 2013-07-12 15:49:51 UTC
The a4j:log component works fine on JPP 6.1 ER2 within the Richfaces Showcase.

This leads me to believe there is something specific about how the metamer portlet is using a4j:log, or the surrounding facelet code, that is causing a problem here.

Is there any way to narrow down what the issue might be?

Comment 3 Petr Mensik 2013-07-22 08:49:20 UTC
I finally got it, A4JLogBean is using ConversationScoped so I just needed to enable CDI in Metamer portlet.

Note You need to log in before you can comment on or make changes to this bug.