Which version are you using? If you are using 3.1, then did you clean
osgi-cache of glassfish before restarting? Otherwise I can't imagine
osgi-cdi bundle not available during subsequent restart while using
3.1.1. If you can provide more details to reproduce the issue, we can
look into it.
Thanks,
Sahoo
On Wednesday 09 November 2011 05:44 AM, forums_at_java.net wrote:
> Hi,
>
> I instaled a bundle using "asadmin --type osgi: command.
> my bundle contains a dependency in osgi-cdi. osgi-cdi comes oob with
> glassfish and is located in modules\autostart folder.
>
> After I run the asamin command, everything is fine. The bundle is
> installed
> and the domain.xml file is updated with the my osgi application.
> The problem starts when I restart glassfish. Looks like glassfish is
> trying
> to deploy my bundle *before *osgi-cdi is installed (and probably
> before all
> the bundles in modules\autostart) and then I get:
> Unresolved constraint in bundle...missing
> requirement...org.glassfish.osgicdi
>
> But... when I put osgi-cdi under *modules *(instead of modules/autostart)
> everything is fine.
> Is it a known issue/bug?
> Thanks
>
>
>
>
>
> --
>
> [Message sent by forum member 'Karo']
>
> View Post: http://forums.java.net/node/861935
>
>