On May 26, 2006, at 11:05 PM, Gennady Kushnir wrote:
Were the documentation for WOLongResponsePage can be found?
It is not descripted neither in WO API nor in reference.
There is a WOLongResponsePage javadoc page, but it merely lists the
public API.
The WOLongResponsePage.java source is
On 27 May 2006, at 10:05, Gennady Kushnir wrote:
Were the documentation for WOLongResponsePage can be found?
It is not descripted neither in WO API nor in reference.
And there are several other WOExtensions that seem useful but are
not documentated.
Try looking in:
/Developer/Examples/Java
I'm sorry but it is not an answer but a question.
Were the documentation for WOLongResponsePage can be found?
It is not descripted neither in WO API nor in reference.
And there are several other WOExtensions that seem useful but are not
documentated.
Regards,
Gennady Kushnir
On 25.05.2006,
Of course it is rather intriguing that DirectAction detects an error
that ComponentAction does not. But as it seems to me, it is more
reasonable to look for an error not in DirectActions but where thrown
Exception locates it.
It says that you have a ClassCast error in your
inetOrgPerson_E
Put a breakpoint in your session constructor, see where it has come from.
Watch out for any images on your main page that you are using WOImage
to render. If you have not got those wired up properly, they will kick
off a session creation.
HTH,
Geoff
On 26/05/06, Helen He <[EMAIL PROTECTED]> wr
To deal with low UP bandwidth uploaded file should be compressed on the client side. So that is NOT server-side WO app's affair.Server-side affair will be to decompress incoming zip file. java.util.zip package will help with that task.I've implemented unzipOnTheFly upload behavior on my app. If you
I assume, making your first (login) page DirectAction should help.
If session is not created until successful login, no spiders/surfers
may disturb your app.
Regards,
Gennady Kushnir
On 26.05.2006, at 21:41, Helen He wrote:
On May 26, 2006, at 12:00 PM, Chuck Hill wrote:
Override dispatc
