2 Replies Latest reply on Apr 15, 2008 12:55 AM by dougorr

    jbpm component deployment

    dougorr

      I want to configure the list of process definitions and page-flow definitions in a separate resource file instead of the component.xml file.


      I tried to create a jbpm.component.xml file according to the instructions in the 4.3 Fine-grained configuration files section of the Seam Reference guide, but it didn't work. Can you tell me if this is possible?

        • 1. Re: jbpm component deployment
          pmuir

          The file would need to be called org.jboss.seam.bpm.jbpm.component.xml and placed in /org/jboss/seam/bpm.

          • 2. Re: jbpm component deployment
            dougorr

            I created the following xml file:


            
            <components xmlns="http://jboss.com/products/seam/components"
            
                        xmlns:core="http://jboss.com/products/seam/core"
            
                        xsi:schemaLocation=
            
                            "http://jboss.com/products/seam/core http://jboss.com/products/seam/core-1.2.xsd">
            
            
               <!-- For use with jBPM pageflow or process management -->
            
               <core:jbpm>
            
                  <core:process-definitions></core:process-definitions>
            
                    <core:pageflow-definitions>
            
                        <value>newregistration.jpdl.xml</value>
            
                    </core:pageflow-definitions>
            
               </core:jbpm>
            
                  
            
            </components>
            
            



            I named the file org.jboss.seam.bpm.jbpm.component.xml and deployed it in the WEB-INF of the war file in a folder called org/jboss/seam/bpm.


            This did not work.


            I am using Seam 1.2.1 and the jbpm class seems to be in the package called org.jboss.seam.core, so a changed the prefix of the filename and folder and redeployed but this did not work either.


            Can you see any errors in the format of the xml elements?