Add some translations
[BZ 965833 - Potential bug in join/fetch/avoidance code]
It is now possible to lazily fetch fields defined in super classes.

The avoidance of the join-fetch with limits exposed a missing feature that
was present in the code from the day one. It would be failing if the
criteria query was used to fetch a custom object (i.e. not the primary
persistent class of the criteria object) using an "altered projection" and
a fetch would be set on a field defined in a super class of the persistent
class of the criteria object. Only by chance this has never happened
before, because we don't use the altered projections on the criteria
queries that often.

Now that we lazily fetch fields much more often (to avoid join fetch
with limits) this is a problem even in cases without an altered projection.

The fix is fortunately very simple - we need to also search the
superclasses of the criteria's persistent class when looking for a field
to lazily fetch.

The possibility of fields being present in super-classes was taken into
account on other places in the CriteriaQueryGenerator class, too.

Documentation on the getJoinFetchFields() and alterProjection() was
enhanced to hopefully better explain the conditions underwhich you can
combine fetching and altered projection together.
Merge pull request #1 from lzoubek/master

Merging the rhq bot improvements
Bug 920214 - [as7] add async avail check support to AS7 plugin

Only applies to server level resource (Standalone, Domain and Managed servers)
Use only apache logger and not the jboss logger from the base class.
Bug 966665
- Criteria queries with paging and sorting on non unique fields may return same item on different pages

All paged criteria queries now apply ID as the least significant
ordering field (see exceptions below).  Since ID is unique, this ensures
that queries for pages always return the same ordering of rows.

ID will not be automatically appended as an ordering field if:
- the paging is unlimited (i.e. no pagesize, all rows returned)
- the Criteria class does not support an ID sort
- the caller has set the Criteria class instance to not support the ID sort
- ID is already specified as an ordering field
- the max number of ordering fields has already been set (3)

Note that CriteriaQuery has had its support for implicit ID sorting removed,
as the new mechanism, which moves support to the CriteriaQueryGenerator,
replaces it.
remove use of method not supported by GWT
[BZ 967622 - Server CLI script can't require modules from rhq://downloads]

This was primarily caused by a new permission required by EAP 6.1 we've
switched to. To access the ModelControllerClient, the code now needs a
RuntimePermission("canAccessModelController").

We need the ModelControllerClient when determining the EAR installation
dir, which we in turn need when determining where to locate the scripts
in the "rhq://downloads" location. This is done while running a script,
which is done in a restricted access control context which does not and
should not have that permission.

The minimal fix is to wrap the getting of the ModelControllerClient in a
privileged action but some more "defensive" code was added in the
RhqDownloadScriptSourceProvider, too, to guard against different times it
might get instantiated during the script execution.

Javadocs were updated to warn about the security considerations when
writing a script source provider available on the server side.
Bug 885686 - Tomcat web application configuration form allows save without Config File required field

It's not a Tomcat specific issue. We had a problem in *EditView classes: the check to enable/disable the save button was only based on the invalid properties set having been changed. Now it also looks at the set being empty or not.
Make sure sub-queries used for updates do not include implicit
paging/sorting.

Also, make a small change to test cleanup in related test class.

Note: Fix by lkrejci
[BZ 967542] - UI shows confusing units when editing Availability Duration alert condition type

I improved the DurationItem component to use internally the SelectItem
instead of ComboBoxItem. When using ComboBoxItem, it was possible to
write to the combobox and this is something that shouldn't happen in
this component because the unit types should be fixed. The DurationItem
is also used from the operation tab view, but no reggression was
introduced by this commit in this view.

Modifying also the DurationItem.setAndFormatValue() to populate the time correctly when
!isReadOnly.
BZ 967990 the installer now turns off the admin console
[BZ 968269] Make endpoints for pushing metric data more consistent

Endpoints for pushing metrics to server are now consistent (following way):
PUT metric/data/{scheduleId}/raw/{timeStamp} with body {'value':123}
PUT metric/data/{scheduleId}/trait/{timeStamp} with body {'value':'trait
value'}

This commit also fixed Bug 964227