[Design of JBoss jBPM] - Re: Command facade API
by heiko.braun@jboss.com
This thread has been hijacked by the discussion about the WS facade. However I would like to get back my initial concern, which is the current command API in place and especially the detyped nature of the pattern.
I stumbled across a quiet good explanation of my concerns here: http://fiatdev.com/2005/06/15/the-ambiguous-command-anitpattern
In short here's few things that are really bad with the pattern as it's used right now:
* Ambiguity: Both command parameters as well as return values are ambiguous. You actually need to know the command implementation and the final receiver in order to work with the API
* The orig pattern works best for unidirectional, fire/forget style invocations. I.e. things that should be queued. But we are looking at a broad range of uses cases here.
* Currently it exposes too much implementation details. If you combine this with lack of type safety, you get the perfect mess. No control what so ever.
>From my understanding the command API should become a central piece to interact with JBPM. In that case I would reconsider this approach and maybe drop the command pattern at all and actually chose quiet the opposite solution:
Use well specified, strongly typed API that allows the callee to work with a blackbox JBPM.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132172#4132172
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132172
18 years, 1 month
[Deployers on JBoss (Deployers/JBoss)] - Re: HOWTO deploy webapp dynamically
by thomas.diesler@jboss.com
I am getting further. The endpoint deploys
| 14:32:59,417 INFO [TomcatDeployment] deploy, ctxPath=/jaxws-endpoint-servlet, vfsUrl=
| 14:33:00,357 INFO [DefaultEndpointRegistry] register: jboss.ws:context=jaxws-endpoint,endpoint=EndpointBean
|
However, there seems to be a problem with the JACC service
| 14:33:00,690 ERROR [AbstractKernelController] Error installing to Instantiated: name=jboss.jacc:id=endpoint-deployment,service=jacc state=Described mode=Manual requiredState=Configured
| org.jboss.deployment.DeploymentException: Unable to createMBean for jboss.jacc:service=jacc,id=endpoint-deployment
| at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:52)
|
| ...
|
| Caused by: javax.management.InstanceNotFoundException: jboss:service=defaultClassLoader is not registered.
| at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:529)
| at org.jboss.mx.server.MBeanServerImpl.getClassLoader(MBeanServerImpl.java:1094)
| at org.jboss.system.ServiceCreator.installPlainMBean(ServiceCreator.java:191)
| at org.jboss.system.ServiceCreator.install(ServiceCreator.java:115)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132169#4132169
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132169
18 years, 1 month