Cannot get the Package History in a content of deployment.

[guillo]

Hi.

From a Java client. i'm trying to get the InstalledPackageHistory of a Deployment Resource, with this 2 lines:

InstalledPackage pack = remoteClient.getContentManager().getBackingPackageForResource(subject, deployment.getId());

List<InstalledPackageHistory> packageHistory = (List<InstalledPackageHistory>)pack.getPackageVersion().getInstalledPackageHistory();

However, pack.getPackageVersion().getInstalledPackageHistory() always returns null.. The PackageHistory List is empty.

The Deployment resource name is Test1 and the deployment.getId() returns the good id, so the pack variable is correctly instanciated, but with a empty PackageHistory.

When I display the PackageHistory of this Deployment from JON interface, i can see many update of the package in the History List. Please refer to the attached .png.

Why JON interface show the history list and the RHQ API getInstalledPackageHistory() show empty list ?

The reason i'm trying this is beacuse i want to get the status of the package update upcoming after a call method ClientProxyMethodHandler.updateBackingContent(...)

I want to be able to evaluate if the update of the package of the deployment resource was sucessful.

Anyone have an idea ?

thank you in advance.

[jayshaughnessy]

The reason for this, I think, is that pack.getPackageVersion() does return the PackageVersion, but not its lazy loaded data, like package history.

Perhaps try something like this:

...

PackageVersionCriteria c = new PackageVersionCriteria();

c.addFilterId( pack.getPackageVersion().getId() );

c.fetchInstalledPackageHistory( true );

PackageVersion pv = remoteClient.getContentManager().findPackageVersionsByCriteria( subject, c ).get(0);  // assumes a single result, may want to protect against null here

pv.getInstalledPackageHistory(); // should be there, I think

[guillo]

Wow!

It worked fine.

thank you very much.

[jayshaughnessy]

You're welcome.  In short the "getters" on the entity objects will not have any of the lazy loaded data, for efficiency reasons we don't pull everything at all times.  We have a whole bunch of "Criteria" objects and methods that allow you to perform fetches with powerful filtering (c.addFilterXXX) and also the ability to request optional data (c.fetchXXX).

The Criteria stuff is really useful when using the RHQ Remote API and CLI.

See https://docs.jboss.org/author/display/RHQ/Criteria+API+Tips for more!