[
https://issues.jboss.org/browse/WFLY-4555?page=com.atlassian.jira.plugin....
]
Michał Piotrowski commented on WFLY-4555:
-----------------------------------------
It looks like it works without problem if there is an empty beans.xml file. Data in a log
file is correct (just what the test case was intented to do).
I have also tested this case with no beans.xml file at all, which I guess should be an
implicit bean archive, but it gives the same error - converter is not properly created.
I am no expert in CDI specification but as far as I understand the specification it should
work also with no beans.xml and with basic beans.xml file like in my test case.
But there is a very easy workaround so I guess it is a minor bug.
I haven't tested what will happen if I need to have some entries in beans.xml file and
if it would be a problem.
Faces converter is not properly assigned if it is a CDI @Named bean
-------------------------------------------------------------------
Key: WFLY-4555
URL:
https://issues.jboss.org/browse/WFLY-4555
Project: WildFly
Issue Type: Bug
Affects Versions: 8.2.0.Final
Environment: Tested on openjdk version "1.8.0_45"
OpenJDK Runtime Environment (build 1.8.0_45-b13)
OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)
Reporter: Michał Piotrowski
Assignee: Jason Greene
Attachments: ConverterTest.zip
If I try to use converter declaring it with attribute converter (e.g. on selectOneMenu)
and use expression which points to a @Named CDI bean it isn't properly registered.
I will try to attach simple maven test case project.
The same converter class can be used if it is @Inject (-ed) to a CDI managed bean and
provided through some getter method to a converter attribute.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)