[jboss-jira] [JBoss JIRA] Resolved: (BPEL-291) Document JBoss AS deployment order feature which causes exceptions upon restart

[Alejandro Guizar (JIRA)]

     [ https://jira.jboss.org/jira/browse/BPEL-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alejandro Guizar resolved BPEL-291.
-----------------------------------

    Resolution: Done


Added to user guide, chapter "Getting started"

> Document JBoss AS deployment order feature which causes exceptions upon restart
> -------------------------------------------------------------------------------
>
>                 Key: BPEL-291
>                 URL: https://jira.jboss.org/jira/browse/BPEL-291
>             Project: JBoss jBPM BPEL
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Documents
>    Affects Versions: jBPM BPEL 1.1 GA
>            Reporter: Alejandro Guizar
>            Assignee: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1.1
>
>
> There is an issue with the deployment order in JBoss AS which results in exceptional behavior upon server restart: WARs are deployed before EARs. The jBPM BPEL classes are deployed in an EAR, whereas the web services provided by each process definition are deployed as WARs. Upon restart, the service WARs get deployed before jbpm-bpel.ear, causing ClassNotFoundExceptions to be thrown around.
> There is no way to fix this on the jBPM side, as it is a JBoss AS *feature*. Fortunately it is easy to change the deployment order in JBoss AS. See the following wiki page for a full description.
> http://wiki.jboss.org/wiki/Wiki.jsp?page=MainDeployerEnhancedSuffixOrder
> The quick and direct solution is:
> 1. Edit <jboss_server_profile>/conf/xmdesc/org.jboss.deployment.MainDeployer-xmbean.xml
> 2. Look for attribute EnhancedSuffixOrder
> 3. Insert suffix jbpm-bpel.ear anywhere you see fit, *before* the .war suffix. For example:
> 250:.rar,300:-ds.xml,400:.jar,450:jbpm-bpel.ear,500:.war,550:.jse,650:.ear,800:.bsh
> Et voilà, jbpm-bpel.ear will be deployed before the .war modules, without affecting the deployment order of other modules. This solution must be documented in the user guide.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira