Re: S2 send wrong Portlet Window States - May be a bug
Those interested in the progress of this issue can follow it here: https://issues.apache.org/struts/browse/WW-2062 On 7/26/07, tom tom [EMAIL PROTECTED] wrote: I already made a change request. Thanks, --- Nils-Helge Garli [EMAIL PROTECTED] wrote: 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=listsid=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] Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: S2 send wrong Portlet Window States - May be a bug
I already made a change request. Thanks, --- Nils-Helge Garli [EMAIL PROTECTED] wrote: 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=listsid=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] Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: S2 send wrong Portlet Window States - May be a bug
I was busy, I will work on this and give you a update or make a JIRA issue. BUT for the time being ignore all the issues and arguments about uPortal and think about the following scenario. In our entire application we got portlets (developed using S2) and other channels developed using CWebProxies etc. Both runs on the same uPortal 2.5.3. Other channels work as expected with regards to the minimize and maximize functionality. S2 portlets minimize maximize does not work as other channels. In addition to this previously we had portlets developed using struts-bridge running on same uPortal 2.5.3, worked fine with no issues with regards to minimize maximize functionaliy. At this I do not know how those work with same uPortal server. this is the argument which made me to think about the S2 framework instead of uPortal. Similar to the S2, Struts-Bridge also a independent framework which works on other portal servers. Any how I will work more on this. Hope you will work on this as well. Thanks, --- Nils-Helge Garli [EMAIL PROTECTED] wrote: 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=listsid=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
Re: S2 send wrong Portlet Window States - May be a bug
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=listsid=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]
Re: S2 send wrong Portlet Window States - May be a bug
We are using uPortal 2.5.3. We still can't figure why it returns wrong window states. Waiting for a reply, 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=listsid=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] Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: S2 send wrong Portlet Window States - May be a bug
I have tested uPortal 2.5 and 2.6RC and from what I can see, clicking maximize on the portlet window is for some reason treated as restore (normal) in uPortal for all portlets (not only S2 portlets). It might be that the focus icon/mode is supposed to be the maximized state? You could try to programatically set the window state to maximized and see if the behaviour is as expected, but from what I can see this is probably a uPortal (naming?) issue. But if you can create an example that illustrates that this is a S2 problem, and attach it to a jira issue, I'll look into it more detailed. I also read in the reply to your post in the uPortal users mailing list that there might be some issues with the window state handling in uPortal: https://lists.wisc.edu/read/messages?id=1976749 Nils-H On 7/22/07, tom tom [EMAIL PROTECTED] wrote: We are using uPortal 2.5.3. We still can't figure why it returns wrong window states. Waiting for a reply, 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=listsid=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] Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/ - 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]
Re: S2 send wrong Portlet Window States - May be a bug
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=listsid=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]
Re: S2 send wrong Portlet Window States - May be a bug
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=listsid=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]
S2 send wrong Portlet Window States - May be a bug
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=listsid=396545433 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: S2 send wrong Portlet Window States - May be a bug
Hi, Could you make a minimal example that illustrates the problem in uPortal, and then put it somewhere to download? Nils-H 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=listsid=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]
