That was fast! I found the section on interceptors in the Seam reference, but
that section seems to be describing interceptors that happen before a
particular action is executed.
I'm assuming this means that I need to read up on the EJB3 spec some more to
find out about client-side interceptor
OK, so I have implemented client-side interceptors for Seam. All you do is
write a normal Seam interceptor (using @Interceptors as a meta-annotation),
and then annotate the actual interceptor class @Interceptor(type=CLIENT).
That is a good place to handle stuff like remote exceptions.
View the o
"[EMAIL PROTECTED]" wrote : 3. You need to implement your own exception
handling layer for this. Either deal with the exception in client code, or in a
servlet filter or web.xml. Unfortunately JSF (amazingly) does not provide any
good place to handle these kinds of exceptions :-(
H. One th
1. At least in CVS it is conceptually possible to have a remote Seam component.
(I forget whether a nonbuggy implementation made it into 1.0.1.)
However, this feature requires that the implementation class for the remote
bean is in the client classpath, which is not usually the case. (I'm not q
