How to write package-meta-data.xml in multiple Java classes scenario

[tnomura]

Hello NSO experts,

Are there any recommendations/guidance on how to write package-meta-data.xml when you

have multiple service callbacks and multiple Java classes that are annotated with the

ServiceCallback annotations?

After some readings and testings, I found there are two approaches.

But I can't quite figure out which one is preferred.

1. Multiple java-class-names in a component

  <component>

    <name>ServiceName</name>

    <callback>

      <java-class-name>com.cisco.parentRfs</java-class-name>

      <java-class-name>com.cisco.childRfs</java-class-name>

    </callback>

  </component>

2. Multiple components and each of them have one java-class-name

  <component>

    <name>ParentService</name>

    <callback>

      <java-class-name>com.cisco.parentRfs</java-class-name>

    </callback>

  </component>

  <component>

    <name>ChildService</name>

    <callback>

      <java-class-name>com.cisco.childRfs</java-class-name>

    </callback>

  </component>

Two approaches differ in the way how daemon ids are assigned to each services in stacked service

scenario.

Same daemon id is assigned to parent and child servicees in Approach1 while different dameon ids

are assigned in Approach2.

Not sure if this diffence should be taken into consideration though.

Any comment would be very much appreciated.

Best regards,

Takeru Nomura

[Dan.Sullivan · Accepted solution]

Hi Takeru,

I guess you can do it either way, although I've only used method 2. In the production deployment for a particular project I worked on their were 16 components in the file. In my cases each of the callbacks were separate functionality and I wanted them to be deployed that way.

-Dan

[tnomura]

Appreciate your comment!