Mailing-List: contact users-help@deltaspike.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@deltaspike.apache.org
Received-SPF: pass (nike.apache.org: domain of lightguard.jp@gmail.com
 designates 209.85.192.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53D79A5A.4040403@gmail.com>
References: <53D79A5A.4040403@gmail.com>
Date: Wed, 30 Jul 2014 07:06:46 -0600
Message-ID: 
 <CAF9TksPU959j+MOmAcwEDDAmAgwxJmvAANgGDKn_zcNjtask3A@mail.gmail.com>
Subject: Re: DS SecurityInterceptor with DS ExceptionHandler in an ear
 deployment
From: Jason Porter <lightguard.jp@gmail.com>
To: "users@deltaspike.apache.org" <users@deltaspike.apache.org>
Content-Type: multipart/alternative; boundary=001a11c127781347a204ff68d428

--001a11c127781347a204ff68d428
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Sounds like an isolation problem between the EJB module and the web module.
Off the top if my head I can think of nothing else besides what you're
doing to fix that.

On Tuesday, July 29, 2014, Rainer Sch=C3=B6n <rainer.schoen.dev@gmail.com> =
wrote:

> Hello
>
> I am using a DS SecurityInterceptor in both modules (ejb and war) and one
> DS ExceptionHandler in the web module. Since [DELTASPIKE-449] is closed,
> security violations integrate with DS exception handling. Now my problem:
> If a security violation in the ejb module is detected, DS does not find t=
he
> ExceptionHandler in the web module. Instead of an AccessDeniedException I
> get an IllegalStateException in the web layer:
>
> Could not find beans for Type=3Dclass xx.xxxxx.FacesExceptionHandler and
> qualifiers:[]  [1]
>
> org.apache.deltaspike.core.api.provider.BeanProvider.
> getContextualReference(BeanProvider.java:150)
> org.apache.deltaspike.core.api.provider.BeanProvider.
> getContextualReference(BeanProvider.java:119)
> org.apache.deltaspike.core.api.provider.BeanProvider.
> getContextualReference(BeanProvider.java:100)
> org.apache.deltaspike.core.impl.exception.control.
> HandlerMethodImpl.notify(HandlerMethodImpl.java:194)
> org.apache.deltaspike.core.impl.exception.control.
> ExceptionHandlerBroadcaster.executeHandlers(ExceptionHandlerBroadcaster.
> java:153)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ... more
>
> Within the web module, the exception handler works fine. Any regular CDI
> events thrown in the ejb module are delivered to listeners in the web
> module without any problem.
>
> My workaround for  the moment is an ExceptionHandler in the ejb module
> catching the AccessDeniedException, mark the event as handled, extract th=
e
> original event and throw it manually. Throwing it again with any of the
> ExceptionEvent throwing methods results in the same error as described
> above.
>
> The error is reproducible easily. My configuration is GF4 and DS 1.0.0.
>
> Any better ideas?
>
> Regards, Rainer
>
> [1]
> @RequestScoped
> @ExceptionHandler
> public class FacesExceptionHandler {
> ...
>


--=20
Jason Porter
http://en.gravatar.com/lightguardjp

--001a11c127781347a204ff68d428--