The plugin loading order takes 15 mins to implement. Getting OSGi to
work with Convention, 3 days and counting, I am losing my nerve
already :)

musachy

On Sun, Apr 5, 2009 at 4:54 PM, Wes Wannemacher <w...@wantii.com> wrote:
> On Sunday 05 April 2009 15:17:24 Chris Pratt wrote:
>> Sorry, I tried to make it clear that the optional attribute would be
>> available to intrinsically denote load order without imposing any
>> all-or-nothing dependency.  Basically the point is to tell struts that the
>> requirement is "if you want Convention to be able to use OSGi, check to see
>> if it's available before loading Convention".  That would not make OSGi a
>> required dependency of Convention, just an optional ability.
>>   (*Chris*)
>>
>
> You were clear enough, by the time I read Musachy's response, I had forgotten
> about the "optional." I think the thing right now is that up until now, all
> plugins have avoided interdependencies and related problems. A simple solution
> to guarantee one plugin loads before another is enough, but if you want to
> enhance it, feel free and post it in JIRA and we'll likely apply it.
>
> -Wes
>
> --
>
> Wes Wannemacher
> Author - Struts 2 In Practice
> Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more
> http://www.manning.com/wannemacher
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
>



-- 
"Hey you! Would you help me to carry the stone?" Pink Floyd

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Reply via email to