Originally posted by Gregg Bolinger:
There is nothing special about JSF once it's on the browser. At that point it's all HTML and it still uses the HTTP protocal to handle requests and responses. If you are looking for vulnerabilities, look for them in HTTP, not the framework used.
Originally posted by marc weber:
That's my interpretation. I tried to get an overflow with a tangled web of constructors going around in circles calling each other, but the compiler was "smart enough" to catch it.
[ February 24, 2006: Message edited by: marc weber ]
where both methods take the same �<EventListenerType>� type argument, where the �<EventListenerType>� type extends the �java.util.EventListener� interface, where the first method starts with �add�, the second method starts with �remove�, and where the �<EventListenerType>� type name ends with �Listener�.
Originally posted by Bert Bates:
Thanks for your help,
Originally posted by Alexander Jesse:
I would say here is your problem...
JSF is not made to listen to such URL-parameters.
This is not a workaround, but the only correct way to do it...
Originally posted by Sergey Smirnov:
Why do you try /jsftest2.jsf, but not /jsftest2.jsp ?