myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <>
Subject [jira] Created: (PORTLETBRIDGE-97) Portlet Bridge is incompatible with Weblogic Portal 10.3?
Date Wed, 21 Oct 2009 23:15:00 GMT
Portlet Bridge is incompatible with Weblogic Portal 10.3?

                 Key: PORTLETBRIDGE-97
             Project: MyFaces Portlet Bridge
          Issue Type: Question
    Affects Versions: 1.0.0-beta
         Environment: Weblogic 10gR3, myfaces core 1.2.7-SNAPSHOT(with some modifications
for do not load faces-adapter.jar or weblogic jsf native portlet)
            Reporter: Leonardo Uribe


I tried to run this bridge on weblogic portal 10.3 creating a test with Workshop for Weblogic
10gR3. For my surprise this bridge does not work, because weblogic removes the namespace from
the request attributes sent when a h:commandButton or h:commandLink is clicked.

For example, if you have something like this:

    <h:inputText id="name" ..... />
    <h:commandButton ....../>

and the id of PortletNamingContainerUIViewRoot is portlet_1 something like this is rendered

<input id="portlet_1_name">

Then, when the form is submitted the key of the value put on request parameter map is:


but it should be


like apache pluto or liferay 5.2.3 does.

At this point there are two possibilities:

1. This is a weblogic bug related to its own JSR-168 implementation, and should be referred

2. This is not a bug, so portlet bridge should deal with this and do some hack to workaround

It could be good if someone knows how to submit this bug to weblogic, or give a opinion about
how to deal with this one.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message