REST interface problem

View: New views
3 Messages — Rating Filter:   Alert me  

REST interface problem

by bartlomiej.jendyk@gmail.com :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


hi again,

John, I'm really desperate - I've given up the RMI and started
experimenting with openwfe's REST interface. everything goes well - I
can log in as admin, launch the workflow and this is it. next thing I
want to do is to connect to the status service (http://localhost:7078)
to check if a workflow item has arrived in the store of my interest
(in this particular case, "Store.alpha"). at this point (having REST
session opened from my client app), either pointing my browser to this
URL or:

URL url = new URL("http://localhost:7078");
URLConnection c = url.openConnection(); // connect to status

hangs the worklist component completely, cpu usage raises to 100% and
the only way to get the stability back is to kill it with taskmgr.

this DID NOT occur in my previous version of code, which I posted
yesterday using RMI as standalone application. there, having a RMI
session open, the I had no problems with obtaining the engine's status
while a workflow instance was running and the workitem was waiting to
retrieve it from the store.

how this issue can be fixed?

regards,
bart

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE users" group.
To post to this group, send email to openwfe-users@...
To unsubscribe from this group, send email to openwfe-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-users?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: REST interface problem

by John Mettraux :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

2007/5/19, Bartłomiej Jendyk <bartlomiej.jendyk@...>:

>
> hi again,
>
> John, I'm really desperate - I've given up the RMI and started
> experimenting with openwfe's REST interface. everything goes well - I
> can log in as admin, launch the workflow and this is it. next thing I
> want to do is to connect to the status service (http://localhost:7078)
> to check if a workflow item has arrived in the store of my interest
> (in this particular case, "Store.alpha"). at this point (having REST
> session opened from my client app), either pointing my browser to this
> URL or:
>
> URL url = new URL("http://localhost:7078");
> URLConnection c = url.openConnection(); // connect to status
>
> hangs the worklist component completely, cpu usage raises to 100% and
> the only way to get the stability back is to kill it with taskmgr.
>
> this DID NOT occur in my previous version of code, which I posted
> yesterday using RMI as standalone application. there, having a RMI
> session open, the I had no problems with obtaining the engine's status
> while a workflow instance was running and the workitem was waiting to
> retrieve it from the store.
>
> how this issue can be fixed?

Hi Bart,

I've been following the mail exchange of yesterday rather remotely. I
don't undersand why you connect to the status service to determine if
there is a workitem in a store. You simply have to connect to the
worklist and call getHeaders() for the store.

As for the issue, the first step to its fix would be a clear
identification with an how to reproduce in a bug report :
http://sourceforge.net/tracker/?group_id=54621&atid=474244


Best regards,

--
John Mettraux   -///-   http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE users" group.
To post to this group, send email to openwfe-users@...
To unsubscribe from this group, send email to openwfe-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-users?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: REST interface problem

by bartlomiej.jendyk@gmail.com :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


it's ok, it took me a night to code the solution, but I've managed to
do it. connecting to status service wasn't necessary, though, the
headers lookup did the thing. all is working fine now over REST
interface, no reason to panic ;)

kind regards,
bart

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "OpenWFE users" group.
To post to this group, send email to openwfe-users@...
To unsubscribe from this group, send email to openwfe-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/openwfe-users?hl=en
-~----------~----~----~----~------~----~------~--~---

LightInTheBox - Buy quality products at wholesale price