Runtime specification of viewId in Redirect ?

[lcoetzee]

Hi,

I am making use of the @Redirect tag as below:

@ApplicationException(rollback=true)
@Redirect(viewId = "/secure/structure/management/adminHome.xhtml")
public class NAPException extends Exception implements Serializable {

This works well. However, ideally I would like to configure the viewId at runtime to direct to a specfic page (depending on what the user was doing and where the exception got thrown).. eg.

@Name("napException")
@ApplicationException(rollback=true)
@Redirect(viewId = "#{napException.viewId}")
public class NAPException extends Exception implements Serializable {
 @Out(required=false)
 private String viewId;
 public NAPException(String message) {
 super(message);
 }

 public NAPException(String viewId, String message) {
 super(message);
 this.viewId=viewId;
 }

 public String getViewId() {
 return viewId;
 }


 public void setViewId(String viewId) {
 this.viewId = viewId;
 }
}

and invoked through:

throw new NAPException("/secure/structure/management/adminHome.xhtm",e);

Unfortunately the above does not work, Is there a way I can specify the target viewId ?

Thanks

Louis

[gavin.king]

Not at this time, but add a feature request to CVS. I think the best way to implement this would be to have "exception rules", ie:

<from-view-id>/xxx.jsp</from-view-id>
<from-exception>com.myapp.NAPException</from-exception>
<to-view-id>/error.jsp</to-view-id>
<redirect/>

JSF should really have this built-in, but it seems the JSF spec group never considered exception handling as an issue in enterprise applications :-/

[gavin.king]

I mean, add something to JIRA.

[lcoetzee]

Jira. Will do.

One possible solution for now is probably just to have different exceptions classes, each one annotated to point to a different viewId. Slightly cumbersome, but it will also do the trick (if you remember to throw the right exception in the right place ;-).

Thanks

L