We're updating the issue view to help you get more done. 

Redesign JBoss remote deployer JAR loading model

Description

Currently, to remotely deploy to JBoss 5+, one needs to depend on the jboss-deployer JAR and some JBoss JARs.

This tasks aims at breaking that dependency requirement.

Design idea is the following (inspired from the JOnAS configurator):

1) jboss-deployer API becomes a separate JAR
2) all jboss-deployers implement that API
3) the JBoss container depends on the jboss-deployer API + includes the JARs for all implementations
4) when loading:
4.a) a new ClassLoader with current + the correct implementation JAR is created
4.b) if required, JBoss JARs are included from TCCCL
4.c) implementation is instantiated from that ClassLoader

Status

Assignee

Savas Ali Tokmen

Reporter

S. Ali Tokmen

Components

Fix versions

Priority

Major