You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the resources are in the different bundle it's not possible to access them in this way.
The code should be adapted to be able to work with OSGi.
The implementation suggestion:
Make a service in flow-server.
flow-client depends on the flow-server so it may implement a service and register it.
flow-server should check the presence of OSGi and if we are in OGSi container use the service, otherwise use plain Java approach.
we will need to have a code which depends on the OSGi classes which may not be in the classpath during runtime. So OSGi dependency should be added to the flow-server module as provided and OSGi related code should be separated from other code so that there will be no runtime exception on resources load.
That's one of the suggestion.
There can be other ways (don't know about them unfortunately) but I'm going to implement it in this way for now.
The implementation may be changed later on. But the issue is still the same: the resources are in the other bundle and we need a way to access them.
The text was updated successfully, but these errors were encountered:
BootstrapHandler
class needs generated resource in theflow-client
module.The way how it's done is :
Since the resources are in the different bundle it's not possible to access them in this way.
The code should be adapted to be able to work with OSGi.
The implementation suggestion:
flow-server
.flow-client
depends on theflow-server
so it may implement a service and register it.flow-server
should check the presence of OSGi and if we are in OGSi container use the service, otherwise use plain Java approach.flow-server
module asprovided
and OSGi related code should be separated from other code so that there will be no runtime exception on resources load.That's one of the suggestion.
There can be other ways (don't know about them unfortunately) but I'm going to implement it in this way for now.
The implementation may be changed later on. But the issue is still the same: the resources are in the other bundle and we need a way to access them.
The text was updated successfully, but these errors were encountered: