-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Nguyen, Trieu Viet escribió:
> Hi all,
> I currently learn markup fragment rendered by portlet. I read WSRP v1 and
> JSR 168 specification.
> The WSRP specification said that markup fragment contains the URL of the
> portlet in Producer and other things (e.g. MarkupResponse) but it don't said
> any things about HTML format of fragment. My question is whether the fragment
> have HTML format or not. If yes what is it ? Where can I find this document ?
> How about markup fragment rendered by portlet written by JSR 168 ?
>
> Thanks,
> Trieu Viet Nguyen
>
>
> This email may contain material that is confidential, privileged and/or
> attorney work product for the sole use of the intended recipient. Any review,
> reliance or distribution by others or forwarding without express permission
> is strictly prohibited. If you are not the intended recipient, please contact
> the sender and delete all copies.
First of all, you shouldn't send the same message to dev & user lists.
This is a question for the user list.
About your question, I'm not sure what are you asking. In JSR-168, the
markup can be anything supported by the portlet and indicated on the
portlet descriptor (portlet.xml), for instance:
<portlet-app>
<portlet>
...
<supports>
<mime-type>text/html</mime-type>
<portlet-mode>view</portlet-mode>
<portlet-mode>edit</portlet-mode>
<portlet-mode>help</portlet-mode>
</supports>
<supports>
<mime-type>text/vnd.wap.wml</mime-type>
<portlet-mode>view</portlet-mode>
</supports>
...
</portlet>
</portlet-app>
Then you can generate the markup for each mime type the way you want
(for instance, using JSP or Velocity templates). The markup generated
depends on what you specify on your template, and later, that fragment
gets mixed with other fragments from other portlets rendered by your
portal (if you are using one). You can view an example on WSRP4J
Testportlet.
About WSRP, the markup generated depends on the method your WSRP
producer uses:
* As a consumer you don't care which way it's generated, you only get
the markup fragments on the mime-type you specify on the request (if
it's supported by the producer of course).
* As a producer, you implement the backend for your portlets. It can be
a custom solution based on your own mapping or something more standard.
WSRP4J Producer, for instance, uses Pluto as a backend, so the portlets
are JSR-168 portlets. Whenever a request for a portlet arrives to the
producer, the producer asks the Pluto backend to render the markup for
that portlet, which in turn is a JSR-168 portlet.
I hope this answers your question.
Regards.
Diego.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFcBvfgyzZYflJelERAiW3AJ4hpkmOUAQ/uJ9Uh7HxTuwBec1L2QCeOLGF
Hn7LYzgbxaueMICk2zPe/wA=
=NXMH
-----END PGP SIGNATURE-----
