Hi,
thanks a lot for checking that. My problem was caused by a JPA entity's
lazy loading (not loaded) property.
The simple example in my last mail doesn't work anyway (also tried with
valueType attribute) but it is a case that really never occures.
I am working on a generator so that picklists cou
Hi
I have checked the component and it is ok.
The problem described happens because ValueExpression.getValueType()
returns Object.class when an structure like:
private List> multipleValues = new LinkedList>();
is used. You could try setting valueType attribute to java.util.List
in this way:
Hello again,
Replacing myfaces 2.1.2 api and impl with corresponding myfaces 2.1.7 jars
in Tomee 1.0.0 beta 2 does also not solve the problem.
Please help!
regards,
Max
2012/4/11 Max Goltzsche
> Hello dear myfaces users,
>
> I've already described my problem in my last mail but I forgot to tel
Hello dear myfaces users,
I've already described my problem in my last mail but I forgot to tell you
the environment I am working with:
tomee 1.0 beta 2 with myfaces 2.1.2 + tomahawk 1.1.11 for JSF2
In my example the first t:selectManyPicklist works fine but not the second
nested in a ui:repe
Hello,
I think there is a bug in tomahawk's selectManyPicklist component: Although
the POST values have been sent they are not assigned to the corresponding
bean's property if the picklist component is nested in a h:dataTable or
ui:repeat component (tested with both components but may also affect
5 matches
Mail list logo