Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: IdGeneratorConfigurer causes 'Context initialization failed'

  1. #11
    Join Date
    Jan 2009
    Location
    Ukraine, Kharkov
    Posts
    632

    Default

    Yes, Dennis, it does.
    I understand getBeansOfType code.

    I want to say you're going to catch the same problem with any other invokes of this method not only on IdGeneratorConfigurer.
    We can simply fix it for you as allowEagerInit = false, but where are the guarantees that evething will be OK in many features of other frameworks...

  2. #12
    Join Date
    Jan 2012
    Location
    Hannover, Germany
    Posts
    9

    Default

    You are right, I know, it is a problem that we have corrupt beans in our project, from time to time... But I can't avoid it in this big project...

    My thinking was: In the other cases if I use a framework-method and run into this problem, I could/must handle this problem. But in this case here, I doesn't invoke anything... The framework does and I can't even startup my application.

    I don't know, and yes, perhaps it is a chance to clean up the project and to enforce more attention by my collegues

  3. #13
    Join Date
    Oct 2005
    Location
    Boston, MA
    Posts
    2,840

    Default

    Ultimately, if you have invalid configuration, it's going to result in an error at some point. It just happens that the IdGeneratorConfigurer is the first thing trying to initialize beans as defined within your context.

  4. #14
    Join Date
    Jan 2012
    Location
    Hannover, Germany
    Posts
    9

    Default

    I know and try to convince my team.

Posting Permissions

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