[jira] Created: (PORTLETBRIDGE-143) WriteBehindResponse mechanism(s) not working properly

Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman Multiple problems: in portlet 2.0 the wrapper used by the bridge conflicts with the servlet filter mechanism. In addition the examples that demonstrate how to write

[jira] Created: (PORTLETBRIDGE-142) Facelets 1.1.4 doesn't work with Bridge 1.0 PortletNamingContainerUIViewRoot

: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman Problem is when using Facelets with Portlet 1.0 Bridge the UIViewRoot id never gets set (usually done by the jsp

[jira] Resolved: (PORTLETBRIDGE-142) Facelets 1.1.4 doesn't work with Bridge 1.0 PortletNamingContainerUIViewRoot

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-142. Fix Version/s: 1.0.0 Resolution: Fixed Fix was as mentioned

[jira] Resolved: (PORTLETBRIDGE-141) External context implementation returns content-type header

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-141. Fix Version/s: 1.0.0 Resolution: Fixed Problem was header

[jira] Resolved: (PORTLETBRIDGE-112) Improve compatibility with Liferay Portal for portlets that extend GenericFacesPortlet

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-112. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-131) If redirect occurs within JSF rendering -- don't write/flush output

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-131. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-130) ExternalContext.getResponseCharacterEncoding and getResponseContentType fail

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-130. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-134) Portlet 2.0 Bridge doesn't render correctly if event follows a render (without any previous actions)

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-134. Resolution: Fixed Fix Version/s: 2.0.0 Portlet 2.0 Bridge

[jira] Resolved: (PORTLETBRIDGE-129) FacesContext.release() throws ConcurrentModificationException

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-129. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-133) VIEWSTATE param getting encoded in the portlet:currentView URL when it shouldn't

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-133. Resolution: Fixed Fix Version/s: 2.0.0 Fix is to have

[jira] Resolved: (PORTLETBRIDGE-132) Websphere claims there are no private parameters in an action but we expect them

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-132. Resolution: Fixed Fix Version/s: 2.0.0 Websphere 6.1

[jira] Updated: (PORTLETBRIDGE-136) TCK missing pom.xml in submodule

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman updated PORTLETBRIDGE-136: --- Resolution: Fixed Fix Version/s: 1.0.0 Status

[jira] Updated: (PORTLETBRIDGE-137) TCK: Missing Lifecycle test web app

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman updated PORTLETBRIDGE-137: --- Resolution: Fixed Fix Version/s: 1.0.0 Status

[jira] Created: (PORTLETBRIDGE-138) Bridge doesn't work correctly with ViewHandlers using deprecated StateManager APIs

Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman The Bridge provides its own StateManager that overrides writeState in order to detect

[jira] Created: (PORTLETBRIDGE-139) Bridge doesn't properly detect/adjust xml escaping in query strings

Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman There are places in the code that incorrectly reference \amp;\ rather than amp; -- This message is automatically

[jira] Resolved: (PORTLETBRIDGE-138) Bridge doesn't work correctly with ViewHandlers using deprecated StateManager APIs

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-138. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-139) Bridge doesn't properly detect/adjust xml escaping in query strings

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-139. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Created: (PORTLETBRIDGE-128) BridgeUtil needs to account for not running in a Faces context

Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman The static utility methods in BridgeUtil (like isPortletRequest()) rely on getting at the request attributes via

[jira] Deleted: (PORTLETBRIDGE-128) BridgeUtil needs to account for not running in a Faces context

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman deleted PORTLETBRIDGE-128: --- BridgeUtil needs to account for not running in a Faces context

[jira] Created: (PORTLETBRIDGE-129) FacesContext.release() throws ConcurrentModificationException

Issue Type: Bug Reporter: Michael Freedman Assignee: Michael Freedman Code was recently changed to release all request attributes added during Faces processing when the FacesContext is released. The code used causes a ConcurrentModificationException when run in certain

[jira] Created: (PORTLETBRIDGE-130) ExternalContext.getResponseCharacterEncoding and getResponseContentType fail

: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha Reporter: Michael Freedman Assignee: Michael Freedman Both of the above methods have the same incorrect check: if (getPortletPhase() != null mPortletRequest

[jira] Created: (PORTLETBRIDGE-131) If redirect occurs within JSF rendering -- don't write/flush output

Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman Current code checks to see if a redirect occurred from within the JSP during rendering and does the right thing

[jira] Created: (PORTLETBRIDGE-132) Websphere claims there are no private parameters in an action but we expect them

Project: MyFaces Portlet Bridge Issue Type: Bug Affects Versions: 2.0.0-alpha Reporter: Michael Freedman Assignee: Michael Freedman The bridge restricts the view of parameters via the ExternalContext to the privateParameters. On websphere this is coming back

[jira] Created: (PORTLETBRIDGE-133) VIEWSTATE param getting encoded in the portlet:currentView URL when it shouldn't

Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha Reporter: Michael Freedman Assignee: Michael Freedman Portlet 1.0 bridge correctly handles this by carrying forward all params in the original request

[jira] Created: (PORTLETBRIDGE-134) Portlet 2.0 Bridge doesn't render correctly if event follows a render (without any previous actions)

/browse/PORTLETBRIDGE-134 Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha Reporter: Michael Freedman Assignee: Michael Freedman Currently, the bridge doesn't establish a scope until the first

[jira] Created: (PORTLETBRIDGE-122) BridgeUtil.isPortletRequest throws nullPointerException is no tin FacesContext

: MyFaces Portlet Bridge Issue Type: Bug Components: API Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman This method wil throw a NullPointerException if there is no current FacesContext. As the bridge

[jira] Created: (PORTLETBRIDGE-123) Bridge's PortletNamingContainerUIViewRoot throws NullPointException if its id is never set

-123 Project: MyFaces Portlet Bridge Issue Type: Bug Components: API Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman In some component kits (Facelets at least) the id of the UIViewRoot isn't

[jira] Resolved: (PORTLETBRIDGE-122) BridgeUtil.isPortletRequest throws nullPointerException is no tin FacesContext

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-122. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-123) Bridge's PortletNamingContainerUIViewRoot throws NullPointException if its id is never set

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-123. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Created: (PORTLETBRIDGE-121) Exception thrown if PRP bean associated with PRP mapping doesn't exist

Bridge Issue Type: Bug Affects Versions: 2.0.0-alpha Reporter: Michael Freedman Assignee: Michael Freedman If you have a PRP mapping with an EL statement to a backing bean and this backing bean doesn't exist a exception is thrown. One reason this occurs

[jira] Resolved: (PORTLETBRIDGE-121) Exception thrown if PRP bean associated with PRP mapping doesn't exist

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-121. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Created: (PORTLETBRIDGE-113) Remove AFTER_VIEW_CONTENT request attribute after renderering from it

Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman This will avoid it being reused in local portals where portlets in the same web app run in the same underlying

[jira] Created: (PORTLETBRIDGE-114) FacesContext.release should release the request attributes added during bridge/faces lifecycle

/PORTLETBRIDGE-114 Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman to avoid them getting in the way of other portlets running

[jira] Created: (PORTLETBRIDGE-115) Reacquire preexistingRequestAttributes in renderRedirect after FacesContext.release

Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman As FacesContext.release now releases all request attributes that didn't exist prior

[jira] Created: (PORTLETBRIDGE-116) Bridge (BridgeImpl) Lifecycle listener should only process if this instance (thread) is the active in the lifecycle

: https://issues.apache.org/jira/browse/PORTLETBRIDGE-116 Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman A Faces Lifecycle

[jira] Created: (PORTLETBRIDGE-117) Portlet 2.0 Bridge ExternalContext.redirect during render must encode PublicRenderParameters into url prior to encoding as an action

: PORTLETBRIDGE-117 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-117 Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha Reporter: Michael Freedman Assignee: Michael Freedman

[jira] Created: (PORTLETBRIDGE-118) BridgeRenderRequestWrapper needs to individually manage public and private parameters

Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha Reporter: Michael Freedman Assignee: Michael Freedman BridgeRenderRequestWrapper is used (in part) to handle render redirect. The bridge wraps

[jira] Created: (PORTLETBRIDGE-119) Portlet 2.0 Bridge redisplay after redirect needs to update redirects PublicRenderParameter Map if redisplay sends new/different PRPs

: PORTLETBRIDGE-119 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-119 Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha Reporter: Michael Freedman Assignee: Michael Freedman

[jira] Created: (PORTLETBRIDGE-120) Portlet 2.0 Bridge -- not all AddPhaseListeners in bridge lifecycle are followed by a RemovePhaseListener

://issues.apache.org/jira/browse/PORTLETBRIDGE-120 Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha Reporter: Michael Freedman Assignee: Michael Freedman Clean up BridgeImpl so that all the Bridge's lifecycle

[jira] Resolved: (PORTLETBRIDGE-119) Portlet 2.0 Bridge redisplay after redirect needs to update redirects PublicRenderParameter Map if redisplay sends new/different PRPs

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-119. Resolution: Fixed Fix Version/s: 2.0.0 Does what the bug

[jira] Resolved: (PORTLETBRIDGE-120) Portlet 2.0 Bridge -- not all AddPhaseListeners in bridge lifecycle are followed by a RemovePhaseListener

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-120. Resolution: Fixed Fix Version/s: 2.0.0 Added the necessary

[jira] Resolved: (PORTLETBRIDGE-118) BridgeRenderRequestWrapper needs to individually manage public and private parameters

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-118. Resolution: Fixed Fix Version/s: 2.0.0 Now manages each Map

[jira] Resolved: (PORTLETBRIDGE-117) Portlet 2.0 Bridge ExternalContext.redirect during render must encode PublicRenderParameters into url prior to encoding as an action

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-117. Resolution: Fixed Fix Version/s: 2.0.0 Added encoding

[jira] Resolved: (PORTLETBRIDGE-116) Bridge (BridgeImpl) Lifecycle listener should only process if this instance (thread) is the active in the lifecycle

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-116. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-115) Reacquire preexistingRequestAttributes in renderRedirect after FacesContext.release

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-115. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-114) FacesContext.release should release the request attributes added during bridge/faces lifecycle

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-114. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-113) Remove AFTER_VIEW_CONTENT request attribute after renderering from it

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-113. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Created: (PORTLETBRIDGE-109) ExternalContext encodeAction/resource URL should only unXML encode URLs that aren't XML encoded

/PORTLETBRIDGE-109 Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman When the bridge relies on the underlying portlet container

[jira] Created: (PORTLETBRIDGE-110) Bridge relies on a URL/QueryString utility class that doesn't support XML encoding

Project: MyFaces Portlet Bridge Issue Type: Bug Reporter: Michael Freedman The bridge's QueryString utility class that is used to decode/encode QueryStrings to/from its parameters doesn't parse QueryStrings that use the XML encoded amp; seperator. It should

[jira] Created: (PORTLETBRIDGE-111) Bridge RequestParamValues and RequestHeaderValues Map don't support equals() correctly

Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman Both externalContext.getRequestParameterValues() and getRequestHeaderValues

[jira] Resolved: (PORTLETBRIDGE-111) Bridge RequestParamValues and RequestHeaderValues Map don't support equals() correctly

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-111. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-110) Bridge relies on a URL/QueryString utility class that doesn't support XML encoding

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-110. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-109) ExternalContext encodeAction/resource URL should only unXML encode URLs that aren't XML encoded

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-109. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Created: (PORTLETBRIDGE-106) Add support for new spec feature that enables use of portlet: url syntax to target the current view

/browse/PORTLETBRIDGE-106 Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman The spec was recently updated to allow the portlet

[jira] Created: (PORTLETBRIDGE-107) Portlet ELresolver throws nullProperty exception if getValue is called with a base != null

-107 Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman It should just return null rather than throw the above exception. Check

[jira] Created: (PORTLETBRIDGE-108) Bridge FacesContext should set currentInstance FacesContext on the ELContext

: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman Currently the bridge sets its FacesContext instance on the ELContext (so it can be grabbed later

[jira] Resolved: (PORTLETBRIDGE-106) Add support for new spec feature that enables use of portlet: url syntax to target the current view

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-106. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-108) Bridge FacesContext should set currentInstance FacesContext on the ELContext

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-108. Resolution: Fixed Changed to set the CurrentInstance not use

[jira] Resolved: (PORTLETBRIDGE-107) Portlet ELresolver throws nullProperty exception if getValue is called with a base != null

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-107. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Created: (PORTLETBRIDGE-104) GFP reads defaultCharacterEncoding/defaultCharSetEncoding from wrong location

: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman It reads it from the PortletContext initParameter but it should read it from the PortletConfig

[jira] Created: (PORTLETBRIDGE-105) ExternalContext.encodeResourceURL mishandles encoding portlet:render URL

Portlet Bridge Issue Type: Bug Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman Code sees this as an absolute opaque URl vs recognizing this as a special bridge URL that means link to this portlet -- i.e. it should

[jira] Resolved: (PORTLETBRIDGE-105) ExternalContext.encodeResourceURL mishandles encoding portlet:render URL

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-105. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-104) GFP reads defaultCharacterEncoding/defaultCharSetEncoding from wrong location

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-104. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-103) Bridge.destroy fails to release ELContextListener

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-103. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Created: (PORTLETBRIDGE-103) Bridge.destroy fails to release ELContextListener

Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman and by not releasing this ContextListener the next request (to any bridged portlet) throws a NullPointerException because the bridge instance that has

[jira] Resolved: (PORTLETBRIDGE-100) Locale setting not working in JSF CarDemo

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-100. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Resolved: (PORTLETBRIDGE-101) GenericFacesPortlet uses the wrong name for the bridge class initialization parameter according to the spec

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-101. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Created: (PORTLETBRIDGE-102) Null/Empty viewId in InitParameter causes NullPointer Exception in bridge

Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman The Bridge doesn't check if a default viewId passed by the portlet is not null or empty -- yielding

[jira] Resolved: (PORTLETBRIDGE-102) Null/Empty viewId in InitParameter causes NullPointer Exception in bridge

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-102. Resolution: Fixed Fix Version/s: 2.0.0

[jira] Created: (PORTLETBRIDGE-100) Locale setting not working in JSF CarDemo

: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman The first page of the JSF sample CarDemo has you set the locale for the demo. You choose a language/region and the rest of the views use strings earmarked

[jira] Commented: (PORTLETBRIDGE-99) RequestScopeListener not Serializable

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772062#action_12772062 ] Michael Freedman commented on PORTLETBRIDGE-99: --- Can you clarify your

[jira] Commented: (PORTLETBRIDGE-99) RequestScopeListener not Serializable

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772078#action_12772078 ] Michael Freedman commented on PORTLETBRIDGE-99: --- Note: If the problem

[jira] Commented: (PORTLETBRIDGE-99) RequestScopeListener not Serializable

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772082#action_12772082 ] Michael Freedman commented on PORTLETBRIDGE-99: --- Sounds like

[jira] Resolved: (PORTLETBRIDGE-97) Portlet Bridge is incompatible with Weblogic Portal 10.3?

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-97. --- Resolution: Fixed See prior comment -- this is a WLP bug -- for which

[jira] Commented: (PORTLETBRIDGE-98) Wrapper for ExternalContext that only implements jsf 1.1methods does not work in portlet case

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12769551#action_12769551 ] Michael Freedman commented on PORTLETBRIDGE-98: --- I don't understand why

Re: [TRINIDAD] Portlet 2.0 compatibility

The TrinidadDemo that is included in TrinidadExample distribution download on the MyFaces/Trinidad site runs against the current version of the Portlet 2.0 bridge. There are some problems -- mostly related to lack of Trinidad pop-up support in the portlet environment which the example relies

[jira] Created: (PORTLETBRIDGE-95) Trinidad GoLink/Faces CommandLink broken in bridge 2.0 if nav to another Faces view

Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 2.0.0 Reporter: Michael Freedman Assignee: Michael Freedman Trinidad GoLinks and Faces CommandLink's that reference another Faces view ultimately

[jira] Resolved: (PORTLETBRIDGE-95) Trinidad GoLink/Faces CommandLink broken in bridge 2.0 if nav to another Faces view

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-95. --- Resolution: Fixed Fix Version/s: 2.0.0 Fix in the manner

[jira] Created: (PORTLETBRIDGE-94) No render after action in some portlet containers

Components: Impl Affects Versions: 2.0.0-alpha, 2.0.0 Reporter: Michael Freedman In the latest Oracle WLP portlet container, the render following an action doesn't render. This occurs because the VIEW_STATE parameter isn't seen by the bridge and hence Faces thinks we aren't

[jira] Resolved: (PORTLETBRIDGE-94) No render after action in some portlet containers

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-94. --- Resolution: Fixed Fix Version/s: 2.0.0 Added

Re: [VOTE] Release of Portlet Bridge 2.0.0-alpha-2

+1 Scott O'Bryan wrote: Hi, I'm trying to release the MyFaces Portlet Bridge 2.0.0-alpha-2 and am now beginning the formal vote. The Jetty Pluto plugin is not yet updated for the latest Pluto release so the jetty:run target will not function in the demo projects. The demo should deploy

[jira] Resolved: (PORTLETBRIDGE-93) Exception thrown because viewId's state can't be found by Faces during restore

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-93. --- Resolution: Fixed Fix Version/s: 2.0.0 1.0.0

[jira] Resolved: (PORTLETBRIDGE-89) ExternalContext.encodeActionURL incorrectly encodes invalid portletMode

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-89. --- Resolution: Fixed Fix Version/s: 2.0.0 1.0.0

[jira] Resolved: (PORTLETBRIDGE-88) ExternalContext.encodeActionURL doesn't parse portlet: URLs correctly

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-88. --- Resolution: Fixed Fix Version/s: 2.0.0 1.0.0

[jira] Resolved: (PORTLETBRIDGE-92) Refresh of faces view using client-side state saving fails (in Mojarra) with class cast expection of PortletUIViewRootNamingContainer

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-92. --- Resolution: Fixed Fix Version/s: 2.0.0 1.0.0

[jira] Resolved: (PORTLETBRIDGE-91) HttpUtils need to be updated to the latest URI spec with respect to reserved characters

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-91. --- Resolution: Fixed Fix Version/s: 2.0.0 1.0.0

[jira] Resolved: (PORTLETBRIDGE-87) getActionURL doesn't encode extra params correctly if the actionURl returned from the delegation returns a queryString

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-87. --- Resolution: Fixed Fix Version/s: 2.0.0 1.0.0

[jira] Resolved: (PORTLETBRIDGE-86) Extra parameters on a viewId can cause view target miss on subsequent request and hence a restore view fail

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-86. --- Resolution: Fixed Fix Version/s: 2.0.0 1.0.0

[jira] Resolved: (PORTLETBRIDGE-85) GenericFacesPortlet.doDispatch() has bad mode equality check

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-85. --- Resolution: Fixed Fix Version/s: 2.0.0 1.0.0

[jira] Resolved: (PORTLETBRIDGE-84) Null values on Request map cause error

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman resolved PORTLETBRIDGE-84. --- Resolution: Fixed Fix Version/s: 2.0.0 Null values on Request

[jira] Created: (PORTLETBRIDGE-93) Exception thrown because viewId's state can't be found by Faces during restore

: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman When running in Pluto we get these intermittent Exceptions thrown during the render of a portlet

[jira] Created: (PORTLETBRIDGE-92) Refresh of faces view using client-side state saving fails (in Mojarra) with class cast expection of PortletUIViewRootNamingContainer

: PORTLETBRIDGE-92 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-92 Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael

[jira] Created: (PORTLETBRIDGE-91) HttpUtils need to be updated to the latest URI spec with respect to reserved characters

Project: MyFaces Portlet Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Current impl is based on the the original RFC -- but the latest RFC contains additional definitions of reserved

[jira] Created: (PORTLETBRIDGE-85) GenericFacesPortlet.doDispatch() has bad mode equality check

Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman GenericFacesPortlet.doDispatch() has bad mode equality check. It checks for equality by mode == PortletMode.EDIT when it should

[jira] Created: (PORTLETBRIDGE-86) Extra parameters on a viewId can cause view target miss on subsequent request and hence a restore view fail

://issues.apache.org/jira/browse/PORTLETBRIDGE-86 Project: MyFaces Portlet Bridge Issue Type: Bug Reporter: Michael Freedman The bridge allows viewIds to contain query strings (for the default view and for switching between modes/etc. in faces-config.xml navigation rules

[jira] Created: (PORTLETBRIDGE-87) getActionURL doesn't encode extra params correctly if the actionURl returned from the delegation returns a queryString

URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-87 Project: MyFaces Portlet Bridge Issue Type: Bug Reporter: Michael Freedman The bridge's getActionURL allows the incoming viewId to contain QS params. The semantics are supposed to be to append

[jira] Created: (PORTLETBRIDGE-88) ExternalContext.encodeActionURL doesn't parse portlet: URLs correctly

Bridge Issue Type: Bug Components: Impl Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman Code: if (isPortletURL(url)) { isPortletURL = true; nonFacesAction = true; //URL

[jira] Created: (PORTLETBRIDGE-89) ExternalContext.encodeActionURL incorrectly encodes invalid portletMode

Bridge Issue Type: Bug Affects Versions: 2.0.0-alpha, 1.0.0-beta Reporter: Michael Freedman Assignee: Michael Freedman During encodeActionURL the JSF target that the bridge encodes is prepended with the URLs mode so we can ensure that the subsequent request

[jira] Reopened: (PORTLETBRIDGE-84) Null values on Request map cause error

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Freedman reopened PORTLETBRIDGE-84: --- Submitted fix is only a partial fix. Though it correctly checks for o

Re: [VOTE] Release of Portlet Bridge 1.0.0 Beta 2

It would be nice if the demo distribution additionally carried a .war file for installing the demo on pluto. -Mike- Scott O'Bryan wrote: Hi, I'm trying to release the MyFaces Portlet Bridge 1.0.0 Beta 2 and am now beginning the formal vote. You can find the signed release candidate at

<    1   2   3   4   5   >