Hi,
could you try with the latest 4.0.0-SNAPSHOT?
For this you'd need to have a vanilla karaf first, or at least no Pax Web
3.1.x bundles installed,
add the 4.0.0-SNAPSHOT feature url to your repository and install the Pax
Web 4.0 features.
You'd gonna miss the web and http commands but I'd think
Hi
There's something I haven't quite understood yet in OSGI, it seems.
I have two bundles (A and B) and bundle A uses a class from bundle B.
In my pom file of bundle A I specify in the maven-bundle-plugin
...
import-Package
javax.xml.bind,
According to your pom, bundle B is the exporter of this package, not the
importer? So either your class isn't being packaged correctly by Maven, or
you've got your inports and exports the wrong way around in your POM?
On 18 Jun 2014, at 21:35, Laci Gaspar wrote:
Caused by:
Hi,
how did you install the bundle in question?
is it a maven coordinate? Like, mvn:groupId/artifactId/version
or is it a file:
or is it a combination of wrap and file or maven?
cause I think the later is hard for the bundle:watch to determine if it's
updated.
regards, Achim
2014-06-18
Hi,
the bundle in question is org.apache.openejb.core-osgi 4.5.2.
It is installed as a maven coordinate:
mvn:org.apache.openejb/openejb-core-osgi/4.5.2.
Regards,
Simon
--
View this message in context:
Thanks.
What is the repo and feature URL for the 4.0.0-SNAPSHOT feature?
I added
https://oss.sonatype.org/content/repositories/ops4j-snapshots@id=ops4j.snapshot
to my repositories and then I can do:
repo-add mvn:org.ops4j.pax.web/pax-web-features/4.0.0-SNAPSHOT/xml/features
This works fine.
I'm trying to get familiar with Blueprint. I don't think a Blueprint container
is being created for my bundle because I don't see a message in the log saying
it's been destroyed when I shut Karaf down. I assume that's a pretty good
indicator.
If that's correct, is there a good way to
I'm not sure if this is completely right or not, but I figured out I can do:
feature:install pax-jetty
feature:install pax-http
feature:install pax-war
Although the last one results in this error:
Error executing command: Manifest not present in the first entry of the zip
Hi Folks,
I'm working on producing karaf features for ECF's upcoming Luna release
(next week), and I'm wondering: should I target Karaf 3.0.1 or Karaf 4?
I've seen discussion of Karaf 4 on this mailing list, but I couldn't
find details of it on the karaf roadmap [1]. e.g. which OSGi
A quick way, I have found is to use org.slf4j.Logger and log an info
statement in your init method. You see pretty quick when you start your
bundle that things are working.
If you don't see the message, then:
* Where is your activator.xml located? (Under OSGI-INF/blueprint)
* What is the
Karaf 3.0.x is already OSGI 5.0, are there additional requirements
that would preclude it going on 3.0.x or 3.1.x?
Cheers,
Jamie
On Wed, Jun 18, 2014 at 2:17 PM, Scott Lewis sle...@composent.com wrote:
Hi Folks,
I'm working on producing karaf features for ECF's upcoming Luna release
(next
The first stage is to make sure your blueprint file is processed at all.
So make sure it is at the correct location (OSGI-INF/blueprint/*.xml)
and that the namespace is correct.
If the file is processed you should see logging messages and the bundle
list should show the blueprint status too.
Hi Jamie,
On 6/18/2014 10:08 AM, Jamie G. wrote:
Karaf 3.0.x is already OSGI 5.0, are there additional requirements
that would preclude it going on 3.0.x or 3.1.x?
No, not if the underlying frameworks are OSGi 5 compliant. What I was
going by for Karaf 3.X was this on the Karaf home page:
Ah, we'll have to update the main page. I tend to use the dependencies matrix:
http://karaf.apache.org/index/documentation/karaf-dependencies/karaf-deps-3.0.x.html
Cheers,
Jamie
On Wed, Jun 18, 2014 at 2:55 PM, Scott Lewis sle...@composent.com wrote:
Hi Jamie,
On 6/18/2014 10:08 AM, Jamie G.
Hi Scott,
1/ using la, what's the state of your bundle ?
2/ where your blueprint XML are located ?
3/ what's the name space ?
4/ anything in log:display or in data/karaf.log ?
Regards
JB
On 06/18/2014 05:56 PM, Leschke, Scott wrote:
I’m trying to get familiar with Blueprint. I don’t think a
On 6/18/2014 10:32 AM, Jamie G. wrote:
Ah, we'll have to update the main page. I tend to use the dependencies matrix:
http://karaf.apache.org/index/documentation/karaf-dependencies/karaf-deps-3.0.x.html
Ok...thanks.
Returning to the original question: any info or pointers on Karaf 3.X
Tim Jones wrote
There are probably many arguments against using Spring ranging from
'Spring oriented technologies have a very unmodular streak in them'...
Thought I'd comment on this particular statement... We really shouldn't be
making (or spreading) unfounded statements like this.
Hi Scott,
Karaf 3 uses:
- Felix Framework 4.2.1
- Equinox 3.8.2
So it means full OSGi r4.3 support, and partial r5 support.
I upgraded Karaf 4 to use Felix Framework 4.4.0 and Equinox 3.9.1,
providing a full OSGi r5 support.
In term of release plan, I schedule Karaf 3.0.2 at least for end
Hi Scott (again ;))
for R6, I would wait to have a first framework implementing the spec
before updating.
Regards
JB
On 06/18/2014 07:39 PM, Scott Lewis wrote:
On 6/18/2014 10:32 AM, Jamie G. wrote:
Ah, we'll have to update the main page. I tend to use the dependencies
matrix:
Hi,
ok, you're using the last 3.0.1 Karaf right, we had a issue with the
feature installer that looks for the Manifest file which usually is the
first entry in a jar, but looks like that particular one is missing it,
I'll try to re-animate the wrap for that bundle again.
Besides this flaw you're
Achim,
Yes, I'm using the released 3.0.1. I'll try again later today.
Kevin
On Wed, Jun 18, 2014 at 10:58 AM, Achim Nierbeck bcanh...@googlemail.com
wrote:
Hi,
ok, you're using the last 3.0.1 Karaf right, we had a issue with the
feature installer that looks for the Manifest file which
Hi Jean, Guillaume, Jamie, others,
Just to be clear about our plans and needs here:
1) Our upcoming Luna release (what I'm currently preparing karaf
features for) is R5 compliant. It will therefore work with Karaf 3.X,
and I fully expect for 4.X as well.
2) We are finishing a 3.9 release
Looks good so far, the only thing that puzzles me, it's a released version,
why would you want to do a bundle:watch / dev:watch on that. I'm not even
sure this works.
regards, Achim
2014-06-18 15:56 GMT+02:00 sprinz simon.pr...@doubleslash.de:
Hi,
the bundle in question is
23 matches
Mail list logo
