I did start some work around making a DS solution for Camel using enRoute as a
base, am not successful yet in making that happen. i have repo here
https://github.com/kameshsampath/org.workspace7.osgi.enroute.camel. I am facing
some technical issues in getting it running even the simplest Camel r
I am using Apache Aries with Camel, as part of my test with pax-jdbc I have
registered the JNDI datasource via Karaf cfg – it all works fine when deployed
in Karaf, when doing the testing via CamelBlueprintTest am getting the
following error :
“
Caused by: javax.naming.NoInitialContextException
IMHO, the subsystem type “osgi.subsystem.feature” is a unscoped subsystem,
ideally the Export/Import packages from them will not have any effect.
For “osgi.subsystem.feature” you can play with imports/exports within the
respective Subsytem resources instead at the subsystem level.
On 29/07/15
ystem type application
exports nothing (afaik). So this would fit my application. The application
doesn't share anything with any other subsystem. The only thing it exposes to
the outside of the subsystem would be events.
2015-07-14 8:43 GMT+02:00 Kamesh Sampath :
Am not much aware on K
karaf.
I always tried the subsystem type application and it didn't work with it. When
I switched to subsystem type feature everything worked fine. Though feature is
not what i necessarily wanted.
2015-07-10 18:39 GMT+02:00 Kamesh Sampath :
Yeah the old link does not work while the new one wor
BTW ... it all worked when I dropped the bundles into the deploy folder. I used
the maven esa plugin for building the ESA file.
Thanx
Mihael
2015-07-10 16:12 GMT+02:00 Kamesh Sampath :
Hi Mihael,
BundleActivator has nothing to do with Subsytems, “Subsystem” is a mechanism
to deploy a collecti
Hi Mihael,
BundleActivator has nothing to do with Subsytems, “Subsystem” is a mechanism
to deploy a collection of resources (bundles).
I hope you have set up the Karaf based like said [1] and did you try building
your esa using the tools [2]
[1] http://aries.apache.org/modules/subsystems.h
Can you please post your SUBSYSTEM.MF and the pom.xml which generates the Esa ?
On 03/04/15 5:11 pm, "Jeroen Baekelandt" wrote:
>Hi,
>
>We have an esa with following structure:
>
>--- service-user-subsystem-0.0.1-SNAPSHOT.esa
>-- OSGI-INF/SUBSYSTEM.MF
>-- service-subsystem-0.0.1-SNAPSH
ugin and saw this warning
> in logs, so checking if there is an impact. If will ignore if you say so!!!
>
> From: Kamesh Sampath [mailto:kamesh.samp...@liferay.com]
> Sent: Monday, March 30, 2015 4:35 PM
> To: user@aries.apache.org
> Subject: Re: esa-maven-plugin is not marked
but why do you need the maven plugin to be thread safe, its just build tool. my
thought would be to ignore it.
-Kamesh
> On 30-Mar-2015, at 4:31 pm, Goyal, Arpit wrote:
>
> Hi Colleagues,
>
> We are using the esa-maven-plugin and I was running, using option –T (mvn –T
> 1.5C clean install)
on the API bundle exporting the packages but the wiring bundles
does not know which host exports the API so we need to define the `wiring.host`
name in the API bundle and list the services that provider or requirer might
use.
HTH
—
Kamesh Sampath
Sr.Architect, Liferay India
Twitter <http
does not index the esa as it does not know
how/what to index, currently even in OSGi spec we dont have the right defs for
it.
@David, please feel to add if i had missed any point.
—
Kamesh Sampath
Sr.Architect, Liferay India
Twitter <https://twitter.com/@kamesh_Sampath> | LinkedIn
am not seeing be.aca.service.api in the obr:list, where is that bundle ?
—
Kamesh Sampath
Sr.Architect, Liferay India
Twitter <https://twitter.com/@kamesh_Sampath> | LinkedIn
<http://in.linkedin.com/pub/kamesh-sampath/4b/934/338/>
> On 25-Mar-2015, at 6:02 pm, Tim
You are right Jeron right now there is no tooling around it, to build a tool we
need to have the subsystem indexing spec defined so that tools like bndtools
can generate the index.xml
-Kamesh
> From: yrn...@gmail.com
> To: user@aries.apache.org
> Subject: Generating repository xml containi
I am trying to deploy a subsystem on to my OSGi container, my subsystem was
successfully installed but I see the following issues:Hi,
I am trying to deploy a subsystem on to my OSGi container, my subsystem was
successfully installed but I see the following issues:
* The subsystem getting insta
d I'm sure.
>
> Best,
>
> David
>
> [1] https://github.com/bndtools/bnd/blob/master/REPOINDEX.md
>
> On 31 December 2014 at 14:56, Kamesh Sampath
> wrote:
> > Hi,
> >
> > How can index the ESA bundles? Currently we can index the normal OSGi
>
> tool [1] or the maven bundle plugin. AFAIK there is currently no
> ready-made tool that can do this yet. Both are open source, so more
> help is always appreciated I'm sure.
>
> Best,
>
> David
>
> [1] https://github.com/bndtools/bnd/blob/master/REPOINDEX.md
>
t;
> [1] https://github.com/bndtools/bnd/blob/master/REPOINDEX.md
>
> On 31 December 2014 at 14:56, Kamesh Sampath
> wrote:
> > Hi,
> >
> > How can index the ESA bundles? Currently we can index the normal OSGi
> > bundles using the Apache maven bundle plugin or using
Hi,
How can index the ESA bundles? Currently we can index the normal OSGi bundles
using the Apache maven bundle plugin or using the bndtools indexing tool. But
I dont see how I can index Subsystem archives *.esa.
I was following David Bosschaert blog posts on Subsystems and download his
demo
19 matches
Mail list logo
