Thanks.  But why don't we use this one as the exercise we do together next week so I can learn how the process works?
     -Mike-

Scott O'Bryan (JIRA) wrote:
     [ https://issues.apache.org/jira/browse/PORTLETBRIDGE-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott O'Bryan reassigned PORTLETBRIDGE-19:
------------------------------------------

    Assignee: Michael Freedman  (was: Scott O'Bryan)

Hey Mike, I can help you commit this if you need any help...

  
PortletExternalContextImpl.encodeResourceURL seems to return prepend the context path twice
-------------------------------------------------------------------------------------------

                Key: PORTLETBRIDGE-19
                URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-19
            Project: MyFaces Portlet Bridge
         Issue Type: Bug
         Components: Impl
   Affects Versions: 1.0.0-SNAPSHOT
        Environment: exo-enterprise-webos-r21645 (includes Tomcat 6.0.10), JSF RI 1.2_05 and Windows XP 
           Reporter: Kito D. Mann
           Assignee: Michael Freedman
            Fix For: 1.0.0-SNAPSHOT

        Attachments: guessnumberportlet-301.war, jira_19.patch, jira_19b.patch


I've been experimenting with several portlet bridges with the standard guessnumber app. The following JSF tag declaration:
<h:graphicImage id="waveImg" url="" />
Generates this URL with the portlet bridge:
<img id="I26380823I:j_id_jsp_1712459602_0:helloForm:waveImg" src="" />
In this application, the web app _and_ the portlet have the same name "guessnumberportled-301". I've tested eXo with he MyFaces and Apache Portals bridges, and neither of them have this problem, so I think this may be a problem with this particular bridge. 
Everything works fine with if you remove the first slash:
<h:graphicImage id="waveImg" url="" />
This generates the expected outcome:
<img id="I26380823I:j_id_jsp_1712459602_0:helloForm:waveImg" src="" />
I haven't had a chance to actually step through the bridge's code or try this in Pluto.
    

  

Reply via email to