Hi there,
I found the recent discussion on the mailing list about clean URLs
seemingly failing to find the right event handler when a form is POSTed,
and saw a variety of solutions to creating the URL oneself.
After trying to debug the same issue myself, I think the reason for this
behaviour is
succeed in placing a slash and matching your JSP structure.
Or am I missing something...?
--Nikoloas
Rose William wrote:
Hi there,
I found the recent discussion on the mailing list about clean URLs
seemingly failing to find the right event handler when a form is
POSTed, and saw
handler methods to the name you pass in param of @HandlesEvent ?
ie:
public Resolution save() throws SchedulerException {
instead of:
@HandlesEvent(save)
public Resolution saveJob() throws SchedulerException {
Regards,
Sam
On Thu, Feb 3, 2011 at 11:21 AM, Rose William william.r
areas... and are off topic... .
Does this not address your problem / the bug you found?
--Nikolaos
Rose William wrote:
Hi Nikolaos,
It probably is!
In my case, the only thing in my folder structure was JSPs, so
moving
them to some other folder
Hi Enrico,
The CSS path is resolved from the client-visible path of your action,
not the server path, because the resolution is done by the client
browser not the server.
So if you have an action at http://yoursite.com/yourcontext/bean that
produces a page containing link rel=stylesheet
