nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Modules, Methods and Java Libraries

AndyGoodman

I have a single jar file that contains one central class that promotes, demotes and suspends the lifecycle. The jar also contains three classes that call the central class, one for each action. It is these three classes that are called from the methods. How am I supposed to set this up in Composer 6.5?

I have set up a java definition file containing the jar and three methods which currently have the commands such as com....wf_suspendlifecycle_java. I know that the commands should now be the name of the modules. If I set up three modules (one for each action) then I get a warning that one jar file should be associated with one module or I should be using a java library. However, I can't find any information on how to use or setup java libraries.

If anybody could shed some light on this it would be very helpful.

Thanks

Andy Goodman

Find more posts tagged with

Documentum

Comments

CláudioGil

Each method refers to a verb that is the name of a module (in a java method). Each module needs to have an implementation class that implements IDfModule and IDfMethod. So, to have this you need to add a jardef as the implementation of the module and choose a class. This may be the jardef you already have, in the case the classes already implement the required interfaces, or yet another jardef just to make the bridge. It's in this last case that you may add the auxiliary classes as a library. A Java library is created like any other object in Composer. You then add jardefs to it and add the library itself to a module by opening the module, choosing the tab "Deployment" and adding the library there.

AndyGoodman

Hi Claudio,

Could you confirm that I need to setup three jardefs, each pointing to the same jar file. Then I setup a three modules utilising the three jardefs and specifying differing classes. The names of these modules then form the verbs of the respective methods? Seems to make sense except for the duplicated jardefs. The classes have already been modified to implement IDfModule and IDfMethod.

Regards

Andy

CláudioGil

You don't need 3 jardefs. It's perfectly fine if you have 1 jar with all classes and then, for each module, choose that jardef as an implementation jar and then the repective implementation class. The only inconvenient with this setup is that whenever a class changes, the jar changes and, when you update the jardef, all modules are affected.

An example:

JAR Definition
- a.jar.jardef containing:
  - A.class implements IDfMethod, IDfModule
  - B.class implements IDfMethod, IDfModule
  - C.class implements IDfMethod, IDfModule
Methods
- m_a.method { Command = a }
- m_b.method { Command = b }
- m_c.method { Command = c }
Modules
- a.module { ImpJars = a.jar; Class name = A.class }
- b.module { ImpJars = a.jar; Class name = B.class }
- c.module { ImpJars = a.jar; Class name = C.class }

AndyGoodman

Claudio,

Thanks for the explanation, however, when I set the project up like that I get the following warning:

Jar definition 'WFLifecycleTransitions' is used by multiple modules. One Jar definition should be used by one module only. If want to be shared in multiple modules, please use java library.

It is this that I am trying to get around - or should I just ignore it?

Cheers

Andy