Alexander Jesse

Originally posted by Chris Schalk:
Try them both?

Good idea... your book is available as a eBook? (That's one advantage of Kito Manns "JSF in Action" ;) )

Originally posted by Ed Burns:
Well, naturally we hope you buy the book, but just in case you don't my opinion of the IDEs that support JSF the best are, in decreasing order of quality of support.

Sun JavaStudio Creator
Exadel Studio
Oracle JDeveloper
NetBeans 5
Eclipse

add: MyEclipseIDE and Weblogic Workshop (former NitroX)

about the order one can always quarel ;)

Put it that way:
if you are the Netbeans-type go for JavaStudioCreator
if you are the Eclipse-kind of developer go for Exadel
if you are the point-and-click type JavaStudioCreator of Rational-products are better
if you like to see (and understand) the "real" sourcecode Exadel and MyEclipse are for you

regards
Alexander

Originally posted by Chris Schalk:
The book covers JSF 1.2 throughout the book, but it is primarily geared towards 1.1 development since that is the level most people are working with.

I'm not aware of any production IDEs that currently support 1.2. Servers are now starting to support it though.. glassfish is an example of this.

https://glassfish.dev.java.net/
-Chris

Well Exadel 4.0 also can help with JSF 1.2... Even has a setup for JSF 1.2, facelets on Tomcat 5.5

regards
Alexander

JSF is a specification controlled by the JCP.

JSF-RI (RI == Reference Implementation) is Sun's JSF-implementation and everything else than dead. Right now it's the only implementation that is on the JSF 1.2 level.

MyFaces is an Apache Project delivering some items:
- MyFaces JSF implementation
- Tomahawk component library
- Tobago a donated (now opensource) component library
- Trinidad, parts of Oracle's ADF-Faces which have been opensourced

hth
Alexander

I ordered it on amazon.de some time ago, and am happy with the book.

Well using the forum search (To the right of the moose.... there is a search link) I found that within the last 30 days we had this thread... asking for the same information. Maybe it helps you too.

JavaRanch Thread: Suggest good book for JSF

hth
Alexander

Do not use a forward in the index.jsp, try with a redirect.

Why?

index.jsp usually is not called with the faces-lifecycle and a forward can be considered just a "method-call". That's why inputname.faces is missing its needed faces-lifecycle.

hth
Alexander

what URL are you using to call this index.jsp?

If it is "..../index.jsp", then the JSF-lifecycle is not entered, and all JSF-tags cough up.
If it is "..../index.jsf" then the lifecycle is not entered because the web.xml has the not corresponding mapping...

If it is "..../faces/index.jsp" then the lifecycle is entered and therefor the message should not be shown.

hth
Alexander
[ May 15, 2006: Message edited by: Alexander Jesse ]

1st: check out what is blocking you: memory or cpu or data transfer

2nd if memory:
- there is a parameter (web.xml - context param) to control the number of saved views (if you use server-state), don't know its name right now
- check what your app packs into the session!!!

2nd if cpu:
- using client-state? if your memory is no problem, you might consider switching to server-state
- test using MyFaces (tests with the "non-lates" RI showed an advantage for MyFaces in terms of processing time, but YMMV)

2nd if data transfer:
- would AJAX be a solution? But be aware, AJAX means the damned old Javascript again

hth
Alexander

The controller (as known eg within Struts) is not existant in JSF. You call a managedbean-method which does the usecase-work and then returns the navigation-outcome.

The navigation-outcome can point to different result-pages in dependance from the source-page...

Isolate your db-accesses into a service-layer. Each service concentrating on one business-object.

For Cross-object-boundary functionality, write facade-objects.

Objects that travel the layer-boundaries are DTO's (DataTransferObjects).

From your managed beans access either
pure: only facade-objects (needs a few more)
mixed: facade-objects and services

How to find the services? Either use a service-lookup facility or use Spring.

hth
Alexander

Originally posted by Sergey Smirnov:
BTW, Weblets is a name for the IBM's alphawork project ( http://www.alphaworks.ibm.com/aw.nsf/html/weblets ) . Are you OK with such naming conflict?

Looking at that links it seems a quite dead project... the site reads: "comming soon in january" and further down: "will be posted in januarry 2000"...

Originally posted by John Fallows:
Yes, we already have received messages on the Weblets user mailing list from folks using Weblets to server JAR-packaged resources in a non-JSF environment.

Kind Regards.

Cool... I'll check there.
Maybe we can use that stuff inhouse here...

Following up on weblets:
Have you made tests in a non-JSF-environment?
I think that it's idea might solve problems that lots of web-applications have, as soon as they must be deployed using automated procedures...

Possible alternatives are:
- AJAX (a security nightmare, as it is based on Javascript)
- Javascript pure (sort of AJAX do-it-yourself)
- Eclipse RCP-application using webservices or remote-EJB to communicate with the backend
- Java-Applet (doing your own protocol for backend-access)