voyent
Messages posted by: pabreau  XML
Profile for pabreau -> Messages posted by pabreau [23] Go to Page: 1, 2 Next 
Author Message
That's great to hear you've got the apps running. Yes, regarding why Fedora ships with GCJ, that's a good question. I understand that it's a licensing issue. Up until now, Sun hasn't granted the right to redistribute Java on Linux distro's. That's just changed apparently (http://www.internetnews.com/dev-news/article.php/3606656), so perhaps you'll see newer distro's including Sun's Java.

Thanks,
Philip
Hi Finn,
Do you mean you're running Apache Tomcat? It looks like you're running 5.5.15. Usually this sort of an error points to problem with the server compiling a JSP. I would suggest trying out the Tomcat examples first to see if they run. What version your JAVA_HOME environment variable is set to? That might have something to do with it.

Thanks,
Philip
Interesting problem.

Well, I'm not exactly sure how you're implementing this, but perhaps you're trying to do too much in the JavaScript world and not enough in the JSF world. Instead of a JavaScript timer, why not a IntervalRenderer. If you look at the TimeZoneBean class in the TimeZone tutorial, it uses an IntervalRenderer to update application state (strangely enough ;) at regular intervals. Perhaps you might more easily set a lastUpdated timestamp variable in your application and check this every 15 seconds. Set a valueChangeListener on the input fields that updates the lastUpdated timestamp. Then the IntervalRenderer can just check timestamp. If the lastUpdated time is greater than 15 seconds, just set the fields to null. JSF and ICEfaces will take care of the rest. The client side will be automatically updated. Make sure your JSF fields have their partialSubmit attribute set to true, and then you most likely won't see that ugly flashing screen posting back and resetting itself.
That's one of the great things about ICEfaces, you don't need to worry about fancy JavaScript foot work on the client side. Just do what you want to do on the server side, and the client side will take care of itself.

Thanks,
Philip
Hi,
How are you trying to start these Threads? Can you provide some code that might shed some more light on what's happening? What have you changed in the TimeZone example?

Thanks,
Philip
Thanks Graham,
Yes, I see what you're saying about quoted strings not coming out properly in inputText components. The quotation marks aren't escaped and the output html looks something like:
value=""Node 8"">
which is invalid HTML. I've passed this on to our developers , who'll look into it shortly.

I'm not exactly sure what you mean when you say that when you expand a tree node the all of the quoted values vanish though. Could you elaborate on this?

Thanks,
Philip
GCJ is the Gnu compiler for Java. What OS are you running? GCJ is not yet a complete implementation (see the status at http://gcc.gnu.org/java/status.html). I would suggest installing the Sun implementation of JDK 1.4.2. You can download the JDK from java.sun.com.

Thanks,
Philip
You can just use a ice:panelGrid, which will translate to a regular html table, and your calendar will be nested in the table. If you want a pop-up calendar (by setting renderAsPopup="true") the pop-up will render over the table when the calendar icon is clicked.

Thanks,
Philip
Hi,
Glad to hear you're using the Studio Creator Plugin. There's nothing special you need to do to get background images working with ICEfaces here. Normal CSS or HTML rules should apply. If using a CSS rule, your image url should be relative to the css file, eg.

background-image:url('../images/address-bkgnd.gif');

or relative to the JSF template file if the CSS rule is inlined.
You can also just use a normal HTML attribute on the body tag, eg.
<body background="myImage.gif">
W3Schools has some good tutorials on these:
http://www.w3schools.com/html/html_backgrounds.asp

Thanks,
Philip
Justin,
Yes, I think you're right. The styleClass attribute doesn't seem to have an effect on the Calendar component right now. Our developers are looking into it. In the meantime, I tested work-around that may be helpful to you. You can override the styleClass with an inline style attribute in the Calendar. ie:
<ice:selectInputDate style="color: pink;"
imageDir="#{styleBean.imageDirectory}"
value="#{dateSelect.date1}"/>

Thanks,
Philip
Regarding your question about whether the info on all panels are loaded at once.. the answer is no, that's one of the great things about ICEfaces, you get incremental view updates on demand. You can see the ui updates to a panel by starting the JavaScript console (cntrl-shift-T) and watching exactly what gets updated when you interact with the panel.

Philip
Yes :) The new 1.0 Community Edition release includes a Studio Creator complib for the ICEfaces Component Suite that supports design-time drag-and-drop visual design in Studio Creator using the ICEfaces components. You'll find it in the tools directory of the CE download. And we'd love to hear your feedback after you've tried it.

Thanks,
Philip
Sorry, that code snippet didn't come out clearly, try this:
<servlet-mapping>
<servlet-name>Blocking Servlet</servlet-name>
<url-pattern>/module/assets/block/*</url-pattern>
</servlet-mapping
Well, the previous suggestion fixed the two rootNodes problem, which allowed the tree be rendered. This is another problem that comes from an issue the Blocking Servlet has with connecting to pages nested in project subdirectories. If the Blocking Servlet cannot connect with the server, when the user first interacts with the view, and the client attempts to communicate that interaction with the server, which fails, the 'Connection Lost' message appears. The current work-around is to add servlet mapping for the subdirectory, like so:
<servlet-mapping>
<servlet-name>Blocking Servlet</servlet-name>
<url-pattern>/module/assets/block/*</url-pattern>
</servlet-mapping

After adding this to the web.xml file, the tree correctly collapses and expands.

Philip
Maarten,
I got your test to work after removing the binding attribute from the tree tag. Your original code:

<ice:tree id="tree" value="#{TreeBean.model}"
binding="#{TreeBean.treeComponent}"
actionListener="#{TreeBean.navigate}" hideRootNode="false"
hideNavigation="false" var="item"
cssImageDirectory="../../xmlhttp/css/xp/css-images/">
<ice:treeNode>
<f:facet name="icon">
<ice:panelGroup style="display: inline">
<h:graphicImage value="#{item.userObject.icon}" />
</ice:panelGroup>
</f:facet>
<f:facet name="content">
<ice:panelGroup style="display: inline">
<ice:outputText value="#{item.userObject.text}" />
</ice:panelGroup>
</f:facet>
</ice:treeNode>
</ice:tree>

was producing the following error:
javax.faces.FacesException: Can't parse stream for /module/assets/files.jspx The tree tag requires a single child treeNode tag. Found [2]

I guess having both a binding and a value on the tree was causing the component engine to produce a tree with two ndoes, which is not allowed.
After removing the binding, it worked. I've also included the war file.

Philip
ICEsoft Technologies Inc.
This thread to check about resource bundles and locale configurations might help. (http://support.icesoft.com/jive/thread.jspa?messageID=3291)
 
Profile for pabreau -> Messages posted by pabreau [23] Go to Page: 1, 2 Next 
Go to:   
Powered by JForum 2.1.7ice © JForum Team