facebook

f:attribute with JSF 1.2

  1. MyEclipse Archived
  2.  > 
  3. ICEfaces Integration
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #281696 Reply

    meteocat
    Member

    Hi,

    as I am developing an app, discovering icefaces,
    I also discover some bugs that affect me like this

    http://jira.icefaces.org/browse/ICE-1934

    As with the myEclipse plugin for icefaces version of icefaces
    is 1.6.1…
    could be any patch to fix it?

    What can I do?
    or… do you know another way to do this:

    <ice:commandLink actionListener=”#{sectorsBean.viewSector}”
    binding=”#{sectorsBean.sectorLink}” type=”submit”
    value=”#{sector.secNom}”>
    <f:attribute value=”#{sector.idSec}” name=”idSector”></f:attribute>
    </ice:commandLink>

    ???

    #281893 Reply

    Riyad Kalla
    Member

    meteocat,
    You can actually manuall update the 1.6.1 libs that we ship by going to Window > Prefs > MyEclipse > Project Capabilities > ICE Faces, and then removing the libs we ship (you can always restore with the Defaults button) and putting in the JARs from the updated ICEfaces download to replace them.

    Then those JARs will be used for building/deploying your project instead of the older ones.

    #281925 Reply

    meteocat
    Member

    Hi,

    I had done so, but the bug is also at 1.6.2.
    Only commercial 1.6.3 and 1.7 fix it.

    Is there any new about release date of 1.7?
    Will pass much time since 1.7 be released to MyEclipse 1.7 integration? (days? weeks? months?)

    Thanks!!

    #281952 Reply

    Riyad Kalla
    Member

    Is there any new about release date of 1.7?
    Will pass much time since 1.7 be released to MyEclipse 1.7 integration? (days? weeks? months?)

    Shouldn’t be too long. It depends if the update causes changes to the designer integration. Then it can take longer.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: f:attribute with JSF 1.2

You must be logged in to post in the forum log in