On Saturday 21 May 2011 10:06 AM, Stuart Douglas wrote:
I was thinking that at the moment we are creating the module very
late in the the deployment process, which seems unnecessary, as all the information we
need to create it is available quite early on in the parse phase.
I think it would simplify quite a lot of the code if we changed the deployment order so
the module gets created much earlier, and is availible during parsing of EJB components
etc. At the moment we seem to have a lot of code that stores information into string
representations of a class/method, only to change it into a Class/Method object in a later
phase. If this code could just work the the DeploymentReflectionIndex straight away, I
think it could result in much cleaner code.
Does this seems like a good idea, or or there some drawbacks to this that I am missing?
+1. This will really help reduce all those conversions at various places
and make it much more simpler to setup the components.
-Jaikiran