The way systems (Wiki) fail, will it change with Seam 3 and JSF 2.0

[luxspes]

Today, for the second time, I lost a post.

There use to be a forum to discuss issues with this site... it no longer exists...

But that is, of course, not relevant as a post in this forum...

Except for one reason:

It is an example of the way systems fail with JSF/Seam:

I wrote medium sized a post (it took me around 15 minutes, it was an answer and it is hard to get the Wiki Text Markup correctly between the blockquotes).

I click Save...

And I am greeted with this error page.

After that I clicked the back button of my browser... but it was useless, my message was gone.

Now, this is typical of web pages, nothing new with that... except because I had a similar experience with a system developed where I work (by someone else), and it
did not lost my data... what fancy technology did it use? raw JSP to produce XML files that are read using raw XMLHttpRequest... and JavaScript that only works in IE6.
What? No fancy JSF? No fancy AJAX remoting framework? and still did not loose your data? How is that possible? You may ask...

Well it turns it is really simple! The code that sends data in the system developed  by this coworker sends the data using javascript, so handling a failure in the server is as
easy as writing a try{}catch{} that means that by default, with this very primitive way of doing AJAX his application is more robust than a JSF application like this Wiki...

If that is not a really serious indicator that JSF has a serious abstraction leak... then... why did this site lost my post? what would it take to modify its source
so that it is resilient against simple errors such as JBSEAM-4171? Remember I am not asking here for fancy Google Gears like functionality, all I want is a chance to push the submit button again...

Is that too much to ask?

[fuzzy333]

I feel your pain. Try using Chrome, it reacts a little better to this kind of thing (accidentally pressed the back button? click forward, cross your fingers, HAHA I EAT YOUR POST TEXT FOOL! not with Chrome). I never write long text in any other browser anymore specifically because of this.

[asookazian]

If I start writing a long(er) thread/post in this particular forum, I sometimes copy the text to textpad as manual backup.  That's why I like gmail, it auto-saves drafts of your emails for you.

[jamesjmp]

Sometimes I´ve suffered this, and I usually copy drafts to wordpad to avoid wasting time. Anyway, Francisco, I agree with you that the forum regarding wiki issues should be enabled and that what you are suggesting is not too much to ask for.