ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

Hi,

I eventually figured out the solution, but unfortunately I can't remember. But what I do remember is that it was a weird configuration issue. Everything has to be done exactly right for one path only, the other paths never worked for me... You'll find information that says to do it one way, but that doesn't work, do it another way, etc. Eventually I just figured it out after some time.

I wish I could remember, but it was getting exactly configured perfectly for one specific path.

This is why it will be great when the IceFaces people provide us with an example Facelet demo! From what I hear they're working on this...

Regards,
Steph

Did you also change how you add the tags to:

Code:

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

Regards,
Steph

Hi Wilbur,

Actually, it has nothing to do with me, I'm quite sold on your implementation. I've actually already written more than 1/2 the webapp with it already with great success!

It's not really the security that has caused the push-back, but the scalability. Can it handle the throughput? Our current implementation gets several million unique visitors a month, and therefore the forces that be are a little risk adverse, which I can't blame them in any way!

They initially wanted an AJAX implementation, which is why we found with your amazing implementation. However at this stage of the game, they've decided to pull back all AJAX functionality and slowly introduce small AJAX features rather than a larger scale AJAX roll out. As we don't have full metrics on this scale, they'd rather move slowly to be safe.

There's not much to do to convince them, it's basically a risk minimization decision based on our scale. We will be introducing AJAX functionality, just not all at once as we initially expected.

That being said, is there a way to turn off the AJAX'iness without having to recode a lot of it (for example, moving a lot of the code from just event handling to navigation rule, etc.) just to have to re-bring it back later when we get the go ahead?

Regards,
Steph

Hi,

I know this counter-intuitive, but is it possible to turn off the AJAX part of IceFaces and just use it as a normal JSF implementation?

The reason I ask is that we were planning on using AJAX support but this has been postponed for now (there is concern over the potential risk of AJAX). Therefore since we're eventually heading there, and I don't want to have to convert everything to the myfaces implementation only to reconvert it back to IceFaces. Is there a way to just turn off the AJAX'iness of IceFaces?

Regards,
Steph

Hi,

I think this may have been the issue. It's possible that I had a jar conflicting with another one...

Regards,
Steph

No problems. Just thought you'd like to know.

Regards,
Steph

Hi,

Is it just me or is the component showcase page not working today?

http://component-showcase.icefaces.org/component-showcase/

Regards,
Steph

Hi Philip,

Very good point!

I'm looking for your zipped attachment and I can't seem to find it in the previous comments in this thread. Would you mind reposting it?

Thanks,
Steph

Hi,

To answer your questions:

1. Yes, I'm using all the jars. I haven't yet had the time to minimize the list.
2. Yes, those are the ones provided by IceFaces. That was also one of my first thoughts, incompatibilities between versions.

What's really weird is that sometimes this setup works, and other times it doesn't seem to want to accept it...

It's great to hear it worked for you guys! Thanks for checking it out, it's very appreciated!!!

We have a couple new people coming in today, and 3 of us are changing boxes, so I'll see if it replicates itself...

Regards,
Steph

Hi,

I posted an earlier thread here about an issue I'm having trying to get facelets to work with IceFaces. http://www.icefaces.org/JForum/posts/list/2982.page

I still haven't solved it but what I did is create an extremely small and simple example application. Please find it attached here.

If you remove the facelet hooks, it correctly displays the backend bean values. If you run it as is on tomcat 5.5, it displays nothing...

To remove the facelets hooks, just delete the myOwn.taglib.xml, the reference to it in the web.xml and the reference to it in main.xhtml.

Your assistance would be greatly appreciated!!!

Regards,
Steph

I've gotten a little further! It seems related to the facelets... When I remove the following blurps of code below, it seems to work correctly...

The good news is that in JBoss I get a completely different error. Although this error doesn't mean much more to me, I'm hoping it means something to you :)

Code:

16:46:10,368 INFO  [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 26s:360ms
 16:46:13,602 ERROR [STDERR] Nov 30, 2006 4:46:13 PM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
 INFO: Added Library from: jar:file:/C:/data/downloads/jboss-4.0.5.GA/jboss-4.0.5.GA/server/default/./deploy/poolNow7.war/WEB-INF/lib/icefaces-facelets.jar!/META-INF/jstl-fn.taglib.xml
 16:46:13,696 ERROR [STDERR] Nov 30, 2006 4:46:13 PM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
 INFO: Added Library from: jar:file:/C:/data/downloads/jboss-4.0.5.GA/jboss-4.0.5.GA/server/default/./deploy/poolNow7.war/WEB-INF/lib/icefaces-facelets.jar!/META-INF/jsf-ui.taglib.xml

I also forgot, this is my current code:

web.xml I added:

Code:

	<context-param>
 		<param-name>facelets.LIBRARIES</param-name>
 		<param-value>/WEB-INF/facelets/tags/cpc.taglib.xml</param-value>
 	</context-param>

cpc.taglib.xml is:

Code:

<?xml version="1.0"?>
 <!DOCTYPE facelet-taglib PUBLIC "-//Sun Microsystems, Inc.//DTD Facelet Taglib 1.0//EN" "facelet-taglib_1_0.dtd">
 <facelet-taglib>
       <namespace>http://www.canadapost.com/jsf</namespace>
 	<tag>
 		<tag-name>dimensions</tag-name>
 		<source>dimensions.xhtml</source>
 	</tag>
 </facelet-taglib>

And in the xhtml file I have:

Code:

<f:view xmlns:cpc="http://www.canadapost.com/jsf" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:ice="http://www.icesoft.com/icefaces/component">
 ...
 		<cpc:dimensions fieldName="selectedPanel" entity="#{centerControllerPanelStackHandler.selectedPanel}" />
 ...
 </f:view>

Regards,
Steph

Hi Philip,

Yes, we're using Tomcat 5.5. As for IDE, it's Eclipse 3.2.1.

As for loads a new environment, I mean a new instance of Eclipse, tomcat, etc. Checks out the code from CVS and then adds:

Code:

	<Context path="/myContextx" debug="4" reloadable="true" cachingAllowed="false" privileged="true" 
 		docBase="C:\eclipse-SDK-3.2.1-win32\eclipse\workspace\MyProject\WebRoot"> 
 		<Logger className="org.apache.catalina.logger.SystemErrLogger" verbosity="4"/> 
 		<Logger className="org.apache.catalina.logger.SystemOutLogger" verbosity="4"/> 
 	</Context>

to the tomcat/conf/server.xml file.

I've also adjusted the context.xml to add:

Code:

    <Manager pathname="" />

To remove any persistence issues related to tomcat.

Sometimes it seems to load fine, and on another person's computer it doesn't start up and gives the error message I posted. As well all the fields displaying a backend bean are blank... It's only when you click on a button (that's linked to a backend method) that it blows up because it can't find it (it just seems to put empty fields for all the displays otherwise).

I've also got it configured with facelets, which I finally got working yesterday! When I went to load it on another person's computer today, I kept getting this error. That's when I decided to restart from scratch on my box from cvs and got this same error. Another person did it and it seemed to work...

Based on the error message, I'm not sure where to look...

Regards,
Steph

Hi,

Can someone please help me with this error. It seems to occur randomly when someone loads a new environment:

Code:

2006-11-30 14:55:10 ERROR - com.icesoft.faces.webapp.xmlhttp.PersistentFacesServlet:433 - Exception executing lifecycle or setting up persistent context. /inc/tap/singleItem/searchResults/singleItemSuccessfulSearchResultPanel.xhtml @17,220 actionListener="#{singleItemSearchResultAccordian.toggleDetailedItemInformationDisplayCommandButtonListener}": Target Unreachable, identifier 'singleItemSearchResultAccordian' resolved to null
 javax.faces.el.EvaluationException: /inc/tap/singleItem/searchResults/singleItemSuccessfulSearchResultPanel.xhtml @17,220 actionListener="#{singleItemSearchResultAccordian.toggleDetailedItemInformationDisplayCommandButtonListener}": Target Unreachable, identifier 'singleItemSearchResultAccordian' resolved to null

Now the backend bean can be any backend bean! I've even tried <ice:outputText value="#{someBean.property}"/> which print outs nothing on the screen.

This was a working application that I moved to another instance of tomcat (clean instance) that no longer works (same building within eclipse for example). Some times it seems to work, other times not so much...

Any suggestions would be greatly appreciated!

Regards,
Steph

Hi,

I have a few questions about how you manage sessions.

1. When I start a new browser, connect to the website in IE, then close it, move to FireFox, it seems to remember my session information from IE. How does it do this? Also, what happens if you have multiple people coming from the same IP address?

2. When I disconnect the server and still have the webpage open, it seems to hang with the wait cursor. No message, nothing. After several minutes it's still hanging...

3. If I reconnect the server and click on different buttons, it still seems to be in the hanging stage. How can I prevent this?

Regards,
Steph

Hi,

Some more remarks :)

- That's pretty much the same thing. After today I won't have any .jsp files, just .xhtml.

- I think you're right. However if I add it my editor doesn't complain nearly so much with error and warning flags because it can't find the definitions.

- Actually, you do have to restart after each page change with tomcat, no matter what. But what's more irritating is that it keeps the session information between the restarts unless you change the persistent manager (which is not very well documented). Not a big issue, but something that you need to be aware of that can be very aggravating!

Regards,
Steph