[1079027] Storage Node (un)deployment can cause deadlock in rhq_storage_node table
Initial commit that attempts to remove umbrella transactions starting at
many entry points, such that scheduling operations happens in their own
trans context.  Needs review and testing...
Transaction delimiters have been updatedin StorageNode beans to try and prevent
db-locking issues.  This caused a problem for storage node deployment
during mergeInventory, because it relied on an umbrella transaction providing
a persisted (but not yet committed) Resource.

Added a general mechanism for performing post-commit actions on newly
merged resources and leveraged it to perform linking a StorageNode to a
Resource.
Make sure StorageNode is committed before we try and deploy it.
More changes to LinkStorageNode to try and get the transactioning right.
BZ_1080171 - defer adding of "WHERE" keyword until we know that it is needed.
[BZ 1070243] - (JON3-31) Add "Recent Events" portlet into JON
Dashboard

To make the filtering (based on resource name) working, I had to add also
 the new method to the EventCriteria class.

To sum it up, it is possible to filter by:
 * time ("from, to" or "last n mins/hours/days")
 * resource name - only for global Recent Alerts portlet; it accepts also a substring of a name
 * event source path - it accepts also a substring of a path
 * severity (almost the same as alert priority filtering)
 * result counts (5 is default)

Having that said, the performance shouldn't be an issue, because the
filters may be set to fetch only a few records.
Updated checks after comments from @metlos.
Merge pull request #17 from pilhuhn/bz1080171

BZ_1080171 - defer adding of "WHERE" keyword until we know that it is needed.
Since the Hibernate4 standard dialect resolver does not recognize
Oracle 12, we need to ensure the hibernate.dialect system property
is set when running the i-tests.
[BZ 1081554] - Cannot load metrics error on a resource with no enabled metrics - Not performing the problematic DB query, when no metric on the resource is enabled. Also saving 2 (client-server)) round trips if the enabled metrics # equals to zero.
To support oracle 12c, updating the default driver version. It should be backward
compatible to our earlier, supported releases.
Add a missing colon in toString that was confusing
[BZ 1082767] Group view does not display proper content when user reaches
AutoGroup via URL

Fixed ResourceGroupTreeView to optionaly select target group after tree is
loaded
[BZ 1076605] The link to Autocluster group alert definition is wrong
[1079027] Storage Node (un)deployment can cause deadlock in rhq_storage_node table
Fix issue with new transactioning that left some entity changes uncommitted.
Merge branch 'jshaughn/storage'

Conflicts:
	modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/cloud/StorageNodeManagerBean.java
Very useful typo correction
[668870] Replace Tanuki Java Service Wrapper with EAP native components to support 32-bit and 64-bit base architecture types
- Update JSW with version 3.4.1 and add the 64-bit community version for
  distribution.
- Update scripts to use the proper JSW version based on Win OS architecture
  and JVM architecture.
- Update wrapper .conf and .inc files as needed.
  - add new server .conf java.additional prop required to prevent logger
    initialization problem between JSW and EAP.
  - update logfile loglevel to STATUS for all wrapper logging, this provides
    more useful logging for server and storage wrapper logs, and trims
    excessive logging in the agent wrapper log.
  - fixed numbering issue in dev-container server-wrapper.inc
Bug 1079361 - Postgres Plugin - Scheduling A New List Process Statistics Operation Fails

The execution of this operation involves a query on the pg_stat_activity view, which format has changes in 9.2 (see http://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.2#pg_stat_activity_and_pg_stat_replication.27s_definitions_have_changed)

Now the server plugin component adapts the query depending on the Postgres server version
[BZ 1080909] DynaGroup expression evaluator is not strict when grouping by
resource configuration property

Dynagroup expressions using  pluginConfiguration[prop] or
resourceConfiguratoin[prop] will now be matched 'strict' to property name.
Strict match in means resulting SQL would be 'simple.name = :argX' instead
of original 'simple.name LIKE :argX'.