Results 1 to 2 of 2

Thread: Roo 1.1.5: adding findAllMethod="" to @RooEntity doesn't remove findAll in the .aj

  1. #1
    Join Date
    May 2006
    Location
    Madrid
    Posts
    382

    Default Roo 1.1.5: adding findAllMethod="" to @RooEntity doesn't remove findAll in the .aj

    Hello:

    I'd like to avoid the findAll method in the Entities, not just in the Integration test (in the meantime I'm using @RooIntegrationTest(..., findAll=false))

    Some context here:

    I have an Entity whose findAllTest fails:

    Code:
    java.lang.AssertionError: Too expensive to perform a find all test for 'Commerce', as there are 260218 entries; set the findAllMaximum to exceed this value or set findAll=false on the integration test annotation to disable the test
    260218 entries are a lot of entities in development, and I presume that will be much more in production. So I prefer not to include the findAll method. I've tried to delete a findAllMethod using @RooEntity(..., findAllMethod="") but it doesn't work.

    However, I have done this a lot with previous versions. For instance, it works in 1.1.4.RELEASE [rev f787ce7].

    In fact, the current version (1.1.5.RELEASE [rev d3a68c3]) undo the changes that 1.1.4 made and I have again a findAll method.

    According https://jira.springsource.org/browse/ROO-589, it's a problem already solved.

    Can you take a look to that? Thank you very much.
    Last edited by jbbarquero; Sep 28th, 2011 at 05:24 AM. Reason: Avoid bold to be more polite

  2. #2
    Join Date
    Mar 2007
    Posts
    561

    Default

    In Roo 1.2.2 this bug still exists for @RooJpaActiveRecord
    How can I disable certain methods, like findAll etc.?

Posting Permissions

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