[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8330) JBPM 3 process definiton wizard creates files with new (JBPM 4?) naming convention
joe freeman (JIRA)
jira-events at lists.jboss.org
Mon Feb 7 13:10:39 EST 2011
[ https://issues.jboss.org/browse/JBIDE-8330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580563#comment-12580563 ]
joe freeman commented on JBIDE-8330:
------------------------------------
I knew I shouldn't have put that in there! We currently load all processdefinition.xml files on the classpath and not from a DB. Now we need to load against other patterns since there doesn't seem to be a way to create definitions with the old naming conventions.
My main point with this Jira is that someone changed the naming conventions for a "mature" tool without anything obvious showing up in the release notes Jira list. This change along with the one mentioned in JBIDE-8331 have had a real impact on us. I eventually found comments his change in "what's new" but I had to do a lot of searching before I found it.
Our current workaround is to copy/paste existing definitions in the file manager and then edit/delete/insert in Eclipse.
> JBPM 3 process definiton wizard creates files with new (JBPM 4?) naming convention
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-8330
> URL: https://issues.jboss.org/browse/JBIDE-8330
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jbpm
> Affects Versions: 3.2.0.M1, 3.2.0.CR1
> Reporter: joe freeman
> Assignee: Koen Aers
> Fix For: 3.2.1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> We just upgraded to the 3.2.0 JBoss JBPM editing tools and the behavior has changed for the definition creation wizard. It looks like the JBPM 3 wizard now creates files with the JBPM 4 naming convention.It used to create files with the name gpd.xml, processdefinition.xml and processimage.jpg. Now it creates files with <def_name>.jpdl.xml, process.jpg and .<def_name>.gpd.xml.
> This broke our file system loader code and we can't find any release notes or Jira tickets that describe why or when this change was made. I found notes in http://docs.jboss.org/tools/whatsnew/jbpm/jbpm-news-3.2.0.M1.html that show that this was intentional.
> I guess this could be changed to an enhancement that there should have been a property or something to support the old format. This is a moderately large change to a product that is essentially in maint mode.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list