Extract remote interfaces into own module
Heiko W.Rupp
hrupp at redhat.com
Mon Aug 4 20:39:03 UTC 2014
Hey,
I think it could be good to move all the remote EJB-Interfaces (plus needed
Pojo classes) into a separate maven module and package(*) that would then
form the remote interface that is e.g. used with the cli.
Reasons
- smaller remote interface package
- EJB Beans and server side utilities stay server side and can't accidentally be used
- Easier scoping of what is in the remote interface and what not
- Easier application of e.g. checkstyle rules to only this module
Wdyt?
Heiko
*) Technically for compatibility reasons with the CLI it may be better to move the
non-remote classes into a new package and keep the existing one for the
Remote interfaces.
More information about the rhq-devel
mailing list