[Design of JBoss jBPM] - Re: Classloader-Registry in AS/ESB allows one central jbpm i
by camunda
In our current project we have the following concept for versioning (sorry for not posting that the first place):
Versioning is applied to applications and services, normally correspond to one EAR (with Java classes, maybe web pages, wsdl, whatever. Depends on the kind of service). There are two versioning schemes:
1.) Major Versions: Bigger changes. These may be not compatible. New major versions may be run in parallel to older services.
2.) Minor versions = patches. These are patches, bug fixes or compatible changes. New Minor versions replace the existing service.
The EAR includes the version in its name, so all beans and stuff include the version in the JNDI-Name. jBPM-processes are included in this EAR. New major versions will create new processdefinition names (basically the version is added to the process name, e.g. "websale_3"). "Normal" jbpm versioning is only applied on patch level.
anonymous wrote : It is a more generic problem than just jBPM.
Exactly, normally you have to take care of versioning for a lot of artefacts, so I think this solution makes sense... And I like having bytecode and classpath stuff in EAR files more than in the jBPM database...
anonymous wrote : So maybe we could come up with something together with the seam guys
Yeah, maybe. But I think it is not only seam, but much more. Especially if you look into the direction of the ESB with whatever services connected to it. This direction (to the backend) is also very interessting.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179617#4179617
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179617
16 years, 2 months
[Design of POJO Server] - Re: JBAS-5953; jar override issue
by adrian@jboss.org
I don't see the crash problem that Shelley is seeing,
but I do see the test failing.
If I put a sleep between the copy of the file and redeploy,
then the test passes.
| [ejort@warjort testsuite]$ svn diff
| Index: src/main/org/jboss/test/jmx/test/UndeployBrokenPackageUnitTestCase.java
| ===================================================================
| --- src/main/org/jboss/test/jmx/test/UndeployBrokenPackageUnitTestCase.java (revision 78789)
| +++ src/main/org/jboss/test/jmx/test/UndeployBrokenPackageUnitTestCase.java (working copy)
| @@ -152,6 +152,8 @@
|
| Files.copy(goodjar, thejar);
| getLog().info("Redeploying testPackage: " + testPackage);
| +
| +Thread.sleep(10000);
|
| redeploy(testPackage);
| Object home = getInitialContext().lookup("EntityA");
|
So this is clearly either a caching issue inside the VFS/JDK
or there is some issue with the Files.copy() not flushing properly to the file system
so the server is seeing a corrupt file.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179581#4179581
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179581
16 years, 2 months