I would be sad for any clients that did JSF the way it is now, since I 
think those clients will go to .NET controls soon. (Same as EJB, anyone 
who uses EJB goes to .NET ADO next year).

I am looking forward to Oct. 8th:
http://developer.java.sun.com/developer/community/chat/

I hope to hear that they will start from scratch and that 
http://www.qbizm.cz/newsletter.html was a mistake and it will do 
opposite from that.

Why JSF might not consider these comments?
Because applets provide the GUI. (Of course no one does this or should 
use Java on Client Side.) So in order to “promote” Java applets client 
side, lets not do rich GUI, since they can always do WebStart.
As a consultants I advise against applets, they are slow, hard to 
deploy, etc. etc.

What clients want for JSF is things like 
http://www.salmonllc.com/website/Jsp/vanity/Jade.jsp?nav=5
Or Koribix.com or JSTL…. But it must emit JavaScript for GUI.

Rich GUI means tags that emit JavaScript!
Maybe support XHTML so people could XSLT (on browser side XSLT to other 
formats)

What is minimum JSF could do?
Make Struts the reference application! It must be MVC (Servlets and JSP 
should have a reusable bean defined outside of JSP or Servlet – This 
should be a part of JSP and Servlet specs)
Require that a J2EE compliant editor must expand the tags like Dream 
Weaver or IBM editor do. (This way Eclipse and NetBeans will offer it).

What would be nice for JSF to do?
Provide client side controls, like .NET, (tags that emit JavaScript, 
Tree, drop down, move to from list box to list box, )

What would be even nicer?
A .NET ADO. Such as a DAO interface that JDO, and OJB (Jakarta) and 
Expresso or JDBC RowSet could implement, so people could chouse persistence.
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/src_05d/basicPortal/src/org/apache/commons/DAO/BasicDAO.java?rev=1.2&content-type=text/vnd.viewcvs-markup
 
could be implemented by most.
And then you could have a bean generator, where you enter a SQL command 
as a string and the IDE writes the getters and setters.
(Why not do this for JSF? EJB! Of course most clients throw out EJB )

OT:
I now think Sun is “gone” company and best thing for Java is that Sun 
goes away sooner. There is IBM VM, JRockit, TowerJ, many compilers like 
Jikes and open source Java.
Sun can’t sell SW and has slow HW.

I recommend clients avoid Sun HW and Sun for the good of Java.

Vic





_______________________________________________
MVC-Programmers mailing list
[EMAIL PROTECTED]
http://www.netbean.net/mailman/listinfo/mvc-programmers

Reply via email to