...
The purpose of the spike was to see if it was possible to create another module and pull out code from the monolithic application module into savings another module. (now called appdomain)
Why?
At present we are creating service facades (application services) which at present are used by the presentation layer but which we also want to expose these for use by tests and in future a for data migration moduleuse. At present this is not possible becuase code from application is released as class files within a WAR archive. We would like the services to be exposed within a JAR so people could use its dependency and launch an application context with platform services running.
...
2) Spent a bit of time concentrating on removing 'persitencepersistence' dependencies from core domain classes like 'AccountBO'. Taking this middle-up approach was successful enough but the level of refactoring required is just too much.
...
The only feasible way at present to make services releasable/reuseable from a JAR file is to pull out all non ui/mvc related code from application and put into another module that products produces a JAR that application will depend on.
...