[jbpm-issues] [JBoss JIRA] Assigned: (JBPM-2635) Error deploying a process with a bad version format

[Joram Barrez (JIRA)]

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

Joram Barrez reassigned JBPM-2635:
----------------------------------

    Assignee:     (was: Joram Barrez)


> Error deploying a process with a bad version format
> ---------------------------------------------------
>
>                 Key: JBPM-2635
>                 URL: https://jira.jboss.org/jira/browse/JBPM-2635
>             Project: jBPM
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Runtime Engine
>    Affects Versions: jBPM 4.2
>         Environment: MySQL  Ver 14.12 Distrib 5.0.75, for debian-linux-gnu (i486) using readline 5.2
> Java version "1.6.0_16"
> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
> Java HotSpot(TM) Server VM (build 14.2-b01, mixed mode)
> JBoss AS 4.2.3 GA
> JBoss Portal 2.7.2
> Hibernate Core 3.3.2.GA
> Hibernate EntityManager 3.4.0.GA
> Hibernate Annotations 3.4.0.GA
> Hibernate Validator 3.1.0.GA
> Hibernate Commons Annotations 3.1.0.GA
> Seam 2.2.0.GA
> Richfaces 3.3.1.GA
> Portlet Bridge 1.0.0.CR2
>            Reporter: Javier Alperte
>
> Error uploading a jpdl file with a wrong version format (aka: 1.0.0) which leaves the database inconsistent (bad formatted jpdl file)  and does not let upload a new process definition with the same Name, because the service attempts to retrieve the previous version and throws an exception when parse the file. (NOTE: I am uploading a BAR file and the jpdl file is inside the bar)
> In the RepositorySessionImpl you are doing the following steps:
>            session.save(deploymentImpl); // will also save the attached resources
>            deployerManager.deploy(deploymentImpl);
> That saves the Deployment data before checking the consistency of the jpdl file.

-- 
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