Yes, it uses pluto for it's JSR168 support, but there's still a lot of integration- and extension points that can behave differently, so that is unfortunately not conclusive.
There's absolutely no layer between the JSR168 dispatcher and the portlet API/container, so the portlet request that the dispatcher sees, is the current request, un-touched by the dispatcher, that is processed by the container. Since all my findings so far point in one direction, there's not much more I can do unless you can give some concrete information that illustrates the issue. I don't think we'll get much further here, so what you should do is: - Create a JIRA issue, with a detailed description of the problem (is the window state set programatically, or which icons do you click etc, and some screenshots of the portlet in different states) - Create a simple example application which illustrates the problem, preferrably also an identical "struts-bridge" example that shows how it should work, and attach these to the JIRA issue. Then we'll continue the discussion and research in JIRA. And please, do try it in a different portal server, just to make sure. I have tested the S2 portlet sample application in both pluto and uPortal, and the behaviour is indeed different. Something else you can try is to create a plain JSR168 portlet (not using S2/struts-bridge or anything else) and see if the window state is reported differently. I'll also bring the issue up on the uPortal mailing lists and see if we can get any further there. Nils-H On 7/23/07, tom tom <[EMAIL PROTECTED]> wrote:
In my opinion, I hardly believe this is something to do with uPortal, reason is we got other portlet develelopment strategies like (struts-bridge) working fine with uPortal. I think even the product is called uPortal it got pluto container underneath. Any how you may have other ideas as well as we may be wrong. Thanks, --- Nils-Helge Garli <[EMAIL PROTECTED]> wrote: > Which version of uPortal are you using? > > On 7/19/07, tom tom <[EMAIL PROTECTED]> wrote: > > Hi, > > > > We got some portlets developed using S2 running of > > uPortal. > > > > It looks like When we switch between Window states > and > > try to print window states in JSR168Dispatcher it > > prints window states incorrectly. > > > > For e.g When I minimize a portlet it says the > window > > states is minimized but when I maximize the same > > portlet it says the window state as normal (which > > should be maximized). > > > > Can some one let us know what is going on here. > > > > For sure there is no issue with the portal server > as > > we got portlets developed using struts-bridge > prints > > the window states correctly on uPortal. > > > > Please let us know how to get the correct window > > state. > > > > Thanks, > > > > > > > > > ____________________________________________________________________________________ > > Be a better Heartthrob. Get better relationship > answers from someone who knows. Yahoo! Answers - > Check it out. > > > http://answers.yahoo.com/dir/?link=list&sid=396545433 > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > ____________________________________________________________________________________ Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
