REST + Call activity

[afenske]

Hello.

I've got a problem. I have a process from which I refer to a separate process using a call activity. When execution reaches this separate process I want to get process instanse details, but instead of this information I get an problem:
HTTP/1.1 500 Internal Server Error [Date: Fri, 21 Dec 2012 11:03:28 GMT, Accept-Ranges: bytes, Server: Restlet-Framework/2.0.14, Vary: Accept-Charset, Accept-Encoding, Accept-Language, Accept, Content-Type: text/html;charset=UTF-8, Content-Length: 486, Connection: close]
I think this happens due to my separate process which invoked as an inner process (using call activity).

What problem?

[udoderk]

Hello.

I've got a problem. I have a process from which I refer to a separate process using a call activity. When execution reaches this separate process I want to get process instanse details, but instead of this information I get an problem:
HTTP/1.1 500 Internal Server Error [Date: Fri, 21 Dec 2012 11:03:28 GMT, Accept-Ranges: bytes, Server: Restlet-Framework/2.0.14, Vary: Accept-Charset, Accept-Encoding, Accept-Language, Accept, Content-Type: text/html;charset=UTF-8, Content-Length: 486, Connection: close]
I think this happens due to my separate process which invoked as an inner process (using call activity).

What problem?

when I had problems with REST, the LOG output on Tomcat have helped…

[afenske]

Hello.

I've got a problem. I have a process from which I refer to a separate process using a call activity. When execution reaches this separate process I want to get process instanse details, but instead of this information I get an problem:
HTTP/1.1 500 Internal Server Error [Date: Fri, 21 Dec 2012 11:03:28 GMT, Accept-Ranges: bytes, Server: Restlet-Framework/2.0.14, Vary: Accept-Charset, Accept-Encoding, Accept-Language, Accept, Content-Type: text/html;charset=UTF-8, Content-Length: 486, Connection: close]
I think this happens due to my separate process which invoked as an inner process (using call activity).

What problem?

when I had problems with REST, the LOG output on Tomcat have helped…

Unfortunately, I don't understand the reason of that problem.

Could you help me?

[img]http://www.pictureshack.ru/images/75328_log.png[/img]

[udoderk]

…

Could you help me?

[img]http://www.pictureshack.ru/images/75328_log.png[/img]

Nice screenshot :ugeek: The exeption stacktrace in text form would be better :roll:

Look at that post with same exception

WARNING: Exception or error caught in resource
java.lang.NullPointerException
        at org.codehaus.jackson.node.ObjectNode.toString(ObjectNode.java:344)
        at org.codehaus.jackson.node.ArrayNode.toString(ArrayNode.java:403)
        at org.codehaus.jackson.node.ObjectNode.toString(ObjectNode.java:344)
        at java.lang.String.valueOf(String.java:2826)
        at java.lang.StringBuilder.append(StringBuilder.java:115)
        at org.restlet.service.ConverterService.toRepresentation(ConverterService.java:213)
        at org.restlet.resource.UniformResource.toRepresentation(UniformResource.java:667)
        at org.restlet.resource.ServerResource.doHandle(ServerResource.java:464)
        at org.restlet.resource.ServerResource.get(ServerResource.java:645)

It may be the problem solution:

mprzycho 
Post subject: Problem with retrieving properties of task form via REST API
Posted: Mon Aug 22, 2011 7:47 am

I tried to get properties of task from via:
http://localhost:8080/activiti-rest/service/form/{taskId}/properties
I got following exception:
…..
—-
frederikheremans What properties does the task exactly have (keys + values) you were trying to get?
—-
mprzycho Process definition looks like that:….and the problem occurs. When I did couple of changes it worked:

I had to add script before this task and initialize variable, e.g. nameVar.
then I set expression of this task to "${nameVar}".
Now the proper value was returned.
…..
Is it neccessary to both initialize variables (this way or by passing it through start step) and declare task formProperties to get this service done?
—
frederikheremans If you set the variable attr readable to "true", the variable SHOULD exist when the task props are fetched, it expect a variable with that name.