Forums for ICEfaces and ICEpdf

I was curious if anyone has used the ice:portlet tag in liferay. The 1.7 docs are a bit vague about using it and doesn't include an example. I'm assuming that it would be the next element after f:view? I almost got the impression maybe it replaces the ice:form element? The portlets seem to look fine without using it so I haven't tried it. Just curious if there is some benefit I don't know about by trying it. I think the docs mentioned about automatically picking up the theme of the container if you use that tag as well, but I'm not sure what that means.. such as do I remove all style information from the components? Do I remove the outputStyle tag?

Thanks!

The <ice:portlet> component is new for 1.7 DR1 and, yes, the documentation is, shall we say, sketchy. ;-) That'll improve as we get closer to a final 1.7 release.

The <ice:portlet> component should be used to surround all of your portlet content and does NOT replace <ice:form>. The main benefit for the DR1 release was to help with some navigation issues so you may not see any difference using it in your existing portlets. We may leverage the component for other things as we proceed in building better support for portlets and it likely be required at some point along the way.

As for portlet themes, the <ice:portlet> component does not currently relate to work in that area. In order to better support a portlet picking up the proper styles of the theme supplied by the portal container, certain components will not automatically add the specified style names as outlined in the JSR 168 spec.

No worries.. I figured rather than fiddle with it, I'm probably better off just asking instead. I probably won't give it a try as of yet though. One more question in this regard, so on a portlet page, if I wanted to use it.. the structure would be similar to:

<f:view>
<ice:portlet>
<ice:form>
</ice:form>
</ice:portlet>
</f:view>

I didn't realize the portlet spec actually specified styles, I guess I would know that if i could read it without falling asleep. :)

Exactly. It should surround all the "visible" content. It outputs as a <div> in the markup and should have the portlet namespace set as the id attribute.

Hello,

I'm trying to solve a navigation problem I'm having with an icefaces portlet, I read this post and tried to use the <ice.portlet> tag.
Now, nothing appears anymore.
I'm using facelets, and the latest from the 1.7 trunk of today. I'm deploying om liferay 4.3.3
The navigation rules simply don't seem to work.
Any suggestions what I can try to make them work, or to make the <ice:portlet> tag work?

Regards, Bo

The latest 1.7 from the trunk may not be all that reliable at the moment so I'd recommend going back to a 1.7DR1 or DR2 and see if it still doesn't work.

As for navigation, can you include some of your application info or, better still, a simple war file that exhibits the problem?

Hello,

with some portlets the navigation does work, so it must somehow be component dependent. As far as I can see, the only new component here is the <ice:dataTable>.
Ajax calls get processed correctly, error messages are displayed after validation, but once I clic the button to go to the next page, no ajax calls work. The html components continue to work, but no calls seem to be made to the server.

Bo

hi all
if you use like this
Code:

 <f:view>
 <ice:portlet>
 <ice:form>
 </ice:form>
 </ice:portlet>
 </f:view>

you should remove all html component <html> ,<head>,<body> ,<br> e.t.c

Ok, that worked!

thanks, Bo

Now that I'm using the <ice:portlet> tag, back to the navigation problem...

I face 2 different behaviours with 2 different portlets, none of which I understand/desire:

1. one still doesn't allow navigation with the <ice:commandButton>; as long as fields are incomplete, error messages are shown, so ajax messaging is working. But as soon as it's allowed to pass to the next screen, the ajax functionality stops. When I introduce erroneous input, no error messages appear anymore. When I go to another page and come back, it shows the screen I wanted to go to.

2. One portlet does do the navigation, but it reloads the entire page. How is that possible??

Has anybody faces these issues?

Regards, Bo