Hide util classes in Java Mapping Archive

[tobit_kollenberg]

Hello,

I have created an external Java Mapping and imported it to the ESB as an jar-Archive. When I want to include the mapping within an operation mapping, I can see all the files which are included in the jar archive, even those who do not extend the AbstractTransformation class which is the entry point for the mapping runtime. So I am wondering if there is a way to hide such util classes which are only used by my mapping program internally and can not be integrated directly in the Operation mapping?

Kind regards,

Tobit

[anupam_ghosh2]

Hi Tobit,

              Just include the entry point that is the class extending abstracttransformation in operation mapping. The  other classes (along with the one you have imported in OM) will remain imported archive they need not show up in OM.

Regards

Anupam

[tobit_kollenberg]

Hi Anupam,

well, I know that I just have to include the class that extends the abstractTransofrmation. My question points on the fact, that all the other classes of the archive are also shown in the input assistance of the operation mapping. So, if a consultant uses my jar, he has to know which of all those classes is the right one. The better way would be, to hide all the other classes from the ESB users 😉

Regards,

Tobit

[anupam_ghosh2]

HI Tobit,

              Sorry I misunderstood your requirement. In our project a separete namespace has been created where all common class files are kept in an imported archive which are called by all other java classes in other namespaces under same SWCV.  Thus I do not repeat all util classes in all the individual namespace. Not sure if this approach is a solution to your problem. In this way in OM no other classes show up while editing the same in the same namespace, only relevant one is available in same namespace.

Regards

Anupam 

[nageshwar_reddy]

Have you tried making the other classes package private?

[tobit_kollenberg]

yes, but that did not work.