You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Ioannis Canellos <io...@gmail.com> on 2011/04/07 20:08:51 UTC
Inconsistent behavior on war deployment
I had some issues earlier today deploying a war bundle on Karaf 2.2.0.
I was trying to deploy it using osgi:isntall -s
webbundle:mvn:groupId/artifactId/version/war.
The result was that the bundle was installed having is headers
*slightly* modified.
By modified I mean that some Imports that existed in the MANIFEST.MF were
not present using osgi:headers. Also the BundleClasspath was different from
the one delcared inside the MANIFEST.MF.
I installed the same bundle by dropping it inside karaf's deploy folder and
everything worked great.
I've already talked to Achim and he told me that pax-url-war could change
the headers in some situations.
I am not sure of what is the root cause. Shall I open a jira here, shall I
open it to ops4j?
--
*Ioannis Canellos*
*
http://iocanel.blogspot.com
Apache Karaf <http://karaf.apache.org/> Committer & PMC
Apache ServiceMix <http://servicemix.apache.org/> Committer
*
Re: Inconsistent behavior on war deployment
Posted by Ioannis Canellos <io...@gmail.com>.
I forgot to say thanks!
On Thu, Apr 7, 2011 at 9:28 PM, Ioannis Canellos <io...@gmail.com> wrote:
> Ok that makes sense, when I do it without the prefix war or webbundle it
> seems to work.
>
>
>
> On Thu, Apr 7, 2011 at 9:11 PM, Guillaume Nodet <gn...@gmail.com> wrote:
>
>> If your war is already a bundle, you should not use the webbundle url
>> handler.
>> I think that's what happen when you drop it in the deploy folder, as
>> any bundle will be installed directly bypassing any custom installer
>> iirc.
>> What happen if you just run "osgi:install -s mvn:xxx" on your war ?
>>
>> On Thu, Apr 7, 2011 at 20:08, Ioannis Canellos <io...@gmail.com> wrote:
>> > I had some issues earlier today deploying a war bundle on Karaf 2.2.0.
>> >
>> > I was trying to deploy it using osgi:isntall -s
>> > webbundle:mvn:groupId/artifactId/version/war.
>> >
>> > The result was that the bundle was installed having is headers
>> > *slightly* modified.
>> > By modified I mean that some Imports that existed in the MANIFEST.MF
>> were
>> > not present using osgi:headers. Also the BundleClasspath was different
>> from
>> > the one delcared inside the MANIFEST.MF.
>> >
>> > I installed the same bundle by dropping it inside karaf's deploy folder
>> and
>> > everything worked great.
>> >
>> > I've already talked to Achim and he told me that pax-url-war could
>> change
>> > the headers in some situations.
>> >
>> > I am not sure of what is the root cause. Shall I open a jira here, shall
>> I
>> > open it to ops4j?
>> >
>> > --
>> > *Ioannis Canellos*
>> > *
>> > http://iocanel.blogspot.com
>> >
>> > Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> > Apache ServiceMix <http://servicemix.apache.org/> Committer
>> > *
>> >
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>
>
>
> --
> *Ioannis Canellos*
> *
> http://iocanel.blogspot.com
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> Apache ServiceMix <http://servicemix.apache.org/> Committer
> *
>
>
>
>
>
>
--
*Ioannis Canellos*
*
http://iocanel.blogspot.com
Apache Karaf <http://karaf.apache.org/> Committer & PMC
Apache ServiceMix <http://servicemix.apache.org/> Committer
*
Re: Inconsistent behavior on war deployment
Posted by Ioannis Canellos <io...@gmail.com>.
Ok that makes sense, when I do it without the prefix war or webbundle it
seems to work.
On Thu, Apr 7, 2011 at 9:11 PM, Guillaume Nodet <gn...@gmail.com> wrote:
> If your war is already a bundle, you should not use the webbundle url
> handler.
> I think that's what happen when you drop it in the deploy folder, as
> any bundle will be installed directly bypassing any custom installer
> iirc.
> What happen if you just run "osgi:install -s mvn:xxx" on your war ?
>
> On Thu, Apr 7, 2011 at 20:08, Ioannis Canellos <io...@gmail.com> wrote:
> > I had some issues earlier today deploying a war bundle on Karaf 2.2.0.
> >
> > I was trying to deploy it using osgi:isntall -s
> > webbundle:mvn:groupId/artifactId/version/war.
> >
> > The result was that the bundle was installed having is headers
> > *slightly* modified.
> > By modified I mean that some Imports that existed in the MANIFEST.MF were
> > not present using osgi:headers. Also the BundleClasspath was different
> from
> > the one delcared inside the MANIFEST.MF.
> >
> > I installed the same bundle by dropping it inside karaf's deploy folder
> and
> > everything worked great.
> >
> > I've already talked to Achim and he told me that pax-url-war could change
> > the headers in some situations.
> >
> > I am not sure of what is the root cause. Shall I open a jira here, shall
> I
> > open it to ops4j?
> >
> > --
> > *Ioannis Canellos*
> > *
> > http://iocanel.blogspot.com
> >
> > Apache Karaf <http://karaf.apache.org/> Committer & PMC
> > Apache ServiceMix <http://servicemix.apache.org/> Committer
> > *
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
--
*Ioannis Canellos*
*
http://iocanel.blogspot.com
Apache Karaf <http://karaf.apache.org/> Committer & PMC
Apache ServiceMix <http://servicemix.apache.org/> Committer
*
Re: Inconsistent behavior on war deployment
Posted by Guillaume Nodet <gn...@gmail.com>.
If your war is already a bundle, you should not use the webbundle url handler.
I think that's what happen when you drop it in the deploy folder, as
any bundle will be installed directly bypassing any custom installer
iirc.
What happen if you just run "osgi:install -s mvn:xxx" on your war ?
On Thu, Apr 7, 2011 at 20:08, Ioannis Canellos <io...@gmail.com> wrote:
> I had some issues earlier today deploying a war bundle on Karaf 2.2.0.
>
> I was trying to deploy it using osgi:isntall -s
> webbundle:mvn:groupId/artifactId/version/war.
>
> The result was that the bundle was installed having is headers
> *slightly* modified.
> By modified I mean that some Imports that existed in the MANIFEST.MF were
> not present using osgi:headers. Also the BundleClasspath was different from
> the one delcared inside the MANIFEST.MF.
>
> I installed the same bundle by dropping it inside karaf's deploy folder and
> everything worked great.
>
> I've already talked to Achim and he told me that pax-url-war could change
> the headers in some situations.
>
> I am not sure of what is the root cause. Shall I open a jira here, shall I
> open it to ops4j?
>
> --
> *Ioannis Canellos*
> *
> http://iocanel.blogspot.com
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> Apache ServiceMix <http://servicemix.apache.org/> Committer
> *
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com