Why don't you give me a list of things that you think I will not be able
to do in an EGL environment.
Good idea.
--- Deep linking ---
Let's say you wanted to send an order receipt email confirmation to
customers and you wanted to provide them a link to get right to that exact
order from the email. How would you do this with EGL? JSF is HTTP POST
driven (i.e. it ignores everything after '?' in the URL). Deeplinking is
fundemental IMO.
--- Back button ---
This is one that I don't entirely understand, but am guessing it has to do
with the JSF lifecycle. Using the back button, while saving state on the
server side, will cause the user to have to click a commandLink twice for it
to successfully execute. Would you be able to publish one of your CRUD apps
on the internet so I can see if IBM's EGL has the issues I have experienced?
--- dynamic download of a file ---
You said this wasn't fair game, I disagree. Downloading files from an
online application is fundemental no matter how you slice it. Many times you
don't just want to give them deep link access to the file even it statically
exists on the filesystem.
Those are a start of some of the issues I have had with JSF.
I am sure you have heard of Matt Raible (he's on the JSF expert team among
many others). Some of his opinions of JSF match mine. Notice that both of
us still use JSF. We aren't saying that because we found flaws it is
completely useless. Instead we are critisizing the framework so people KNOW
what they are getting themselves into.
Here's a comparison Matt did this past year:
http://static.raibledesigns.com/repository/presentations/ComparingJavaWebFra
meworks-ApacheConUS2007.pdf
Let me know what you come up with concerning the above points,
Aaron Bartell
http://mowyourlawn.com
midrange.com
