[JBoss AOP] - Re: Problems getting AOP to work on jboss4.0.4GA
by system.out
I have the same problem, using Jboss 4.0.4.GA/Jboss IDE with default config.
Apparently, this has nothing to do with AOP, but as u mentioned with cache features. Here is the error:
--------------------------------------------------------------------------------
00:57:48,078 INFO [JBossCacheManager] init(): replicationGranularity_ is 0 and invaldateSessionPolicy is 2
00:57:48,078 ERROR [JBossCacheManager] JBossCacheService to Tomcat clustering not found
java.lang.NoClassDefFoundError: org/jboss/cache/CacheException
at org.jboss.web.tomcat.tc5.session.JBossCacheManager.init(JBossCacheManager.java:144)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:332)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967392#3967392
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967392
19 years, 8 months
[JBoss Portal] - Unable to set CMS preferences
by PeterJ
Back in 2.4.0CR3, I was able to create a new instance of the CMSPortlet and set the indexPage preference to some other html page.
With 2.4.0GA, and what I loaded from CVS this morning, I can no longer do this. Instead, when I click the Update button after entering in the new html page name, such as /deafult/project.html, I get a huge among of stack trace, part of which is shown:
2006-08-24 20:05:56,875 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/portal-core]] Error calling action method of component with id jbp15f0ce3b_id98:jbp15f0ce3b_id102
| javax.faces.FacesException: Error calling action method of component with id jbp15f0ce3b_id98:jbp15f0ce3b_id102
| at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:74)
| at javax.faces.component.UICommand.broadcast(UICommand.java:106)
| at javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:90)
| at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:164)
| at org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:316)
| at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
| at org.apache.myfaces.portlet.MyFacesGenericPortlet.processAction(MyFacesGenericPortlet.java:221)
| at org.jboss.portal.portlet.container.PortletContainer.invokeAction(PortletContainer.java:494)
| at org.jboss.portal.portlet.container.PortletContainer.dispatch(PortletContainer.java:435)
| at org.jboss.portal.portlet.container.PortletContainerInvoker$1.dispatch(PortletContainerInvoker.java:143)
| at org.jboss.portal.portlet.invocation.PortletInvocation.dispatch(PortletInvocation.java:242)
| ...
| at java.lang.Thread.run(Thread.java:595)
| Caused by: javax.faces.el.EvaluationException: /WEB-INF/jsp/management/plugins/preferences.xhtml @75,70 action="#{action.updateCell}": java.lang.Error: Handle me gracefully please
| at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:73)
| at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:63)
| ... 220 more
| Caused by: java.lang.Error: Handle me gracefully please
| at org.jboss.portal.core.portlet.management.actions.PreferenceAction.updateCell(PreferenceAction.java:147)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at com.sun.el.parser.AstValue.invoke(AstValue.java:130)
| at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:274)
| at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68)
| at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:69)
| ... 221 more
| Caused by: org.jboss.portal.portlet.InvalidPortletIdException: Cannot configure producer offered portlets
| at org.jboss.portal.portlet.state.producer.StatefulPortletInvoker.setProperties(StatefulPortletInvoker.java:477)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| ...
| at $Proxy57.setProperties(Unknown Source)
| at org.jboss.portal.federation.impl.FederatedPortletInvokerService.setProperties(FederatedPortletInvokerService.java:169)
| at org.jboss.portal.federation.impl.FederatingPortletInvokerService.setProperties(FederatingPortletInvokerService.java:179)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| ...
| at $Proxy41.setProperties(Unknown Source)
| at org.jboss.portal.core.impl.model.instance.InstanceImpl.setPreferences(InstanceImpl.java:209)
| at org.jboss.portal.core.portlet.management.actions.PreferenceAction.updateCell(PreferenceAction.java:140)
| ... 229 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967388#3967388
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967388
19 years, 8 months
[JBoss jBPM] - allow swimlanes to perform assignment at each reference?
by stibrian
Swimlanes are a very effective way to perform assignment, and we have implemented several that are nicely reusable.
A swimlane though, isn't always (to my mind) the same actor or actors throughout the life of a process instance. In our case (and we've several use cases where this is applicable) a swimlane may represent an actor(s) that are related to a particular object or object in the process.
The problem arises when the user(s) that are related to said object change in a long-running process.
For example, a long running requisition process. The manager of the user who made the requisition may wish to have notifications as the process goes along (we have integrated email functionality in a custom extension). The most intuitive way to handle this as a process author is to use a swimlane that defines the relationship. The current jBPM TaskMgtInstance will only perform the assignment once per swimlane though, assuming that the SAME actor(s) will be used for the life of the process. Depending on what you're orchestrating, this may not be tenable.
I think at the least there ought to be a way to allow a swimlane to configure a swimlane to perform its work every time it is referenced rather than using the previously determined actor(s).
I've made a modification to jBPM to force swimlane instances to ALWAYS perform assignment, and while this fixes the issue in the short term, eventually I plan to modify either the global config for swimlanes, and better, add an attribute to the swimlane declaration that allows configurable behavior on a swimlane that will override the global default. In this way you could have the current behavior or configure the global setting to behave as I've discussed and provide an override to the current behavior on a case by case basis.
You can get this behavior using nested assignment delegations, but there are reusability issues as well as the general cleanliness of the jPDL language to consider. We think swimlanes are in many cases more intuitive, and make the process definition much more readable.
As we've discussed in internally, this seems reasonable, and seems to be required in a flexible environment supporting long running processes.
What do you think?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967387#3967387
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967387
19 years, 8 months