You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by Guillaume Nodet <gn...@gmail.com> on 2007/02/09 16:05:31 UTC

Re: svn commit: r504332 [1/2] - in /incubator/ode/trunk: axis2/src/main/java/org/apache/ode/axis2/ bpel-api/src/main/java/org/apache/ode/bpel/iapi/ bpel-compiler/src/main/java/org/apache/ode/bpel/compiler/ bpel-obj/src/main/java/org/apache/ode/bpel/o

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, mriou@apache.org <mr...@apache.org> 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/

Re: svn commit: r504332 [1/2] - in /incubator/ode/trunk: axis2/src/main/java/org/apache/ode/axis2/ bpel-api/src/main/java/org/apache/ode/bpel/iapi/ bpel-compiler/src/main/java/org/apache/ode/bpel/compiler/ bpel-obj/src/main/java/org/apache/ode/bpel/o

Posted by Guillaume Nodet <gn...@gmail.com>.
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 <gn...@gmail.com> 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, mriou@apache.org <mr...@apache.org> 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/