Darren Hartford wrote:
+1 to oracle!
Support Werner's observation of the JSF ide portion of Jdeveloper. I
have been having huge issues with JavaStudioCreator (stability, 'random'
changes, lack of component support (for myfaces of course ;-)).
Actually lack of component support was basically the biggest issue
for staying away from Studio creator from my side as well, that and
the bug issues with their form designer.
Another big minus for me was that the entire data binding code basically
was pure JDBC, which is rather contraproductive in my opinion.
So I gave it a short testrun, saw that it lacked severely on the
component side, ran into various issues by trying to make some forms so
the whole we force you to use JDBC part, and basically dropped it.
Although I really liked the basic idea behind it and also the execution
(but not the execution state)
I have been using MyEclipse and myfaces since then, and als bought
myself Exadel (which I have not used because at the time I needed it I
moved already to 3.1 Eclipsewise and my Codebase to JDK 5.0)
Jdeveloper picks up where JavaStudioCreator lacks -- just need to get
the datasources in Jdeveloper taken care of.
And, again, Oracle stepped up with JSR 276 for JSF Designtime. I am
really impressed with JSF technology, and also really impressed with the
amount of support Apache/MyFaces and now Oracle is giving it. (Tree's in
the web?? Thank you!!!).
Yes I am also very amazed, given that Oracle in the past was rather
tightlipped and hush.
My guess is, Oracle has a winner on their hands with that tool.
Not for raw coding, but for the people who really need something VB like
for creating webapps in a decent timeframe.
Face it JSF is a complex standard, and having to mess with various xml
binding files, and other nasty maintenance problems is not really that
easy (although you get used to it over time), good ides can help a lot.
After all, all this xml binding was mainly introduced to ease the life
of the tool vendors not that of the developers.
If you ever worked with a decent pageflow editor, you start to shudder
at the thought of having to do manual xml pageflows, same goes for
having to bind the backend beans to the forms yourself constantly.
