You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Srikanth Hugar <sr...@gmail.com> on 2014/09/23 08:23:19 UTC
wrong choice by karaf 3.0.0, pax web 3.0.5, cxf 2.7.7...????
Hello All,
I am not sure whether i have made wrong choice by karaf 3.0.0, pax web
3.0.5, cxf 2.7.7.
I have been facing multiple problems from beginning and some problems which
are very important/critical for my product, i don't have the answers.
Did anybody tried with above libraries? Were you successful?
1. https://ops4j1.jira.com/browse/PAXWEB-738
2.
http://mail-archives.apache.org/mod_mbox/karaf-user/201409.mbox/%3CCAOUabB0dRPd==d+6sxiGzFGfe4A4HZ8reACHeeQd6_h8y0+iMA@mail.gmail.com%3E
3. No i have another problem, i wanted to run always with https, bit by
configurin jetty.xml, service is also listening at 8080.
....... list goes on.
--
Srikanth
w <http://www.srikanthugar.in>ww.gharki.com
Re: wrong choice by karaf 3.0.0, pax web 3.0.5, cxf 2.7.7...????
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi Srikanth,
maybe it's been a to long mail from me, but for 2 there is a working
solution available :) see link [6] in my previous mail.
for 1. this entirely depends on your use-case, that's why we need more
information.
Is it an issue with CXF? in that case Jean-Babtist gave you already the
needed hint, it needs to be done with CXF.
Is it a WAR use-case, I think I've shown you plenty of doable solutions.
If it is a Http-Service/Whiteboard use-case, again take a look of what I've
told you so far.
I think we gave you plenty of information (threads), you'll need to stich
this together for yourself to a have a nice coat ;)
The blueprint is there.
Regards, Achim
2014-09-23 11:32 GMT+02:00 Srikanth Hugar <sr...@gmail.com>:
> Thank you all for quick response. I resolved some issues after our
> discussion. As of now i have only 2 issues now.
>
> 1. Multiple connectors - run bundle with specific connector.
> 2. And serving static files as i mentioned in previous mail.
>
>
>
>
>
> On Tue, Sep 23, 2014 at 1:20 PM, Charlie Mordant <cm...@gmail.com>
> wrote:
>
>> Hi Srikanth,
>>
>> You've not made the wrong choice but the best one :)!
>> As Achim said, you just have to forget all about the 'all in a war' J2EE
>> way of thinking.
>> Put all your services in different Web-ContextPath Manifest entry filled
>> plain old Jars.
>> Learn to fragment all your monolitic applications into reusable bundles,
>> then you'll see the incredible power of the choice you've made.
>> Unfortunately, I can't answer for your problem due to lack of
>> informations and knowledge on Pax-Web, Achim is the man! :).
>>
>> Regards, Charlie
>>
>>
>> 2014-09-23 8:44 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
>>
>>> HI Srikanth,
>>>
>>> I fear we are missing your use-case to beginn with, to understand what
>>> you are trying to achieve.
>>> Only with some breadcrumbs of information we just can help you on
>>> certain topics.
>>> In general I don't think using Karaf 3.x with cxf and Pax Web is a wrong
>>> decision. You just have to get rid of the "old" war thinking.
>>>
>>> First of all make sure you configure the Webcontainer right. I think
>>> this is the first Time you talk of that you only want to have SSL, this is
>>> a real easy task and if you look at the samples in combination with the
>>> integration tests of Pax Web, you'll see how easy it actually is. Btw. the
>>> Apache Karaf Cookbook [1] also does contain enough explanation and examples
>>> on how to work with Apache Karaf in general and it does cover Pax Web with
>>> a big chapter explaining simple use-cases to get going with CXF, so at this
>>> point there are resources available.
>>>
>>> For working with SSL, you might want to also look at [2] the integration
>>> test fulfilling this task. Or if you want a blog post [3][4]. And actually
>>> there is also documentation available on how to configure SSL at Pax Web
>>> [5]. Besides that you just need to make sure you turn off the std. http
>>> port.
>>>
>>> Regarding CXF as I already stated there is a book available also
>>> covering this [1]
>>> and as JB already noted if you want to bind a certain CXF servlet to a
>>> special connector you'll need to configure this to CXF itself, the
>>> mechanism for WARs doesn't work there. This is due to the fact that CXF
>>> itself just uses the HttpService.
>>>
>>> Regarding PAXWEB-738, looks like you found a bug, cause afaik it used to
>>> work. I'll work on this as soon as possible but not within the next two
>>> weeks. What you can do to work around that issue is to actually use what is
>>> done in the sample at [6]. It uses the HttpService to achieve the task.
>>>
>>> regards, Achim
>>>
>>>
>>> [1] - http://bit.ly/1ps9rkS
>>> [2] -
>>> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/WarBasicAuthSecuredIntegrationTest.java
>>> [3] -
>>> http://blog.nanthrax.net/2013/02/multiple-http-connectors-in-apache-karaf/
>>> [4] -
>>> http://blog.nanthrax.net/2012/12/how-to-enable-https-certificate-client-auth-with-karaf/
>>> [5] - https://ops4j1.jira.com/wiki/display/paxweb/SSL+Configuration
>>> [6] -
>>> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/WhiteboardAliasIntegrationTest.java
>>>
>>> 2014-09-23 8:23 GMT+02:00 Srikanth Hugar <sr...@gmail.com>:
>>>
>>>> Hello All,
>>>>
>>>> I am not sure whether i have made wrong choice by karaf 3.0.0, pax
>>>> web 3.0.5, cxf 2.7.7.
>>>> I have been facing multiple problems from beginning and some problems
>>>> which are very important/critical for my product, i don't have the answers.
>>>>
>>>> Did anybody tried with above libraries? Were you successful?
>>>>
>>>> 1. https://ops4j1.jira.com/browse/PAXWEB-738
>>>> 2.
>>>> http://mail-archives.apache.org/mod_mbox/karaf-user/201409.mbox/%3CCAOUabB0dRPd==d+6sxiGzFGfe4A4HZ8reACHeeQd6_h8y0+iMA@mail.gmail.com%3E
>>>> 3. No i have another problem, i wanted to run always with https, bit by
>>>> configurin jetty.xml, service is also listening at 8080.
>>>>
>>>> ....... list goes on.
>>>>
>>>>
>>>> --
>>>> Srikanth
>>>> w <http://www.srikanthugar.in>ww.gharki.com
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Apache Member
>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
>>> & Project Lead
>>> blog <http://notizblog.nierbeck.de/>
>>>
>>> Software Architect / Project Manager / Scrum Master
>>>
>>>
>>
>>
>> --
>> Charlie Mordant
>>
>> Full OSGI/EE stack made with Karaf:
>> https://github.com/OsgiliathEnterprise/net.osgiliath.parent
>>
>
>
>
> --
> Srikanth
> www.srikanthugar.in
>
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Software Architect / Project Manager / Scrum Master
Re: wrong choice by karaf 3.0.0, pax web 3.0.5, cxf 2.7.7...????
Posted by Srikanth Hugar <sr...@gmail.com>.
Thank you all for quick response. I resolved some issues after our
discussion. As of now i have only 2 issues now.
1. Multiple connectors - run bundle with specific connector.
2. And serving static files as i mentioned in previous mail.
On Tue, Sep 23, 2014 at 1:20 PM, Charlie Mordant <cm...@gmail.com>
wrote:
> Hi Srikanth,
>
> You've not made the wrong choice but the best one :)!
> As Achim said, you just have to forget all about the 'all in a war' J2EE
> way of thinking.
> Put all your services in different Web-ContextPath Manifest entry filled
> plain old Jars.
> Learn to fragment all your monolitic applications into reusable bundles,
> then you'll see the incredible power of the choice you've made.
> Unfortunately, I can't answer for your problem due to lack of informations
> and knowledge on Pax-Web, Achim is the man! :).
>
> Regards, Charlie
>
>
> 2014-09-23 8:44 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
>
>> HI Srikanth,
>>
>> I fear we are missing your use-case to beginn with, to understand what
>> you are trying to achieve.
>> Only with some breadcrumbs of information we just can help you on certain
>> topics.
>> In general I don't think using Karaf 3.x with cxf and Pax Web is a wrong
>> decision. You just have to get rid of the "old" war thinking.
>>
>> First of all make sure you configure the Webcontainer right. I think this
>> is the first Time you talk of that you only want to have SSL, this is a
>> real easy task and if you look at the samples in combination with the
>> integration tests of Pax Web, you'll see how easy it actually is. Btw. the
>> Apache Karaf Cookbook [1] also does contain enough explanation and examples
>> on how to work with Apache Karaf in general and it does cover Pax Web with
>> a big chapter explaining simple use-cases to get going with CXF, so at this
>> point there are resources available.
>>
>> For working with SSL, you might want to also look at [2] the integration
>> test fulfilling this task. Or if you want a blog post [3][4]. And actually
>> there is also documentation available on how to configure SSL at Pax Web
>> [5]. Besides that you just need to make sure you turn off the std. http
>> port.
>>
>> Regarding CXF as I already stated there is a book available also covering
>> this [1]
>> and as JB already noted if you want to bind a certain CXF servlet to a
>> special connector you'll need to configure this to CXF itself, the
>> mechanism for WARs doesn't work there. This is due to the fact that CXF
>> itself just uses the HttpService.
>>
>> Regarding PAXWEB-738, looks like you found a bug, cause afaik it used to
>> work. I'll work on this as soon as possible but not within the next two
>> weeks. What you can do to work around that issue is to actually use what is
>> done in the sample at [6]. It uses the HttpService to achieve the task.
>>
>> regards, Achim
>>
>>
>> [1] - http://bit.ly/1ps9rkS
>> [2] -
>> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/WarBasicAuthSecuredIntegrationTest.java
>> [3] -
>> http://blog.nanthrax.net/2013/02/multiple-http-connectors-in-apache-karaf/
>> [4] -
>> http://blog.nanthrax.net/2012/12/how-to-enable-https-certificate-client-auth-with-karaf/
>> [5] - https://ops4j1.jira.com/wiki/display/paxweb/SSL+Configuration
>> [6] -
>> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/WhiteboardAliasIntegrationTest.java
>>
>> 2014-09-23 8:23 GMT+02:00 Srikanth Hugar <sr...@gmail.com>:
>>
>>> Hello All,
>>>
>>> I am not sure whether i have made wrong choice by karaf 3.0.0, pax
>>> web 3.0.5, cxf 2.7.7.
>>> I have been facing multiple problems from beginning and some problems
>>> which are very important/critical for my product, i don't have the answers.
>>>
>>> Did anybody tried with above libraries? Were you successful?
>>>
>>> 1. https://ops4j1.jira.com/browse/PAXWEB-738
>>> 2.
>>> http://mail-archives.apache.org/mod_mbox/karaf-user/201409.mbox/%3CCAOUabB0dRPd==d+6sxiGzFGfe4A4HZ8reACHeeQd6_h8y0+iMA@mail.gmail.com%3E
>>> 3. No i have another problem, i wanted to run always with https, bit by
>>> configurin jetty.xml, service is also listening at 8080.
>>>
>>> ....... list goes on.
>>>
>>>
>>> --
>>> Srikanth
>>> w <http://www.srikanthugar.in>ww.gharki.com
>>>
>>>
>>
>>
>> --
>>
>> Apache Member
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
>> & Project Lead
>> blog <http://notizblog.nierbeck.de/>
>>
>> Software Architect / Project Manager / Scrum Master
>>
>>
>
>
> --
> Charlie Mordant
>
> Full OSGI/EE stack made with Karaf:
> https://github.com/OsgiliathEnterprise/net.osgiliath.parent
>
--
Srikanth
www.srikanthugar.in
Re: wrong choice by karaf 3.0.0, pax web 3.0.5, cxf 2.7.7...????
Posted by Charlie Mordant <cm...@gmail.com>.
Hi Srikanth,
You've not made the wrong choice but the best one :)!
As Achim said, you just have to forget all about the 'all in a war' J2EE
way of thinking.
Put all your services in different Web-ContextPath Manifest entry filled
plain old Jars.
Learn to fragment all your monolitic applications into reusable bundles,
then you'll see the incredible power of the choice you've made.
Unfortunately, I can't answer for your problem due to lack of informations
and knowledge on Pax-Web, Achim is the man! :).
Regards, Charlie
2014-09-23 8:44 GMT+02:00 Achim Nierbeck <bc...@googlemail.com>:
> HI Srikanth,
>
> I fear we are missing your use-case to beginn with, to understand what you
> are trying to achieve.
> Only with some breadcrumbs of information we just can help you on certain
> topics.
> In general I don't think using Karaf 3.x with cxf and Pax Web is a wrong
> decision. You just have to get rid of the "old" war thinking.
>
> First of all make sure you configure the Webcontainer right. I think this
> is the first Time you talk of that you only want to have SSL, this is a
> real easy task and if you look at the samples in combination with the
> integration tests of Pax Web, you'll see how easy it actually is. Btw. the
> Apache Karaf Cookbook [1] also does contain enough explanation and examples
> on how to work with Apache Karaf in general and it does cover Pax Web with
> a big chapter explaining simple use-cases to get going with CXF, so at this
> point there are resources available.
>
> For working with SSL, you might want to also look at [2] the integration
> test fulfilling this task. Or if you want a blog post [3][4]. And actually
> there is also documentation available on how to configure SSL at Pax Web
> [5]. Besides that you just need to make sure you turn off the std. http
> port.
>
> Regarding CXF as I already stated there is a book available also covering
> this [1]
> and as JB already noted if you want to bind a certain CXF servlet to a
> special connector you'll need to configure this to CXF itself, the
> mechanism for WARs doesn't work there. This is due to the fact that CXF
> itself just uses the HttpService.
>
> Regarding PAXWEB-738, looks like you found a bug, cause afaik it used to
> work. I'll work on this as soon as possible but not within the next two
> weeks. What you can do to work around that issue is to actually use what is
> done in the sample at [6]. It uses the HttpService to achieve the task.
>
> regards, Achim
>
>
> [1] - http://bit.ly/1ps9rkS
> [2] -
> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/WarBasicAuthSecuredIntegrationTest.java
> [3] -
> http://blog.nanthrax.net/2013/02/multiple-http-connectors-in-apache-karaf/
> [4] -
> http://blog.nanthrax.net/2012/12/how-to-enable-https-certificate-client-auth-with-karaf/
> [5] - https://ops4j1.jira.com/wiki/display/paxweb/SSL+Configuration
> [6] -
> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/WhiteboardAliasIntegrationTest.java
>
> 2014-09-23 8:23 GMT+02:00 Srikanth Hugar <sr...@gmail.com>:
>
>> Hello All,
>>
>> I am not sure whether i have made wrong choice by karaf 3.0.0, pax
>> web 3.0.5, cxf 2.7.7.
>> I have been facing multiple problems from beginning and some problems
>> which are very important/critical for my product, i don't have the answers.
>>
>> Did anybody tried with above libraries? Were you successful?
>>
>> 1. https://ops4j1.jira.com/browse/PAXWEB-738
>> 2.
>> http://mail-archives.apache.org/mod_mbox/karaf-user/201409.mbox/%3CCAOUabB0dRPd==d+6sxiGzFGfe4A4HZ8reACHeeQd6_h8y0+iMA@mail.gmail.com%3E
>> 3. No i have another problem, i wanted to run always with https, bit by
>> configurin jetty.xml, service is also listening at 8080.
>>
>> ....... list goes on.
>>
>>
>> --
>> Srikanth
>> w <http://www.srikanthugar.in>ww.gharki.com
>>
>>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
>
> Software Architect / Project Manager / Scrum Master
>
>
--
Charlie Mordant
Full OSGI/EE stack made with Karaf:
https://github.com/OsgiliathEnterprise/net.osgiliath.parent
Re: wrong choice by karaf 3.0.0, pax web 3.0.5, cxf 2.7.7...????
Posted by Achim Nierbeck <bc...@googlemail.com>.
HI Srikanth,
I fear we are missing your use-case to beginn with, to understand what you
are trying to achieve.
Only with some breadcrumbs of information we just can help you on certain
topics.
In general I don't think using Karaf 3.x with cxf and Pax Web is a wrong
decision. You just have to get rid of the "old" war thinking.
First of all make sure you configure the Webcontainer right. I think this
is the first Time you talk of that you only want to have SSL, this is a
real easy task and if you look at the samples in combination with the
integration tests of Pax Web, you'll see how easy it actually is. Btw. the
Apache Karaf Cookbook [1] also does contain enough explanation and examples
on how to work with Apache Karaf in general and it does cover Pax Web with
a big chapter explaining simple use-cases to get going with CXF, so at this
point there are resources available.
For working with SSL, you might want to also look at [2] the integration
test fulfilling this task. Or if you want a blog post [3][4]. And actually
there is also documentation available on how to configure SSL at Pax Web
[5]. Besides that you just need to make sure you turn off the std. http
port.
Regarding CXF as I already stated there is a book available also covering
this [1]
and as JB already noted if you want to bind a certain CXF servlet to a
special connector you'll need to configure this to CXF itself, the
mechanism for WARs doesn't work there. This is due to the fact that CXF
itself just uses the HttpService.
Regarding PAXWEB-738, looks like you found a bug, cause afaik it used to
work. I'll work on this as soon as possible but not within the next two
weeks. What you can do to work around that issue is to actually use what is
done in the sample at [6]. It uses the HttpService to achieve the task.
regards, Achim
[1] - http://bit.ly/1ps9rkS
[2] -
https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/WarBasicAuthSecuredIntegrationTest.java
[3] -
http://blog.nanthrax.net/2013/02/multiple-http-connectors-in-apache-karaf/
[4] -
http://blog.nanthrax.net/2012/12/how-to-enable-https-certificate-client-auth-with-karaf/
[5] - https://ops4j1.jira.com/wiki/display/paxweb/SSL+Configuration
[6] -
https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/WhiteboardAliasIntegrationTest.java
2014-09-23 8:23 GMT+02:00 Srikanth Hugar <sr...@gmail.com>:
> Hello All,
>
> I am not sure whether i have made wrong choice by karaf 3.0.0, pax
> web 3.0.5, cxf 2.7.7.
> I have been facing multiple problems from beginning and some problems
> which are very important/critical for my product, i don't have the answers.
>
> Did anybody tried with above libraries? Were you successful?
>
> 1. https://ops4j1.jira.com/browse/PAXWEB-738
> 2.
> http://mail-archives.apache.org/mod_mbox/karaf-user/201409.mbox/%3CCAOUabB0dRPd==d+6sxiGzFGfe4A4HZ8reACHeeQd6_h8y0+iMA@mail.gmail.com%3E
> 3. No i have another problem, i wanted to run always with https, bit by
> configurin jetty.xml, service is also listening at 8080.
>
> ....... list goes on.
>
>
> --
> Srikanth
> w <http://www.srikanthugar.in>ww.gharki.com
>
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Software Architect / Project Manager / Scrum Master
Re: wrong choice by karaf 3.0.0, pax web 3.0.5, cxf 2.7.7...????
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Srikanth,
CXF 2.7.7 is more focused on Karaf 2.3.x.
Anyway, most of use cases should work on Karaf 3.x.
Let me take a look on your issues.
Regards
JB
On 09/23/2014 08:23 AM, Srikanth Hugar wrote:
> Hello All,
>
> I am not sure whether i have made wrong choice by karaf 3.0.0, pax
> web 3.0.5, cxf 2.7.7.
> I have been facing multiple problems from beginning and some problems
> which are very important/critical for my product, i don't have the answers.
>
> Did anybody tried with above libraries? Were you successful?
>
> 1. https://ops4j1.jira.com/browse/PAXWEB-738
> 2.
> http://mail-archives.apache.org/mod_mbox/karaf-user/201409.mbox/%3CCAOUabB0dRPd==d+6sxiGzFGfe4A4HZ8reACHeeQd6_h8y0+iMA@mail.gmail.com%3E
> 3. No i have another problem, i wanted to run always with https, bit by
> configurin jetty.xml, service is also listening at 8080.
>
> ....... list goes on.
>
>
> --
> Srikanth
> w <http://www.srikanthugar.in>ww.gharki.com <http://ww.gharki.com>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com