@ApplicationScoped public class ValidatorManager extends Object
The @FacesValidator
is by default not eligible for dependency injection by @Inject
nor @EJB
.
There is a workaround
for EJB, but this is nasty and doesn't work out for CDI. Another way
would be to make it a JSF or CDI managed bean, however this doesn't register the validator instance into the JSF application context,
and hence you won't be able to make use of Application.createValidator(String)
on it.
Initially, this should be solved in JSF 2.2 which comes with new support for dependency injection in among others all
javax.faces.*.*Factory
, NavigationHandler
, ResourceHandler
,
ActionListener
, PhaseListener
and SystemEventListener
instances.
The Converter
and Validator
were initially also among them, but they broke a TCK test and were at the
last moment removed from dependency injection support.
The support is expected to come back in JSF 2.3, but we just can't wait any longer.
MyFaces CODI has support for it,
but it requires an additional @Advanced
annotation.
OmniFaces solves this by implicitly making all FacesValidator
instances eligible for dependency injection
without any further modification, like as JSF 2.2 would initially do, hereby providing a transparent
bridge of the code to the upcoming JSF 2.3.
The ValidatorManager
provides access to all FacesValidator
annotated Validator
instances which are made eligible for CDI.
OmniApplication
,
OmniApplicationFactory
Constructor and Description |
---|
ValidatorManager() |
Modifier and Type | Method and Description |
---|---|
Validator |
createValidator(Application application,
String validatorId)
Returns the validator instance associated with the given validator ID,
or
null if there is none. |
public Validator createValidator(Application application, String validatorId)
null
if there is none.application
- The involved JSF application.validatorId
- The validator ID of the desired validator instance.null
if there is none.Copyright © 2012–2015 OmniFaces. All rights reserved.