I found the solution for it using getter injection or @Configure annotation for non spring bean.
-Dan Dan Tran wrote: > > > Create a new instance using a different name and manually inject it to my > runnable solves the problem. > > Now I have another concern, not related to Orchestra, where how to I > create new instance on the fly > (not thru spring configuration ) to be inject for each new thead ( yeah, I > will have schedulers spin off > threads left to right ) > > Comments are welcome, and thank you very much the advice on the previous > issue. > > Thanks > > -D > > Mario Ivankovits wrote: >> >> Hi Dan! >>> My thread has the same service bean that is in the main thread has, so I >>> guess both thread sharing >>> the same Persentent Context. >>> >>> Now I need to figure out how to Create my Persitent Context in the child >>> thread which a little >>> disappointed. My goal is to use the same service bean. Is there a way >>> to >>> use the same service bean >>> but with diffrent persistent context? >>> >> You mean the same instance of the bean or just the same class? The same >> instance might not be possible. >> But what if you configure your service bean two times? Then you'll be >> able to get two instances. >> >> If this wont help, could you provide some small code-pieces (spring >> config, beans, service bean, thread stuff) to figuring out what you'll >> going to do more exactly. >> Maybe as a patch against our examples would be great. >> >> >> Ciao, >> Mario >> >> >> > > -- View this message in context: http://www.nabble.com/-orchestra--unable-to-persist-in-sub-thread-tf4395808.html#a12566528 Sent from the My Faces - Dev mailing list archive at Nabble.com.
