Converter not found

[Marco Noronha]

Guys, Is there something wrong with my converter?

@ManagedBean(name = "tipoAcaoConverter")
@RequestScoped
public class TipoAcaoConverter extends 
BaseConverter<TipoAcao, Integer> 
implements Serializable {

	private static final long serialVersionUID = 1L;

	@ManagedProperty("tipoAcaoService")
	private TipoAcaoService tipoAcaoService;

	public TipoAcaoConverter() {
	}

	@PostConstruct
	public void init() {
		super.setEntityClass(TipoAcao.class);
		super.setBaseService(tipoAcaoService);
	}

}

Here is MyBase:

public abstract class BaseConverter<T, PK extends Serializable>
 implements Converter {

	private BaseService<T, PK> baseService;

	private Class<T> entityClass;

	public BaseConverter() {
	}

	@SuppressWarnings("unchecked")
	@Override
	public Object getAsObject(FacesContext arg0, UIComponent arg1, String arg2) {
		if(arg2 == null || arg2.equals("")){
			return null;
		}
				
		return this.getBaseService().findOne(
                        (PK) new SimpleTypeConverter().convertIfNecessary(arg2, 
                           ReflectUtil.getPrimaryKeyField(this.getEntityClass()).getType()));
	}

	@Override
	public String getAsString(FacesContext arg0, UIComponent arg1, Object arg2) {
		if (arg2 == null) {
			return "";
		}

		return arg2.toString();

	}

I don´t know what's happening.. I did it on an old project and it worked.

[Tim Holloway]

Converters aren't ManagedBeans. You should be annotating them as @FacesConverter objects.

I should mention also that Converters must be stateless and thread-safe.

[Marco Noronha]

Tim Holloway wrote:Converters aren't ManagedBeans. You should be annotating them as @FacesConverter objects.

I should mention also that Converters must be stateless and thread-safe.

OOpps.. Your wrong there!

Converters CAN BE managedBeans!

the error was on the view:

converter="#{anyConverter}";

instead of:

converter="anyConverter";

thanks !!

[Tim Holloway]

Backing beans can contain converters, but that is just an additional aspect of the Backing Bean.

Documentation is unclear, but I'm pretty sure that when a Backing Bean implements Converter, it's intended to make the backing bean as a whole self-converting. In other words, if BeanX implements Converter, I don't expect the conversion methods to be receiving/emitting anything that isn't a BeanX.

[Marco Noronha]

Tim Holloway wrote:Backing beans can contain converters, but that is just an additional aspect of the Backing Bean.

Documentation is unclear, but I'm pretty sure that when a Backing Bean implements Converter, it's intended to make the backing bean as a whole self-converting. In other words, if BeanX implements Converter, I don't expect the conversion methods to be receiving/emitting anything that isn't a BeanX.

You are right! That´s why my bean doesn´t implement Converter!!
My Generic (BaseConverter) does!!

[dennis deems]

Marco Noronha wrote:

Tim Holloway wrote:Backing beans can contain converters, but that is just an additional aspect of the Backing Bean.

Documentation is unclear, but I'm pretty sure that when a Backing Bean implements Converter, it's intended to make the backing bean as a whole self-converting. In other words, if BeanX implements Converter, I don't expect the conversion methods to be receiving/emitting anything that isn't a BeanX.

You are right! That´s why my bean doesn´t implement Converter!!
My Generic (BaseConverter) does!!

What's the advantage of a design like this? At first glance I would much rather have a separate, dedicated converter class that works on a specific type.