[
https://issues.apache.org/jira/browse/PB-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma resolved PB-65.
-------------------------
Resolution: Fixed
Interface provided.
I'm not going to close this issue yet so its easier to add comments like from
other portal developers announcing they have implemented it ;)
Implementation for Jetspeed-2 is already underway (see: JS2-728) and will be
provided out-of-the-box (version 2.1.1)
> PortletResourceURLFactory: A new generic interface for direct access to a
> portlet, a lightweight version of what Portlet 2.0 ResourceURL will provide
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PB-65
> URL: https://issues.apache.org/jira/browse/PB-65
> Project: Portals Bridges
> Issue Type: New Feature
> Components: common
> Affects Versions: 1.0.2
> Environment: Portlet 1.0 supporting portals
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 1.0.2
>
>
> Getting web frameworks like Wicket running fully functional in a Portlet 1.0
> container is very difficult to realize without some way for direct access to
> the portlet.
> Features like Ajax (which might need generate new Portlet URLs) or even
> dynamic resource generation (like a JCapta image) really need to be served
> through the portlet itself.
> The soon available Portlet API 2.0 will change all this and make life much
> easier for web framework developers.
> One feature the Portlet API 2.0 is likely to add is a new ResourceURL, which
> will support invoking a portlet directly ...
> But, as Portlet API 2.0 isn't available yet, and I need direct portlet access
> *now*, the only option available is using portal specific extensions.
> For Jetspeed-2, I know how to do this, and AFAIK other (open-source) portals
> provide similar extensions.
> As I don't want to bind for instance Wicket portlet support hard coded to the
> Jetspeed-2 portal, I'm going to define a new interface,
> PortletResourceURLFactory, which portals can implement to allow direct
> portlet access in a more generic way, just as what we did with the
> ServletContextProvider interface.
> Note: this interface will be defined obsolete as soon as Portlet API 2.0 is
> available and this functionality then is provided natively.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
