Versions Compared

Old Version 3

changes.mady.by.user Gerhard Petracek

Saved on

compared with

New Version 4

changes.mady.by.user Gerhard Petracek

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You can provide a custom ClassDeactivator via JNDI (name: java:comp/env/myfaces-codi/ClassDeactivator) or VM parameter (-D org.apache.myfaces.extensions.cdi.ClassDeactivator) or via a CODI Java-API ( ClassDeactivation#setClassDeactivator).

Instead of listing all classes which support such a deactivation, you can list all implementations of the Deactivatable interface (via your IDE).

Tip
titleHint

If you would like to filter additional beans, you can provide a custom javax.enterprise.inject.spi.Extension and observe javax.enterprise.inject.spi.ProcessAnnotatedType for calling #veto on an implementation.

Tipnote
titleAPI/Impl

Since the API of MyFaces CODI is separated, you can implement your custom implementation-module for an existing api-module. However, MyFaces CODI is a community project. So it's a good idea to donate improvements of any kind instead of permanently forking the implementation.