This is JDBC Drivers management screen(s)

Functionality will be:

• upload a driver archive into WildFly, provide additional metadata (e.g. driver name), wrap the driver archive and put it into the correct wildfly directory. Activation of the driver will require a restart/reload of the managed server

• list existing drivers with their details

• edit metadata of existing divers (as far as possible, may require a server reload afterwards)

• delete a driver (may fail, will most probably require a server reload) - this may also need on WF-side a checking for usage of the driver. May need a "force delete" or a way to inform the user that the driver is in use and fail the deletion.

Server reloads should not implicit happen, only when authorized or explicitly requested by the user.