Re: [jboss-user] [JBoss Microcontainer Development POJO Server] - Implementing a non-flat deployment for Weld Integration
by Flavia Rainone
Flavia Rainone [http://community.jboss.org/people/flavia.rainone%40jboss.com] replied to the discussion
"Implementing a non-flat deployment for Weld Integration"
To view the discussion, visit: http://community.jboss.org/message/545502#545502
--------------------------------------------------------------
The draft version is committed to this branch:
http://anonsvn.jboss.org/repos/jbossas/projects/weld-int/branches/Deploym... http://anonsvn.jboss.org/repos/jbossas/projects/weld-int/branches/Deploym...
Now we finally have something concrete to use in our discussion. So, my draft version of WELDINT-1 is fully documented in order to make it easier for others to understand and to stimulate discussion :-)
Basically, I created an Archive class that maps to a Module and contains all the info necessary for creating a corresponding BeanDeploymentArchive. An Archive can reach other archives through Classpath, which maps one-to-one to ClassLoader domains and contains a list of archives/bdas. A Classpath can internaly point to another classpath, which corresponds to the parent domain relationship. This sets up the graph structure Pete suggested, which is actually a tree.
At first, when a deployment is created, BDAs are created only for those Archives that contain one or more CDI xml file. After that, as a result of Deployment.loadBeanDeploymentArchive, a BDA may be created by an Archive. Al lthe BDA collections are updated accordingly, mainly by the use of a BDALyfecycleListener.
Take a good look at the ClasspathImpl class. This is a very naïve but simple to understand implementation of the Classpath interface. It returns always a flat collection of all BDAs or archives visible, including
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/545502#545502]
Start a new discussion in JBoss Microcontainer Development POJO Server at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months
Re: [jboss-user] [jBPM] - [jBPM 4.3] Cancel Job/Timer
by Melih Cetin
Melih Cetin [http://community.jboss.org/people/kafsinkaf] replied to the discussion
"[jBPM 4.3] Cancel Job/Timer"
To view the discussion, visit: http://community.jboss.org/message/545478#545478
--------------------------------------------------------------
Hi HuiSheng,
If it is not recommended to signal an execution in the EventListener then could you please let me know the recommended way of handling the following scenario.
We are working with a trading partner and we are putting an asynchronous request to the trading partner via their web service. Completion of the task may take some time for the partner. The way to check if the task is completed is to make an inquiry again using their web service in fixed intervals. The current process definition is:
1. put an asynchronous request to a trading partner via a web service (done via a java task).
2. go to a 'state' and check the completion of task regularly (currently done by a Timer and EventListener).
** If the task status is complete, progress the workflow to the next activity (currently done by the EventListener).
** If the task does not get completed within say 48 hours, progress the workflow to a manual task for error handling (currently done by the EventListener).
How would you suggest us to implement this scenario?
Thanks,
Melih
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/545478#545478]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months