I have fixed that by deserializing the bpel process in the jbi component to be able to retrieve the PortType for the given partner link. This may be a bit slow, but I haven't found any other way.
On 2/9/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
Matthieu, It seems that this change cause a NPE in the JBI component. I think the PortType can be retrieved by another mean, and in the JBI relies mainly on the abstract WSDL, so I'm wondering if we could introduce back this parameter on the BindingContext activateMyRoleEndpoint method. Why was it removed ? On 2/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Author: mriou > Date: Tue Feb 6 14:17:56 2007 > New Revision: 504332 > > URL: http://svn.apache.org/viewvc?view=rev&rev=504332 > Log: > Being smarter about memory management. First the process definitions (OProcess) aren't loaded at startup but are lay loaded at the first request instead. Second a process reaper can be enabled to disassociate (dehydrate) processes according to a specific policy. The default policy controls both the time to live and the total number of processes held in memory. Processes are then rehydrated on demand. > -- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
