Hide Forgot
Link type: Superset, Source: SOA-236, Destination: SOA-284 Date of First Response: 2007-12-14 10:47:45 project_key: SOA 1. verify the SOA-P can be (auto-)discovered by JON 2. verify the EAP part is monitored/administrated by JON 3. create a dummy CP and apply it via JON See docs in JBQA-632 for details, how to perform these tasks
Link: Added: This issue is related to JBQA-632
4) Make sure the dummy CP is only applicable to SOA-P installs and won't be listed when you try to patch other EAP servers with JON, i.e. have SOA-P returns its own unique version string.
Trev, can you talk to Mike and one of you look at this as a priority in the new year? When I asked Ryan who did this for EAP he said: "Mr. Crouch spec'd it & implemented the JON logic. I implemented the build tooling. This repsonsibility has now been transfered to release engineering (Chris O'Brien)." So that should give you a handle on contact points.
Link: Added: This issue incorporates SOA-284
Moving to GA for now, but unless we get something back from the JON team we will have to push this further out.
run.jar -- the manifest file defines Implmentation-Title as "JBoss[SOA]" - jon uses it to recognise SOA. we need to ensure that the string is always there
Link: Added: This issue is related to SOA-325
moving out to CP02 but continuing to check that process works so fixes if needed can get into jon 2
There are now more specific issues.