hi pieter, please provide a bit more details. esp. the first phase of the jsf request lifecycle which has to access this instance and how you would like to access it.
codi tries to restore the window-id as early as possible. the first attempt is before the restore-view phase. if it isn't possible there, codi restores it after the restore-view phase. conversation scoped beans can be accessed as soon as there is a window-id. regards, gerhard 2011/6/30, Pieter Martin <[email protected]>: > Hi, > > I have the following requirement and wondering how to implement it with > codi. > > We want to use conversations and have a database instance that is > conversation scoped. However for every request that we need to put the > conversation scoped database instance in a threadvar where domain > entities can access it later. We are using a graph db and the domain > entities uses the db instance to add vertexes and edges. > > For request scoped use cases it is easy to set the threadvar when > observing the @BeforeFacesRequest event and to clear the threadvar on > the @AfterFacesRequest. > > However this does not work for conversation scoped use cases as the > conversation context is not yet active. > > Is there a suggested way for me to achieve this? > > Thanks > Pieter > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
