[JBoss JIRA] Created: (JBPM-2020) fix timer mapping
by Tom Baeyens (JIRA)
fix timer mapping
-----------------
Key: JBPM-2020
URL: https://jira.jboss.org/jira/browse/JBPM-2020
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Priority: Minor
Fix For: jBPM 4.0.0 Alpha2
As a subclass of JobImpl, TimerImpl will be save to the table of JBPM_JOB ,according to the jbpm.pvm.job.hbm.xml.
However ,there is a one-to-many between TimeImpl and ExecutionImpl, so ,hibernate will know that the ExecutionImpl's timers will be associate to the EXECUTION_ field of JBPM_JOB.
If there is a many-to-many mapping, the table of <set> will be necessary, in this case ,it acts as a association of JBPM_JOB and JBPM_EXECUTION.
table="JBPM_TIMER" must be not necessary. when setting hibernate.hbm2ddl.auto=" create-drop", there no table named JBPM_TIMER be created.
So I think you maybe wrong here.
Best wishes!
-----Original Message-----
From: Tom Baeyens [mailto:tbaeyens@redhat.com]
Sent: Friday, February 06, 2009 4:01 PM
To: aximo.yang
Subject: Re: jbpm4 hibernate mapping file seem not current
i think it is must be there.
regards, tom.
aximo.yang wrote:
> >
> >
> > Hi,
> >
> > I am look the the codes of jbpm4 alpha1 and find that there is unheeding
> > mistake in jbpm.pvm.execution.hbm.xml:
> >
> > < property name = / "hasTimers" / column = / "HASTIMERS_" / />
> >
> > < set name = / "timers" /
> >
> > cascade = / "all-delete-orphan" /
> >
> > table=/"JBPM_TIMER"/>
> >
> > < key foreign-key = / "FK_TMR_EXECUTION" / >
> >
> > < column name = / "EXECUTION_" / />
> >
> > </ key >
> >
> > < one-to-many class = / "org.jbpm.pvm.internal.job.TimerImpl" / />
> >
> > </ set >
> >
> > The table doesn't assigned , for the Hibernate will ignore it ,so there
> > will be not mistake, but make someboby wondering.you can just delete it
> > ,is right?
> >
--
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
15 years, 10 months
[JBoss JIRA] Created: (JBPM-2046) setting the name of a transaction to an unchanged value through the api results in an faulty exception
by Tom Eugelink (JIRA)
setting the name of a transaction to an unchanged value through the api results in an faulty exception
------------------------------------------------------------------------------------------------------
Key: JBPM-2046
URL: https://jira.jboss.org/jira/browse/JBPM-2046
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.3.1 GA
Environment: WindowsXP
Reporter: Tom Eugelink
Priority: Minor
Setting the name of a transition to the value it already has, results in an exception:
Exception in thread "AWT-EventQueue-0" java.lang.IllegalArgumentException: couldn't set name 'state2_to_join1' on transition 'Transition(state2_to_join1)'cause the from-node of this transition has already another leaving transition with the same name
at org.jbpm.graph.def.Transition.setName(Transition.java:223)
at nl.innovationinvestments.jbpm.Jbpm3Editor$1.invoke(Jbpm3Editor.java:131)
at com.mxgraph.util.mxEventSource.fireEvent(Unknown Source)
at com.mxgraph.util.mxEventSource.fireEvent(Unknown Source)
at com.mxgraph.model.mxGraphModel$1.dispatch(Unknown Source)
at com.mxgraph.model.mxGraphModel.endUpdate(Unknown Source)
at com.mxgraph.swing.mxGraphComponent.labelChanged(Unknown Source)
at com.mxgraph.swing.view.mxCellEditor.stopEditing(Unknown Source)
at com.mxgraph.swing.mxGraphComponent.stopEditing(Unknown Source)
at com.mxgraph.swing.mxGraphComponent$6.mouseReleased(Unknown Source)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:273)
....
The exception is quite right, the leaving transition is itself. This naturally is easily fixable, by comparing if the name is identical, but IMHO is the check not correct; it should not validate against itself.
--
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
15 years, 10 months
[JBoss JIRA] Commented: (JBPM-2050) distributed examples cannot be compiled
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-2050?page=com.atlassian.jira.plug... ]
Thomas Diesler commented on JBPM-2050:
--------------------------------------
Please note, that this relies on the given version already being released and uploaded to the repository.
For local testing you need to run
> mvn -DskipTests install
on the branch that you build the distribution with
i.e.
> mvn -Pdistro install
> distributed examples cannot be compiled
> ---------------------------------------
>
> Key: JBPM-2050
> URL: https://jira.jboss.org/jira/browse/JBPM-2050
> Project: JBoss jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Productization
> Reporter: Jiri Pechanec
> Assignee: Thomas Diesler
> Fix For: jBPM-3.2.5.SP2, jBPM 3.2.6 GA
>
>
> If I try to compile jBPM exmaples in the directory jbpm-jpdl/examples the build process fails with message
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.jbpm.jbpm3:jbpm for project: org.jbpm.jbpm3:jbpm-examples:jar:null for project org.jbpm.jbpm3:jbpm-examples:jar:null
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.jbpm.jbpm3:jbpm for project: org.jbpm.jbpm3:jbpm-examples:jar:null for project org.jbpm.jbpm3:jbpm-examples:jar:null
> at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370)
> at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821)
> at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
> at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
> at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> The pom.xml contains the defintion of parent project
> <!-- Parent -->
> <parent>
> <groupId>org.jbpm.jbpm3</groupId>
> <artifactId>jbpm</artifactId>
> <version>3.2.5.SP1</version>
> <relativePath>../../pom.xml</relativePath>
> </parent>
> But the file does not exist
--
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
15 years, 10 months
[JBoss JIRA] Updated: (JBPM-2050) distributed examples cannot be compiled
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-2050?page=com.atlassian.jira.plug... ]
Thomas Diesler updated JBPM-2050:
---------------------------------
Fix Version/s: jBPM-3.2.5.SP2
> distributed examples cannot be compiled
> ---------------------------------------
>
> Key: JBPM-2050
> URL: https://jira.jboss.org/jira/browse/JBPM-2050
> Project: JBoss jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Productization
> Reporter: Jiri Pechanec
> Assignee: Thomas Diesler
> Fix For: jBPM-3.2.5.SP2, jBPM 3.2.6 GA
>
>
> If I try to compile jBPM exmaples in the directory jbpm-jpdl/examples the build process fails with message
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.jbpm.jbpm3:jbpm for project: org.jbpm.jbpm3:jbpm-examples:jar:null for project org.jbpm.jbpm3:jbpm-examples:jar:null
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.jbpm.jbpm3:jbpm for project: org.jbpm.jbpm3:jbpm-examples:jar:null for project org.jbpm.jbpm3:jbpm-examples:jar:null
> at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370)
> at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821)
> at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
> at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
> at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> The pom.xml contains the defintion of parent project
> <!-- Parent -->
> <parent>
> <groupId>org.jbpm.jbpm3</groupId>
> <artifactId>jbpm</artifactId>
> <version>3.2.5.SP1</version>
> <relativePath>../../pom.xml</relativePath>
> </parent>
> But the file does not exist
--
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
15 years, 10 months
[JBoss JIRA] Resolved: (JBPM-2050) jBPM exmaples cannot be compiled
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-2050?page=com.atlassian.jira.plug... ]
Thomas Diesler resolved JBPM-2050.
----------------------------------
Resolution: Done
Done
<!--
Repositories
[JBPM-2050] jBPM exmaples cannot be compiled
-->
<repositories>
<repository>
<id>repository.jboss.org</id>
<url>http://repository.jboss.org/maven2</url>
</repository>
</repositories>
> jBPM exmaples cannot be compiled
> --------------------------------
>
> Key: JBPM-2050
> URL: https://jira.jboss.org/jira/browse/JBPM-2050
> Project: JBoss jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Productization
> Reporter: Jiri Pechanec
> Assignee: Thomas Diesler
> Fix For: jBPM 3.2.6 GA
>
>
> If I try to compile jBPM exmaples in the directory jbpm-jpdl/examples the build process fails with message
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.jbpm.jbpm3:jbpm for project: org.jbpm.jbpm3:jbpm-examples:jar:null for project org.jbpm.jbpm3:jbpm-examples:jar:null
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.jbpm.jbpm3:jbpm for project: org.jbpm.jbpm3:jbpm-examples:jar:null for project org.jbpm.jbpm3:jbpm-examples:jar:null
> at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370)
> at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821)
> at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
> at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
> at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> The pom.xml contains the defintion of parent project
> <!-- Parent -->
> <parent>
> <groupId>org.jbpm.jbpm3</groupId>
> <artifactId>jbpm</artifactId>
> <version>3.2.5.SP1</version>
> <relativePath>../../pom.xml</relativePath>
> </parent>
> But the file does not exist
--
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
15 years, 10 months