June 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBoss jBPM] - Re: New console snapshot published, Task Forms included

by heiko.braun＠jboss.com

anonymous wrote : | One question: What if the task name contain spaces or stuff like that? | | Is it possible (or planned) to provide a mapping between task names and forms? Use case is to use the same form in different tasks (if you make it a bit generic, thats not unusual). | right. it breaks, when the name contains spaces. but I agree, instead of working around that, we should come up with a reasonable solution that covers your use case as well. maybe a resource declaration at process level, with an ID attribute which can be referenced within the task declaration, i.e.: | <process> | <resources> | <resource id="loan-template" name="loan_request_form.ftl"/> | </resources> | [...] | <task name="Verify Loan Request"> | <form-template ref="loan-template"/> | </task> | [...] | </process> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239040#4239040 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239040

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: New console snapshot published, Task Forms included

by camunda

And a second important feature to me: It would be good, if we can signal to Executions in a generic way again. Pretty interessting for showcases :-) Maybe the same goes for completing tasks in case there is no task form configured. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239033#4239033 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239033

16 years, 9 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Parallel deployments

by kabir.khan＠jboss.com

I have a few questions regarding the executor. In the case where a context is asynchronous, and there is no executor in the controller, we decided to log a warning and to deploy the context as normal (i.e. not in a thread). What to do if the executor "is full" and throws a RejectedExecutionException? Log warning and deploy as normal? Also, the executor is currently only set on the main controller. How should asynchronous deployments be handled in a scoped/child controller? Search the parents until an executor is found? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239032#4239032 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239032

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Exception while deploying console from HEAD

by camunda

Hi! Since the CR1 release of the console shows only a blank screen I thought I just use CR2. Hmm, not in the Maven repository. Okay, no problem, building it on my own I thought, maybe interesting anyway... After struggeling with Maven (it always wants to download the 1.1.0-SNAPSHOT instead of using the one, I installed locally in my repos, at the end I used the offline switch) I got it to create a distro with this console. Installing it via the distro, starting up JBoss 5.1 I see the following exception during deployment of the gwt-console-server: Any ideas what to do? | 12:22:24,515 ERROR [[/gwt-console-server]] Exception sending context initialized event to listener instance of class org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap | java.lang.Error: Unresolved compilation problems: | Access restriction: The type DataHandler is not accessible due to restriction on required library C:\java\jdk1.6.0_07\jre\lib\rt.jar | Access restriction: The type DataSource is not accessible due to restriction on required library C:\java\jdk1.6.0_07\jre\lib\rt.jar | Access restriction: The type DataHandler is not accessible due to restriction on required library C:\java\jdk1.6.0_07\jre\lib\rt.jar | Access restriction: The method getDataSource() from the type DataHandler is not accessible due to restriction on required library C:\java\jdk1.6.0_07\jre\lib\rt.jar | Access restriction: The type DataHandler is not accessible due to restriction on required library C:\java\jdk1.6.0_07\jre\lib\rt.jar | Access restriction: The constructor DataHandler(DataSource) is not accessible due to restriction on required library C:\java\jdk1.6.0_07\jre\lib\rt.jar | Access restriction: The type DataHandler is not accessible due to restriction on required library C:\java\jdk1.6.0_07\jre\lib\rt.jar | Access restriction: The type DataSource is not accessible due to restriction on required library C:\java\jdk1.6.0_07\jre\lib\rt.jar | | at org.jboss.bpm.console.server.TaskMgmtFacade.<init>(TaskMgmtFacade.java:33) | at org.jboss.bpm.console.server.ConsoleServerApplication.<init>(ConsoleServerApplication.java:44) | at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) | at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) | at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) | at java.lang.reflect.Constructor.newInstance(Constructor.java:513) | at java.lang.Class.newInstance0(Class.java:355) | at java.lang.Class.newInstance(Class.java:308) | at org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap.contextInitialized(ResteasyBootstrap.java:183) | at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) | at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393) | at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310) | at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142) | at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461) | at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) | at org.jboss.web.deployers.WebModule.start(WebModule.java:97) | 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:597) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | 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:668) | at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) | at $Proxy38.start(Unknown Source) | at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) | at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37) | at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) | at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) | at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) | at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) | at org.jboss.system.ServiceController.doChange(ServiceController.java:688) | at org.jboss.system.ServiceController.start(ServiceController.java:460) | at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163) | at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99) | at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46) | at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) | at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178) | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) | at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) | at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) | at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) | at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) | at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271) | at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) | at org.jboss.Main.boot(Main.java:221) | at org.jboss.Main$1.run(Main.java:556) | at java.lang.Thread.run(Thread.java:619) | Thanks Bernd View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239031#4239031 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239031

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: New console snapshot published, Task Forms included

by camunda

Nice. One question: What if the task name contain spaces or stuff like that? Is it possible (or planned) to provide a mapping between task names and forms? Use case is to use the same form in different tasks (if you make it a bit generic, thats not unusual). Cheers Bernd View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239028#4239028 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239028

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Status / Documentation of gwt-console & report-server

by camunda

And the other forum entry is helpful as well... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239025#4239025 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239025

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Status / Documentation of gwt-console & report-server

by camunda

Hi Heiko. Thanks for the response. Found it. Sorry for disturbing you unnecessary (I thought I searched for it, seems I was too blinf ;-)). Cheers Bernd View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239023#4239023 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239023

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Why is the console a different repos

by camunda

Currently I still try to understand first WHY the jbpm console is a project on its own? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239013#4239013 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239013

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Status / Documentation of gwt-console & report-server

by heiko.braun＠jboss.com

@bernd see this one as well: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155048 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239009#4239009 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239009

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Status / Documentation of gwt-console & report-server

by heiko.braun＠jboss.com

@bernd there is a forms example within the example package. you'd basically need a freemarker template associated with a task activity. it follows a naming convention: <task activity name>.ftl you can then open the form from within the console. the docs will be shipped with GA. Basically this week. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239008#4239008 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239008

16 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2009