[tvalletta]

It seems like many people are interested in the same features that I am. Of some of the big ones that I see mentioned I would just like to see which one people think is the most important. This is just me asking a question (I want it all).

Of course I am going to miss some things. Write-ins are welcome.

[Paul]

Isn’t JSF support already present? I don’t use them yet, so don’t know its maturity. I’d like to see Spring support though. I’d also like to see iBatis support added, though I suspect its smaller user base is working against that.

[Kurtis Williams]

The most important feature I can think of is the “multiple deployments for one web server” feature that’s been oft requested. I develop using exploded archives and desperately need a way to package up the WAR on the fly, whenever I need one. I used to use JBuilder and miss being able to simply right-click on the Web app and generate a WAR with exactly the same configuration as the exploded app.

[arjan.tijms]

At the moment, the most important ‘feature’ I can think of is increased stability and bug fixes. This really should outweigh any other feature.

[nupstone]

I second the support for ibatis DAO and SQLMaps. Integration between them would be great.

I have a suspicion that I can use Ibatis DAO with Hibernate…. [reads docs] … YES. There is a Hibernate Transaction Manager imlementation, so PRIORITY would be to get DAO integration done first. (now I’m off to investigate Hibernate :O]

Also, I’m relatively new to struts, and am finding the pattern used in Ibatis’ jPetstore demo very useful. There has been talk of this being standardised. It would be excellent to have that supported. i.e. Struts action has type com.ibatis.struts.BeanAction, and the action name maps to that method on the bean.

[Ronald van Kuijk]

I agree with Arjan, stability should be the first feature. But after that should come better xdoclet support. I’ve made a two page document (for some of our developers) what to do if they start a new project and want to have it configured so that they can use xdoclet as much as possible. Part of this document is how to remove the results of the servlet wizzard and change it to implement use xdoclet tags.

[Riyad Kalla]

Guys I added a new option and made this sticky, good poll BTW.

[Ronald van Kuijk]

isn’t bugfixing also an ‘enhancment’ of an existing feature 😀

[Riyad Kalla]

I didn’t want users to get confused between enhancements (add the ability to XYZ) and bug fixes (make sure ABC stops crashing). If you think this is confusing, I’m happy to remove it.

[augustientje]

Bugfixing and enhancing an existing feature are indeed quite close. Thinking of what enhancing really means. Adding new ‘features’ to a feature? Maybe. Or does it mean, making it faster, more stable, having it consume less memory?

Maybe you could keep the enhancement and bug fix options, but threat the results simular: people like what’s in myeclipse right now and want that to function really good (again). If that goal is (internally, at your development team) reached by something you would qualify as bug-fixing or enhancement is maybe of lesser importance to us end-users.

Totally new features are always nice, but not at the expense of the current core functionality.

[Ronald van Kuijk]

@support-rkalla wrote:

I didn’t want users to get confused between enhancements (add the ability to XYZ) and bug fixes (make sure ABC stops crashing). If you think this is confusing, I’m happy to remove it.

No, I was just kidding, but the smiley didn’t get trough..

otoh, in what category does my xdoclet ‘request’ go? It’s not that I’d like a new XYZ feature, or more stability for ABC, I’d like more of JKL:-)

Just keep up the good work.

[Riyad Kalla]

Haha, I should add XYZ, ABC and JKL to the poll, that will clear things up!

[Rob Monie]

I’d really like to see the existing hibernate / DB Explorer support enhanced. As I see it now there are many features missing from the generation of hibernate code from database tables and it certainly isn’t close to “round trip” capable. Also i’d love to see Spring supported in this area so I can safely restructure my spring / hibernate / struts config files and myEclipse be aware of how they all fit together. Because i’m using Spring IoC to wire my app up, few of the myEclipse RAD features work anymore…. or am I missing something there. I’m loving where myEclipse is going and how quickly it’s got where it is but improvements in these areas would make it pretty impossible to beat in my opinion.

[George L. Smith]

I would like to see the addition of a visual view editor for Java Server Faces. I know it’s not difficult to hand edit the jsp code for the page, but why should I have to do that when Visual Studio has the ability to visually create their forms and play with the component properties in a properties editor. I should be able to drag and drop available JSF UIComponents onto the JSF view.

It seems to me to be one of the only things that we can’t do in JSF today that the .Net folks are able to do.

With JSF reaching a standards level now, there is no reason not to be able to do this. Of course my exception is that I have neither the time nor the expertise to create the visual editor… I’m a java back end guy…

[tikop]

For me the next major feature should be a visual editor that supports JSP and JSF, not only HTML.

[Author]

Posts