Hello,
My guess is that the problem is more general than just a javascript issue.
In my previous message, I gave the "form submit" situation only as an
example. The problem actually touches more than just this: I cannot sort
my table content by clicking on one column header, I cannot switch from a
StackPanel to another, etc...
By searching a little bit further, I found out that the values that I used
in combo boxes to show a "greater or smaller" choice (for example, age
greater or smaller than 30) are not bound to their java counterpart
anymore. For example:
<ice:selectOneMenu value="#{someController.filter.ageOperator}" id=
"ageOperator">
<f:selectItem itemValue="1" itemLabel="#{msg.search_filter_greater}" />
<f:selectItem itemValue="-1" itemLabel="#{msg.search_filter_less}" />
</ice:selectOneMenu>
This menu was bound to a Java integer as follows:
private int ageOperator;
With 1.1.7, the value is not bound anymore. I needed to change the type of
the attribute in my Java class to String for the binding to work again. Is
there a special converter that I should add, which was not needed in 1.1.2
? I can assure you that this runs fine with 1.1.2 :-)
I am fairly new to MyFaces. Is there something I should do to make the
upgrade easier?
Thanks a lot for your help :-)
Sébastien
Jakob Korherr <[email protected]>
Sent by: [email protected]
01.03.2010 12:25
Please respond to
"MyFaces Discussion" <[email protected]>
To
MyFaces Discussion <[email protected]>
cc
Subject
Re: Trouble upgrading from 1.1.2 to 1.1.7
Hi,
Maybe there's a problem with the javascript that submits the form. I saw
However this is just a shot in the blue...
Regards,
Jakob
2010/3/1 <[email protected]>
> Hello,
>
> I am experiencing quite a lot of trouble while upgrading from MyFaces
> 1.1.2 to 1.1.7.
>
> My application uses IceFaces 1.8.2, Spring 2.5.2 and Hibernate 3.4.0.
>
> The only thing that I changed in my Maven 2 build is the version of
> MyFaces.
> This had an impact on the following jars:
>
> Added:
> myfaces-api-1.1.7.jar
> myfaces-impl-1.1.7.jar
> commons-digester-1.8.jar
> commons-beanutils-1.8.0.jar
>
> Removed:
> myfaces-api-1.1.2.jar
> myfaces-impl-1.1.2.jar
> commons-digester-1.6.jar
> commons-beanutils-1.7.0.jar
> commons-codec-1.3.jar
>
> When I build and deploy my application in Weblogic 9.2.3, the deploy
goes
> fine, but the actions in the app do not work anymore.
> More precisely: as soon as I try to use JSF components like if I submit
a
> form, then nothing happens. This behaviour can be observed with several
> browsers.
>
> I tried to find some upgrading guide but didn't find any guide related
to
> these versions. And since the version change is minor, I expected my
> application to run fine with the new jars.
>
> I tried also tried to override some jar versions, putting back the
> Digester to version 1.6, and the BeanUtils to version 1.7.0, but this
> didn't change anything. At this point, the only thing that had changed
in
> my EAR were the two MyFaces jars.
>
> Another attempt to find the problem was to upgrade the version
gradually.
> I switched to MyFaces 1.1.4, and everything worked fine. That's when I
> switched to MyFaces 1.1.5 that the problem appeared. However, I haven't
> seen anything in the changes from 1.1.4 to 1.1.5[1] that seems suspect.
>
> Is there some configuration changes that I might have missed? Or some
> known compatibility problems regarding this upgrade? Again, I couldn't
> find anything precisely related to these versions up to now, but I'm
still
> looking.
>
> Any help would be highly appreciated! :-)
>
> Best regards,
>
> Sébastien
>
> [1]
>
>
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10600&fixfor=12312310&sorter/field=summary&sorter/order=ASC&sorter/field=resolution&sorter/order=ASC&sorter/field=status&sorter/order=ASC&sorter/field=priority&sorter/order=DESC
>
>
>
> ************************ DISCLAIMER ************************
> This message is intended only for use by the person to
> whom it is addressed. It may contain information that is
> privileged and confidential. Its content does not
> constitute a formal commitment by Lombard Odier
> Darier Hentsch & Cie or any of its branches or affiliates.
> If you are not the intended recipient of this message,
> kindly notify the sender immediately and destroy this
> message. Thank You.
> *****************************************************************
>
************************ DISCLAIMER ************************
This message is intended only for use by the person to
whom it is addressed. It may contain information that is
privileged and confidential. Its content does not
constitute a formal commitment by Lombard Odier
Darier Hentsch & Cie or any of its branches or affiliates.
If you are not the intended recipient of this message,
kindly notify the sender immediately and destroy this
message. Thank You.
*****************************************************************
