after some digging around, it seems the schema used by jbpm-starters-kit-3.1.4 does not deal with mail (http://docs.jboss.org/jbpm/xsd/jpdl-3.1.xsd) whereas the 3.2 schema does... (http://docs.jboss.org/jbpm/xsd/jpdl-3.2.xsd).
As I am a newbie unfortunately, I am not sure how to use the 3.2 schema with my webapp, which is a slightly tweaked version of the one that comes as standard in jbpm-starters-kit-3.1.4.
Is it as simple as changing the schema referenced in my procesDefinition inside eclipse ?
I am guessing that when I upload the process definition to the servlet in the webapp, that the schema to reference gets stored away somewhere in the database? Therefore I may need to also udate my mysql db to cope with the new schema.. sorry guessing,
any help is greatly appreciated,
by using the 3.2 starterkit?
point taken :-)
I will investigate with the latest version
The xml will not be validated against the schema if you manually remove the reference that has been generated by the visual designer (by editing the source tab). But anyway, mail is only supported since 3.2 AFAIR, so you might have to switch to the latest release anyway if you want mail.
I am now running jbpm-jpdl-3.2.GA to check out mail jpdl functionality for events, I designed a simple processDefinition in the eclipse plugin, and deployed, only to get the following exception.. can anyone provide a solution to this?
13:56:09,712 DEBUG [DbPersistenceService] committing hibernate transaction
13:56:09,720 ERROR [DbPersistenceService] hibernate commit failed
org.hibernate.HibernateException: instance not of expected entity type: org.jbpm.graph.action.MailAction is not a: org.jbpm.graph.def.Action
your help is appreciated,
Oh.... shoot, sorry... this was a problem in 3.2GA, you should use 3.2.1.... fixed there
excellent, just tried 3.2.1, deploys fine, thanks for that