ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

Philip.

Thanks again for your reply.

- Mark

Philip,

Thanks for your reply!

- Mark

Hi,

philip_b wrote:

You can get around this warning by sticking the following inside the context declaration in your Tomcat config.

This workaround works, but I think it is only a workaround. Isn't this a problem with how ICEfaces works?

As I understand it, in a clustered environment you want to be able to serialize sessions, (so that they can be moved to a different node to support failover). Doesn't this error message indicate that an ICEfaces session is not serializable, therefore ICEfaces doesn't support clustering?

- Mark

Hi,

As a follow-up to my previous post, can anyone tell me the extent of ICEfaces tool integration in BEA Workshop for JSF?

I am under the impression that the plugin adds the the aforementioned option to create a new ICEfaces ready JSP page, and also adds a context menu to add ICEfaces support to an existing web application.

This context menu then adds the required jar files to WEB-INF/lib, adds icefaces_component.tld to WEB-INF, and mucks about with the web.xml file to add the required servlets and config parameters, and changes STATE_SAVING_METHOD to "server".

As far as I can tell, there is no special help to visually edit JSP pages, or any other features. Am I correct?

I'm asking as I am evaluating the ICEfaces tool integration, alongside the ICEfaces framework.

- Mark

Hi,

With the ICEfaces plugin for BEA Workshop for JSF, when I create a new JSP page I get the option to create a "New ICEfaces File", which produces a *.jsp file with a taglib declaration for the ICEfaces tag library.

However, the tutorial, and other things I've read, states that ICEfaces works with XML format *.jspx JSP documents.

Is this a bug in the plugin, or can I use JSP pages instead?

- Mark

Hi,

The following works with both the Sun RI and MyFaces, and also stops BEA Workshop complaining about missing navigation rules:
Code:

 <navigation-rule>
   <from-view-id>/pages/welcome.*</from-view-id>
   <navigation-case>
     <from-outcome>success</from-outcome>
     <to-view-id>/pages/success.jspx</to-view-id>
   </navigation-case>
 </navigation-rule>

I'm going to investigate a bit further, and have a look at the JSF specs. I don't think I understand the definition of a "view identifier".

- Mark

Hi Liming, and thank you for your reply,

liming_w wrote:

Note faces-config has been slightly changed

Interesting. The changes you made to the faces-config.xml fixes the application, and clicking on the submit commandButton moves to the second page.

The changes are as follows:
Old Code:

   <navigation-rule>
     <from-view-id>/welcome.jspx</from-view-id>
     <navigation-case>
       <from-outcome>success</from-outcome>
       <to-view-id>/success.jspx</to-view-id>
     </navigation-case>
   </navigation-rule>

New Code:

   <navigation-rule>
     <from-view-id>/welcome.iface</from-view-id>
     <navigation-case>
       <from-outcome>success</from-outcome>
       <to-view-id>/success.iface</to-view-id>
     </navigation-case>
   </navigation-rule>

However, the old code, referencing the underlying jspx document, works fine using the MyFaces implementation.

Also, BEA Workshop for JSF is now complaining that it doesn't know about the navigation rules for the application. Specifically, BEA Workshop is warning that

The navigation outcome "success" returned from the "submit" action is not valid from this page.

Actually, the following works as well:
Code:

   <navigation-rule>
     <from-view-id>/welcome.iface</from-view-id>
     <navigation-case>
       <from-outcome>success</from-outcome>
       <to-view-id>/success.jspx</to-view-id>
     </navigation-case>
   </navigation-rule>

- Mark

Hi,

This now works for me, but I don't know what I changed to get it to work.

I'm finding using the ICEfaces framework frustrating, as sometimes things don't work, with no information about why they don't work.

- Mark

Hi Philip,

philip_b wrote:

Does it work if you remove the Tomahawk library or the <ice:selectManyCheckbox> component from the second tab? Are you using a TabChangeListener?

No, removing the Tomahawk jar and removing the <ice:selectManyCheckbox> makes no difference.

I am not using a TabChangeListener.

- Mark

Thanks for your reply.

liming_w wrote:

1. in welcome.jspx, values taken from resource bundle should be value="#{bundle['welcomeTitle']}" instead of value="#{bundle.welcomeTitle}"

These are equivalent ways to reference the entries in a map (or other indexed property): if the key is a string without a '.' in it (e.g. 'welcomeTitle') you can access the value with the '.' operator.

Here's a reference for this part of the JSP 2.0 expression language:
http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSPIntro7.html#wp84857

Changing all these to the form you suggest doesn't make a difference.

liming_w wrote:

2. You have mentioned that you use Sun RI 1.1 but your web.xml shows you use MyFaces

My mistake. Here is the web.xml:

Baleyba wrote:

That is what I thought before.

But the Iceface MyEclipse plugin give this possibility:
...
So I think it should be possible... Otherwise this option shouldn't exist... not ?

Hi,

Yes, I noticed that in the integration plugin for BEA Workshop for JSF, but the very first step in the tutorial section of the Getting Started guide shows you have to use JSP document syntax. I think it is a mistake in the plugin.

See: http://www.icesoft.com/developer_guides/icefaces/htmlguide/gettingstarted/TimezoneTutorial10.html

- Mark

Hi Bal,

As ICEfaces uses jspx files , i.e. JSP documents which are valid XML documents, you need to convert your taglibs to using namespace declarations, as follows:

<f:view
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:ice="http://www.icesoft.com/icefaces/component">...</f:view>

I'm not sure whether MyEclipse understands this part of the JSP spec, but other IDEs such BEA Workshop for JSF do.

I hope this helps.

- Mark

Hi,

Can anyone tell me why the attached page doesn't work as expected? I can't move back to the first tab when I select the second one.

I'm using Tomcat 5.5.20, BEA Workshop for JSF 3.2.1, ICEfaces workshop integration 1.5.1, MyFaces 1.1.4 (Tomahawk 1.1.3 also in WEB-INF/lib), and Internet Explorer 6.0.

- Mark

Hi,

Could anyone explain why the h:commandButton in the following example doesn't work, now that I've integrated ICEfaces?

It all worked before I used the context menu "ICEfaces Integration > Enable ICEfaces...".

The managed bean called "simple" just returns "success". The action listener in the same bean is correctly called.

I'm running: Tomcat 5.5.20, BEA Workshop for JSF 3.2.1, ICEfaces workshop integration 1.5.1, Sun JSF RI 1.1, Internet Explorer 6.0.

- Mark

The faces-config.xml is as follows:
Code:

 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE faces-config PUBLIC
   "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
   "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
 
 <faces-config>
 
   <application>
     <message-bundle>resources.application</message-bundle>
     <locale-config>
       <default-locale>en</default-locale>
     </locale-config>
   </application>
 
   <managed-bean>
     <managed-bean-name>simple</managed-bean-name>
     <managed-bean-class>com.nr.Simple</managed-bean-class>
     <managed-bean-scope>request</managed-bean-scope>
   </managed-bean>
   <navigation-rule>
     <from-view-id>/welcome.jspx</from-view-id>
     <navigation-case>
       <from-outcome>success</from-outcome>
       <to-view-id>/success.jspx</to-view-id>
     </navigation-case>
   </navigation-rule>
 </faces-config>