-
1. Re: seam 3 on glassfish 5
mkouba Apr 24, 2018 2:23 AM (in response to skorejo)Hi Sana,
in CDI 1.1+ an
IllegalArgumentException
must be thrown if the runtime type of an event object is assignable to the type of a container lifecycle event (see also [CDI-245] Promote the right way how extensions should communicate with each other during container initialization - JBos… ). In fact, you should not use Seam 3 anymore (esp. on CDI 1.1+ application servers) - it's not actively developed for a long time. If possible, migrate to CDI 1.1+ and other tools and libraries (such as DeltaSpike). -
2. Re: seam 3 on glassfish 5
skorejo Apr 24, 2018 4:46 AM (in response to mkouba)Hi Martin,
Thank you for suggesting that, I have checked my application and currently it is using @RestrictAtPhase annotation from seam security as well as @FacesRedirect, @ViewConfig, @ViewPattern, @LoginView, @AccessDeniedView from seam faces. Is there any guide on how I can change these to CDI (preferably 2.0) ?
Regards,
Sana
-
3. Re: seam 3 on glassfish 5
skorejo Apr 24, 2018 12:26 PM (in response to mkouba)I have removed dependency of Seam 3 from application still I am getting same error.
-
4. Re: seam 3 on glassfish 5
mkouba Apr 25, 2018 2:29 AM (in response to skorejo)In fact, the failure comes from Solder, a library used by most Seam 3 modules.
-
5. Re: seam 3 on glassfish 5
skorejo Apr 25, 2018 4:28 AM (in response to mkouba)Yes the issue is coming due to seam3, on removing it from application it runs fine, so will i have to move to deltaspike or there is some workaround for legacy application.
-
6. Re: seam 3 on glassfish 5
skorejo Apr 30, 2018 3:21 AM (in response to skorejo)Hi Martin,
How can I convert the code in seam 3 using org.jboss.seam.security.Identity to deltaspike?