Re: WebObjects URL Decoding
Re: WebObjects URL Decoding
- Subject: Re: WebObjects URL Decoding
- From: Chuck Hill <email@hidden>
- Date: Wed, 21 Feb 2007 10:06:01 -0800
My first question is, "Why?". If you are trying to figure out what
link caused an exception, here is what I would do. If you can find
the page that caused this (hint: good logging helps!), just go to
that page and look at the source in a browser and search for ".
0.11.5.5.1". Note that I removed the session specific 110 part. The
rest is static unless you have re-arranged the page content. If you
don't see it, look for conditionals that you can make true to reveal
more of the content.
A better approach is to extend your exception logging by also
including information from the active context() at the time of the
exception. Logging context().page().name() and context().component
().name() can help a lot in tracking this down.
Chuck
On Feb 20, 2007, at 11:18 PM, Owen McKerrow wrote:
Hi All,
Is there any way to track back from a WO url what the link/button
pressed was ?
i.e. for the following URL WebObjects/RIS.woa/wo/
LaxPpG24nbtqCjH1sZbfUw/110.0.11.5.5.1 how can I map back the
110.0.11.5.5.1 to a page and a link inside my app ?
Thanks
Owen McKerrow
WebMaster, emlab
Ph : +61 02 4221 5517
http://emlab.uow.edu.au
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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