Re: Remote services with Karaf question.

2019-08-04 Thread Jean-Baptiste Onofré 
Hi Ryan,

Cellar doesn't support R7 remote services yet (it's on the way).

However, you can use the Cellar Hazelcast feature and use ECF.

Regards
JB

On 04/08/2019 19:34, Ryan Moquin wrote:
> Hi, I was going to start playing with OSGi R7 with Karaf.
> 
> Does Cellar support R7 remote services?  If I was interested in
> Hazelcast under the covers, would the be a reason to use any of the
> other remote services implementations like ECF along with Cellar or just
> use the implementation Cellar provides?
> 
> Is there a generally preferred approach to R7 on Karaf?
> 
> Thanks for any advice!
> 
> Ryan

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Remote services with Karaf question.

2019-08-04 Thread Scott Lewis 

On 8/4/2019 10:34 AM, Ryan Moquin wrote:

Hi, I was going to start playing with OSGi R7 with Karaf.

Does Cellar support R7 remote services?  If I was interested in 
Hazelcast under the covers, would the be a reason to use any of the 
other remote services implementations like ECF along with Cellar or 
just use the implementation Cellar provides?


I'm not sure if Cellar can use R7 remote services, but if it can then I 
think that your desire to use Hazelcast as transport would provde a good 
reason to use ECF's R7 Remote Services impl, as ECF does already have a 
Hazelcast-based provider [1].


One current shortcoming is that the Hazelcast provider does not yet have 
a set of Karaf features for it (like most other ECF RS providers), but 
that would be easy for us to create/produce if requested.





Is there a generally preferred approach to R7 on Karaf?

Thanks for any advice!

Ryan



[1] https://github.com/ECF/HazelcastProvider

Remote services with Karaf question.

2019-08-04 Thread Ryan Moquin 
Hi, I was going to start playing with OSGi R7 with Karaf.

Does Cellar support R7 remote services?  If I was interested in Hazelcast
under the covers, would the be a reason to use any of the other remote
services implementations like ECF along with Cellar or just use the
implementation Cellar provides?

Is there a generally preferred approach to R7 on Karaf?

Thanks for any advice!

Ryan

Re: ClassCastException with useSSH

2019-08-04 Thread Ryan Moquin 
No prob.  It's an odd error.  I didn't think bouncy castle is used by
default.

Ryan

On Sun, Aug 4, 2019, 12:36 AM Jean-Baptiste Onofré  wrote:

> Hi Ryan,
>
> let me try to reproduce. Thanks for the report.
>
> Regards
> JB
>
> On 04/08/2019 03:33, Ryan Moquin wrote:
> > Hi, has anyone tried using the karaf-maven-plugin run goal with the
> > useSsh option set to true?
> > If seems that if you just start up a vanilla 4.2.5 and 4.2.6 with it,
> > you will see this stacktrace:
> >
> > 2019-08-03T21:25:33,790 | WARN  | activator-1-thread-1 | Activator
> >  | 36 - org.apache.karaf.shell.ssh - 4.2.5 | Error
> > starting activator
> > java.lang.ClassCastException: Cannot cast
> >
> org.apache.sshd.common.util.security.bouncycastle.BouncyCastleSecurityProviderRegistrar
> > to org.apache.sshd.common.util.security.SecurityProviderRegistrar
> > at java.lang.Class.cast(Class.java:3369) ~[?:?]
> > at
> >
> org.apache.sshd.common.util.threads.ThreadUtils.createDefaultInstance(ThreadUtils.java:114)
> > ~[39:org.apache.sshd.core:1.7.0]
> > at
> >
> org.apache.sshd.common.util.threads.ThreadUtils.createDefaultInstance(ThreadUtils.java:121)
> > ~[39:org.apache.sshd.core:1.7.0]
> > at
> >
> org.apache.sshd.common.util.threads.ThreadUtils.createDefaultInstance(ThreadUtils.java:107)
> > ~[39:org.apache.sshd.core:1.7.0]
> > at
> >
> org.apache.sshd.common.util.security.SecurityUtils.register(SecurityUtils.java:397)
> > ~[39:org.apache.sshd.core:1.7.0]
> > at
> >
> org.apache.sshd.common.util.security.SecurityUtils.isEDDSACurveSupported(SecurityUtils.java:529)
> > ~[39:org.apache.sshd.core:1.7.0]
> > at
> >
> org.apache.sshd.common.signature.BuiltinSignatures$6.isSupported(BuiltinSignatures.java:103)
> > ~[39:org.apache.sshd.core:1.7.0]
> > at
> >
> org.apache.sshd.common.NamedFactory.lambda$setUpBuiltinFactories$1(NamedFactory.java:63)
> > ~[39:org.apache.sshd.core:1.7.0]
> > at
> >
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
> ~[?:?]
> > at
> >
> java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
> > ~[?:?]
> > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> > ~[?:?]
> > at
> >
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> > ~[?:?]
> > at
> >
> java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> > ~[?:?]
> >
> > As I mentioned, this happens with installing anything into the
> > containing.  Thought it might be useful to be able to have that option
> > turned on.
> >
> > Thanks for any help!
> > Ryan
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>