You are over-engineering, is all. An error page is perfectly acceptable if a
user plays with the URL.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042300#4042300
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042300
Hm, should I go that route, is there any way to force the facesmessages to be
displayed after a GET-request instead of after a POSTback? Right now I'm using
to display an error message, where
I manually manage the initialized boolean.
View the original post :
http://www.jboss.com/index.html?
Ahh, guess I shold have read your first post to the end..
"Ofcourse I could make all my RequestParams String and handle the conversion
myself, but hey..."
Nvm ;)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042250#4042250
Reply to the post :
http://www.j
How about taking care of the conversion yourself, by letting the requestparam
being just a String? A try-catch in your method takes care of any Exceptions,
and some static code somewhere which you can call with params like the name of
the reqparam, and some errorstring that it will set to the fa
I wasn't trying to be hostile or anything, sorry if I came across like that?
What I want, is some mechanism to create (for example) a facesmessage
containing a reference to the parameter name stating that invalid information
is entered. However, 1) we are dealing with a GET, so facesmessages ar
It does react to malformed data, it throws a runtime exception. What more do
you want? Redirect this exception to an error page.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042144#4042144
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=p
Well uhm... what about (ab)users? Of course I'm not going to code such things
into the application logic, but it seemed only natural to me that my
application could respond to malformed data.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042140#4042140
Repl
Well, 'a' is not a number! :) You can't gracefully fail, just don't put illegal
request arguments into your application logic.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042057#4042057
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=pos
I think there's a little misunderstanding... indeed, the conversion is working
just fine when I do:
/app/somepage.xhtml?id=1
which is convertible (by parseLong() I guess) to Long and therefore assignable
to this field:
| @RequestParameter("id")
| private Long id;
|
However, my problem
@RequestParameter conversion from a String request parameter to a Long field or
property is working fine in my app. You need to show some code if you want help.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042048#4042048
Reply to the post :
http://www.jbo
10 matches
Mail list logo
