Mailing-List: contact users-help@deltaspike.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@deltaspike.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAGJtJfEkg0Dgv_UYGftMdK6YHEN_v-Kyx0ArSW2_Cqn96=-TCw@mail.gmail.com>
References: 
 <CACtdb3+FvMp=_Kn7UJ=rH-tytyTqyJbCV3CaiXZzHHtba5UXTg@mail.gmail.com>
 <CAGJtJfEkg0Dgv_UYGftMdK6YHEN_v-Kyx0ArSW2_Cqn96=-TCw@mail.gmail.com>
From: Karl Pietrzak <kap4020@gmail.com>
Date: Thu, 11 Feb 2016 22:53:18 -0500
Message-ID: 
 <CACtdb3L6UMBRMtXRMQQs=UYM8Vc7FP5S8cNxAqP=7f-RNRQRkQ@mail.gmail.com>
Subject: Re: how to test different java.security.Principal's
To: users@deltaspike.apache.org
Content-Type: multipart/alternative; boundary=001a114b33deac65a2052b8a9c76

--001a114b33deac65a2052b8a9c76
Content-Type: text/plain; charset=UTF-8

I'm not sure how to use my custom CDI qualifiers to achieve my goal.  Care
to send a blog post or a link to an example?

I guess one of the confounding problems might be a test executing in Maven
has two bean archives:

   - target/classes
   - target/test-classes

So whatever solution needs to recognize that target/classes might have its
own bean.xml (for production).

Do I need an @Alternative or something?

Thanks!  Any tips would be greatly appreciated.

On Wed, Feb 10, 2016 at 9:24 AM, Gerhard Petracek <
gerhard.petracek@gmail.com> wrote:

> hi,
>
> you can use your own cdi-qualifier/s or you can use just one (central)
> producer which has at least one parameter of type
> javax.enterprise.inject.spi.InjectionPoint.
> (InjectionPoint allows to get information about the target
> -> you can produce dependent-scoped instances e.g. based on the target
> test-class).
>
> regards,
> gerhard
>
>
>
> 2016-02-10 14:27 GMT+01:00 Karl Pietrzak <kap4020@gmail.com>:
>
> > Thanks to Java EE 7, or maybe even before it, you can inject a
> > java.security.Principal
> > <https://docs.oracle.com/javaee/7/tutorial/cdi-adv004.htm>.
> >
> > This is awesome, and I'd love to use this functionality to unit test my
> > code with my own Principal's.
> >
> > Something like:
> >
> > @Dependent
> >
> > @RunWith(CdiTestRunner.*class*)
> >
> > *public* *class* AliceUnitTest {
> >
> >     @Produces
> >
> >     *public* Principal customPrincipal() {
> >
> >         *return* *new* CustomPrincipal("alice@example.com");
> >
> >     }
> >
> >     @Inject
> >
> >     Principal principal;
> >
> >
> >     @Test
> >
> >     *public* *void* injection() {
> >
> >         *assertThat*(principal.getName(), *is*("alice@example.com"));
> >
> >     }
> >
> > @Dependent
> >
> > @RunWith(CdiTestRunner.*class*)
> >
> > *public* *class* BobUnitTest {
> >
> >     @Produces
> >
> >     *public* Principal customPrincipal() {
> >
> >         *return* *new* CustomPrincipal("bob@example.com");
> >
> >     }
> >
> >
> >     @Inject
> >
> >     Principal principal;
> >
> >
> >     @Test
> >
> >     *public* *void* injection() {
> >
> >         *assertThat*(principal.getName(), *is*("bob@example.com"));
> >
> >     }
> >
> >
> > }
> >
> >
> > This results in "WELD-001409: Ambiguous dependencies for type Principal
> > with qualifiers @Default" and "WELD-001318: Cannot resolve an ambiguous
> > dependency between: ".
> >
> > I think I tried every different scope and bean-discovery-mode.  Is this
> > supported at all?
> >
> > Code available at
> >
> >
> https://github.com/The-Alchemist/javaeetesting/tree/testing-different-principals/deltaspike
> >
> > Any tips would be greatly appreciated. :)
> >
> > --
> > Karl
> >
>


-- 
Karl

--001a114b33deac65a2052b8a9c76--