All geek questions in one place

How to use portlets better than just using the server side?

The idea behind portlets is that a website / page can consist of several applications that are developed individually. Then they are fastened on the page by a portal similar to a jigsaw puzzle. This allows you to create functionality independently of each other and fasten them at a later date. This has many obvious advantages.

But. I don’t see how the portlet specification has been improved on older ideas, such as the server one, from the point of view of a developer who needs to do something and not publish a document or make a keynote presentation.

The tone may be a little negative, but my first foray into the portlet world left me completely disappointed.

+3
source share
2 answers

From the point of view of working only “including” some dynamic / static content on a web page, you are right.

However, there are a number of amenities, such as support for personalizing the portlet (at the portlet / "enabled" level) and storing this information, a tougher workflow for configuring what is displayed on the portlet, etc.

Plus, obviously, there is all the portlet layout code that you have to write differently. Some portlet servers do a lot on the client side to build (drag and drop portlets, etc.).

You can find some of the discussions at the URL below: http://www.ibm.com/developerworks/ibm/library/i-portletintro/

+4

, , . (JSR-168, 286) , , . , , , J2EE JSP.

.

J2EE - , .

, , ( ):

  • , .
  • URL
  • , . , .
  • / (JSR-286)
  • ...

, UI - -.

+1

Source: https://habr.com/ru/post/1710259/

More articles:


All Articles