Karaf 2.3.0 will come with pax web 1.1.3 or better.
Karaf 3.0.0 will come with pax web 2.0.0 or better.
So if you can wait this will be the simplest option. Beware though that
pax web 2 comes with Servlet API 3.0.0 this means that you will have to
update the import range of your
bundles if
Hi,
it's possible and it requires some work :)
For Pax Web 1.1.x and 2.0.0 there are features.xml available, see [1] and [2].
Still waiting for either 2.3.0 or 3.0.0 of Karaf is probably easier to handle :)
Regards, Achim
[1] -
My advice would be to wait new version of Karaf which will ship new Pax
Web version (1.1.x for Karaf 2.3.x and 2.0.x for Karaf 3.0.x).
You can upgrade and build your own distribution, but we will certainly
need to upgrade the feature and the commands (http/web).
FYI, if currently the Pax Web
@JB,
sorry right now we won't go for the Pax-Web Features in Karaf since in
Karaf we have additional Commands for it.
I'm thinking about how to handle this, but right now it's not planned
anymore (was postponed to 3.0.1 :) )
regards, Achim
2012/6/19 Jean-Baptiste Onofré j...@nanthrax.net:
My
My mistake, we discussed of that but didn't move forward ;)
Thanks for the update Achim ;)
Regards
JB
On 06/19/2012 09:23 AM, Achim Nierbeck wrote:
@JB,
sorry right now we won't go for the Pax-Web Features in Karaf since in
Karaf we have additional Commands for it.
I'm thinking about how to
Thanks! I'll wait then :)
Yours, Alexey Romanov
On Tue, Jun 19, 2012 at 11:17 AM, jbonofre [via Karaf]
ml-node+s922171n4024894...@n3.nabble.com wrote:
My advice would be to wait new version of Karaf which will ship new Pax
Web version (1.1.x for Karaf 2.3.x and 2.0.x for Karaf 3.0.x).
You
I have a bundle that uses blueprint. When I try to activate it
BlueprintExtender prints this:
Bundle ... is not compatible with this blueprint extender
Why is my bundle not compatible ? Because it uses spring 3 ?
--
View this message in context:
Such a problem is not really a problem ;-)
One possible reason is that you have multiple blueprint extenders
deployed (so multiple blueprint specs exported).
An extender will only manage the blueprint bundles that are compatible
(i.e. it imports the exact same package) as the extender.
The main
From screen shot, it looks you are trying to deploy your bundle to
Maven Central and it is throwing authentication error. I am not Maven
expert but I think to deploy your bundles to repository, you will need
to configure that in your settings.xml file.
Try using mvn install goal to install
