JSF support

Hi there,

just a good advice from me on the JSF support you are planning: try to get the syntactical sugar up and running as soon as possible (particularly: understanding the faces-config.xml, code-complete for managed beans) and postpone the WYSIWYG stuff to a later date. More important right now is the notional help!!!!!

regards,

Martin

7 comments
Comment actions Permalink

I had a big long post, but I'm tired so it rambled. Basically, I agree with this post. I've been evaling a couple JSF editors, and I think the following is very useful (mostly from Exadel)

1) Visual navigation/page mapping screen (hooked into the faces-config.xml)
2) Some type of editor for the faces-config.xml file (like the faces console thing, but a little more)
3) Templates for jsf input controls and constructs

jtext (tab)

<h:inputText ...

4) Code completion for the jsf el.

the last one to me is the big one (tied into the templates, which is doable now). I know general el support is tough because things are not strictly typed. If you don't know what type you're actually working with, how can you show properties? I think the jsf el will be easier. You should be able to get at the config file(s) and figure the managed bean types. After that, I think you're good, right?

I mean, am I going to buy my license of idea 5? Probably, but only because I've been a long time user. Its a tough call though. I still use version 3. I own a copy of 4, but I didn't like it much. Its got more stuff, but its more complicated in a way I didn't jive with. I run a group at my "day job", and we own v4 licenses for everybody, but we're still using 3. I'm personally moving my stuff to version 5, but I don't know if/when we're going to be doing that at the office. I've been averse to auto-deployment features and the like, which I think is why I stuck with version 3. What I really want is stuff like the above.

Personally, if the above jsf stuff was in v5 I'd already have bought it and uninstalled Exadel, Nitro, and (gag) myEclipse evals*.

Speaking of version 3 and the auto-deploy, the reason I personally stayed on 3 was that it didn't try to do too much for me from a deploy perspective. I really was anti-4 when I set up a webapp and it took me a long time to figure out it was inserting my libraries and everything into the package (which I found to be very, very annoying). I think you have a large group of developers like myself who really don't want that stuff. I'll lay out my sources, write my ant scripts, handle deployments manually, etc. I'll copy my jars into the lib directory if I want them there, or somewhere else if that makes more sense. I guess that's what I like and miss about version 3. Also: compile to sources and include classpath in ant script checkbox. Maybe not "proper", but darn convenient. Rant over.

JSF. Auto-complete the el from managed beans. Good stuff.

  • No offense to the myEclipse people. I'm sure everything else is ok, but the JSF is horrible.

0
Comment actions Permalink

Replying to myself. Hmm, lame. Anyway, to be clear, I think if you're using something like IDEA you're probably not in the market for a visual html editor. JSF is partly designed to be RAD visual editor capable. To me, that's ok, but not as important as the effort required to build a really, really good one. A crappy one just ins't worth opening (see myEclipse JSF support for an example).

I think bang for buck, the managed bean introspection and jsf completion coupled with code templates would be a great start. A competent coder would be at least as productive with that as somebody with a visual editor. Probably significantly more so.

0
Comment actions Permalink

Well, another no offense to the MyEclipse people, but the Hibernate support sucked as well. It took me like a day to generate my Java classes from the database, due to the unintuitive interface. Brrr...

I am sure everything else is ok, though !

regards,

Martin

0
Comment actions Permalink

Exactly my point.

If you write a visual editor for JSF, write a really great one. If you do that, you probably need to burn money like hell for that tool.

But - it is not really necessary. If you help us coding JSF like you help us coding everything else, we are satisfied.

regards,

Martin

0
Comment actions Permalink

The developer api includes some facility to add programming languages. Anybody know much about this feature? Any way to maybe extend what's in the jsp editor to add some auto-complete for jsf?

0
Comment actions Permalink

I think the latest EAP build contains a document pertaining to adding a
plugin to support other languages.

Kevin Galligan wrote:

>The developer api includes some facility to add programming languages. Anybody know much about this feature? Any way to maybe extend what's in the jsp editor to add some auto-complete for jsf?

>

0
Comment actions Permalink

Hello all,

Well I am going to stick my 2 pence worth in...

I would like to see a visual JSF editor. I find it very useful that it could create the jsp, the backing beans and all the xml files to go with it. I would also like to see a visual representation of the navigation.

Has anyone seen the EA release of Sun's Java Creator? The GUI in that is quite good (pity about the rest though). Something along those lines as a plug in to IntelliJ would be great.


Regards,

KM.

0

Please sign in to leave a comment.