anonymous wrote : Damn, it seems that linking a Timer to an EJB3 Entity seems not to be possible like in EJB 2.1 (regarding https://jira.jboss.org/jira/browse/JBPM-886 ). In the current implementation the Timer POJO is flushed and loaded as an EJB2 entity bean. It works but looks and feels dirty. If the hack is not easily portable to EJB3 then we should just use two different tables. It does not make sense to sacrifice cleanliness just to save one table. Another thought: the EJB3 stuff should not go into jBPM3, it would mostly bring further maintenance burdens and would certainly not be accepted for inclusion into SOA-P. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209628#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...