Results 1 to 3 of 3

Thread: Bean creation problem

  1. #1
    Join Date
    Sep 2006
    Posts
    20

    Default Bean creation problem

    I have a bean that's defined in the applicationContext that uses the getInstance method of the class (the class was developed elsewhere).

    In another context file (for acegi) I have a bean that references the bean from the application context. Initialization fails because the definition in the acegi file can't find the bean. I use it in the applicationContext just fine. I'm guessing that it's not getting created in time to use it, but I don't know how to force it.
    Thanks

  2. #2
    Join Date
    Sep 2006
    Location
    UK
    Posts
    8,424

    Default

    Is it possible to see the exception. I'm not sure what you mean when you say it can't find it. If you are using container heirarchies that could be your issue.
    Last edited by karldmoore; Aug 27th, 2007 at 03:00 PM.
    Barracuda Networks SSL VPN Lead Developer
    http://pramatr.wordpress.com
    http://twitter.com/karldmoore
    http://www.linkedin.com/in/karldmoore
    Any postings are my own opinion, and should not be attributed to my employer or clients.

  3. #3
    Join Date
    Sep 2006
    Posts
    20

    Default problem resolved

    one of the config files was being picked up by the default naming convention. When I explicitly listed it, the problem disappeared.

Posting Permissions

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