FAQ
BUG? commandLink href URLs too long (jsf_tree_64 value over 6k chars)

The length of the value of the 'jsf_tree_64' parameter is 6517
characters long in my case, causing IE6 to render links that do
nothing when clicked. When reducing the number of characters in the
rendered HTML, IE6 can navigate the links.

I recently upgraded from Tomahawk ver 1.09 where this was not an
issue, to 1.13 where it is now occuring.

Because this URL is embedded in every commandLink of Tree2, this
state is duplicated on the HTML page 16 times - making for
obnoxiously large HTML.

I see this is related to the client state saving - any suggestions on
how I can get this to work again in the new version?

-- Jayson

Search Discussions

  • Mike Kienenberger at Jul 14, 2006 at 12:23 am
    If you use one form for the entire page, you shouldn't need to have
    the attribute duplicated in every commandLink (each of which is
    probably being put into its own form).

    On 7/13/06, jraymond@mcertain.net wrote:
    BUG? commandLink href URLs too long (jsf_tree_64 value over 6k chars)

    The length of the value of the 'jsf_tree_64' parameter is 6517
    characters long in my case, causing IE6 to render links that do
    nothing when clicked. When reducing the number of characters in the
    rendered HTML, IE6 can navigate the links.

    I recently upgraded from Tomahawk ver 1.09 where this was not an
    issue, to 1.13 where it is now occuring.

    Because this URL is embedded in every commandLink of Tree2, this
    state is duplicated on the HTML page 16 times - making for
    obnoxiously large HTML.

    I see this is related to the client state saving - any suggestions on
    how I can get this to work again in the new version?

    -- Jayson
  • Jraymond at Jul 14, 2006 at 2:27 am
    Actually, there is only one form on the page. It's a mystery to me why
    commandLink would render it's href this way and not call common javascript
    on submit so it wouldn't need to be duplicate for every entry in my tree.

    Anyone else with suggestions greatly appreciated -

    --Jayson
    From: "Mike Kienenberger" <mkienenb@gmail.com>
    If you use one form for the entire page, you shouldn't need to have
    the attribute duplicated in every commandLink (each of which is
    probably being put into its own form).

    On 7/13/06, jraymond@mcertain.net wrote:
    BUG? commandLink href URLs too long (jsf_tree_64 value over 6k chars)

    The length of the value of the 'jsf_tree_64' parameter is 6517
    characters long in my case, causing IE6 to render links that do
    nothing when clicked. When reducing the number of characters in the
    rendered HTML, IE6 can navigate the links.

    I recently upgraded from Tomahawk ver 1.09 where this was not an
    issue, to 1.13 where it is now occuring.

    Because this URL is embedded in every commandLink of Tree2, this
    state is duplicated on the HTML page 16 times - making for
    obnoxiously large HTML.

    I see this is related to the client state saving - any suggestions on
    how I can get this to work again in the new version?

    -- Jayson
    >
  • Mike Kienenberger at Jul 14, 2006 at 2:29 am
    Well, I haven't used tree2 myself, but are all of those command links
    inside your one form?

    It almost sounds like an implementation bug.


    On 7/13/06, jraymond@mcertain.net wrote:
    Actually, there is only one form on the page. It's a mystery to me why
    commandLink would render it's href this way and not call common javascript
    on submit so it wouldn't need to be duplicate for every entry in my tree.

    Anyone else with suggestions greatly appreciated -

    --Jayson
    From: "Mike Kienenberger" <mkienenb@gmail.com>
    If you use one form for the entire page, you shouldn't need to have
    the attribute duplicated in every commandLink (each of which is
    probably being put into its own form).

    On 7/13/06, jraymond@mcertain.net wrote:
    BUG? commandLink href URLs too long (jsf_tree_64 value over 6k chars)

    The length of the value of the 'jsf_tree_64' parameter is 6517
    characters long in my case, causing IE6 to render links that do
    nothing when clicked. When reducing the number of characters in the
    rendered HTML, IE6 can navigate the links.

    I recently upgraded from Tomahawk ver 1.09 where this was not an
    issue, to 1.13 where it is now occuring.

    Because this URL is embedded in every commandLink of Tree2, this
    state is duplicated on the HTML page 16 times - making for
    obnoxiously large HTML.

    I see this is related to the client state saving - any suggestions on
    how I can get this to work again in the new version?

    -- Jayson
  • Dennis Byrne at Jul 14, 2006 at 2:34 am
    Jayson,

    Is javascript enabled in the browser? Is javascript rendering disabled on the server JSF app?

    Dennis Byrne
    -----Original Message-----
    From: Mike Kienenberger
    Sent: Thursday, July 13, 2006 10:28 PM
    To: 'MyFaces Discussion'
    Subject: Re: BUG? commandLink href URLs too long (jsf_tree_64 value over 6k chars)

    Well, I haven't used tree2 myself, but are all of those command links
    inside your one form?

    It almost sounds like an implementation bug.


    On 7/13/06, jraymond@mcertain.net wrote:
    Actually, there is only one form on the page. It's a mystery to me why
    commandLink would render it's href this way and not call common javascript
    on submit so it wouldn't need to be duplicate for every entry in my tree.

    Anyone else with suggestions greatly appreciated -

    --Jayson
    From: "Mike Kienenberger" <mkienenb@gmail.com>
    If you use one form for the entire page, you shouldn't need to have
    the attribute duplicated in every commandLink (each of which is
    probably being put into its own form).

    On 7/13/06, jraymond@mcertain.net wrote:
    BUG? commandLink href URLs too long (jsf_tree_64 value over 6k chars)

    The length of the value of the 'jsf_tree_64' parameter is 6517
    characters long in my case, causing IE6 to render links that do
    nothing when clicked. When reducing the number of characters in the
    rendered HTML, IE6 can navigate the links.

    I recently upgraded from Tomahawk ver 1.09 where this was not an
    issue, to 1.13 where it is now occuring.

    Because this URL is embedded in every commandLink of Tree2, this
    state is duplicated on the HTML page 16 times - making for
    obnoxiously large HTML.

    I see this is related to the client state saving - any suggestions on
    how I can get this to work again in the new version?

    -- Jayson

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupusers @
categoriesmyfaces
postedJul 13, '06 at 5:18a
activeJul 14, '06 at 2:34a
posts5
users3
websitemyfaces.apache.org

People

Translate

site design / logo © 2019 Grokbase