ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dileep_sivaraman <dileep_sivara...@infosys.com>
Subject Re: Debugging Support for BEL Processes
Date Wed, 10 Dec 2008 09:52:17 GMT

Hi Milinda,

I have set the global breakpoint through remote calls itself.

Snippet:

rmiServer = (OdeRemote) (registry.lookup("jcaServer"));

// call the remote method

OdeTransportPipeRemote pipe = rmiServer.newPipe();


pipe.invokeConnectionMethod("addGlobalActivityBreakpoint(java.lang.String,java.lang.String)",new
Object[] 
{"{http://ode/bpel/unit-test}HelloWorld2-6","assign1" });


I hope this helps and sorry for replying late.



Thanks

Dileep




Milinda Pathirage wrote:
> 
> Hi Dileep,
> 
> How you set the global breakpoint using Management API? Through a remote
> call?
> 
> Thanks,
> Milinda
> 
> On Sun, Nov 30, 2008 at 9:18 PM, Milinda Pathirage <
> milinda.pathirage@gmail.com> wrote:
> 
>> Thanks Dileep. I'll have a look at it.
>>
>> Milinda
>>
>> On Fri, Nov 28, 2008 at 2:44 PM, dileep_sivaraman <
>> dileep_sivaraman@infosys.com> wrote:
>>
>>>
>>>
>>> Hi Milinda,
>>>
>>> I am not sure if this is exactly what you are looking for.
>>>
>>> To check if debugging actually works or not,I just tested the 'add
>>> breakpoint' and resume functionality provided by management API's.
>>>
>>>
>>> Apache ODE :1.2 version
>>>
>>> Server: Apache tomcat
>>>
>>> Example : hello World that comes packed with the war
>>>
>>>
>>>
>>> 1) I first added a global breakpoint for assign activity "assign1" in
>>> the
>>> hello world example.
>>>
>>> 2) The I ran the Hello World Example.(Sure enough it got suspended)
>>>
>>> Apache Console Log:
>>>
>>> DEBUG - GeronimoLog.debug(66) | SELECT: PickResponseChannel#9: FOUND
>>> match
>>> for N
>>> EW instance mexRef={MyRoleMex#hqejbhcnphr3saqv7i1iir [Client
>>> hqejbhcnphr3saqv7i1
>>> iiq] calling {http://ode/bpel/unit-test.wsdl}HelloService.hello(...)
>>> }
>>> DEBUG - GeronimoLog.debug(66) | Setting execution state on instance
>>> 544603
>>>
>>> 3) I then checked the status of the Process Instance
>>>
>>> My RMI Test Client Log:
>>>
>>> NAME :HelloWorld2
>>>
>>> START DATE :2008-11-28T17:08:43.452+08:00
>>>
>>> LAST ACTIVE DATE :2008-11-28T17:08:43.577+08:00
>>>
>>> STATUS_ :SUSPENDED
>>>
>>>
>>> 4) Next I called the resume() API with the Instance ID:544603
>>>
>>>
>>> 5) The instance ran to completion.
>>>
>>> Apache Console Log:
>>>
>>> DEBUG - GeronimoLog.debug(66) | Reply for
>>> helloWorld.{http://ode/bpel/unit-test.
>>> wsdl}hello
>>> DEBUG - GeronimoLog.debug(66) | Reply message <?xml version='1.0'
>>> encoding='utf-
>>> 8'?>
>>>
>>> testing
>>> World
>>>
>>>
>>> 6) I once again checked the status of that instance.
>>>
>>> My RMI Test Client Log:
>>>
>>> NAME :HelloWorld2
>>>
>>> START DATE :2008-11-28T17:08:43.452+08:00
>>>
>>> LAST ACTIVE DATE :2008-11-28T17:09:32.733+08:00
>>>
>>> STATUS_ :COMPLETED
>>>
>>>
>>>
>>>
>>> So atleast I can assure you that Debugging works.Now what you want is
>>> actually upto you.
>>>
>>>
>>> Thanks
>>> Dileep
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Debugging-Support-for-BEL-Processes-tp20011863p20731080.html
>>> Sent from the Apache Ode Dev mailing list archive at Nabble.com.
>>>
>>
>>
>>
>> --
>> http://mpathirage.com
>> http://wso2.org "Oxygen for Web Service Developers"
>> http://wsaxc.blogspot.com "Web Services With Axis2/C"
>>
> 
> 
> 
> -- 
> http://mpathirage.com
> http://wso2.org "Oxygen for Web Service Developers"
> http://wsaxc.blogspot.com "Web Services With Axis2/C"
> 
> 

-- 
View this message in context: http://www.nabble.com/Debugging-Support-for-BEL-Processes-tp20011863p20932076.html
Sent from the Apache Ode Dev mailing list archive at Nabble.com.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message