ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

Just saw that 1.52 is out (have been away from JSF/IceFaces for a while).

Are these DnD issues resolved with the current version?

Thanks,
Thomas

The styling attributes of selectInputText are not compatible with the "IceSoft standard":

- not "styleClass" determines the CSS class, but the name of the embedded f:facet

- the width of selectInputText can only be set with the "width" attribute (which translates its content to style="width: NNNpx"). Thus, one cannot determine the width in em units (as one should do in most cases). It would be better to remove the width attribute alltogether.

Is there a workaround - except styling all my other input fields in px units?

We had the same problem, which is solved after setting the backing bean variable to Long, instead of Integer.

But:
Isn't this an error in IceFaces?
Your examples use Integer variables for ice:outputText. Why should ice:inputText require something different?

Dear Christian, dear Todd,

it's nice to see you working so hard to solve these problems ... while still being on holiday. ;-)

Good luck!
Thomas

I don't know if this means anything, but the tomcat.log displays an exception when tomcat is stopped:

ERROR Thread-1 org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/component-showcase] - Exception sending context destroyed event to listener instance of class com.icesoft.faces.util.event.servlet.ContextEventRepeater
java.lang.NullPointerException
at org.apache.catalina.loader.WebappClassLoader.findResourceInternal(WebappClassLoader.java:1766)
at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1570)
at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:850)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1299)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1181)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at com.icesoft.faces.util.event.servlet.ContextEventRepeater.contextDestroyed(ContextEventRepeater.java:82)
at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3710)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4283)
at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:892)
at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1143)
at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1115)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:313)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1053)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1065)
at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:447)
at org.apache.catalina.core.StandardService.stop(StandardService.java:512)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:717)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:586)
at org.apache.catalina.startup.Catalina.start(Catalina.java:561)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)

My collegue Christian is on holidays. Just wanted to tell you that ACEGI seems to work smoothly with IceFaces 1.0.1.

Thank you very much!
Thomas

I checked the problem again and found something even more mysterious:

- Effects work for me if I use *your* component-showcase at http://demo.icesoft.com/component-showcase/

- Effects do NOT work if I use component-showcase.war deployed to my local Tomcat 5.5.9 (in fact, I tried 2 different tomcat 559 servers).

- Collegues tried the same with different browsers (IE, Firefox, Opera): all get the same (wrong) result.

Is there any dependency on the application server? Or do you have any other idea?

Thanks a lot for your help!

PS: this problem is not too important to me. But my DnD problem (http://support.icesoft.com/jive/thread.jspa?threadID=1852) is a real blocker for our development.

Setting the styleClass attribute of panelTabSet correctly defines the base name for derived CSS classes. But additionally, this attribute is translated to <TABLE styleclass="...">, which does not help. I guess this should be <TABLE class="...">.

Just a minor glitch - took me about half an hour to find out why my css stylings did not work... ;-)

For me, the ice-effects are not working.

Even the component-showcase.war example application does not display *any* of the effects (highlight, pulsate,...). Everthing else works as expected.

Any explanations? Has anybody similar problems?

My system:
- Tomcat 5.5
- Firefox 1.5
- icefaces 1.0.1

Thanks!

This is a "cross post" - sorry.
But I do not get an answer in the "General" forum:
http://support.icesoft.com/jive/thread.jspa?threadID=1819&tstart=0

The issue:
========
Drag and drop does not work correctly: the listener "dragPanelListener" is never called. The identical code works correctly, if I remove the facelets view handler "D2DFaceletViewHandler" from my faces-config.xml file. I am quite sure that there is a problem with the D2DFaceletViewHandler!

I have inserted the attached code (see original post) into the timezone6 tutorial application. The result is the same as in my own application: I can move around the draggable panelGroup, but the event listener is never called.

I am using
- IceFaces 1.0.1
- Facelets 1.1.11
- acegi
- Spring
- Tomcat 5.5
- Java 1.5

Can you please confirm if you can reproduce this problem? - and possibly provide a solution?

Thanks in advance!

Message was edited by: Thomas Stahl

Thank you - this was the answer I expected. :-)

I tried your workaround - and made two interesting observations in my log files:

1) getTabSet() is called exactly ONCE during the lifetime of the application. I had expected that it would be called more often.

2) setTabSet() is called with every form submit (click on the tabs or link to a different page). This time, I had expected much fewer calls. Every call of setTabSet sets the SAME tabSet object, its selectedIndex being the index *before* the click.

Question: Is this the correct behaviour - would *you* have expected the above?

I solved my problem with the following code:

public void setTabset(PanelTabSet tabset) {

if( isNew )
{
tabset.setSelectedIndex(0);
isNew = false;
}
}

Far from ellegant, but working as it seems.

Thank you very much!

Message was edited by: Thomas Stahl

I would like to force my panelTabSet to display the first panelTab (index=0) whenever the corresponding backing bean GKS is reloading. GKS has request scope. To achieve this, I use a value binding for selectedIndex:

<ice:panelTabSet selectedIndex="#{GKS.tabIndex}" >

During the construction of the GKS bean, the property tabIndex is set to 0. Of course, there are [gs]etTabIndex methods.

I can see from the logs, that the GKS bean is constructed and the tabIndex property set to 0. However, the panelTabSet still displays the panelTab shown immediately before the reload and ignores the value of selectedIndex.

- Did I misunderstand the role of selectedIndex?
- Is there a better way to achieve the desired effect?

I would prefer a solution that does not require me to implement the whole panelTabSet in Java... ;-)

Thanks!

Just a typo correction: timezone6 (not timezone5).

Drag and drop does not work correctly: the listener "dragPanelListener" is never called. The identical code works correctly, if I remove the facelets view handler "D2DFaceletViewHandler" from my faces-config.xml file. I am quite sure that there is a problem with the D2DFaceletViewHandler!

I have inserted the attached code into the timezone5 tutorial application. The result is the same as in my own application: I can move around the draggable panelGroup, but the event listener is never called.

I am using
- IceFaces 1.0.1
- Facelets 1.1.11
- acegi
- Spring
- Tomcat 5.5
- Java 1.5

Can you please confirm if you can reproduce this problem? (I am sure you can!) - and possibly provide a solution?

Thanks in advance!

Thank you very much - that solved the problem.
Thomas