Current state of the POJO API?

[ogeisser]

Hi,

what is the current state of the POJO API?

In 5.0 RC 1 the user guide still talks about POJO API (chapter "Process Virtual Machine API"), but the example does not work anymore. The ProcessDefinitionBuilder is gone.

I've read about the project/module restructuring (PVM out/in) but I'm not quite sure what this means for the POJO API use case (process definitions configured via code, no persistence for process execution).

What is the current state?
What are the plans and timeframes in the future?

Thanks for the clarification.

Greetings
Olli

[ogeisser]

Hi,

to follow up my own question.

When I say "ProcessDefinitionBuilder is gone" I mean the Javadocs.

It's still there in the org.activiti.engine.impl.pvm package.

What I want to know is:

If we have a need for the POJO API use case shall we use this package?
Because from the name of the package (and the absence from the javadocs) I assume it's only internal and we should not rely on this API.

Are there any alternatives now or in the future?

Could someone from the core developers clarify the situation, please?

Thank you
Olli

[jbarrez]

The reason why it is moved to the internal package, is because we don't want to give the POJO API the same stability guarantees as the service API.
That's also the reason why it is gone from the javadocs.

Don't get me wrong, the POJO is API is something we definitely like and want to keep in Activiti!
It's just that at this point in time, we want to expose the BPMN 2.0/service API as our primary API.

[tombaeyens]

don't expect the pojo api to be stable in the next year.

http://forums.activiti.org/en/viewtopic.php?f=4&t=382