[
https://issues.jboss.org/browse/WFCORE-3457?page=com.atlassian.jira.plugi...
]
Darran Lofthouse updated WFCORE-3457:
-------------------------------------
Description:
We currently compile to 323 classes, as this subsystem is almost exclusively about
management representation (Model and XML) rather than implementation all 323 of these
classes will need to be loaded when the subsystem is installed.
By switching to builders where we can instead of anonymous inner classes and possibly
using more common classes I believe a reasonable early target could be drop this to 200 to
250 classes so possibly up to a 33% saving.
Even without restructuring our resource registrations a lot of our classes exist just to
logically group related resources rather than any other purpose.
was:
We currently compile to 308 classes, as this subsystem is almost exclusively about
management representation (Model and XML) rather than implementation all 308 of these
classes will need to be loaded when the subsystem is installed.
By switching to builders where we can instead of anonymous inner classes and possibly
using more common classes I believe a reasonable early target could be drop this to 200 to
250 classes so possibly up to a 33% saving.
Even without restructuring our resource registrations a lot of our classes exist just to
logically group related resources rather than any other purpose.
Reduce Classes in the Elytron Subsystem
---------------------------------------
Key: WFCORE-3457
URL:
https://issues.jboss.org/browse/WFCORE-3457
Project: WildFly Core
Issue Type: Task
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 4.0.0.Alpha6
We currently compile to 323 classes, as this subsystem is almost exclusively about
management representation (Model and XML) rather than implementation all 323 of these
classes will need to be loaded when the subsystem is installed.
By switching to builders where we can instead of anonymous inner classes and possibly
using more common classes I believe a reasonable early target could be drop this to 200 to
250 classes so possibly up to a 33% saving.
Even without restructuring our resource registrations a lot of our classes exist just to
logically group related resources rather than any other purpose.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)