Hi Geertjan,

Thank for reply me, afte enble pluging fro wicket netbean is hanging and cant able to open any file. and i tried restart NetBean again and again but didn't work. This issue is same reported by sawerset on 28 May and you also provide solution.
But how i will remove userdir(please provide step specific).

Hi I want to add wicket plugin in Netbean but https://netbeans.org/kb/69/web/framework-adding-support.html
page is not working can anyone gelp me on this issue.

Hi, I reported two bugs in wicket plugin. They are here: https://netbeans.org/bugzilla/show_bug.cgi?id=156853, https://netbeans.org/bugzilla/show_bug.cgi?id=185067. Could you please fix this bugs?

OS Arch Linux

jdk 1.7.0_21

Restarting IDE doesn`t helps.
1. Create wicket web project
2. open com.myapp.wicket.HomePage.java
3. hangs

From log


INFO [org.netbeans.spi.lexer.MutableTextInput]: !!WARNING!! Missing READ-LOCK when accessing TokenHierarchy: input-source:org.netbeans.modules.editor.NbEditorDocument@2a3f9b94, mimeType='text/html', kitClass=null, length=539, version=1, file=org.netbeans.modules.html.HtmlDataObject@4df6d719[/home/witcher/NetBeansProjects/wicket/src/java/com/myapp/wicket/HomePage.html@1f97d04d:3b9d11f]
java.lang.Exception
at org.netbeans.lib.lexer.TokenHierarchyOperation.ensureReadLocked(TokenHierarchyOperation.java:397)
at org.netbeans.lib.lexer.TokenHierarchyOperation.tokenSequence(TokenHierarchyOperation.java:422)
at org.netbeans.api.lexer.TokenHierarchy.tokenSequence(TokenHierarchy.java:201)
at org.netbeans.modules.web.wicket.tree.HtmlTreeBuilder.analyze(HtmlTreeBuilder.java:67)
at org.netbeans.modules.web.wicket.tree.HtmlTreeBuilder.getTree(HtmlTreeBuilder.java:57)
at org.netbeans.modules.web.wicket.verification.WicketProblemAnnotationProvider.annotate(WicketProblemAnnotationProvider.java:188)
at org.netbeans.modules.web.wicket.verification.WicketProblemAnnotationProvider.annotate(WicketProblemAnnotationProvider.java:175)
at org.netbeans.modules.web.wicket.verification.WicketProblemAnnotationProvider.annotate(WicketProblemAnnotationProvider.java:118)
at org.netbeans.modules.web.wicket.verification.WicketProblemAnnotationProvider.annotate(WicketProblemAnnotationProvider.java:88)
at org.openide.text.CloneableEditorSupport.ensureAnnotationsLoaded(CloneableEditorSupport.java:420)
at org.openide.text.CloneableEditor$DoInitialize$3.run(CloneableEditor.java:870)
at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1432)
at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2044)

When I create wicket project, and open any file of project, netbeans hangs

What about support for Netbeans 7.3?

Many thanks for the exciting blog posting! I really enjoyed reading it, you are a brilliant writer. I actually added your blog to my favorites and will look forward for more updates.Great Job,Keep it up. What is SEO

I have been following your work on wicket (https://blogs.oracle.com/geertjan/), not on this plugin, i have just seen and installed it. Thank you.

Hello geertjan, i have been following for a while with your great work with wicket. Just asking is there a repo for this plugin? Could i see code?

Thanks.

Wicket 1.6.0 support now available.

The 7.1 plugin works the same in 7.2. Not updating to Wicket 6.0 yet, until Wicket 6.0 is released. I went through the tutorial and checked that everything works correctly.

http://www.netbeans.org/kb/docs/web/quickstart-webapps-wicket.html

The link to the "Introduction to the Wicket Web Framework" tutorial is dead. Could you guys help with that please?

I'd like to get it to you in the next few weeks but it could be delayed slightly because of my job. Nothing earth shattering here & mostly aesthetic changes with some refactoring of the css which would give the starter project a cleaner, more professional looking page.

I'd also like to suggest the following which is a typical use case that involves the wicket library distributed with the plugin:
1) Allow for the selection of the wicket library to use when creating a new project but continue to default to the one distributed in the plugin. Why? Because often when dealing with trunk releases of Wicket it is common to create a new Library via Netbeans Library support and use that instead of the distributed library.

@Gj I love the idea of code completion for the wicket ids. One suggestion regarding this & if you already intended this just ingore: allow for this to work in both the java and html files: that would be awesome.

Wicket development with Netbeans is incredible & I've managed to convert my coworkers to switch to Netbeans from Eclipse and not just for Wicket related projects but for most of our Java related projects and tasks as well. It didn't take much arm twisting either as my coworkers were easily able to do a side by side comparison of both IDEs and come to their own conclusions.

Life is way too short to have to work with mismatched tools and NetBeans just rocks!

Jeff

Great job !

After some usage, I would suggest you some enhancements:
- My first point is that the plugin does not consider the case of html files located into the resources folder of project, as Maven does. So I made a patch (which is still in test on my side) to take this case into account. If my patch works I will submit to you so you can integrate it officially if you like.
- My second point is about a more difficult part: the parsing of html and java, and the detection of problems. Well, i would say that it doesn't seem to work very well on my side, maybe due to the fact that my wicketIds are not used in the same order in the markup and in the java. I tried to look at it, but I don't know where to start, as I don't understand what part is problematic: parsing of html/java ? or finding difference (TreeDiff.java). So, do you have any suggestions for me about how debugging that part (I'm novice into developing Netbeans platform), and testing (it would be great if we could use unit tests)
- My last point is a new feature: i would like to have an autocompletion of wicketIds on the Java part during Wicket component constructor use, displaying the components available on the HTML side. The opposite would be great too (on HTML, autocomplete with ids used in the Java).

Thank you, Geertjan and I was afraid you'd say that lol.

Yes, absolutely - if anyone else is developing using Mac OS and having a similar problem please share here so that we can gather momentum to have the issue addressed.

Jeff

Hi Geertjan,

Jeff here. My company has a mixed environment of Windows & Mac development computers. Netbeans 7 with the Wicket plugin on Windows works perfectly but when we install the plugin on Mac OS we are running into issues: The install works but when we restart Netbeans 7 after installing the plugin we lose all Java EE features in Netbeans 7. We've tried this with 2 Mac OS machines and both had the same problem. Are there any known issues with Netbeans 7 for Mac OS and the Wicket plugin? Thanks in advance for any assistance.

Jeff

A semi-experimental feature, hope you'll all like it, feedback on the concept is welcome:

http://blogs.oracle.com/geertjan/entry/visual_wicket_parsing

Created a solution enabling multiple Wicket versions to be supported by the NetBeans Wicket plugin in a loosely coupled way:

http://blogs.oracle.com/geertjan/entry/modular_wicket_versioning

http://netbeans.dzone.com/how-2-contribute-samples-2-nbwicketsupport

Hi geertjan,
I'm very interesting in this wicket plug-in project. As I remember this project is open source, but it is missing at original web site. Would you mind tell me what happen to it?

Thanks,
Charles

It is going to be hard to keep up with the Wicket point releases; version 4 has seen 17. What I do is when there is a new release I just copy the new jars into the Wicket library that the plugin installed and from that point on whenever I generate a new application it will have the latest jars.

But if you want to update the library sure, update it with the jars from the 4.17 release.

One suggestion, Geertjan, and I hope you don't mind but when you package the jars into the library can you also include the wicket-ioc jar? If you can that would make using some of the wicket-stuff add on libraries easier as some of them require it like javaee-inject, for instance.

Jeff

The current version of Wicket is at 4.17, while there is also a version 5 RC 3. Can anyone give guidance on which version the NetBeans Wicket plugin (which currently bundles Wicket version 4.10) should support?

I am also planning to include a large set of samples in the NetBeans Wicket plugin, to help newbies get up and started very quickly. Thoughts on this?

Geertjan,

I just sent you what you requested. Please let me know if there anything else I can do.

Jeff

NetBeansWicket70b.zip fixes the regressions -- i.e., now both sides of the Wicket page/component should open together again and the Frameworks panel should correctly display the fact that Wicket is included in the app. Please try it out. (Probably still some problems with Maven, would be good to identify those as precisely as possible.)

Jeff, please create a Wicket application from the template, change it to what you think it should contain (since I don't really understand your blog entry) and then ZIP up that changed template and send it to me at g_wielenga@yahoo.com and I'll use that as the basis of the starter project from NetBeansWicket70d.zip onwards.

Put your footer here

May I suggest that when generating the starter project that markup inheritance be used for BasePage. When creating a standard layout for a site one would put the header, sidebar, footer, etc. in the base page associated markup file as well as a child tag which home page would then extend. This is more 'Wickish' than just sublcassing from a markup-less class.

Not intentional, will investigate. Let me know if any other strangeness occurs.

NetBeansWicket70b.zip fixed the problem. Much thanks!

I'm using maven and wicket. When I'm enabling wicket support (via add framework) it overwrites existing stuff. This shouldn't happen.

Also a NPE is thrown: http://statistics.netbeans.org/analytics/exception.do?id=505300

Thanks a lot, it works properly.

just in case that matters, Geertjan. I haven't tried it with the other distros.

I have this problem :
Some plugins require plugin Editor Library to be installed. The plugin Editor Library is requested in version >= 1.37.0.8.2 (release version 1) but only 3.8.1.13.8 (of release version different from 1) was found. The following plugin is affected:
Wicket Support

and this pack is 15 MB but say it 10.31 MB

that was fast! I just posted last night before I went to bed. I just woke up and what a great surprise :).

Regarding Wicket popularity, here in NYC I know that a lot of high tech companies are using it, especially on new projects which makes me very happy. I preach Wicket every chance I get and blog about it often at http://jeff-schwartz.blogspot.com/ (shameless plug). Amazingly, a lot of the developers I talk to don't even know about this plugin and use Eclipse with its spartan support for Wicket. Those that I've convinced to give it a try are frequently amazed that they've been in the dark about it. But I am confident that we are getting there.

Thank you for your continued commitment and dedication to this effort.

Jeff

Like I said: "And, if massive popularity of Wicket can be proven, then the chance of this plugin being included in the standard NetBeans distribution will be significantly increased."

7.0 version of Wicket plugin is available. However, I'm having some problems uploading it into this plugin portal page at the moment. Also setting up the sources on java.net.

And, if massive popularity of Wicket can be proven, then the chance of this plugin being included in the standard NetBeans distribution will be significantly increased.

After wrighting down the whole stuff, i found the solution.

In the nb-userlibrary "Wicket" I included all jars from ~/wicket/lib.

Now I removed wicket-velocity-1.4.8.jar - and all works fine.

NetBeansWicket691c.zip adds support for Java EE 5 Maven projects in the IDE. Create a new Maven Web application, go to the Properties panel, then go to the Frameworks tab and add Wicket. Next update will be to add support for Java EE 6 (i.e., no entries in web.xml because Java EE 6 does not, by default, work with web.xml anymore.) The comment above from hantsy has also been handled.

Uploaded "NetBeansWicket691b.zip", provides support for Wicket 1.4.10 (support for sources and javadoc included too) for Ant as well as Maven projects. Change log is above on this page, under "What's New in this Version?".

My blog today summarizes the current status: http://blogs.sun.com/geertjan/entry/wicket_support_in_netbeans_ide

Could you please point me to the source code for this plugin. I would be more than willing to see what needs to be done to get this to work in 6.9

Any chance of getting this to work in Netbeans 6.9? Has anyone had any luck?

Hello

I cant install the Wicket Support plugin because I got this error:
The plug-in Editor Library is requested in version >= 1.37.0.8.2 (release version 1) but only 2.10.1.10.2 (of release version different from 1) was found. The following plug-in is affected: Wicket Support

Who says it doesn't work in 6.9? What's the error message? And what features do you want in the plugin?

Great plugin and thanks for the effort put forth. I'm going to try to run it in 6.8 and revert back to 6.7 if necessary.

geertjan,

Any news as to when we can expect an updated version of this great plug-in. Working fine in 6.8 but like to get to those additional features you talked about earlier and in your blog.

Keep up the great work and let us know

Yes, I was there, why didn't you say hi? And sorry about above tone of voice and yes a lot of development is taking place on the Wicket plugin but there are still several problems to fix before the 6.8 release (see my blog today for some rough points). So watch this space and thanks very much for the support and encouragement.

puppala, where on this page do you see anything at all about this plugin working in 6.8? Right now, 6.8 doesn't even exist, there's a Beta only. Or are you expecting that the Wicket plugin will be updated for each and every milestone build as well as the Beta? Please, wait until 6.8 is released, around that time this plugin will be upgraded too. There will be several new features (especially a palette with Wicket items that you'll be able to drag into your HTML files, with matching Java code added on the Java side automatically), so it will be worth the wait.

Just installed NetBeans 6.8 Beta and getting some exceptions from wicket plugin classes.

Hopefully Geertjan is working on this ...

:-)

I have questions regarding Templates. In sample pictures I can see 4 templates for different wicket components: Wicket Border, Wicket Page, Wicket Panel and Wicket Panel w/ Form
But in my NetBeans I can see only 2 templates: Wicket Page and Wicket Panel
I've installed 3 nbm files and when I'm looking into org-netbeans-modules-wicket-templates.jar file I can see following files:$ jar -tf org-netbeans-modules-wicket-templates.jar
META-INF/
META-INF/MANIFEST.MF
org/
org/netbeans/
org/netbeans/modules/
org/netbeans/modules/wicket/
org/netbeans/modules/wicket/templates/
org/netbeans/modules/wicket/templates/BodyBorderTemplate.html
org/netbeans/modules/wicket/templates/BodyBorderTemplate.txt
org/netbeans/modules/wicket/templates/BodyBorderTemplateDescription.html
org/netbeans/modules/wicket/templates/Bundle.properties
org/netbeans/modules/wicket/templates/FilePanel$1.class
org/netbeans/modules/wicket/templates/FilePanel.class
org/netbeans/modules/wicket/templates/FileTemplateWizardPanel.class
org/netbeans/modules/wicket/templates/FileTemplates.class
org/netbeans/modules/wicket/templates/PageTemplate.html
org/netbeans/modules/wicket/templates/PageTemplate.txt
org/netbeans/modules/wicket/templates/PageTemplateDescription.html
org/netbeans/modules/wicket/templates/PanelTemplate.html
org/netbeans/modules/wicket/templates/PanelTemplate.txt
org/netbeans/modules/wicket/templates/PanelTemplateDescription.html
org/netbeans/modules/wicket/templates/PanelWithFormTemplate.html
org/netbeans/modules/wicket/templates/PanelWithFormTemplate.txt
org/netbeans/modules/wicket/templates/PanelWithFormTemplateDescription.html
org/netbeans/modules/wicket/templates/WicketLookupProvider.class
org/netbeans/modules/wicket/templates/WicketPrivilegedTemplates.class
org/netbeans/modules/wicket/templates/layer.xml
I'd really like to use Wicket Border template. How can I take it in use?
Here's my NetBeans info:
Product Version: NetBeans IDE 6.7.1 (Build 200907230233)
Java: 1.5.0_20; Java HotSpot(TM) Client VM 1.5.0_20-141
System: Mac OS X version 10.5.8 running on i386; MacRoman; en_US (nb)
and I've installed latest wicket-support-plugin from 1250804142217_Wicket4NB67-3.zip

i just want to say a " BIG THANK YOU " to all the commiters of this wicket plugins...

Pleasure, Jeff. :-) Feedback welcome. Also on the start of the new palette for Wicket components:

http://blogs.sun.com/geertjan/entry/wicket_components_in_netbeans_html

There may need to be a pinky wrestle between you all:

http://blogs.sun.com/geertjan/entry/navigation_for_related_wicket_artifacts

Read all about it here:

http://blogs.sun.com/geertjan/entry/updates_for_wicket_plugin_in

geertjan,

Thank you, geertjan. I know that I can delete the plugin's included libraries and add the most recent ones but I am not concerned about myself. Rather, I am thinking about novice Netbeans users and Wicket developers who might not know how to do that.

You might not know but I am striving to make Wicket the preeminent Java Web framework and anything that can entice new developers to the fold will be very helpful. It is my belief that once a developer sees how easy it is to use Wicket to create feature-rich Web applications they will be sold on the framework.

Sincerely,
Jeff
http://jeff-schwartz.blogspot.com/

Hi geertjan,

Yes, as you know Wicket v1.4 has been released so the Wicket JARs in the plugin need to be updated similarly.

Also, do you have any idea as to when the 2 issues I previously identified (safe removal of non java files from project and deploy on changes to non java files) will be addressed?

Thank you in advance.

Jeff

Hi jatco, do you only mean that the Wicket JARs in the plugin should be updated? Or something/s else?

Any time frame in mind for updating the libraries in the plugin to Wicket v1.4?

Jeff

It also works with GlassFish v3. I noticed that about 2.1, but didn't know why. Do you?

The generated web.xml does not work with glassfish 2.1 (it works with Tomcat)? Is this a known issue?

Geertjan,

I will file the 2 issues I previously reported as you requested at http://nbwicketsupport.dev.java.net/ and hopefully they will be addressed as soon as possible which will go to make Netbeans an even better development platform for us Wicket developers. Thanks again.

Jeff

http://blogs.sun.com/geertjan/entry/wicket_support_for_maven_projects

just wanted to add that I have installed the plugin and ported my project to 6.7 and all works as expected.

Thanks for the effort

I created a new project with it and I was able to deploy to Glassfish v2.1 with no problem.

As a future enhancement :) perhaps you can include the option of setting the default DOCTYPE that is generated for html files. This could could be done at the project level or at the time the html file is created.

I did notice the following issuess which might be related more to the IDE than to the plugin but I thought I'd bring them to your attention anyway and perhaps get your feedback as to what is the best way to get these addressed:

1) Changes to html files as well as resources in java packages do not trigger a build and deployment to the server.

2) html files as well as resources which reside side-by-side with java files in java packages have no facility for "safely" deleting them as there is for java files.

Shameless Plug - On my blog at http://jeff-schwartz.blogspot.com/ I have numerous Netbeans/Wicket related articles with the latest one about using Wicket, Netbeans, EJBs and Dependency
Injection in a Java EE5 enterprise application container such as GlassFish.

hantsy, please follow the tutorial listed in the plugin's description. Then, tell me where the problem occurs, i.e., in which step in the tutorial. Otherwise, I cannot reproduce your problem.

Any comments at all (good/neutral/bad) is more than welcome, especially from those who have been clamoring for this update. :-)

http://blogs.sun.com/geertjan/entry/wicket_plugin_ready_for_netbeans

I would like to join other users and express my appreciation for this plugin. I would also like to join other users and ask you to post an update on when you are planning to port Wicket plugin to Netbeans 6.7.

We just need to know what and when to expect so that we can plan our development accordingly.

Thank you, geertjan.

I couldn't install the plugin 'cause i got the following error message:

Warning: Could not install some modules:
Wicket support - the module named org.netbeans.modules.editor.deprecated.pre61completion/0 was needed and not found.

Is there any solution for this error?

I don't know what "installed 6.7 (latest release)" means. Right now, 6.7 doesn't exist. There's only daily builds, a Beta, and upcoming release candidates. I am definitely not planning to create a new release of the Wicket support for each of these. However, there will definitely be a full update for the Wicket plugin once 6.7 is officially released.

The last time I tried installing the plugin it failed under 6.7 indicating that some compatibility module was missing.

I will ty again and let you know.

Now that the next release is close to becoming a reality are you planning to update the Wicket plugin.

I am trying to integrate spring into my wicket application which was create with this plugin. I added the following to my web.xml file:


MyApplication

org.apache.wicket.protocol.http.WicketFilter

applicationFactoryClassName
org.apache.wicket.spring.SpringWebApplicationFactory

When I run the application I get the following error:

org.apache.wicket.protocol.http.WebApplicationFactoryCreationException: Unable to create application factory of class org.apache.wicket.spring.SpringWebApplicationFactory
at org.apache.wicket.protocol.http.WicketFilter.getApplicationFactory(WicketFilter.java:1014)
at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:663)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:262)
at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:375)
at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:119)
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4497)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5343)
at com.sun.enterprise.web.WebModule.start(WebModule.java:456)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:922)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:906)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:696)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:2205)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1890)
at com.sun.enterprise.web.WebApplication.start(WebApplication.java:85)
at com.sun.enterprise.v3.server.ApplicationLifecycle.start(ApplicationLifecycle.java:560)
at com.sun.enterprise.v3.server.ApplicationLifecycle.start(ApplicationLifecycle.java:547)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:189)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:329)
at com.sun.enterprise.v3.admin.CommandRunner$2.execute(CommandRunner.java:302)
at com.sun.enterprise.v3.admin.CommandRunner.doCommand(CommandRunner.java:312)
at com.sun.enterprise.v3.admin.CommandRunner.doCommand(CommandRunner.java:119)
at com.sun.enterprise.v3.admin.CommandRunner.doCommand(CommandRunner.java:99)
at org.glassfish.deployment.admin.ReDeployCommand.execute(ReDeployCommand.java:94)
at com.sun.enterprise.v3.admin.CommandRunner$2.execute(CommandRunner.java:302)
at com.sun.enterprise.v3.admin.CommandRunner.doCommand(CommandRunner.java:312)
at com.sun.enterprise.v3.admin.CommandRunner.doCommand(CommandRunner.java:119)
at com.sun.enterprise.v3.admin.CommandRunner.doCommand(CommandRunner.java:99)
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:250)
at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:176)
at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:147)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:180)
at com.sun.grizzly.http.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:633)
at com.sun.grizzly.http.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:570)
at com.sun.grizzly.http.DefaultProcessorTask.process(DefaultProcessorTask.java:827)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:152)
at com.sun.enterprise.v3.services.impl.GlassfishProtocolChain.executeProtocolFilter(GlassfishProtocolChain.java:71)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:67)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:56)
at com.sun.grizzly.util.WorkerThreadImpl.processTask(WorkerThreadImpl.java:325)
at com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:184)
Caused by: java.lang.ClassNotFoundException: org.apache.wicket.spring.SpringWebApplicationFactory
at org.glassfish.web.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1509)
at org.apache.wicket.protocol.http.WicketFilter.getApplicationFactory(WicketFilter.java:1000)
... 42 more


I checked for org.apache.wicket.spring in the jars but I cannot find it. Is it missing or am I doing something else wrong?

Thanks in advance.

Jeff

I like the plugin while it's getting me started fast. But sadly I run in trouble when using a webservice via JAX-RPC. After import of the WSDL file, the project doesn't compile anymore with the error:
wscompile-init:
WebApplication1/nbproject/build-impl.xml:367: taskdef class com.sun.xml.rpc.tools.ant.Wscompile cannot be found
This problem doesn't occure with i.e. a normal Java Desktop Application project and adding the same webservice. Does someone know a solution or workaround. The libraries for JAX-RPC are added (automatically) in both cases.

Do you expect me to test this plugin whenever a new development build is released? I.e., every day? This plugin is for 6.5 final release. If it works in anything after that, then that's nice but unintended.

The sources and javadocs for all releases are in http://repo2.maven.org/maven2/org/apache/wicket/wicket/, in my humble opinion, the binaries, sources and javadocs (and perhaps some dependencies like slf4j) could be provided as a library module, and the project support would depend on that library. If you feel this approach is better, I can build the library modules.

Yes, the Sources tab contains the 1.3 sources JAR. I couldn't find the 1.4RC1 sources JAR. Maybe better would have been for me to remove the 1.3 sources JAR in that case. What do you think? Happy to fix this, your choice how I do so.

Just install this one. Do not install another one. Do not go somewhere else. Just do this: Click the Download button that you see on this page. Not on another page. This page. This page, right here. Go on, click it. You will have "1.4" in the name of the ZIP that you download.

This plugin definitely saves time when you're new to Wicket and just want to get something up and running. I found it very useful.

Those features were never supported, tprochazka. You are welcome to join the project and add them!

I cannot download this plugin for some reason is there something with the link ?

Yes you are right does work i tried download on a different computer and it downloaded , on my main computer i use Free download manager and for some reason would not allow. Thanks.




Installed plugin ok netbeans 6.1 so far everything working except example login application it loads in browser but link to login throws exception as well as change password. Any info on this ?

The download file is different from the one listed in the plugin manager?
I downloaded the file directly , and add them to install , It works.

Plug-in works just fine in NB 6.1.
For those who like to start with wicket, here are another good resources:
http://wicketstuff.org/wicket13/
http://www.nabble.com/ - discussion forums

After updating the latest patch for nb6.1 , this plugin is down

Also you can check out the Wicket Wiki, http://cwiki.apache.org/WICKET/.

Hi,
Many thanks for this smart plugin ;).
Just one thing: why doesn't it use Wicket Filter instead of the Servlet ? I think that the Filter (introduced in Wicket 1.3) is a much better choice.

Cheers,

Great plugin, thanks! Keep up this good work!

mike

1.3 final is out can we get the library updated here as well.
Thanks
Steve

Installed the plugin in Netbeans 6 Beta 1, works perfectly! thanks all of you! keep up the good work....