Roadmap dates
by Heiko Braun
Did the roadmap change? I remeber a discussion about introducing
another CR.
/Heiko
17 years
[Design of JBoss jBPM] - Re: JBPM4 - org.jbpm.pvm.internal.session.DbSession & org.hi
by galanfish
thanks, shekharv
yes, org.jbpm.pvm.internal.hibernate.DbSessionImpl is an implementation of org.jbpm.pvm.internal.session.DbSession, but maybe you don't understand me(my english is so poor).
what I don't understand is that:
the methods #svae/#delete/#flush/... in DbSessionImpl are delegated forward to the corresponding method(same method name) call of org.hibernate.Session, it seems the author would like to see DbSession rather than org.hibernate.Session in this program, but why make it internal? and, in modules like pvm/jpdl/enterprise, I found lots of references to org.hibernate.Session directory(in some commands, activities, etc.), which are retrived from the Environment, why not using DbSession instead?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238659#4238659
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238659
17 years
Maven drives me crazy: Negative seek offset
by Bernd Rücker
Hi!
I tried to build the distro and tests locally, but somehow maven doesnt
let me, I have a strange exception when building the docs:
[INFO]
------------------------------------------------------------------------
[INFO] Building jBPM 4 - Developers Guide
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
[INFO] [site:attach-descriptor]
[INFO] [javadoc:jar {execution: attach-javadocs}]
[INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[WARNING] POM for 'org.jboss:jbossorg-docbook-xslt:pom:1.1.0:compile' is
invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0
POM. for project org.jboss:jbossorg-docbook-xslt at C:\Dokumente und
Einstellungen\ruecker\.m2\repository\org\jboss\jbossorg-docbook-xslt\1.1.0
\jbossorg-docbook-xslt-1.1.0.pom
[WARNING] POM for 'org.jbpm.jbpm4:docbook-style:pom:1.0.0:compile' is
invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0
POM. for project org.jbpm.jbpm4:docbook-style at C:\Dokumente und
Einstellungen\ruecker\.m2\repository\org\jbpm\jbpm4\docbook-style\1.0.0\do
cbook-style-1.0.0.pom
[INFO] [jdocbook:resources {execution: default}]
[INFO] unpacking dependency resource [C:\Dokumente und
Einstellungen\ruecker\.m2\repository\org\jbpm\jbpm4\docbook-style\1.0.0\do
cbook-style-1.0.0.jdocbook-style] to staging-dir
[D:\Projekte\jbpm4\modules\devguide\target\docbook\staging]
[INFO] Expanding: C:\Dokumente und
Einstellungen\ruecker\.m2\repository\org\jbpm\jbpm4\docbook-style\1.0.0\do
cbook-style-1.0.0.jdocbook-style into
D:\Projekte\jbpm4\modules\devguide\target\docbook\staging
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Rendering problem
Embedded error: Error unpacking file [C:\Dokumente und
Einstellungen\ruecker\.m2\repository\org\jbpm\jbpm4\docbook-style\1.0.0\do
cbook-style-1.0.0.jdocbook-style] to
[D:\Projekte\jbpm4\modules\devguide\target\docbook\staging]
Negative seek offset
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 48 seconds
[INFO] Finished at: Wed Jun 17 17:37:12 CEST 2009
[INFO] Final Memory: 35M/63M
[INFO]
------------------------------------------------------------------------
Any hints?
Cheers
Bernd
17 years
[Design of JBoss jBPM] - Re: Undeployment in JBosss Deployer
by heiko.braun＠jboss.com
anonymous wrote :
| you can reactivate it if it was by mistake
|
Why should it be different then any other Java EE deployment? You guys always try to come up with extraordinary requirements for processes. If you delete an EAR there is no backup either. I think people are smart enough to understand the impact.
But in general you should discuss wether or not to keep the deployer at all.
The way it was written, it did intend additional changes to the core runtime. Especially classloader association upon deployment. In order to get the classloader scoping right, we would need to associate the classloader that the deployer framework provides and not write class info to the database. Similiar to what Bernd did to jbpm3.
If we would complete it in that way, the question of deletion versus suspension would become different.
But honestly, that whole deployment discussion has been going on since december last year and I am tired of repeating myself.
I'd say either you complete the deployer or you remove it at all.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238448#4238448
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238448
17 years
[Design of JBoss jBPM] - Blank page issues in console CR1
by heiko.braun＠jboss.com
Here's the actual fix for the blacnk page problem on IE and FF 3.x.
The closing script tags have been missing:
| Bonanova:war hbraun$ svn diff -r4964:5056
| Index: src/main/resources/org/jboss/bpm/console/public/Application.html
| ===================================================================
| --- src/main/resources/org/jboss/bpm/console/public/Application.html (revision 4964)
| +++ src/main/resources/org/jboss/bpm/console/public/Application.html (revision 5056)
| @@ -3,14 +3,14 @@
| <title>GWT Console Application</title>
|
| <!-- BPM console configuration -->
| - <script type="text/javascript" src="console.config.js"/>
| + <script src="console.config.js" type="text/javascript"></script>
|
| <!-- -->
| <!-- This script loads your compiled module. -->
| <!-- If you add any GWT meta tags, they must -->
| <!-- be added before this line. -->
| <!-- -->
| - <script language='javascript' src='org.jboss.bpm.console.Application.nocache.js'/>
| + <script src="org.jboss.bpm.console.Application.nocache.js" type="text/javascript"></script>
|
| <link rel="stylesheet" href="console.css" type="text/css">
|
|
It's been commited to trunk.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238442#4238442
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238442
17 years
