Results 1 to 9 of 9

Thread: table.tagx bugged?

  1. #1

    Default table.tagx bugged?

    Spring roo 1.1.4
    The created list.jspx shows incorrect values for the field concatenting the date evaluated in the previous row to all the text fields:

    es:
    Code:
    this is a test      |12/06/2001|13/06/2011
    foo13/06/2011       |05/06/2007|14/05/2011
    thirdrow14/05/2011  |04/01/2011|13/05/2007
    ecc..
    Modifing table.tagx solved my problem:
    after this:
    Code:
                <c:set var="columnMaxLength" value="${lengths[num.count-1]}" />
                <c:set var="columnType" value="${types[num.count-1]}" />
                <c:set var="columnDatePattern" value="${patterns[num.count-1]}" />
    add this:
    Code:
                <c:set var="colTxt" value=""/>

  2. #2
    Join Date
    Mar 2008
    Location
    Sydney, AU
    Posts
    974

    Default

    Roo concatenates all column values to a max of 10 characters by default for list views. This is so things keep looking nice. You can change these defaults by setting the maxColumnLength attribute in form:display elements.
    Stefan Schmidt
    Software Engineer, Spring Roo
    SpringSource - a division of VMware
    twitter @schmidtstefan

  3. #3

    Default

    I don't understand your reply...
    why this tag library concatenate the last date value with all the text value columns of the next row? I can't imagine a reason for this.
    It seems to me that is a bug, and I've proposed a correction.

  4. #4

    Default

    I think it's related to this problem:
    http://forum.springsource.org/showth...444#post364444

    in my original table.tagx i have this:
    Code:
                    <c:otherwise> 
                   		<spring:eval expression="item[column]"/>
                    </c:otherwise>
    instead of this:
    Code:
                    <c:otherwise>
                    	<c:set var="colTxt">                            
                      		<spring:eval expression="item[column]"/>
                      	</c:set>
                    </c:otherwise>

  5. #5
    Join Date
    Mar 2008
    Location
    Sydney, AU
    Posts
    974

    Default

    Ah, ok, thanks for letting us know. This explains the confusion. Roo also offers a command to manually update changed tag definitions: http://static.springsource.org/sprin...vc-update-tags.

    HTH,
    Stefan
    Stefan Schmidt
    Software Engineer, Spring Roo
    SpringSource - a division of VMware
    twitter @schmidtstefan

  6. #6

    Default

    updating with "web mvc update tags" command changed that line in table.tagx with :
    Code:
      <c:otherwise> 
             <spring:eval expression="item[column]" var="colTxt"/>
      </c:otherwise>
    that resolves the previous issue, but introduce a new one. With this solution the tag does not use the registered custom converter for an object, it call the toString method of the object-
    The tag has to be exactly like this to work with converters:
    Code:
                    <c:otherwise>
                    	<c:set var="colTxt">                            
                      		<spring:eval expression="item[column]"/>
                      	</c:set>
                    </c:otherwise>

  7. #7
    Join Date
    Mar 2008
    Location
    Sydney, AU
    Posts
    974

    Default

    Can you please open a Jira ticket for this?
    Stefan Schmidt
    Software Engineer, Spring Roo
    SpringSource - a division of VMware
    twitter @schmidtstefan

  8. #8

  9. #9
    Join Date
    Mar 2008
    Location
    Sydney, AU
    Posts
    974

    Default

    This has already been resolved and should be available with Roo 1.1.5.
    Stefan Schmidt
    Software Engineer, Spring Roo
    SpringSource - a division of VMware
    twitter @schmidtstefan

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •