[windup-dev] Problem with WindupConfigModel

Lincoln Baxter, III lincolnbaxter at gmail.com
Fri Sep 12 07:04:58 EDT 2014


Discussion moved to pull request: https://github.com/windup/windup/pull/228

On Sat, Sep 6, 2014 at 9:01 AM, Ondrej Zizka <ozizka at redhat.com> wrote:

> Problem with WindupConfigModel is that *currently* it needs context
> initialized, since it is initialized like this:
>
>      WindupConfigurationModel config =
> GraphService.getConfigurationModel(context);
>
> And at the same time this config "DTO" needs to be passed into the
> top-level API (currently WindupProcessor).
>
> I can see 2 solutions:
>
>     A) Continue using WCM, implement    WINDUP-147 GraphService.merge()
> to store classes implementing the model interface
>             so that supports adjacent models (needed for the scan packages)
>
>     B) Have WindupConfig, and copy stuff to WCM (which is the same as A,
> only done manually)
>
>     C) What I am currently doing, an ugly hack - passing final variables
> into GraphLifecycleListener
>
> Ondra
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140912/6db8083e/attachment.html 


More information about the windup-dev mailing list