![]() I'd rather use the JSF standard way of placing components, which is using a panel grid for layout right inside a JSF form component. I prefer dropping the components in the navigator page instead of directly in the JSP design view, since dropping the components in the design view results in CSS absolute positioning. ![]() Under Windows, I wasn't able to drag components from the palette into the navigator page, this it is possible using NetBeans standard Visual Web JSF functionality (oddly enough, I was able to do this under Ubuntu Linux). ![]() ), therefore we end up with classes in nonstandard packages. The project name never adheres to standard Java package naming conventions (i.e. The first issue I ran into is that the Java package for managed beans defaults to the project name and cannot be changed. Since Woodstock will no longer be developed, I figured now is a good time to take the NetBeans IceFaces plugin for a spin, to see how well it works, turns out, it doesn't work very well, at least the current version available from the NetBeans Plugin Manager. An IceFaces plugin has been available for a while to develop JSF applications visually using the IceFaces components, the plugin works in a way that is very similar to the standard Visual Web JSF NetBeans plugin. Sun is now recommending that current Woodstock applications be migrated to IceFaces. This announcement affects NetBeans Visual Web projects, since they use Project Woodstock JSF components behind the scenes. Some maintenance will be done in the project, but no new features are planned. Recently Sun announced that there will be no further development for Project Woodstock.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |