On Jun 7, 2010, at 7:35 AM, Ivan wrote: > I have finished most of the codes, but after I modeled all the session > synchronization callbacks in the interceptor datas, even the methods from > the bean class itself, some new questions are coming :-(
That frowny-face should be a smiley-face, I love questions :) > The most problem is that in current spec, InvocationContext.getParameter > should throw IllegalStateException within a lifecycle callback method, from > my understanding, afterCompletion is also a lifecycle callback method > (actually current OpenEJB codes also think so), but we need the > getParameters to get the parameter values. What is your opinion ? Thanks ! Good catch. Hmmm. I can't think of anything simple and direct for bending the rules for this one method. Maybe for now we should just let it throw the IllegalStateException, at least temporarily. My gut says there must be some nice and elegant way to work around it, but my brain isn't cooperating with any answers :) -David
