[JBoss jBPM] - Re: Trying to run jbpm outside tomcat on mysql
by dingo001
Upgrade hibernate to the latest, not the old one you have running on ur hdd. for me it was hibernate3.2(latest).
next problem will be no transaction defined or something similar. change the example code to
| jbpmConfiguration = JbpmConfiguration
| .parseXmlString("<jbpm-configuration>"
| +
|
| // A jbpm-context mechanism separates the jbpm core
| // engine from the services that jbpm uses from
| // the environment.
|
| " <jbpm-context>"
| + " <service name='persistence' "
| + " factory='org.jbpm.persistence.db.DbPersistenceServiceFactory' />"
| + " <service name='tx' factory='org.jbpm.tx.TxServiceFactory' />"
| + " </jbpm-context>"
| +
|
| // Also all the resource files that are used by jbpm are
| // referenced from the jbpm.cfg.xml
|
| " <string name='resource.hibernate.cfg.xml' "
| + " value='hibernate.cfg.xml' />"
| + " <string name='resource.business.calendar' "
| + " value='org/jbpm/calendar/jbpm.business.calendar.properties' />"
| + " <string name='resource.default.modules' "
| + " value='org/jbpm/graph/def/jbpm.default.modules.properties' />"
| + " <string name='resource.converter' "
| + " value='org/jbpm/db/hibernate/jbpm.converter.properties' />"
| + " <string name='resource.action.types' "
| + " value='org/jbpm/graph/action/action.types.xml' />"
| + " <string name='resource.node.types' "
| + " value='org/jbpm/graph/node/node.types.xml' />"
| + " <string name='resource.varmapping' "
| + " value='org/jbpm/context/exe/jbpm.varmapping.xml' />"
| + "</jbpm-configuration>");
|
|
well, this fixed it
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073209#4073209
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073209
18Â years, 10Â months
[JBoss jBPM] - Re: Exception when deploying a process definition to Mysql
by dingo001
"sujeewanie" wrote : Ok.Got it again.
| In the jbpm-configuration created by the example, no services are created.
| I commented that code and obtained a context throgh the default settings like
|
| JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
|
| Fanally it works now
Change to this
| jbpmConfiguration = JbpmConfiguration
| .parseXmlString("<jbpm-configuration>"
| +
|
| // A jbpm-context mechanism separates the jbpm core
| // engine from the services that jbpm uses from
| // the environment.
|
| " <jbpm-context>"
| + " <service name='persistence' "
| + " factory='org.jbpm.persistence.db.DbPersistenceServiceFactory' />"
| + " <service name='tx' factory='org.jbpm.tx.TxServiceFactory' />"
| + " </jbpm-context>"
| +
|
| // Also all the resource files that are used by jbpm are
| // referenced from the jbpm.cfg.xml
|
| " <string name='resource.hibernate.cfg.xml' "
| + " value='hibernate.cfg.xml' />"
| + " <string name='resource.business.calendar' "
| + " value='org/jbpm/calendar/jbpm.business.calendar.properties' />"
| + " <string name='resource.default.modules' "
| + " value='org/jbpm/graph/def/jbpm.default.modules.properties' />"
| + " <string name='resource.converter' "
| + " value='org/jbpm/db/hibernate/jbpm.converter.properties' />"
| + " <string name='resource.action.types' "
| + " value='org/jbpm/graph/action/action.types.xml' />"
| + " <string name='resource.node.types' "
| + " value='org/jbpm/graph/node/node.types.xml' />"
| + " <string name='resource.varmapping' "
| + " value='org/jbpm/context/exe/jbpm.varmapping.xml' />"
| + "</jbpm-configuration>");
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073207#4073207
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073207
18Â years, 10Â months
[JBoss Seam] - feature idea - conversation names
by matt.drees
Does anyone else think it'd be useful to let conversations have a logical name?
e.g.
| <begin-conversation name="book room"/>
| or
| @begin(name="book room")
|
Then you could restrict which conversations components can run in.
e.g.
| @Conversational(legalConversations={"book room", "modify booking"})
| or maybe
| <page>
| <legal-conversations>
| <name>book room</name>
| <name>modify booking</name>
| <legal-conversations>
| ...
| </page>
|
This would be particularly helpful for nested conversations. E.g., say 'book room' sometimes has a child conversation 'room preferences', and say you don't want users to access roomPreferences.xhtml unless they're in the 'room preferences' conversation. Note that conversation-required isn't helpful here, because there *is* a conversation, but it's the wrong one. In this case, you could redirect to no-conversation-view-id, or maybe make a wrong-conversation-view-id attribute.
Note that this is just an idea I was thinking about; I haven't run into a business requirement for this. And I think you could probably imitate most of this already with a conversation-scoped ConversationName component and page actions. But the syntax seems handy. And it seems like your code might be more self-documenting this way, and it would probably help identify programmer errors more quickly (I've had some frustrating debugging sessions resulting from components being put in a parent conversation instead of the child one).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073197#4073197
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073197
18Â years, 10Â months