May 2010 - jboss-user - Jboss List Archives

Re: [jboss-user] [Spring Integration] - @Autowiring of beans from Spring applicationcontext

by Susana Quintana

Susana Quintana [http://community.jboss.org/people/sahra] replied to the discussion "@Autowiring of beans from Spring applicationcontext" To view the discussion, visit: http://community.jboss.org/message/541326#541326 -------------------------------------------------------------- Hi, Im using your example to do something similar, but in any case my bean is not wired. Can someone help me to figure out the problem, or could you post your working example. Thanks: Im using JBOSS 5.1.0 GA and \jboss-spring-3.2.CR1.deployer ------------------------- Ear structure: ------------------------ <application xmlns=" http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation=" http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd http://java.sun.com/xml/ns/javaee/application_5.xsd"> <display-name>app-server</display-name> <module> <java>persistence.jar</java> </module> <module> <java>controller.jar</java> </module> </application> ------------------------- dao-context.xml (is in persistence.jar /meta-inf ------------------------ <bean id="trackingRecordDAO"> <constructor-arg index="0"> <ref bean="dataSource"/> </constructor-arg> <constructor-arg index="1" value="-5"/> </bean> <bean id="datasource"> <property name="jndiName"> <value>demotracking.databasePool</value> </property> </bean> </beans> ------------------------- jboss-spring.xml (is in controller.jar /meta-inf ------------------------ <description>BeanFactory=(SpringDao)</description> <import resource="classpath*:dao-context.xml"/> <bean id="jobDetail"> <property name="targetObject" ref="gao_receiver02" /> <property name="targetMethod" value="readTags" /> <property name="concurrent" value="false" /> </bean> <bean id="gao_receiver02"> <constructor-arg value="100.105.130.224"/> </bean> <bean id="simpleTrigger"> <property name="jobDetail" ref="jobDetail" /> <property name="startDelay" value="0" /> <property name="repeatInterval" value="60" /> </bean> <bean> <property name="triggers"> <list> <ref bean="simpleTrigger" /> </list> </property> </bean> </beans> -------- ------ I did try the following code line to instatiate the bean in a class which is in the controller.jar but the bean is not wired :( @Autowired public TrackingRecordDAOImpl dao; -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541326#541326] Start a new discussion in Spring Integration at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 8 months

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/541305#541305 -------------------------------------------------------------- > Jim Ma wrote: > > Sorry , I may do not explain this problem well . We now create SPI endpoint from ServletMetaData in web.xml . How to distinguish the jms tranport endpoint and create jms endpoint/MD from the user provided jbossws-cxf.xml You can start separate jbossws-dev forum thread for that. But I'd think about it like *How CXF does it?* > Jim Ma wrote: > > AFAIK, the hornetq deployers create BeanMetaData for queue/topic deployment descriptor > and KernalDeploymentDeployer will start/stop these BeanMetaData represents queue/topic created by hornetq deployers. > I understood your suggestion : use deployer input to put the JMS DA after the deployer deployed jms destination. In AS5 , we should put JMSDA after the last real stage deployer ServiceDeployer . AS6, we put JMSDA after KernalDeploymentDeployer. IOW, we do not rely on AS deployer frameworks' deployment dependency mechinism , we rely on the deployer order to resolve the deployment dependency. If this is acceptable and if you do not see any other problems , I will follow your suggestion (as your pseudocode shows) to rewrite . I don't see the conflict here with the suggestions I provided you. Deployers ordering is working properly these days. But as discussed on IRC, forget about AS 5 integration. Just go forward with AS 6 ;) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541305#541305] Start a new discussion in JBoss Web Services Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 8 months

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/541304#541304 -------------------------------------------------------------- Hi Jim, I just reviewed your SPI and ASIL prototypes and here are my 2 cents: SPI: Remove org.jboss.wsf.spi.metadata.endpoints.EndpointsFactory (proprietary DD xml JBXB parsing) Remove org.jboss.wsf.spi.metadata.endpoints.AbstractEndpointsDeployment (to don't publish proprietary DD) I like org.jboss.wsf.spi.metadata.endpoints.jms.JMDDestinationMetaData I like org.jboss.wsf.spi.metadata.endpoints.jms.JMDDestinationMetaData but remove static fields from it (proprietary DD xml JBXB parsing) I like org.jboss.wsf.spi.metadata.endpoints.AddressMetaData (but it's name should be AbstractAddressMetaData because it's abstract class) I like org.jboss.wsf.spi.metadata.endpoints.EndpointsMetaData (but remove URL related methods & fields) I like org.jboss.wsf.spi.metadata.endpoints.EndpointMetaData (but here's some overlap with org.jboss.wsf.spi.deployment.Endpoint you should investigate/fix) ASIL: Remove org.jboss.webservices.integration.deployers.WSEndpointsDescriptorParserDeployer (proprietary DD xml parsing deployer) Rewrite org.jboss.webservices.integration.deployers.WSEndpointsRealDeployer - it have to be DA - I would name it MetaDataBuilderJMS - I would place it in package org.jboss.webservices.integration.metadata (because it provides JMS metadata) Update WSDeploymentAspectDeployer to specify proper inputs/outputs according to passed DeploymentAspect type (JMS/Servlet) Provide another DeploymentType (DeploymentType.JAXWS_JMS) Update org.jboss.webservices.integration.deployers.deployment.WSDeploymentBuilder - remove hacky code - and provide proper DeploymentModelBuilderJAXWS_JMS integration Implement org.jboss.webservices.integration.deployers.deployment.DeploymentModelBuilderJAXWS_JMS - so it properly integrates with SPIEndpoint - it handles new DeploymentType.JAXWS_JMS -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541304#541304] Start a new discussion in JBoss Web Services Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 8 months

1
0
0 / 0

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

by Jim Ma

Jim Ma [http://community.jboss.org/people/jim.ma] replied to the discussion "CXF jms integration" To view the discussion, visit: http://community.jboss.org/message/541296#541296 -------------------------------------------------------------- > 1) AFAIK jbossws-cxf.xml is generated only in case there isn't one provided. > The scenario of deploying both JMS and Servlet endpoints in one war > using one jbossws-cxf.xml DD should be supported. > I don't expect any real issues with this scenario. Sorry , I may do not explain this problem well . We now create SPI endpoint from ServletMetaData in web.xml . How to distinguish the jms tranport endpoint and create jms endpoint/MD from the user provided jbossws-cxf.xml like : <jaxws:endpoint id='HttpHelloService' implementor='org.jboss.test.ws.jaxws.samples.HelloImpl> </jaxws:endpoint> <!--jms endpoint-> <jaxws:endpoint id='JMSHelloService' wsdlLocation="./wsdl/jms-samples.wsdl" implementor='org.jboss.test.ws.jaxws.samples.HelloImpl> </jaxws:endpoint> > True, you cannot resolve dependency on JMS deployers in DA code. This can be done only in deployers. > But you're able to detect if particular DA is JMS DA or Servlet DA. See my suggestion (the pseudocode) > in my previous post how to resolve this issue in our WSDeploymentAspectDeployer constructor. > IOW *you shouldn't introduce additional deployers in AS IL*. You should *do everything in DAs* and just *leverage the AS IL integration code*. AFAIK, the hornetq deployers create BeanMetaData for queue/topic deployment descriptor and KernalDeploymentDeployer will start/stop these BeanMetaData represents queue/topic created by hornetq deployers. I understood your suggestion : use deployer input to put the JMS DA after the deployer deployed jms destination. In AS5 , we should put JMSDA after the last real stage deployer ServiceDeployer . AS6, we put JMSDA after KernalDeploymentDeployer. IOW, we do not rely on AS deployer frameworks' deployment dependency mechinism , we rely on the deployer order to resolve the deployment dependency. If this is acceptable and if you do not see any other problems , I will follow your suggestion (as your pseudocode shows) to rewrite . -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541296#541296] Start a new discussion in JBoss Web Services Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 8 months

1
0
0 / 0

[jBPM Development] - Task Form - select option to have variable item list (coming from java class & execution variable)

by Sukla Nag

Sukla Nag [http://community.jboss.org/people/SuklaJbpm] created the discussion "Task Form - select option to have variable item list (coming from java class & execution variable)" To view the discussion, visit: http://community.jboss.org/message/541282#541282 -------------------------------------------------------------- Hi I want to show on the Task Form a list of values of an array variable as select option for the user to choose from. The values are computed by a java class. But I am not able to use execution variable ( like item_list created by java class) as option values in a select clause - this is easliy attainable by jsp scripts. Can any one suggest a method to go about it or is there something already avaialble in jbpm ftl syntax ? Thanks in advance -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541282#541282] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 8 months

1
0
0 / 0

Re: [jboss-user] [jBPM] - find User tasks

by Jaber C. Mourad

Jaber C. Mourad [http://community.jboss.org/people/newbeewan] replied to the discussion "find User tasks" To view the discussion, visit: http://community.jboss.org/message/541280#541280 -------------------------------------------------------------- Ok, I was melting candidate and assignee I have also found a workaround with : taskService.createTaskQuery().candidate("john").list(); Thanks for your replies ! -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541280#541280] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 8 months

1
0
0 / 0

Re: [jboss-user] [jBPM] - find User tasks

by Michael Wohlfart

Michael Wohlfart [http://community.jboss.org/people/mwohlf] replied to the discussion "find User tasks" To view the discussion, visit: http://community.jboss.org/message/541277#541277 -------------------------------------------------------------- use assignee instead of candidate-users -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541277#541277] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 8 months

1
0
0 / 0

Re: [jboss-user] [jBPM] - find User tasks

by zecas zecas

zecas zecas [http://community.jboss.org/people/zecas] replied to the discussion "find User tasks" To view the discussion, visit: http://community.jboss.org/message/541272#541272 -------------------------------------------------------------- Hi, You have defined the users as candidate-users="...", and that makes the tasks available on the group task list. For a user to list, you must call: tasks = taskService.findGroupTasks("john"); Then if you want to work with it, you must pick it up, so the task is given a specific assignee, and no other person picks it up: taskService.takeTask(tasks.get(0).getId(), "john"); You must work out the tasks.get(0).getId() part :) Hope it helps. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541272#541272] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 8 months

1
0
0 / 0

Re: [jboss-user] [jBPM] - find User tasks

by HuiSheng Xu

HuiSheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "find User tasks" To view the discussion, visit: http://community.jboss.org/message/541271#541271 -------------------------------------------------------------- Hi Jaber, If you used candidate-users or candidate-groups to set the participants of a Task. You should use taskService.findGroupTask("John") to get the group task list. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541271#541271] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 8 months

1
0
0 / 0

Re: [jboss-user] [jBPM Development] - JBPM-2537

by HuiSheng Xu

HuiSheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "JBPM-2537" To view the discussion, visit: http://community.jboss.org/message/541268#541268 -------------------------------------------------------------- Hi Maciej, For TaskCancel and TaskTimeout, I think we could reference the TaskDelete. The constructor of TaskDelete allowed providing a reason for deleting task. We already have the state in HistoryTask, it is much easy for us to merge the TaskCancel and TaskTimeout into a TaskCancel class and let outside give this history a reason message. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541268#541268] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user May 2010