AnsweredAssumed Answered


Question asked by bcoulson on Mar 18, 2011
Latest reply on Feb 7, 2012 by jalxm

We have been struggling with an issue for a few weeks now and whilst I see alot of other folks have struggled as well, I do not see any solutions. Here is the situation. We have a workflow process that is not being started by Alfresco. When we attempt to deploy it using Eclipse BPM plugin, we get an error as shown in the log below.

SEVERE: Servlet.service() for servlet JBPMDeployProcessServlet threw exception
org.alfresco.service.namespace.NamespaceException: Namespace prefix ipdswf is not mapped to a namespace URI
   at org.alfresco.service.namespace.QName.createQName(
   at org.alfresco.service.namespace.QName.createQName(
   at org.alfresco.repo.workflow.jbpm.JBPMEngine.getTaskDefinition(
   at org.alfresco.repo.workflow.jbpm.JBPMEngine.createWorkflowTaskDefinition(
   at org.alfresco.repo.workflow.jbpm.JBPMEngine.createWorkflowDefinition(
   at org.alfresco.repo.workflow.jbpm.JBPMEngine.createWorkflowDeployment(
   at org.alfresco.repo.workflow.jbpm.JBPMEngine$1.doInJbpm(
   at org.springmodules.workflow.jbpm31.JbpmTemplate$1.doInHibernate(
   at org.springframework.orm.hibernate3.HibernateTemplate.doExecute(
   at org.springframework.orm.hibernate3.HibernateTemplate.execute(
   at org.springmodules.workflow.jbpm31.JbpmTemplate.execute(
   at org.alfresco.repo.workflow.jbpm.JBPMEngine.deployDefinition(
   at org.alfresco.repo.workflow.WorkflowServiceImpl.deployDefinition(
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(
   at java.lang.reflect.Method.invoke(…

The process definition file is below and is in the <tomcat_install>/webapps/alfresco/web-inf/classes/alfresco/extension/workflow/SimpleApproval directory.

<?xml version="1.0" encoding="UTF-8"?>

<process-definition  xmlns=""  name="ipdswf:SimpleApproval">
   <swimlane name="initiator" />

   <swimlane name="managers">
      <assignment class="org.alfresco.repo.workflow.jbpm.AlfrescoAssignment">

   <start-state name="start">
      <task name="ipdswf:submitApprovalTask" swimlane="initiator" />
      <transition name="" to="Submit"></transition>
   <node name="Submit">
      <event type="node-enter">
            <variable name="approveCount" access="read,write"/>
               approveCount = 0;
      <transition name="" to="end1"></transition>

   <end-state name="end1"></end-state>

The workflow model file which is located in the <tomcat_install>/webapps/alfresco/web-inf/classes/alfresco/extension/model directory.

<?xml version="1.0" encoding="UTF-8"?>
<!– Definition of new Model –>
<model name="ipdswf:workflowmodel"

   <!– Optional meta-data about the model –>
   <description>IPDS Workflow Model</description>
   <author>Zunsik Lim</author>

   <!– Imports are required to allow references to definitions in other models –>
      <import uri=""
         prefix="d" />
      <import uri=""
         prefix="bpm" />

   <!– Introduction of new namespaces defined by this model –>
      <namespace uri=""
         prefix="ipdswf" />


      <type name="ipdswf:submitApprovalTask">

The context file which is in the <tomcat_install>/webapps/alfresco/web-inf/classes/alfresco/extension directory.

<?xml version='1.0' encoding='UTF-8'?>

    <!– Registration of new models –>
    <bean id="extension.dictionaryBootstrap" parent="dictionaryModelBootstrap" depends-on="dictionaryBootstrap">
        <property name="models">
   <!– Registration of resource bundles –>
    <bean id="extension.workflowBootstrap"
        <property name="workflowDefinitions">
               <prop key="engineId">jbpm</prop>
               <prop key="location">alfresco/extension/workflows/SimpleApproval/processdefinition.xml</prop>
               <prop key="mimetype">text/xml</prop>
               <prop key="redeploy">true</prop>
        <property name="labels">

We have tried the following.
1. Uninstalled and reinstalled Alfresco
2. Changed the name of the namespace prefix
3. Deployed the process on another local machine with Alfresco. The fact that the error still occurs tells us it is not due to previous existing versions of the model or workflow but rather a data issue, but we can't figure it out! And it's a simple workflow proof of concept at the moment.
4. Tried deploying it as a Spring bean AND via Eclipse plugin, either way, the error persists.

We look at the workflow definitions in the workflow-console and there is no sign of this process.
None of these had any effect - the results were always the same. If anyone could shed some light on this for us, we would greatly appreciate it.