topic Re: Problems with 5.12 demo in Alfresco Archive

Problems with 5.12 demo

groopk — Mon, 18 Mar 2013 19:40:33 GMT

The Simple Approval Demo example is new in the 5.12 distro, and includes a form type of "user". When we run a fresh download & install of activiti, we get a console full of errors related to this. Are we missing something or is something missing from the distro?It also prevents us from accessin

Re: Problems with 5.12 demo

jbarrez — Wed, 20 Mar 2013 08:59:03 GMT

The custom form types are plugged into the engine in the spring config of the Explorer app:

 <bean id="formPropertyRendererManager" class="org.activiti.explorer.ui.form.FormPropertyRendererManager" lazy-init="true">
       …
    <property name="propertyRenderers">
      <list>
        …
        <bean class="org.activiti.explorer.ui.form.UserFormPropertyRenderer" />
        ….
      </list>
    </property>
  </bean>

And that bean is plugged into the process engine configuration.

Are you using Explorer with a custom configuration? Because out of the box it should work as far as I can see.

Re: Problems with 5.12 demo

groopk — Wed, 20 Mar 2013 14:57:50 GMT

We have both the activiti-explorer and activiti-rest deployed, pointing at the same database. Perhaps this is not how they were intended to be used?

We ended up just turning off the demoProcessDefinition/Model/Report Data generation inside activti-explorer and redeployed everything on a fresh database and now it seems to be fine.

Re: Problems with 5.12 demo

jbarrez — Thu, 21 Mar 2013 11:26:54 GMT

Ah yes, I discovered that problem too recently. If you want to point them to the same db, then indeed the rest config must be adapted to also know these form types. Which is not a good thing.

I've got it on my list to fix very soon, as it struck me too.

Indeed disabling the demo data would also do the truck, as it only would be used when you actually have a process with a user form property type (which the demo data has)

Re: Problems with 5.12 demo

non — Tue, 21 May 2013 12:21:29 GMT

Any ideas for an absolute beginner to get explorer+rest+demos run?

Got activiti-explorer and activiti-rest up and running sharing a postgresql database, but can't play with REST.

(After a longer reading trip around the camunda fork story, I arrived back at activiti and plan to stay )

Re: Problems with 5.12 demo

frederikherema1 — Wed, 22 May 2013 06:11:33 GMT

What do you mean by "can't play with rest"?

Re: Problems with 5.12 demo

non — Wed, 22 May 2013 08:13:59 GMT

Please see initial question. I'm faced with the same problems:
> unknown type 'user' approver

I think the problem is the missing component from activiti-explorer. But:
* Howto add the missing component to activiti-rest?
* How much sense does it make to add an ui component to the REST API?

At the end I want to have 1 database and 1 process-engine accessed by explorer and rest-api.

Re: Problems with 5.12 demo

jbarrez — Wed, 22 May 2013 15:08:33 GMT

Are you using 5.12.1? The rest service there contains a DemoDataGenerator bean which installs some demo users.

To work on the same database, simply adapt db.properties on both rest and explorer wars and point them to the same db (eg local mysql)

Re: Problems with 5.12 demo

non — Wed, 22 May 2013 16:37:22 GMT

Yes. I'm using the current version.

Let me repeat myself, more verbose this time: I followed the documentation and got activiti-explorer up in a few minutes; with demo data. Everything works as expected.
Then I wanted to test the REST API: I deployed activiti-rest to tomcat and intuitively expected to get access to the same process instances, status, etc.. What I got was a second independent in-memory database. Next step: Set up a postgres user and database and configured those into both: activiti-rest and activiti-explorer. Now I can authenticate as "kermit" and access SOME data from the activiti-explorer, because of the problem from the beginning of this threat:

org.activiti.engine.ActivitiIllegalArgumentException: unknown type 'user' approver

As I understood from above, this is because demo data from activiti-explorer is somehow bound to components that only exist in activiti-explorer and not in activiti-rest:

org.activiti.explorer.ui.form.UserFormPropertyRenderer

Now I could delete demo data and start with a clean database (as suggested). But I got another problem: I'm not feeling comfortable with the idea of running two process engines on the same database (and same data). What I could find in the forums is, that it should be fairly easy to pick the components of both (explorer and rest) and put them in one webapp with only one process engine running. The only thing missing is a description of these easy steps.
And maybe even demo data don't crashes the REST API anymore in this combined webapp.

Re: Problems with 5.12 demo

frederikherema1 — Thu, 23 May 2013 06:57:22 GMT

If you take over the "userType" configuration (not renderer, but the actual type), the REST-webapp wil work independently on the same database. It's perfectly fine to have 2 engines pointing at the same DB, nothing to be uncomfortable about. Offcourse, it's indeed possible to combine both explorer and rest into a single war-file.

Re: Problems with 5.12 demo

jbarrez — Thu, 23 May 2013 07:12:25 GMT

That's why I asked which version you are running on: I assumed we had the error fixed on Activiti 5.12.1. But it seems you are hitting it (altough i did remember I tested it).

We have split up the webapps on purpose: most people want only the rest api or explorer, not the both combined.
You can indeed combine both web applications. But as it is a standard Java webapp, it's basically just creating a standard WAR.

But your point is valid: this stuff should be easier. I'll look into it and see if I can write something down.

Re: Problems with 5.12 demo

non — Thu, 23 May 2013 07:37:32 GMT

OK. Thank you.

Re: Problems with 5.12 demo

non — Thu, 23 May 2013 07:50:05 GMT

Thanks.

A short step-by-step guide leading to the combined solution would help a lot.

At the moment I'm not a day-by-day java developer and don't know all concepts by rote. Now I got everything up in eclipse, created a webapp project and added all the dependent libs from the war files and the configuration files to the webapps/WEB-INF folder. (before I tried automatic maven dependency resolution, but failed )

The app loads perfectly in tomcat now, but complains about "org.activiti.engine.ActivitiException: No router defined" when I try to access "/service"

To be continued…

Re: Problems with 5.12 demo

rookies — Thu, 23 May 2013 08:47:51 GMT

I met this problem today.
error message :
"
2013-05-23 15:37:19 [org.activiti.engine.impl.interceptor.CommandContext]-[ERROR] Error while closing command context
org.activiti.engine.ActivitiIllegalArgumentException: unknown type 'user' approver
"

I fixed the problem by deleting all demo data on activiti-explorer…deploy a process without any form…

suggestion:
1.mention that "activiti-explorer and activiti-rest use different h2 db even though deploy on same webserver(eg.tomcat)" in user guide
2.mention that"activiti-rest rest api just a demo for show, you should modify db.properties to the same db both on activiti-explorer and activiti-rest if you want to get the "correct" result"

ps.
1.when this problem will be fixed?
2.do you fill a little strange when you should delpoy jar both on activiti-rest and activiti-explorer web app lib?
3.is there a combined version for activiti-rest and activiti-explorer?

Re: Problems with 5.12 demo

frederikherema1 — Tue, 04 Jun 2013 13:33:02 GMT

You should call ann actual REST-service method, rather than the root "/services"…

Re: Problems with 5.12 demo

joshgubler — Thu, 08 Aug 2013 17:24:31 GMT

Hey Joram,

I'm still seeing this issue in 5.13. I've worked around it by undeploying the demo processes.

-Josh

Re: Problems with 5.12 demo

b_schnarr — Mon, 10 Feb 2014 14:07:12 GMT

Is there any progress on this issue? Tried with activiti 5.14 and the REST-Calls still crashes with the demo data. Same deplyoment as described above: both web apps share the same db.
It would be very useful if the user form type could be used in the rest app. Especially for document-approval processes, the user form type is very important.
Therefore, it would be great if you could integrate this form type in the rest web app.

Re: Problems with 5.12 demo

trademak — Tue, 11 Feb 2014 15:25:56 GMT

For 5.15 we've added these form types to the REST app as well.

Best regards,