[Design of JBoss jBPM] - Re: MessageService and JMS
by mteira
Everything seems to build correctly now.
But I've followed the same workflow (adding your -1 and 0 steps) and the error remains the same:
10:12:21,208 INFO [EARDeployer] Init J2EE application: file:/C:/apps/jboss-4.0.
| 4.GA/server/jbpm/deploy/jbpm.ear
| 10:12:21,228 ERROR [MainDeployer] Could not initialise deployment: file:/C:/apps
| /jboss-4.0.4.GA/server/jbpm/deploy/jbpm.ear
| org.jboss.deployment.DeploymentException: Invalid module content, must be one of
| : ejb, web, java, connector, service, har,
It seems that war is not a recognized module type for the application.xml, at least for what's recognized by my Jboss (and it's the one installed using jbpm itself).
It sound really strange that the host operating system could be the cause (as it's failing in my solaris and windows deployments). Aren't you able to reproduce the error following the same steps:
1.-Checkout a fresh CVS HEAD.
2.-Delete the ${user.home}/jbpm/repository/jbpm directory. actually the clover subdirectory doesn't have to be deleted. but the other directories might contain old versions of snapshot builds that are used instead of the newly stuff that is build from the sources.
3.-Do ant get.dependencies in the build/build.xml
4.-Run 'ant package' at jpdl/dist.
5.-Run 'ant install.jboss.and.configure.jbpm' in 'jboss/configuration'
A fresh jboss install appeared at C:\apps\jboss-4.0.4.GA
6.-Run 'ant' at 'enterprise/ear' to get the jbpm.ear built.
7.-Inside C:\apps\jboss-4.0.4.GA\server\jbpm\deploy:
Delete the jbpm-console.war (as it is included in the jbpm.ear)
Copy the generated jbpm.ear at ${user.home}/jbpm/repository/jbpm/enterprise\3.2-Alpha1-SNAPSHOT
to C:\apps\jboss-4.0.4.GA\server\jbpm\deploy.
8.-Start jboss running:
C:\apps\jboss-4.0.4.GA\bin\run.bat -c jbpm
Regards.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972842#3972842
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972842
19 years, 6 months
[Design of JBossCache] - SingletonStoreCacheLoader in 2.0
by galder.zamarreno@jboss.com
Couple of things came to my mind while I was coding this:
- AsyncCacheLoader and SingletonStoreCacheLoader share the same
paradigm in that none of them write to the actual store, but delegate to an
underlying cache loader. I thought about extending the CacheLoader
interface, creating an interface named DelegatingCacheLoader. This would
containg a getCacheLoader() method that would return the underlying
CacheLoader instance. This would also simplify
CacheLoaderInterceptor.isCustomCacheLoaderConfigured() implementation
as the instanceOf would be done by DelegatingCacheLoader instead of the
individual caches.
- Also, let's say a customer creates a singleton and async cacheloader. The
delegating order should not be any problem, but I'd quite likely have singleton
on top so that if the node is not the coordinator, don't even bother with the
async layer.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972839#3972839
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972839
19 years, 6 months