Bug 1313209

+++ This bug was initially created as a clone of Bug #1311695 +++

Description of problem:

EAP7 is discovered incorrectly by agent using old plugin (update02). 
It should be fixed when updated to update03, but still remains.

Version-Release number of selected component (if applicable):
JON 3.3.5 (Foreman's group JON/Server/JON3.3.0/CP5), 
EAP7
JON agents, updated while test running 

Steps to Reproduce:
1. VM1: creating JON3.3 through Foreman, after foreman's installation plugins are 'old' (and after any restarts as well)
2. VM2: install JON agent from foreman, install EAP7 (secure, standalone)
3. VM1: updating JON plugins by copying *.jars into 'plugins/'. Restart JON.
4. VM2: through Agent console mode update plugins from agent's side
5. VM1: in JON GUI go -> 'Servers - Top Level Import'

Actual results:

Availability as GREEN
Type: 'JBossAS7 Standalone server'
Version: 'EAP 7.0.0.GA'
but Description: still  'Standalone JBoss Enterprise Application Platform 6 server'

Expected results:
Description: still  'Standalone JBoss Enterprise Application Platform 7 server'

Additional info:
intermediate result (between items 2./3.):
Availability as RED
Type: 'JBossAS7 Standalone server'
Version: 'EAP 7.0.0.GA'
but Description: still  'Standalone JBoss Enterprise Application Platform 6 server'

--- Additional comment from Michael Burman on 2016-02-29 08:38:36 EST ---

We don't do ProductType rediscovery currently. So if you update EAP6 to say JDG, this would fail as well (this isn't EAP7 related).