No parent container for NanoWAR at request level!

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    nanowar

Description

using nanocontainer.groovy to configure nanoweb containers is rather broken at the moment. There is no parent container at the request level.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brian McCallister added a comment -

Maniax says it needs more tests

Show
Brian McCallister added a comment - Maniax says it needs more tests
Hide
Permalink
Brian McCallister added a comment -

Looks like the script builder is the culprit. It previously either always supplied a parent container, or the pico constructor accepted a single null arg.

Show
Brian McCallister added a comment - Looks like the script builder is the culprit. It previously either always supplied a parent container, or the pico constructor accepted a single null arg.
Hide
Permalink
Michael Rimov added a comment -

Brian,

Could you check this with the latest code?

There was a race condition that caused a similar experience for me that has been fixed that may take care of your problem as well. Currently, I'm getting request parents properly.

-Mike (R)

Show
Michael Rimov added a comment - Brian, Could you check this with the latest code? There was a race condition that caused a similar experience for me that has been fixed that may take care of your problem as well. Currently, I'm getting request parents properly. -Mike (R)

People

  • Assignee:
    Unassigned
    Reporter:
    Brian McCallister
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: