Hi,
can you check if the cellar-dosgi bundle contains Dynamic-Import with * ?
As the transport is via DOSGi/Hazelcast, it has to contain the dynamic import.
Regards
JB
On 02/22/2018 07:39 AM, Dominik Marciniszyn wrote:
> Hi,
>
> I've checked the DynamicImport. I used DynamicImport in packages
Hi,
For now I've added the DynamicImport to all my bundles. I have got four
bundles: service-api, service-impl, character, and client. In each I have
got *, my.bundle.needed .
After this I once again build each bundle and update them on cluster and
instances.
Regards,
Dominik
--
Sent from: h
I found the solution for this. I remove fro my pom.xml files Dynamic-Import
and use dynamic-import command in karaf instances on bundle:
[ Apache Karaf :: Cellar :: Hazelcast ]
Then ClassNotFoundException disappears and now objects are passing between
nodes.
I am using:
Apache Karaf version 4.1.4
That's exactly what I meant ;)
You got it. I think I already fixed that on Cellar to use * for Dynamic-Import
by default.
Regards
JB
On 02/22/2018 01:49 PM, Dominik Marciniszyn wrote:
> I found the solution for this. I remove fro my pom.xml files Dynamic-Import
> and use dynamic-import command i
I have a configuration type that has a fragment in it as shown below.
@ProviderType
@ObjectClassDefinition(name = "Provider Configuration")
public @interface MetricProviderConfig
{
String schedule() default "0";
}
If the associated property in a .cfg file exists but has no value, as in:
s
As I mentioned a few weeks ago, I'm trying to create a service instance
programmatically and write the associated .cfg file for it. Based on feedback
I got, I create the following method.
The goal is to create the service instance and then get its configuration which
at this point will mostly
Hi Scott,
why don't use a managed service factory ?
It would automatically create a service based on a cfg. So for your user, he
creates the cfg file, and then, automatically, the corresponding service is
created.
Thoughts ?
Regards
JB
On 02/22/2018 09:18 PM, Leschke, Scott wrote:
> As I ment
Thanks JB,
Initially, the .cfg would be populated almost entirely with the defaults the
service receives using a configuration type so the idea is that the service
creation needs to come first so that the service can be used to get the values
to write the .cfg.
Is there a way to get those val
Hi Scott,
Service Managed Factory is the other way around: you start from the cfg file,
then the service is created. The content of the file can be default or whatever,
it doesn't matter.
Basically, you would have:
etc/org.scott.foo-one.cfg
etc/org.scott.foo-two.cfg
etc/org.scott.foo-three.cfg
