[Design of JBoss Web Services] - Re: Dynamic Endpoint Deployment
by kabir.khan@jboss.com
"richard.opalka(a)jboss.com" wrote :
| anonymous wrote :
| | Somehow the new deployment created internally needs to either include the original Module,
| |
| I don't know how to achieve that because web service endpoint is published from servlet and we do not have access to DeploymentUnit from it :(
|
If you have the deployment's ClassLoader, you can obtain the Module by calling
org.jboss.classloading.spi.dependency.ClassLoading.getModuleForClassLoader()
This method exists in the version of jboss-cl that exists in AS Branch_5_0.
I am not sure if adding the Module as an attachment to the created deployment will have any effect since it looks like a Module is always created by AbstractClassLoaderDescribeDeployer/VFSClassLoaderDescribeDeployer, but you can try.
If that doesn't work I think you need to create a ClassLoadingMetaData from the Module, and put that into the deployment as an attachment.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209542#4209542
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209542
15 years, 9 months
[Design of JBoss jBPM] - first cut of the new history
by tom.baeyens@jboss.com
HistoryEvents are fired during process execution.
We maintain history information on 2 levels: process instance and activity instance.
Process instance start and process instance end generate history events are fired directly from within the implementation.
ActivityBehaviour implementations are responsible for calling the historyXxx methods that are exposed on the ActivityExecution
All the HistoryEvents are delegated to a HistorySession. The default HistorySessionImpl will invoke the process() method on the history events themselves.
The HistoryEvents are temporary events. In the process method, they build up the information in the history model. There is a HistoryProcessInstance and there is a whole class hierarchy starting with HistoryActivityInstance.
In the HistoryEvent.process methods, the history events create model entities or merge information into the model entities. For instance, a ProcessInstanceStart history event will create a HistoryProcessInstance entity/record. And the ProcessInstanceEnd will set the endTime property in the existing HistoryProcessInstance entity/record.
Similar pattern for the activities. But for automatic activities, there is an optimisation so that only 1 event is created and all the information is stored in one single insert (as all this happens inside 1 transaction).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209523#4209523
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209523
15 years, 9 months