On Wed, Oct 17, 2012 at 12:54 PM, Paul Illingworth
<
pillin...@gmail.com> wrote:
> By inline you mean take the source for the UniqueAnnotations and drop it
> into the gwt-dispatch library? Or do you mean using some maven-bundle-plugin
> magic that can pull in packages from dependencies like Guice and include
> those? I am not too sure if it can be used for individual classes.
It's a configuration option for the maven-bundle-plugin, which
delegates to bnd. I'm not sure of the exact syntax right now.
>
> As I see it I have a couple of options
>
> 1) Update the pom for gwt-dispatch; change from jar packaging to bundle
> packaging and use the maven-bundle-plugin to generate the manifest. Also
> copy/paste the UniqueAnnotations class from Guice. Submit this back to the
> gwt-dispatch project and hopefully get it in the next version of
> gwt-dispatch.
>
> 2) Do this externally to gwt-dispatch - create my own gwt-dispatch-osgi
> project that has gwt-dispatch as dependency, also add the code for
> UniqueAnnotations from Guice and then repackage it and generate the
> manifest.
>
> I am not too sure about the legalities of "pinching" and redistributing the
> Guice UniqueAnnotations code. I guess as it uses the Apache 2 licence this
> is ok.
>
> Option 1 is better for me long term. Option 2 I can do on my own.
>
> Thoughts?
I'd be happy to accept a contribution, given that the jar remains
usable for non-OSGi environments.
Robert
>
>
> On Tuesday, 21 August 2012 14:11:05 UTC+1, Evan Ruff wrote:
>>
>> Hey guys,
>>
>> Has anyone attempted to get GWT-Dispatch working with Peaberry in a
>> Felix/OSGi container? I'm getting some errors around finding the
>> ActionHandler:
>>
>> java.lang.NoClassDefFoundError:
>> net/customware/gwt/dispatch/server/guice/ActionHandlerModule
>>
>> I'm a total newbie to the OSGi/Peaberry world, so my first inclination
>> would be to think I need to OSGi-fy the JAR, so I'll try that, but I figured
>> I'd post in case someone has experience with the error/config.
>>
>> Thanks!
>>
>> E