We are using Sun's Studio Creator and I installed your icefaces tools support in Creator and was able to launch the icefaces components demo app from Creator. Then I created a JSF app in Creator and added icefaces support via the context menu you guys added to Creator. I created a table component via the Creator Component Pallet and attempted to run the webapp. The app came up in the browser but the table component did look right and didn't behave correctly.
Now to my question: you support Sun's RI of JSF and MyFaces which is nice but is there any chance you could support Sun's Rave JSF components (which is what Studio Creator uses)?
ICEFaces is an amazing product, by the way, and we will definately purchase the Enterprise ICEFaces when it becomes available. If you cannot support Sun's Rave components we will most likely use MyFaces but I'll take some flack for changing our webapp's appearance. I know ICEFaces uses style sheets for its look but Rave's table component has a lot of interesting behavior that would be missed if we switched to MyFaces.
From that posting you will see that the Sun table component is currently not supported in ICEfaces. You are not the first to inquire about ICEfaces support for the Sun components and specifically the table component, so we will be looking to address your requirements as soon as possible. We would be interested to know what are the highest priority Sun components to support from your perspective?
Our most important component is the Rave table. Other than that one we could use your components as substitutes (or even MyFaces for that matter). More important than supporting the Sun components is supporting the ICEFaces components via complib. With complib support your components would appear in Creator's component pallet and property editors.
Looking forward to your May 1.0 release. I've worked with Oracle's ADF component set (and JDeveloper) but have a strong preference for ICEFaces.