ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

What version of ICEfaces are you working with?

Not entirely sure what you're asking for but do you need to prevent interaction with the page once a submission is made? Perhaps this is what you are looking for:

http://wiki.icefaces.org/display/ICE/blockUIOnSubmit

Additionally, the ACE Showcase example also comes in a portlet version:

Code:

icefaces.dir/samples/showcase/showcase-portlets

That you can build and deploy to Liferary 6.1 to see how the components work as portlets.

http://wiki.icefaces.org/display/ICE/Getting+Started
http://wiki.icefaces.org/display/ICE/Portlet+Development

Couple of things:

Can you be more specific about the exact version of ICEfaces you are using? It looks like it might be 2.0.0. The latest release on that track is 2.0.2 so perhaps upgrading might solve some problems.

You mention that you are using Liferay but the stack traces don't show any indication that the portal container (Liferay) or the PortletFaces Bridge are handling any of the requests. Are you running your application as a portlet or is it just a normal web application?

If you open a JIRA:

http://jira.icefaces.org/secure/Dashboard.jspa

and attach your fix, we'll look at including it in the next release.

http://www.icesoft.org/community/contribute.jsf

I've opened a JIRA for this issue:

http://jira.icefaces.org/browse/ICE-7754

My guess is that, because the CKEditor resources in question do not currently use JSF resource loading techniques, that the portlet bridge never gets a chance to do it's thing and encode them properly.

Getting Ajax to work properly with WSRP is a non-trivial challenge and is not currently supported in ICEfaces.

Ok, but we'll need more information to help troubleshoot the problem.

Is there anything in the logs on the server or perhaps in the browser console (e.g. Firebug in Firefox) that might provide a clue?

When you say "after a few clicks" can you be more specific about the steps that lead to the issue? Is the same number of interactions, the same order, a certain button that leads to the problem?

Can you provide the simplest .ear file that can be deployed to Glassfish that shows the issue in question?

Can you simply your application to remove the EJB requirement and then try running it on Liferay + Tomcat. Just try to remove Glassfish as a possible factor.

We appreciate your courage and daring ;-). The software world needs its pioneers.

I had captured that in this JIRA a couple of days ago:

http://jira.icefaces.org/browse/ICE-7718

We're code frozen for release so as soon as the repository thaws, I can add this in and you should be able to pick it up.

I opened a JIRA for the jQuery issue:

http://jira.icefaces.org/browse/ICE-7717

I did see some other minor issues when running on Liferay 5 but they were not related to the most recent PortletFaces Bridge (2.0.2). We'll create JIRAs and investigate as we narrow them down. Do you have stack traces or logging output related to the issues you are seeing?

Deryk

Sorry but I don't fully understand your question. Are you asking why the View-scoped beans aren't going out of scope? I'm not sure myself.

You might try verifying that the View-scoped bean lifecycle is being executed as intended by adding @PostConstruct and @PreDestroy annotations on a couple of methods and then logging when the beans are created and destroyed. That might provide clues. Perhaps JSF does let them go out of scope but the Liferay Messaging system retains a reference.

I might try removing the "throws Exception" from the method. Perhaps it doesn't like that signature.

You can build and run the Component Showcase example as a portlet:

cd icefaces.dir/samples/compat/component-showcase-portlets
ant clean liferay6.servlet-profile

The resulting .war file should be deployable to Liferay and has lots of different portlets showing off various components, including the command button.

We would have tested against 6.0.6 as we don't typically test against pre-release versions of platforms. Probably worthwhile to run against 6.0.6 and see if you get the same issue.

I downloaded the 6.1 Beta and a clean binary version of ICEfaces 3.0 RC 1 and was able to deploy the Accordion Panel example without hitting the issue you are seeing. I do get an exception regarding the source code resources:

Code:

18:12:30,336 INFO  [PortalImpl:4678] Current URL /comp-suite/sourcecodeStream.html?path=%2FWEB-INF%2Fclasses%2Forg%2Ficefaces%2Fsamples%2Fshowcase%2Fexample%2Face%2Faccordionpanel%2FAccordionPanelBean.java generates exception: null
 java.io.FileNotFoundException: http://localhost:8080/comp-suite/sourcecodeStream.html?path=%2FWEB-INF%2Fclasses%2Forg%2Ficefaces%2Fsamples%2Fshowcase%2Fexample%2Face%2Faccordionpanel%2FAccordionPanelBean.java

but it doesn't interfere with the operation of the portlet. We'll clean that up for final release (just need to comment out the relevant section in content-template.xhtml).

When .war files are deployed to Liferay, it dynamically adds files as well as modifies the web.xml. Perhaps you could check the deployed version of the web.xml file and see what it has in it.