[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ] Scott Marlow edited comment on WFLY-10520 at 6/13/18 10:13 AM: --------------------------------------------------------------- Note from [~gbadner]: {quote} I ran a simple test that executed: s.createQuery( "from A" ).setMaxResults( 0 ).list() When built with 5.1, it returns all A entities. When built with 5.3, it returns an empty list. This is not good. {quote} I can think of two options: # If the WF bytecode transformer doesn't handle Query#getMaxResults, then the application will need to be rewritten to properly use the new Query#getMaxResults as well as Query#setMaxResults() behaviour. # Other approach might be for the WF bytecode transformer to check for calls to Query#setMaxResults and rewrite the bytecode to work, not that we know yet, what code changes are needed to make the 5.1 app code work with 5.3 yet (Gail?). A concern about the second approach of the transformer going a bit deeper into application code rewriting, is if the Hibernate team fixes a bug in 5.3.x that impacts the setMaxResults behaviour, the transformer would also need to be fixed as well. was (Author: smarlow): Note from [~gbadner]: {quote} I ran a simple test that executed: s.createQuery( "from A" ).setMaxResults( 0 ).list() When built with 5.1, it returns all A entities. When built with 5.3, it returns an empty list. This is not good. {quote} I can think of two options: # If the WF bytecode transformer doesn't handle Query#getMaxResults, then the application will need to be rewritten to properly use the new Query#getMaxResults as well as Query#setMaxResults() behaviour. # Other approach might be for the WF bytecode transformer to check for calls to Query#setMaxResults and rewrite the bytecode to work. -- This message was sent by Atlassian JIRA (v7.5.0#75005)