#306 Move GUI-related stuff out of XINS Common

[Ernst de Haan]

In my opinion, a regular XINS deployment in a Java EE container should have no dependencies on graphical libraries like AWT, SWT and Swing.
Currently, there is GUI-related functionality in the XINS/Java Common Library. I propose moving this elsewhere.

For my branch of XINS, at GitHub, I'll probably just deprecate the existing functionality and copy it to a different library, in a different package structure.

[Anthony Goubard]

Note that there is no runtime dependency (and no compile dependency for XINS APIs) on AWT, SWT or Swing.
The classes are utilities classes that are not used by XINS APIs (such as Sprin classes or the internal servlet container).

[Ernst de Haan]

I understand they are not a runtime dependency. But from a software architecture POV, it would IMO be better to move them into their own package (structure), so that the "common" hierarchy really has no dependencies on GUI-related functionality.

It's not a major issue, though. It's just that this would improve the software architecture in my opinion.

[Ernst de Haan]

This is low priority, I agree with Anthony on that.