Provide extended resource adapter configurations

jesper:

Create:
-------

• Archive
• Transaction support (Default, NoTransaction, LocalTransaction,
  XATransaction)
• Resource adapter <config-property>'s
• <connection-definition> <-- there can be multiple of those

• Overview
• Managed connection factory class name
• JNDI name
• Pool name
• <config-property>'s
• Pool / XA Pool (depending on Transaction support)
• min-pool-size
• max-pool-size
• Prefill
• XA Pool == XADataSource's pool settings
• Security
• Application
• Security domain <-- require input
• Security domain and application <-- require input
• Validation
• Enable background validation
• background-validation-millis
• Recovery (if XATransaction)
• Enable recovery

• <admin-object> <-- there can be multiple of those

• Overview
• Admin object class name
• JNDI name
• Pool name
• <config-property>'s

Overview:
---------

• "Resource Adapter" => "Resource Adapters" (under "Profile")

• We will need a different way of displaying a resource adapter deployment,
  since each deployment can have multiple JNDI bindings for connection factories
  and multiple JNDI bindings for admin objects - and they maybe scoped to a
  resource adapter class instance.

• There can be multiple deployment of the same archive too - just using
  different JNDI names of course - so that needs to be taken into account too.

• For connection factories we need to display the pool as currently and add
  information about the statistics (like datasources). Admin objects doesn't
  have pool information.

• The "Properties" for each of the objects type

• Archive level: Resource adapter <config-property>'s
• Connection factory level: <connection-definition> <config-property>'s
• Admin object level: <admin-object> <config-property>'s

• Once you get to <connection-definition> and <admin-object> level it is
  pretty much the same as a datasource (since datasources are backed by a
  resource adapter).

We will leave the rest of the attributes / elements to a future version.