]
Norman Richards commented on JBSEAM-1776:
-----------------------------------------
This is caused by the changes in
The logic in that is clearly in error (lastIndexOf() on a string that you just tested as
empty). Reverting to revision 1.7 solves the problem, but I don't understand how this
would affect JBSEAM-1604.
Exception handling redirects to incorrect URL
---------------------------------------------
Key: JBSEAM-1776
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1776
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0.BETA1
Environment: Seam version used: CVS Based Seam 2
JBoss AS 4.2.1 GA
Reporter: Wolfgang Schwendt
Priority: Critical
Fix For: 2.0.0.CR1
How to reproduce:
Deploy the seamdiscs example with the facelets.DEVELOPMENT config parameter set to false
in web.xml. (Note: in web.xml, as checked out from the Seam CVS repository,
facelets.DEVELOPMENT is set to true, but we need to set it to false in order to test how
exceptions are handled).
After deployment access the following URL:
http://127.0.0.1:8080/seam-discs/artists.seam?artistId=200&actionOutc...
In this URL the artistId is deliberately set to a value for which no entity exists in the
database. The intention is to trigger an EntityNotFoundException when
org.jboss.seam.framework.Home tries to load the artist (entity instance) with id 200.
What happens after above URL is accessed:
Seam redirects to
http://127.0.0.1:8080/seam-discs/artist.seam/error.xhtml?cid=6
But it actually is supposed to redirect to
http://127.0.0.1:8080/seam-discs/error.seam?cid=6
, given the exception definition in pages.xml for the seamdiscs example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: