This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Wicket is a great web framework. There are some unofficial efforts, like http://blogs.sun.com/geertjan/entry/wicket_support_in_netbeans_ide , but, citing, "...it didn't work with 6.9.1.". Is there a chance to have official Wicket support in NetBeans? Since wicket is heavily Java-code-oriented, only few features are really needed: http://ondra.zizka.cz/stranky/programovani/java/web/wicket/netbeans-wicket-support-wishlist.texy * One-step creation of html + java files * Validation in HTML files aware of wicket: namespace * Check consistency of HTML vs. Java files * Check consistency of property strings – e.g. new PropertyModel<String>(this, "path") Thanks for considering.
and rfe should be filed as an enhancement... not a defect.
Found Geertjan's plugin: http://plugins.netbeans.org/PluginPortal/faces/PluginDetailPage.jsp;jsessionid=3c9bc76c4868f042b056450faf8e?pluginid=3586 Now just to make it supported to keep it working with releases :)
Geertjan, any plans with the wicket plugin?
Sure, you can get the latest branch from the repo and check it into contrib. I think pjiricka was working on this a while ago.
I ment whether you have some plan with the plugin yourself. The page claims it is aimed for 6.9.1 but I reckon this is wrong, isn't it?
No, it's not wrong. Have a look at the comments, and read the texts, you'll see its for 6.9.1., it even has Maven support.
I see. I misunderstood the pekarna's citation in the very first comment. Lets keep the RFE as P2, we'll see what can be done in 7.0.next. I do not see any *wicket* module in contrib. pjiricka, is there any result of the work Geertjan mentioned?
Confirming it works well with 6.9.1; I cited an old comment. Sorry for confusion.
Adding to the wishlist: * Component ID's completion - would list IDs from .html in .java and vice versa. * Navigation between ID's - Ctrl+click on ID in .html would navigate to that ID in .java and vice versa. Assuming unique IDs per component (or taking the first one) is OK (to prevent complex implementation of this functionality). * Locating component ID - search component IDs for a given pattern. Component IDs in .java can be distinguished as String constants used as first attribute to a constructor of any instanceof org.apache.wicket.Component.