Given that the Thread Context Classloader is used, can you just set this to the correct value before invoking DefaultComponentFactory.createComponent()? I don't know the fully calling context, so perhaps that won't work. If the TCCL is the wrong choice but happens to work in a non-OSGi environment, the right solution generally is to allow for an alternate classloader to be passed in.
On Thu, Sep 14, 2017 at 11:24 PM Paul F Fraser <pa...@a2zliving.com> wrote: > Hi, > > I do not have the slightest idea if this situation can be handled, but > perhaps some kind person can > assist. > > Vaadin uses forName in the following situation and the classes are not > found when used in OSGi project. > > > https://github.com/vaadin/framework/blob/master/server/src/main/java/com/vaadin/ui/declarative/Design.java > (~ line 200) > > > https://github.com/vaadin/framework/blob/master/server/src/main/java/com/vaadin/server/VaadinServiceClassLoaderUtil.java > > If possible it would be a good contribution if we could suggest a way to > Vaadin as to how this > should/could be handled. > > Paul Fraser > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev >
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
