AW: Exceptions originting from non-existing DirectActions
AW: Exceptions originting from non-existing DirectActions
- Subject: AW: Exceptions originting from non-existing DirectActions
- From: "Ruenagel, Frank" <email@hidden>
- Date: Tue, 8 Feb 2011 13:53:24 +0100
- Thread-topic: Exceptions originting from non-existing DirectActions
Hi,
i guess the URL of your Image is not an WO-generated-Resource-URl and it does not begin with a Slash. So
it is
interpreted as relative to the current "page".
I would recommend: Always
use in non-WO-covered _javascript_ and css Urls relative to your document-root,
beginning with /.
Hallo,
I get sometimes Error Messages containing DirectActions which do not
exist.
Some of them happen when a page is not yet fully loaded and a _javascript_ is
executed
containing a image, then the image appears in a DirectAction call like
this:
FusszeielundImpressumaendern_b-poster.jpgAction()
The image is in the page, but the Action not.
Has someone an explanation for this and perhaps a
solution to avoid this?
Can one catch
a java.lang.reflect.InvocationTargetException and if yes, where should I do
this?
In DirectAction.java? In Application?
I would like to catch all Exceptions originating from
non-existing DirectAction Calls if possible.
Any insight appreciated
Regards
Ute
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden