On Thu, Aug 13, 2015 at 3:06 PM, Daniel Stoch <[email protected]> wrote:
> On Wed, Dec 10, 2014 at 4:46 PM, Martin Grigorov <[email protected]> > wrote: > > Patches and/or Pull Requests are always welcome! > > > > Wicket-Bootstrap uses webjars and OSGi users haven't complaint so far. > > It doesn't work for me under OSGi. I think Wicket-Webjars does not > currently support OSGi, because it performs resource searching only > through directly specified class loaders. When I try to use > Wicket-Atmosphere integration on my page I have an exception: > > A ResourceReference wont be created for a resource with key [scope: > > de.agilecoders.wicket.webjars.request.resource.WebjarsJavaScriptResourceReference; > name: webjars/jquery-atmosphere/null/jquery.atmosphere.js; locale: > null; style: null; variation: null] because it cannot be located. > > Wicket-Webjars cannot find a proper version for jquery.atmosphere.js. > I am curious how Wicket-Bootstrap users using it under OSGi? According > Apparently there are not such users... (No one likes to suffer!) > to this issue it looks that this problem is not solved yet and it > looks like it will not be solved soon (this issue is over 2 years > old): > https://github.com/l0rdn1kk0n/wicket-webjars/pull/2 I'll take a look at this soon! > > There are no good extension points in Wicket-Webjars when I can > plug-in my own implementation. Eg. there is IRecentVersionProvider but > its implementation cannot be changed - there are many statics which > cannot be overriden. > > > PS. I still think that the whole webjars concept is a little bit > overdesigned and a good example how to complicate simple things ;). > One can say the same for OSGi (only with a bigger magnitude!) > > -- > Daniel >
