Bug 805227 - Resource path handling change over Portlet Bridge
Summary: Resource path handling change over Portlet Bridge
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: PortletBridge
Version: 5.2.1.ER02
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: 5.2.1.GA
Assignee: Ken Finnigan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-20 17:04 UTC by Miroslav Cupák
Modified: 2015-01-05 11:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-06 13:02:27 UTC
Type: Bug


Attachments (Terms of Use)
Error from the server log after accessing the RichFaces Demo. (108.66 KB, text/x-log)
2012-03-20 17:06 UTC, Miroslav Cupák
no flags Details

Description Miroslav Cupák 2012-03-20 17:04:27 UTC
Description of problem:
Path to a resource within an application run over Portlet Bridge is now handled in a different way with respect to the location it is pointing to, thus breaking backward compatibility.

Version-Release number of selected component (if applicable):
Portlet Bridge 2.3.0.GA.EPP521

Steps to Reproduce:
Deploy the RichFaces demo, import it and add it on a page. After accessing it, you will see org.ajax4jsf.resource.ResourceNotFoundException in the log.

Comment 1 Miroslav Cupák 2012-03-20 17:06:24 UTC
Created attachment 571479 [details]
Error from the server log after accessing the RichFaces Demo.

Comment 2 Ken Finnigan 2012-03-20 17:17:49 UTC
Which RichFaces Demo did you use?

I didn't see this error when testing it prior to release

Comment 3 Miroslav Cupák 2012-03-20 17:32:24 UTC
The usual showcase from the PBR tag, also bundled with EPP in portletbridge/examples.

Comment 4 Miroslav Cupák 2012-03-22 10:19:12 UTC
FYI, both PBR 2.3.0.Final and 2.2.0.GA.EPP520 are OK on EPP 5.2.1.ER02 with respect to this issue.

Comment 5 Ken Finnigan 2012-03-22 15:44:13 UTC
Tagged 2.3.0.CP01.EPP521 which contains fix.  Honza is currently building it.


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