Well, Sling uses Felix 1.0.4 right? I'm running my tests with 1.4.1 and also I have a newer version of the equinox. After running sling on debug mode here I found that the source I have for the equinox server api is not the same. I wonder if this is the problem. One difference I have is the props.put(EMBEDDED_EXECUTION_PROP, "true"); since it seems that it does not exist anymore.
On Tue, Jan 20, 2009 at 2:15 PM, Vinicius Carvalho < [email protected]> wrote: > Well, I'm still trying here to get it working. As for using Sling, well, if > we could use just the launcher that would be one ideia, but we really would > not like to have the whole sling application just to use web-console. > Although we will need a JCR repository in our app, I don't think we should > have sling embedded . > > Regards > > On Tue, Jan 20, 2009 at 1:44 PM, Carsten Ziegeler <[email protected]>wrote: > >> Vinicius Carvalho wrote: >> > Well, The Activator is receiving the System bundlecontext where the >> > webconsole gets its own bundlecontext. When we register a service >> tracker it >> > tracks services only for the specific bundle? could this be the problem? >> > >> This is correct, the service tracker tracks all services regardless from >> which bundle >> they're comming. >> >> I've no idea what goes wrong in your case, but why are you not just >> using the Sling Webapp? I has nearly no overhead and provides you with a >> usuable setup. Or you can use the standalone jar from Sling. >> >> Carsten >> >> >> -- >> Carsten Ziegeler >> [email protected] >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >
