Re: [wsrp-comment] Public Comment

[Richard Jacob <richard.jacob@de.ibm.com>]

comment-form@oasis-open.org wrote on 11/29/2004 10:26:53 PM:

> Comment from: jmoliere@ucsd.edu
>
> Hello,
> I have a little problem understanding how a WSRP Consumer will
> rewrite the content before the content is rendered on the client's
browser.
>
> Will the content (i.e. HTML content) be rewritten so when a user
> clicks a link, the URL will point back to the portal for the next
> generation of HTML page?

Yes.
There are two mechanisms to accomplish that.
1. Templating
Here the Consumer generates URL templates pointing to itself. These
templates contain placeholders, where the producer/portlets can insert the
necessary stuff.
2. URL rewriting
Here the producer/portlet generate special WSRP rewrite URLs indicated by a
starting and ending token.
The consumer needs to parse the returned markup, find the WSRP rewrite
URLs, and replace them (using the data in the rewrite URLs) with its own
appropriate URLs.

>
> I'm looking at WSRP4J and am not seeing an implementation of the URL
> rewrite similar to how I describe above.  If my understanding is not
> correct, how do we get HTML content to link back to the portal
> instead of back to the producers that (possibly) generatated the HTML?

Your understanding is correct.
Look at the URLRewriterImpl and the URLGeneratorImpl (for example found in
the proxy portlet package).
The rewriter is responsible for rewriting the markup and uses the generator
of the environment to generate the correct Consumer URLs.

cheers
Richard