For example, a producer may use a filter and reduce the number of offered portlets for a particular consumer. Portlet Management Interface optional : This interface gives the consumer control over the life cycle methods of the remote portlet. Processing user interaction When the user clicks on a link or submits form data, the consumer application controls the processing and invokes the performInteraction method. When the producer receives this call, it processes the action and returns the updated state.
To redraw the complete page, the consumer then invokes the getMarkup call to receive the latest markup fragment. Because the state of the produce r has changed since the previous getMarkup call, the markup fragment returned is typically different from the one previously returned. The end user can then perform another action, which starts a new interaction cycle.
See Figure 1. The WSRP protocol supports multiple configurations of a single service. Good example is a lookup in a remote list of the course offerings and subjects offered within a particular course to international students. The list can be configured to display different offerings per semester, different currencies for subject fees or both depending on the consumer country and language prerequisites.
Offer does not apply to e-Collections and exclusions of select titles may apply. Offer expires December 31, Browse Titles. Add to Cart. I think this is mostly due to the fact that prior to JSR becoming mainstream, the standards were loose and vendors built to their own specifications. So becoming compliant with JSR was and still is a big deal. In addition, while the JSR spec has been out since , it took the Portal vendors some time to update their Portal Servers to support the new standard.
Now all the major vendors support JSR on their Portal server. Even many content management systems are supporting JSR portlets on their systems. However, I'm still wondering if there's any meaning to the phrase "JSR compliant portlet" aside from the backwards incompatabilities mentioned below.
Add a comment. Active Oldest Votes. The only exceptions to this rule are: renderResponse. Improve this answer. Yes I've seen that section of the spec, and it answers a slightly different question. That answers the question "Does the portlet run in a compliant portal" However I see people talking about " compliant portlets" which seems to say that while portlets may run, they are treated differently by liferay: vaadin. Your answer contains part of my answer, so I upvoted you for now.
I'm still trying to decide if it counts as a full answer. I think part of the problem is that I had been mislead by the phraseology in other posts, and I was thinking that there was some larger difference, so there probably is not much of an answer to my question in the first place.
If nobody can add to my list below I might give you credit even though it was not new information to me, but rather something I had already found but omitted from my question.
At the time I posted this question I thought liferay might not be providing services if it decided I wasn't " compliant". I don't think that's an issue anymore however, I think I was just reading too much into the way that post was phrased. Must Do: Conform to the 2. Seems unlikely anyway Rely on getProtocol returning null The upshot is, if you simply convert your portlet. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.
Email Required, but never shown. The Overflow Blog.
0コメント