Win a copy of Murach's MySQL this week in the JDBC and Relational Databases forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

Solo state in Portal server

Ranch Hand
Posts: 463
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Does any one know how I can be assured of moving into a solo state.
I read up on info on IBM sites and the only information is that if I set portletWindowState="solo" and click that link, I would push portlet into solo state. That does not seem to be happening.

<h3>Your <a <br />" rel="nofollow">
<% wpsURL.write(out); %>
</wps:urlGeneration>">Statement of Account

then my portlet checks if portlet is in solo state.
But this value always returns back a false.

* @param request
* @return
* $A1
public boolean checkSoloMode(RenderRequest request) {
boolean isSoloMode= false;
System.out.println(" THE WINDOW STATE IN PORTLET="+request.getWindowState());
if (request.getWindowState().equals("solo")) {
return isSoloMode;

Is this an incorrect way of checking solo State in Portlet.

With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic