Read carefully. The first is for Session.java, the second is for Main.java.
Either make the default action a direction action and in defaultAction() return
the fully qualified name of the Main component, or, in Application override
pageForNameWithContext() (or whatever it is is called) and if
No, this is the stack trace I get:
: Exception
occurred while handling request:
java.lang.IllegalArgumentException:
Class 'Session' exists
(interface org.jabsorb.client.Session) but is not a subclass of WOSession.
[2012-2-13 18:33:34 CST] java.lang.IllegalArgumentException:
Class 'Session' ex
Is the Session class name in the stack trace correct? If it is correct, your
app .jar is missing something. If it is not correct, the _sessionClass has the
wrong signature or is in the wrong class.
Chuck
On 2012-02-13, at 4:36 PM, Ted Archibald wrote:
> I'm currently having this same issue
I'm currently having this same issue on a project I haven't touched in
months. I haven't changed wonder, nothing changed in the class path.
There's no obvious reason what's going on, and overriding _sessionClass
doesn't fix the problem, cleaning the project didn't help, restarting the
computer di
Samuel:
Just out of curiosity, are you running IE 9 in compatibility mode? This may not
effect your issue but I have gotten very different results (regarding AJAX
stuff) out of IE 9 when it is running as IE 8 (or less) compatible.
Tim Worman
UCLA GSE&IS
On Feb 13, 2012, at 10:31 AM, Samuel Pe
Hi,
The current Ajax framework has some problem with IE9. The drag and drop example
do not works, the drag does not even begin.
I suppose some javascript patch required for IE need to be disabled for IE9 but
I do not know where to look for them.
Is there someone familiar with this to fix or gi
If it happens again, try wrapping your task logic in a try/finally and put this
in the finally block as a safety net:
ERXEC.unlockAllContextsForCurrentThread();
On Feb 13, 2012, at 1:03 AM, Alexis Tual wrote:
> Looks like ERXEOGlobalIDUtilities.fetchObjectsWithGlobalIds is invol
onClickBefore was the trick... I guess I didn't read the docs properly.
thanks
On Feb 13, 2012, at 2:43 AM, Simon wrote:
> Do exactly what johnny suggested. On the update link you define the UC that
> you want to refresh after the js confirm
>
> On Sunday, 12 February 2012, James Cicenia wro
Do exactly what johnny suggested. On the update link you define the UC that
you want to refresh after the js confirm
On Sunday, 12 February 2012, James Cicenia wrote:
> I don't quite understand.
> My problem is that I don't see how update the parent window from the
confirm dialog's ok button.
> J
