ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

I don't understand why but it stopped working _again_. I started the tomcat standalone and deployed an ICEfaces sample, stopped it and tried to run my project again. Bang.

I needed to remove the project and re-deploy it again. At least I got it working now.

Can someone help me understand what the problem is?

I had the same error and was able to fix it with said disabling of persistence stuff in Tomcat 5.5.25. But I had to remove the project, clean tomcat and re-deploy it (tried several times) to get it correctly working.

Spec stuff: debian 4.0, Sun JDK 5.0_13, Tomcat 5.5.25, eclipse Europe (fall), JSF 1.1_02

Let me know if you need some other info.

Huh? IMHO the document snippet above IS a jspx. Either way, my test file is named test1.jspx and so-called autocomplete is working fine in "Exadel JSP Editor" AND "JSP Editor" (I think from WTP).

This worked for me:
1) install fresh eclipse 3.2.1 + free version of exadel studio 4.0.2 (for jsf / spring plugins)
2) download icefaces eclipse ide integration: ICEfaces-v1.5.1.1-Eclipse.zip
3) extract the zip into a temp dir and copy the plugins folder into your eclipse home directory
4) create a new project like described in the readme.html of the zip (Dynamic Web Project, Icefaces template)
5) create a test.jspx and insert the snipped above. save.
6) at this point auto complete worked for me

Hi,

maybe a bit too late for the original poster, but for anyone who stumbles upon this like me.

Use something like this for a jsp template:
Code:

<?xml version='1.0' encoding='UTF-8'?>
 <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0"
           xmlns:h="http://java.sun.com/jsf/html"
           xmlns:f="http://java.sun.com/jsf/core"
 	  xmlns:ice="http://www.icesoft.com/icefaces/component">
   <jsp:output omit-xml-declaration="true" doctype-root-element="HTML"
               doctype-system="http://www.w3.org/TR/html4/loose.dtd"
               doctype-public="-//W3C//DTD HTML 4.01 Transitional//EN"/>
   <jsp:directive.page contentType="text/html;charset=UTF-8"/>
   <f:view>
     <html>
       <head>
         <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
         <title>untitled1</title>
 	<link href="css/xp/xp.css" rel="stylesheet" type="text/css" />
       </head>
       <body><ice:form>
         </ice:form></body>
     </html>
   </f:view>
 </jsp:root>

Works like charm in Eclipse 3.2.1

Hi,

I'm successfully using the free version of Exadel Studio with Eclipse 3.2.1 and Ice Faces 1.5.1 using the WTP integration. Everything seems to work smooth here.

You have to take care for one thing: when you start your whatever.jsp your browser will open http://host:port/app/whatever.jsp instead of whatever.iface. This will result in an error (FacesContext not found) - just change the url to the above mentioned.

Hope it helps...

Hi philip_b,

thanks for your reply. Is there a way I could notice / get noticed when this behaviour is fixed? It's the only "show stopper" I've found so far.
Our customers solely use internet explorer and - most of the time - have some kind of portal that integrates other web apps via an iframe...

Greets,
Mathias

Hello everybody,

first congrats to ice faces. We're using ADF Faces atm but some of the components are quite impressive, so I'll take a closer look the next few weeks ^_^ I love those pop-ups, really :-)

I noticed an interesting glitch in ice faces that happens only in internet explorer and only if the ice faces site is displayed in an iframe.

Create a html with the following content:
Code:

 <html>
 	<head>
 		<title>
 		IFrame Test	
 		</title>
 	</head>
 	<body>
 		<a href="http://component-showcase.icefaces.org/component-showcase/" target="test">Show test</a><br>
 		<a href="http://www.google.de" target="test">Google</a><br>
 		<iframe src="http://www.icefaces.org" width="800" height="600" name="test">
 		</iframe>
 	</body>
 </html>

If you open the file in a new internet explorer and click "Show test" the component suite showcase is displayed. Everyon any item results in the status monitor going active and then broken after about half a minute.
I could solve this by clicking the other link and then the original one. Everything works fine then.
I could reproduce this error on several machines, but only in internet explorer - no problem in firefox (of course?).

Any ideas?

Keep up the great work!

Greetz,
Mathias