Is there any existing Wicket plugin for Eclipse out there? I thought I remember Wicket Bench or something from a while ago, but think that died?

I know there is some support in NetBeans, but I'm curious about the tooling setup in general around Wicket... that's usually the #1 factor that contributes (or detracts) from a framework getting adopted en-mass across a market.

I'm not familiar with the NetBeans wicket support but I know that there is some. I think NetBeans understands the maven pom created by the quickstart archetype and automatically creates the project from that. Looking at a tutorial it looks like the wicket plugin also provides for creating new projects, pages, panels, etc.

Wicket Bench is still available and works with eclipse 3.3. It doesn't seem to be very active though. It has some basic templates for creating a project, panel or web page. If the java file is opened using the wicket editor it opens the other associated files (html, prop, xml) in tabs along with a preview tab. AFAIK that's about all the plugin does. I'm currently working on wicket projects in another eclipse installation but would certainly like to see the features mentioned by zambizzi supported by myelipse which I would immediately begin using. I would add to that list maven support so the standard wicket project layout structure could be used.

Jim

Jim,
We are actually working on Maven support (http://www.jroller.com/myeclipseblog/entry/myeclipse_what_have_we_been) but I was a bit confused by the "standard wicket project layout" support you mentioned... the times I've used Wicket, I've just used a straight web project with no issues... is there some other constructs in Wicket I'm not aware of that you can't achieve with ME now?

Hi Riyad,

What I meant was that almost all of the wicket projects I've looked at use maven pom's and the project layouts used are not the same as you get when creating a web project from eclipse. I assume the folder structure is standard Maven layout but I'm not too familiar with Maven yet. If you create a quickstart project using maven, the generated structure is typically something like the following:

projectname
....src
........main
............java
................com .....
............resources
................META-INF
............webapp
................WEB-INF
........test
............java
................com ....
....target
........classes

Also when you use maven to create the eclipse project, the library files will point to jar files in the maven repository as specified by the version dependencies in the pom and not to local jar files in a lib folder. I've found that using the maven dependency mechanism makes it very easy to update the project to automatically use newer versions of dependent jar files.

Obviously if one just wanted to use the wicket framework with ME today, it could be done by simply including the jar files in the lib folder in a standard web project. Given the "standard" wicket project structure I'm sure ME could also be tweaked to deal with it but I haven't attempted to do so.

Jim

Jim,
Thanks for the clarification. Yes that's a standard maven layout.

I must say that I have not been using ME lately, simply because of the lack of wicket support. More and more of the development I do is with it, and I would love to move back to ME.

Bruce.

Bruce, what IDE are you using that provides Wicket support? What features would you need to see to come back to MyEclipse?

+1 fro wicket

I vote for this feature.

+1 for me.

+1 for me.

-1 for me. There is a place for alternative frameworks, but unless they are *very* popular (like e.g. Spring or Seam), people using such alternatives could of course look at an alternative plug-in too. I just don't feel that Wicket has the momentum (yet). Devoting time to Wicket means the MyEclipse developers can't devote time to other pressing issues, on which many more people are waiting.

Henk, actually I falled back from MyEclipse to Eclipse EE due to the fact it couldn't work together with JBoss Tools and there is no MyEclipse support for Seam. So Seam isn't a priority for MyEclipse team either. Somewhere you're probably right. But in fact they lose my money.

I could return to MyEclipse when it supports Wicket. Just support of editing pages and placing components onto it.Something like maticce but simplier.

Wicket Bench does not much to be useful.

I would second any request for wicket.

I think having the ability to create & deploy Wicket applications via MyEclipse would definitely help me justify the subscription cost.