[JBoss Portal] - HelloWorld IPC broken in Portal 2.4 CR1 and CR2
by dclancey
The HelloWorld IPC portlet works in portal 2.2, but seems to be broken in 2.4 CR1 and CR2.
I am running the bundled distribution of JBoss 4.04.GA and Portal 2.4CR2 on Windows XP using JDK 1.5.
Here is the stacktrace:
2006-07-24 21:01:36,953 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/C:/jboss-portal-2.4.0-CR2/server/default/deploy/helloworldipcportlet.sar
| org.jboss.deployment.DeploymentException: no protocol: org/jboss/portal/core/event/PortalEventListenerServiceImpl.xml; - nested throwable: (java.net.MalformedURLException: no protocol: org/jboss/portal/core/event/PortalEventListenerServiceImpl.xml)
| at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)
| at org.jboss.system.ServiceController.install(ServiceController.java:226)
| at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.install(Unknown Source)
| at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249)
| at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
| at sun.reflect.GeneratedMethodAccessor88.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy8.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
| Caused by: java.net.MalformedURLException: no protocol: org/jboss/portal/core/event/PortalEventListenerServiceImpl.xml
| at java.net.URL.<init>(URL.java:567)
| at java.net.URL.<init>(URL.java:464)
| at java.net.URL.<init>(URL.java:413)
| at org.jboss.system.ServiceCreator.install(ServiceCreator.java:206)
| at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449)
| at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
|
Could someone indicate what I need to update between Portal versions?
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960564#3960564
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960564
19 years, 9 months
[JBoss jBPM] - How to dispatch workflows/create an event handler loop?
by ryhadley
When I think of what a workflow engine does, it is essentially an event handler loop that is configured to appropriately dispatch the incoming messages:
event loop
| get message from queue
| handle message by one of:
| - start new workflow, or
| - start next activity in a (suspended) workflow
| repeat
Based on the user guide http://docs.jboss.org/jbpm/v3/userguide/index.html, I can see how to define a workflow (as XML) and give the code behind the activities in the workflow (implement ActionHandler interface), but I don't understand how jBPM takes incoming "messages" and dispatches to the appropriate ActionHandlers. i.e. The user guide only has code snippets that are JUnit tests which create a workflow from an XML definition (ProcessDefinition.parseXmlString()) and then execute the workflow by pushing the token through it with token.signal() (i.e. 3.2. Database example in User Guide); there is no practical code example for a workflow application.
Does jBPM provide such an event loop/dispatch capability? Or do I need to figure out how to implement this myself (using something like the code in ProcessInstanceBean.java, from the webapp example, and tie it into the Scheduler from chapter 12 in the User Guide)? If so, is there a simple example available?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960562#3960562
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960562
19 years, 9 months