Debugging process when custom java method is defined through module

6.5 SP1.

I have a process template with an automatic activity which configured to call a custom java method. This method is defined with Module name in its method_verb.

The process runs well on content server side but when I try to debug it inside Process Builder I get java.lang.Exception: Error in loading class <my module name> ... Caused by: java.lang.ClassNotFoundException: <my module name>

Seems like Process Builder knows nothing about modules deployment.

With no success I tried to:

put my module jar into bpm\classes\custom folder
add -Ddfc.development.bof.registry_file=... with property file defining my module to Process Builder's JVM commandline

Is it possible to make Process Builder behave the same way Method Server do when loading modules? If not is there a bug already reported?

Or maybe there is a way to hot-deploy jars into a Method Server (JBoss) without the use of modules so I'll be able to create "old-style" methods with class name in method verb?

I'll be very thankful for a solution which will help me to:

have my workflow java methods classes hot-deployed to method server (without JBoss restrart)
debug process templates in Process Builder

Find more posts tagged with

Comments

Chris_Campbell

The documentation states that unless you extend WorkflowMethod in your custom class, Process Builder can't debug the code. Later today, just for kicks, I'm going to see if the debugger can also pick up a class if it only extends IDfMethod. I'll post my results here on that little experiment.

As for your question about "hot-deploying", that's all going to depend on your IDE and your setup. Somewhere there's a discussion on this on using SBO as a way to hot-deploy. There is an application out there that let's you hook into the VM (I can't remember the name of it at the moment) and make on the fly changes. I'll have to look that up.

I'm not sure if you'll have much success labeling this as a "bug". Technically, the debugging feature works pretty much as advertised. I can take a workflow method in Composer, deploy it as JAR in my custom folder, debug it in Process Builder and if something goes wrong; adjust the code in Composer, redeploy and just rerun the failed task in Process Builder without having to kill any process or restart the workflow or debuging session. This is a MAJOR improvement over what I had to do in the past to troubleshoot.

 I'm not
sure if you'll have much success labeling this as a "bug". 
Technically, the debugging feature works pretty much as advertised.  I
can take a workflow method in Composer, deploy it as JAR in my custom
folder, debug it in Process Builder and if something goes wrong; adjust
the code in Composer, redeploy and just rerun the failed task in
Process Builder without having to kill any process or restart the
workflow or debuging session.  This is a MAJOR improvement over what I
had to do in the past to troubleshoot.

Did you notice that I mentioned Modules? From my understanding the modules deployment feature will make "good-old-java-methods-you-place-into-java_methods-folder" obsolete. Too bad it isn't supported in Process Builder.

By the way I found a workaround earlier this week - I just derive from my method class giving the child a name equal to a module name. After that I deploy such wrappers in a different jar into a relevant Process Builder folder. So in the end I have a JVM debug ability in both cases together with hot deployment.

PS. smne plz give me 10pts

Chris_Campbell

My bad. I didn't explain fully my last comment. That's what I get when I multitask. What I meant to state was that EMC was more than likely take your bug request as more of a feature request. I'll agree with you that it would be extremely helpful to have module debugging, especially since more advanced workflows need to do more than just extend WorkflowMethod. The tricky part is how to implement it so it works at a universal level.

This is just speculation on my part, but the movement towards a single "all-in-one" development environment is a step in that direction.

Oh, and thanks for posting your workaround. If I had points to give, I would because that little tip is going to save me time down the road.

Hartmut_Clausen

You should look in the remote debuggung feature of JBoss/Tomcat. The module are just jar files that are executed on an application server.

A sample how to configure it can be found here (or just google it):

http://oreilly.com/java/archive/eclipse-jboss-remote-debug.html

Wiesnoepersad

Check Support Note: esg96870

Actually I don't get how this support note could be helpful with my question - my question refers to the situation you get into after following the recommendations of this support note.

tusharinamdar

Support for debugging custom methods defined as modules is coming in Process Builder SP2.

If you are looking to (JVM) debug your custom method code, you can start Process Builder in debug mode - here is a relevant post : https://community.emc.com/message/2518#2518

Tushar.

Found workaround for 6.5SP1 and the problem will be possibly fixed in 6.5SP2.