stack trace for testing ropertyActionListener:-

   [junit] Testcase: testValueChangeActionListener took 1.71 sec
    [junit] Caused an ERROR
    [junit] For input string: "1271182360311736000 "
    [junit] java.lang.NumberFormatException: For input string: "1271182360311736000 "
    [junit] at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
    [junit] at java.lang.Long.parseLong(Long.java:412)
    [junit] at java.lang.Long.valueOf(Long.java:518)
    [junit] at com.sun.faces.composite.ValueChangeListenerSetPropertyActionListener01TestCase.testValueChangeActionListener(ValueChangeListenerSetPropertyActionListener01TestCase.java:114)

the trailing space on the string is the problem (can't parse into an integer)...this only occurs with autoid on. When it is off, the trailing space is no longer there.

NOTE:_ this test is testing composite components with EE6 Dependencies, but even when run with EE5, I get the same results.

<p>System.currentTimeMillis():<span id="form:_t14">1271284659672881000</span>
;</p>
 is the markup but it is displayed with a trailing blank:-
System.currentTimeMillis():1271284659672881000 ;

Looks like this when autoid is turned off:-
<p>System.currentTimeMillis():1271287050934045000;</p>

addition of span (with newline after close tag for span) causes the trailing space to be added and it doesn't pass the parsing into a Long value.


original view page:-

<p>System.currentTimeMillis():<h:outputText
       value="#{valueChangeSetPropertyActionListenerBean.nanoTime}" />;</p>

The more critical problem here may be that autoid is affecting layout due to extra whitespace. This test will likely fail anyway due to the extra span tag inserted, but autoid should not affect layout.