[JBoss jBPM] - [bpel] Information about a deployed process
by rainstar79
Hi,
I want to get more information about my process running on the bpel engine, e.g. displaying details on a website about the execution of a certain BPEL process.
Is this possible via the jbpm API?
I created the following Code Snippet, but the jbpmContext instance is always null:
| JbpmContext jbpmContext = JbpmConfiguration.getInstance().getCurrentJbpmContext();
|
| System.out.println("jbpmContext = " + jbpmContext);
| if (jbpmContext != null) {
| try {
| Iterator taskInstancesIterator = jbpmContext.getTaskList().iterator();
| while (taskInstancesIterator.hasNext()) {
| writer.print("<br/><br/><br/>");
| TaskInstance taskInstance = (TaskInstance)taskInstancesIterator.next();
| writer.print("taskInstance.getName() = " + taskInstance.getName());
| writer.print("taskInstance.getDescription() = " + taskInstance.getDescription());
| writer.print("taskInstance.getPriority() = " + taskInstance.getPriority());
| writer.print("taskInstance.getCreate() = " + taskInstance.getCreate());
| writer.print("taskInstance.getDueDate() = " + taskInstance.getDueDate());
| writer.print("taskInstance.getEnd() = " + taskInstance.getEnd());
| writer.print("taskInstance.getId() = " + taskInstance.getId());
| writer.print("taskInstance.getStart() = " + taskInstance.getStart());
| writer.print("taskInstance.hasEnded() = " + taskInstance.hasEnded());
| writer.print("taskInstance.isBlocking() = " + taskInstance.isBlocking());
| writer.print("taskInstance.isCancelled() = " + taskInstance.isCancelled());
| writer.print("taskInstance.isLast() = " + taskInstance.isLast());
| writer.print("taskInstance.isOpen() = " + taskInstance.isOpen());
| writer.print("taskInstance.isSignalling() = " + taskInstance.isSignalling());
| writer.print("taskInstance.getComments() = " + taskInstance.getComments());
| }
| } catch (Exception e) {
| e.printStackTrace();
| } finally {
| jbpmContext.close();
| }
| } else;
Thanks for your help.
Cheers Rainer
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062861#4062861
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062861
18Â years, 10Â months
[JBossWS] - Re:
by palin
"chris05atm" wrote : 22:03:04,797 WARN [PolicyMetaDataBuilder] Cannot get service '{xmlapi_1.0}FindImplService' from the given wsdl definitions! Eventual policies attached to this service won't be considered.
| |
|
This is actually a warning; it says that the policy deployer was not able to get '{xmlapi_1.0}FindImplService' from the given wsdl definition, i.e. most probably the provided wsdl file doesn't match with the service metadata obtained from the annotated classes. For this reason eventual policies (cfr. WS-PolicyAttachment specs) won't be considered. But I think you don't care this, at least at the moment, since you have no attached policies.
"chris05atm" wrote : Considering a possible bug? in the raw soap generation I moved onto using a client created from wsconsume. Same error so this is maybe a WSDL issue... but the WSDL looks correct and the files are generated from the WSDL so now I'm really confused. A possible deployment problem?
|
Do you mean the annotated server classes were generated starting from wsconsume, i.e. using a top-down development strategy http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Top-Do... ? If not, I would try this...
Bye
Alessio Soldano
http://www.javalinux.it
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062855#4062855
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062855
18Â years, 10Â months
[JBoss Seam] - Re: java.lang.out of memory error permgen space
by alexeinov
"saeediqbal1" wrote : Is it safe to use JRockit with Seam?Thanks.
What is "safe"?
I'm using JRockit with Seam, it works. It cannot solve memory leak problems that exist in your application, container or libs though.
JRockit survives longer if a ClassLoader is leaking because it holds all allocated objects in the same heap. The dreaded PermGen error does not occure in it since there's no separate PermGen.
Sun's JVM has two allocation areas: heap and non-heap, PermGen is a section of non-heap area. When a ClassLoader leaks, PermGen runs out of megabytes quickly, and here you are: Out Of Memory PermGen error.
When a ClassLoader leaks in JRockit, it leaks in a main heap allocation area, which is much bigger, hence it takes longer time to exhaust it.
It's not safe to run leaking code, and JRockit does not make it safer, though you get more time between crashes.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062850#4062850
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062850
18Â years, 10Â months