WE NEED JSF SUPPORT TO BE ABLE TO STAY WITH INTELLIJ

Visiting JavaOne, one things becomes very clear: JSF is happening and will become the predominant web-technology for some years to come.

IntelliJ has for some years now been setting the standard for Java IDE's. Arguably IntelliJ is THE best Java IDE around and has always been the most innovative in its class in many, many very subtle ways that most people simply just overlook.

However, I think a lot of developers are going to consider other IDE's simply for their JSF support. I played around with some of the other IDE's and although none of them is anywhere near as good as IntelliJ, the JSF showcases are very compelling.

Forget Visual Fabriek (!!!), developers and companies want standards based solutions and not some proprietary framework. Without innovative JSF support like WYSIWYG drag'n drop, IntelliJ will very soon and very quickly lose marketshare to other IDE's.

Now GO get me some JSF support with the same innovative features that you guys are good at!!

38 comments
Comment actions Permalink

I would buy into a palette of fields you can put in, much like in the UI
designer, but you would:

1- write some html
2- get to the spot where you want to insert a text box or a label or
what ever
3- double click in the palette to insert what you need at that point
4- idea inserts the tag, in text not visual, and you fill in the values.

I can see that being time saving, especially if you can assign key
strokes to insert elements on the page.

Anyway, so you're all threatening to leave IDEA if you don't get JSF
support? Why don't you go sit in the corner with the AOP quitters, file
your JIRA requests, and plot out just what you WANT for JSF support
within IDEA.


:) and they're still sitting there pouting not offering any advice
(pun intended) on how to implement it :)

R

0
Comment actions Permalink

Forget JSF. Check out something like Echo + Echopoint for web development. We have compared project development speeds in house between Echo and standards based JSP/HTML/Taglibs. Forget it. Echo development blows them away - several weeks at a time, almost 2 months in one case.

Ive not seen a single project that absolutely must have JSF. Come to think of it, Ive not seen a single project, ever, that absolutely must use framework/standard XYZ. There is always more than way. Get over it.

As a developer, I dont honestly care about what framework/standard Im using - just get the job done.
Move on.

Drag and drop layout works real well in VB, C++ Builder and Delphi. Java's layout system just doesnt work that way. The web certainly doesnt.

0
Comment actions Permalink

Ok, here my feedback (me also being very disappointed that JSF support was first promised and then ticked off the list):

1) I want no WYSIWYG support, forget it. Your swing GUI builder was the only disappointment I ever had mit IntelliJ, so don't even waste money on something like that ;)

2) I want full support for the configuration of JSF: e.g. if I define a managed bean, I want to be able to choose from any of the classes of the project

I want support for refactoring: e.g.: if a method name changes, I want the action, actionListener and value bindings of JSF to change as well.

If a JSP page name changes, I want the corresponding navigation rules to change as well.

If I enter a new valueBinding in the JSF file, I want code complete to work.

Finally, I want the same support as in JSP and HTML for CSS etc (the IDE should know, e.g. that a style class is bound to the tag by using the attribute 'styleClass')

0
Comment actions Permalink

In general, this level of support is needed for a variety of XML formats, including Spring and Hibernate configuration files. If there were some API way of saying "files with this prefix are XML (with this schema/DTD), but they reference Java objects in this way", you could claim support for a lot of technologies very quickly.

--Dave Griffith

0
Comment actions Permalink

Yep, to me supporting DSLs embedded into XML is the next logical step in
developing the language API.

"hugo.portisch" <tinytoony@gmx.at> wrote in message
news:21700174.1123767099216.JavaMail.itn@is.intellij.net...

Ok, here my feedback (me also being very disappointed that JSF support was

first promised and then ticked off the list):
>

1) I want no WYSIWYG support, forget it. Your swing GUI builder was the

only disappointment I ever had mit IntelliJ, so don't even waste money on
something like that ;)
>

2) I want full support for the configuration of JSF: e.g. if I define a

managed bean, I want to be able to choose from any of the classes of the
project
>

I want support for refactoring: e.g.: if a method name changes, I want the

action, actionListener and value bindings of JSF to change as well.
>

If a JSP page name changes, I want the corresponding navigation rules to

change as well.
>

If I enter a new valueBinding in the JSF file, I want code complete to

work.
>

Finally, I want the same support as in JSP and HTML for CSS etc (the IDE

should know, e.g. that a style class is bound to the tag by using the
attribute 'styleClass')
>


0
Comment actions Permalink

could do that with a set of decent live templates?

0
Comment actions Permalink

But but.. that takes us all back to what servlets plus some crappy HTML-generation beans did 1997... takes us back to: Hey Billy-bob, see what happens if you change the buttons to look like the rest of the customers buttons, here, use this border style and this background.

<Billy-bob> Hold on, I have to re-compile and re-deploy.

- Don't bother. Repeat after me: DO YOU WANT FRIES WITH THAT?

0

Please sign in to leave a comment.