Gliffy

Looks like struts isn't configured to handle error case correctly for requests with no params.

@400000004751a7e125a2644c 2007-12-01 12:28:39,630 WARN [resin-tcp-connection-j2ee.wiki.gliffy.com:6802-23] [apache.struts.action.ActionMapping] findForward Unable to find 'errorCaught' forward.
@400000004751a8061bf084ec 2007-12-01 12:29:16,468 ERROR [resin-tcp-connection-j2ee.wiki.gliffy.com:6802-17] [core.action.client.ClientSaveDiagramAction] logThrowable Throwable caught...
@400000004751a8061bf0948c Thrown object:java.lang.NullPointerException
@400000004751a8061bf09874 Short Description:java.lang.NullPointerException
@400000004751a8061bf0a044 Message:null
@400000004751a8061bf0a42c Stack trace:

Logging out in another tab while editing a diagram produces a similar situation. However testing this with confluences own editor also causes changes to be lost in this situation.

Is there some way that the front end can be changed so that it doesn't redirect to the viewing page if it detects a failure to save the diagram? Also if we could push the error message from the server into the front end as well as the general contact support message that might give the user a better idea of what has gone on.

The saving grace for the confluence editor when this happens is that confluence now has a feature to save drafts of pages as you edit them, perhaps gliffy could also add this feature. (I'm not sure where the temp draft data would get saved in confluence, page properties possibly?)

Saving draft content is a bigger issue that I'd like to put off for now. (We're going to implement real time collaboration on the hosted application which will include auto-save, and we'll likely solve the draft problem using something similar)

I guess I was hoping there would be a way to detect that the session has timed out. I noticed that there does seem to be Ajax support built into Confluence... I wonder if there is a way to detect the session timed out through that? If we can figure out a request that can tell us that the session has timed out, we could certainly handle this on the client.

Can you please check into this possibility?

This has been fixed by:

1) If a user tries to save a diagram and does not have permissions, we handle this error more gracefully
2) A message specific to the Confluence integration tells users that they likely had a session timeout, and they should log back in to save their work.