April 2010 - jboss-user - Jboss List Archives

Re: [jboss-user] [jBPM] - How to assignee this tasks?

by Huisheng Xu

Huisheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "How to assignee this tasks?" To view the discussion, visit: http://community.jboss.org/message/536460#536460 -------------------------------------------------------------- Hi Anand, I make a simple process defintion, and upload it into attach, you could download and have a look at whether it is what you want. cheers -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536460#536460] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-user] [jBPM] - How to assignee this tasks?

by Rudolf Michael

Rudolf Michael [http://community.jboss.org/people/ruds] replied to the discussion "How to assignee this tasks?" To view the discussion, visit: http://community.jboss.org/message/536458#536458 -------------------------------------------------------------- Hello, taskList = taskService.findPersonalTasks(userId); taking into account that userId is registered in the user type that you want and the task jPDL is assigned to a group candidate-groups="USERTYPE" check out the taskService API for more info. regards, Rudolf Michael -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536458#536458] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

[jBPM] - How to assignee this tasks?

by Anand Kumar

Anand Kumar [http://community.jboss.org/people/akstifr] created the discussion "How to assignee this tasks?" To view the discussion, visit: http://community.jboss.org/message/536451#536451 -------------------------------------------------------------- Hi, My problem is: I have an application form (in jsp) and where ever it is submitted to the server, a new processInstance is generated. After processInstance is generated, there are two tasks 1) *Assignee to* & 2) *Cancellation* of generated ProcessInstance. I am using jbpm4.3 with tomcat 6.0 and Oracle as database Based upon user type, his task list should show like: If usertype is *MEMBER* then whenever he submits application, he should be able to cancel the generated ProcessInstance for his application. and at same time *ADMIN* user should get a task like *Assignee to* that application some body. if User type is *ADMIN* then whenever he submits application, he should be able to cancel the generated ProcessInstance for his application. and at same time, he should get a task like *Assignee to* that application some body. How to assignee this tasks? i am able to perform only one thing i.e a user submits application, he is able to cancel the generated ProcessInstance for his application. but unable to assignee the task for Admin at the same time with name *Assignee to* * Can any provide me some pointers on how to proceed further in this problem.* * Thanks in advance :)* -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536451#536451] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-user] [JBoss Web Services Development] - CXF jms integration

by Richard Opalka

Richard Opalka [http://community.jboss.org/people/richard.opalka%40jboss.com] replied to the discussion "CXF jms integration" To view the discussion, visit: http://community.jboss.org/message/536448#536448 -------------------------------------------------------------- Abbreviations: * CXF - CXF integration layer * ASIL - JBossWS Application Server Integration Layer * SPI - JBossWS SPI - the only dependency reused cross different JBossWS abstractions * DA - JBossWS Deployment Aspect * UMDM - JBossWS Universal Meta Data Model * JMS MD - AS JMS Meta Data * AS API - compilation dependency on AS API classes * IAC - in any case Hi Jim, first approach is fundamentally wrong because: * it would violate our abstractions * it wouldn't reuse existing code/architecture We cannot introduce *JBossWSCXF*Deployers* because we would introduce *CXF -> AS API* dependency. Only allowed dependency is http://www.jboss.org/file-access/default/members/jbossws/images/wsf.png CXF -> SPI. This is because AS architecture can/will change over time and we want to be AS agnostic IAC. Yes, the solution 2 is little bit more complex one but we should always follow the golden programmers rule: *Either do it properly or don't do it at all (*otherwise our code would become unmaintanable in the future*).* * * Here are my suggestions how we should proceed with *approach 2* (*ensures proper abstractions, dependencies and code/architecture reuse*): * extend our UMDM (located in SPI) to provide JMS endpoint abstractions * extend our DA framework to distinguish DA aspects intended to create web based endpoints and jms based endpoints * update our ASIL (concretely WSDeploymentAspectDeployer) to distinguish between Web DAs and JMS DAs * implement CXF DA that will map jboss-cxf.xml MD to our UMDM (ensures http://www.jboss.org/file-access/default/members/jbossws/images/wsf.png CXF -> SPI dependency) * implement ASIL DA that will create JMS MD from our UMDM (ensures http://www.jboss.org/file-access/default/members/jbossws/images/wsf.png ASIL -> SPI dependency) * implement CXF DA that will register plain JMS endpoints with CXF (ensures http://www.jboss.org/file-access/default/members/jbossws/images/wsf.png CXF -> SPI dependency) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536448#536448] Start a new discussion in JBoss Web Services Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-user] [JBoss Web Services] - Error on java.lang.IllegalStateException: Cannot build JAXB

by Richard Opalka

Richard Opalka [http://community.jboss.org/people/richard.opalka%40jboss.com] replied to the discussion "Error on java.lang.IllegalStateException: Cannot build JAXB" To view the discussion, visit: http://community.jboss.org/message/536446#536446 -------------------------------------------------------------- You're using JAXB incompatible classes. Double check JAXB documentation how to proceed and to see what's supported. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536446#536446] Start a new discussion in JBoss Web Services at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-user] [JBoss Web Services] - Error on java.lang.IllegalStateException: Cannot build JAXB

by Jim Ma

Jim Ma [http://community.jboss.org/people/jim.ma] replied to the discussion "Error on java.lang.IllegalStateException: Cannot build JAXB" To view the discussion, visit: http://community.jboss.org/message/536445#536445 -------------------------------------------------------------- The problem is in your types classes passed to the wsprovide tool. One of reason I can see from the exception stack trace is the types class implemented interface java.io.Serializable and JAXB can not handle it. Here is the reason why JAXB can not : http://weblogs.java.net/blog/2006/06/06/jaxb-and-interfaces http://weblogs.java.net/blog/2006/06/06/jaxb-and-interfaces -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536445#536445] Start a new discussion in JBoss Web Services at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

[JBoss Web Services Development] - CXF jms integration

by Jim Ma

Jim Ma [http://community.jboss.org/people/jim.ma] created the discussion "CXF jms integration" To view the discussion, visit: http://community.jboss.org/message/536441#536441 -------------------------------------------------------------- After looked at Alessio's work about cxf descriptor deployment and lazy bus load removal , I'd like to discuss with you about my thoughts about jms integration. Here is what in my mind so far .As we talked before , we need to introduce other deployer or deployerAspect to make cxf stack directly deploy/load jbossws-cxf.xml. IMO, the easy approach to implement this is adding several real stage deployers to the current deployer chain to take care of the jms deployment without web.xml: `--org.jboss.webservices.integration.deployers.WSEJBAdapterDeployer@4007f4 `--org.jboss.webservices.integration.deployers.WSTypeDeployer@d6f833 `--org.jboss.webservices.integration.deployers.WSDeploymentDeployer@103ddfd `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@1279d82(org.jboss.wsf.framework.deployment.EndpointMetricsDeploymentAspect(a)b77801) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@1fa6e43(org.jboss.webservices.integration.metadata.ContainerMetaDataDeploymentAspect(a)1e7c7fb) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@fcc66a(org.jboss.wsf.framework.deployment.EndpointHandlerDeploymentAspect(a)18b3f9a) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@124a94(org.jboss.wsf.framework.deployment.BackwardCompatibleContextRootDeploymentAspect(a)6fcd57) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@4aba6a(org.jboss.wsf.framework.deployment.URLPatternDeploymentAspect(a)fb39f6) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@8d69f8(org.jboss.wsf.framework.deployment.EndpointAddressDeploymentAspect(a)13bf9ce) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@1f99aa6(org.jboss.wsf.framework.deployment.EndpointNameDeploymentAspect(a)929ed4) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@1f8a03f(org.jboss.wsf.framework.deployment.VirtualHostDeploymentAspect(a)4a9acb) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@e9635a(org.jboss.wsf.framework.deployment.JAXBIntroDeploymentAspect(a)12cebd2) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@1744996(org.jboss.wsf.stack.cxf.deployment.aspect.DescriptorDeploymentAspect(a)1e890b4) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@864ae7(org.jboss.wsf.stack.cxf.deployment.aspect.ResourceResolverDeploymentAspect(a)1214a13) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@4fdf56(org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect(a)79bca4) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@6e1cbf(org.jboss.wsf.framework.deployment.ContextPropertiesDeploymentAspect(a)827b51) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@786a44(org.jboss.webservices.integration.tomcat.WebMetaDataCreatingDeploymentAspect(a)c9f31e) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@1850507(org.jboss.webservices.integration.tomcat.WebMetaDataModifyingDeploymentAspect(a)b6cddb) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@1ee86f2(org.jboss.webservices.integration.security.JACCPermissionsDeploymentAspect(a)1ec0b9d) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@31613(org.jboss.webservices.integration.injection.InjectionMetaDataDeploymentAspect(a)182ac61) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@1d61032(org.jboss.wsf.framework.deployment.EndpointRegistryDeploymentAspect(a)d91c60) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@1d37602(org.jboss.wsf.framework.deployment.EndpointRecordProcessorDeploymentAspect(a)9f987a) `--org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer@1a30367(org.jboss.wsf.framework.deployment.EndpointLifecycleDeploymentAspect(a)1bb1dd2) + org.jboss.wsf.stack.cxf.deployment.JBossWSCXFMetaDataDeployer(to parse the jbossws-cxf.xml and create JBossWSCXFMetaData) + org.jboss.wsf.stack.cxf.deployment.JBossWSCXFJAXBIntroDeploymentDeployer(to do the jaxb databinding customization) + org.jboss.wsf.stack.cxf.deployment.JBossWSCXFDeploymentBuilderDeployer(to create deployment, service and endpoint etc) + org.jboss.wsf.stack.cxf.deployment.JBossWSCXFDeploymentDeployer(to let the cxf bus load the jbossws-cxf.xml) + org.jboss.wsf.stack.cxf.deployment.JBossWSCXFEndpointRegistryDeployer(to register the endpoint) I marked the new add deployer with "+" prefix and these new add deployers will be put the end of the DeploymentAspect deplyers. As you can see ,there will be some duplicate work/code in the these deployers with above DeploymentAspects. But it makes the deployer structure more clear and these new added deployers are dedicated to handle the jms deployment and other stack specific deployment without web.xml. The another option is we handle it both in integration layer and cxf stack : 1. Create a unified MetaData/holder to reprsent or place the stack specific deployment :jbossws-cxf.xml. 2. Modify the WSDeploymentDeployer to handle the deployment without JBossWebMetaData 3. Add the code in the current DepoymentAspects ,for example EndpointHandlerDeploymentAspect, DescriptorDeploymentAspect and BusDeploymentAspectin to process the stack specific deployment (without web.xml). We can put the code to process the cxf jms deployment in each DeploymentAspect, so this approach will reuse the function in each deployment aspect.This will change a lot in current integration layer and deployers framework and it's a little bit complex. After the comparison, I prefer to the first approach. Because at the moment, only cxf has this requirement to deploy stack specific deployment. And it is also simple :only adding some new additional deployers for cxf stack can make it work . It will not impact the other components : integration layer , spi and framework codebase. You thoughts ? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536441#536441] Start a new discussion in JBoss Web Services Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

[jBPM Development] - oracle donot allow insert blob in batching

by Huisheng Xu

Huisheng Xu [http://community.jboss.org/people/rebody] created the discussion "oracle donot allow insert blob in batching" To view the discussion, visit: http://community.jboss.org/message/536439#536439 -------------------------------------------------------------- Hi all, Oracle do not allow insert blog in batching, So if we want to deploy a process definition into oracle, we have to set <prop key="hibernate.jdbc.batch_size">0</prop>, this setting will affect other operation in hibernate. I think we should have a special treatment for deployment in oracle. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536439#536439] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-user] [jBPM] - ClassCastException

by Huisheng Xu

Huisheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "ClassCastException" To view the discussion, visit: http://community.jboss.org/message/536435#536435 -------------------------------------------------------------- Hi ricardo, I think you should make sure if there is more than one ClassLoader could load the ProcessEngineImpl class. It looks like the ProcessEngineImpl being loaded twice so it can't be cast from a ClassLoader to another one. cheers. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536435#536435] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

1
0
0 / 0

Re: [jboss-user] [jBPM] - How to configure 4.3 the right way?

by Huisheng Xu

Huisheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "How to configure 4.3 the right way?" To view the discussion, visit: http://community.jboss.org/message/536434#536434 -------------------------------------------------------------- Hi Christian, It is strange for me. I have changed both of your projects to use hsqldb. When I execute jbpm43, there are a lot of warning in the console, told me that the hsqldb can't support higher transaction isolation. But there is no warning for jbpm32. Are you using the same example to test jbpm32 and jbpm43? cheers -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/536434#536434] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

16 years

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-user April 2010