Karaf
  1. Karaf
  2. KARAF-1115

Add a jre.properties.cxf with all changes required to run cxf

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.4
    • Fix Version/s: 2.2.5, 3.0.0
    • Component/s: karaf-core
    • Labels:
      None

      Description

      Currently users need to figure out themselves how to change the jre.conf to be able to run cxf.
      Dan has blogged about the changes necessary to run cxf correctly.
      http://www.dankulp.com/blog/2011/11/apache-cxf-in-osgi/

      I propose we add a jre.conf.cxf to the etc dir so people can simply rename this to jre.conf to be able to run cxf.

      Of course a more general solution would be better but currently most people just struggle with cxf and this is a simple solution till we have something better.

        Issue Links

          Activity

          Hide
          Andreas Pieber added a comment -

          OH YES! BIG +1

          Show
          Andreas Pieber added a comment - OH YES! BIG +1
          Hide
          Achim Nierbeck added a comment -

          +1

          Show
          Achim Nierbeck added a comment - +1
          Hide
          David Jencks added a comment -

          -100 This is a really inappropriate solution to the problem of running cxf, at least on trunk where kar files work pretty well ( I don't know about 2.x).

          Here are a couple IMO more appropriate solutions that avoid including cxf-specific goo to confuse all non-cxf users. (I'm not trying to be mean to cxf, I don't think we should include any consuming project specific configuration)

          1. Pack up all of cxf in a kar file including (in resources/etc/jre.properties or whatever files are appropriate) so that when the kar is installed, the etc files are as appropriate for cxf.

          2. Just put the configuration files (jre.properties) in such a kar and let the user try to figure out how to install the rest of cxf by themselves.

          Working with Geronimo I've verified that these ideas work if you construct a custom assembly and install the app-specific kar after the karaf framework kar. I haven't tried just installing a kar in an already built server, but I think it would work too.

          Also a link to Dan's blog about this would be helpful.

          Show
          David Jencks added a comment - -100 This is a really inappropriate solution to the problem of running cxf, at least on trunk where kar files work pretty well ( I don't know about 2.x). Here are a couple IMO more appropriate solutions that avoid including cxf-specific goo to confuse all non-cxf users. (I'm not trying to be mean to cxf, I don't think we should include any consuming project specific configuration) 1. Pack up all of cxf in a kar file including (in resources/etc/jre.properties or whatever files are appropriate) so that when the kar is installed, the etc files are as appropriate for cxf. 2. Just put the configuration files (jre.properties) in such a kar and let the user try to figure out how to install the rest of cxf by themselves. Working with Geronimo I've verified that these ideas work if you construct a custom assembly and install the app-specific kar after the karaf framework kar. I haven't tried just installing a kar in an already built server, but I think it would work too. Also a link to Dan's blog about this would be helpful.
          Hide
          Jean-Baptiste Onofré added a comment -

          Fully agree with David for the trunk.

          However, I think that the Christian's solution is acceptable for 2.2.x branch.

          Show
          Jean-Baptiste Onofré added a comment - Fully agree with David for the trunk. However, I think that the Christian's solution is acceptable for 2.2.x branch.
          Hide
          Christian Schneider added a comment -

          @David I know this solution is not optimal. But it is a real problem our users need to get solved. This is an easy solution that will help people. I do not understand why you are so negative about it. Of course this should not prevent us from providing a better solution. I propose to keep this kind of jre.properties template till we have a better solution in place. Then we can remove it again. It does not help our users if we endlessly debate about the best solution and leave our users alone while we do that. If you have a working solution for 3.0 I am willing to remove the file right now.

          Show
          Christian Schneider added a comment - @David I know this solution is not optimal. But it is a real problem our users need to get solved. This is an easy solution that will help people. I do not understand why you are so negative about it. Of course this should not prevent us from providing a better solution. I propose to keep this kind of jre.properties template till we have a better solution in place. Then we can remove it again. It does not help our users if we endlessly debate about the best solution and leave our users alone while we do that. If you have a working solution for 3.0 I am willing to remove the file right now.
          Hide
          Jean-Baptiste Onofré added a comment -

          As I said, for 2.2.5, to avoid to change in CXF, I'm OK to add a jre.properties CXF sample.

          But, we have to keep in mind, that this file should be provided by CXF, and on trunk, handle with a kar packaging.

          Show
          Jean-Baptiste Onofré added a comment - As I said, for 2.2.5, to avoid to change in CXF, I'm OK to add a jre.properties CXF sample. But, we have to keep in mind, that this file should be provided by CXF, and on trunk, handle with a kar packaging.
          Hide
          Christian Schneider added a comment -

          Do we have an issue for the kar packaging in cxf or karaf?

          Show
          Christian Schneider added a comment - Do we have an issue for the kar packaging in cxf or karaf?
          Hide
          Jean-Baptiste Onofré added a comment -

          No, kar works fine (thanks to David), but it's not the same usage in trunk and karaf-2.2.x.

          Show
          Jean-Baptiste Onofré added a comment - No, kar works fine (thanks to David), but it's not the same usage in trunk and karaf-2.2.x.
          Hide
          Christian Schneider added a comment -

          Added a link to the issue that handles the better solution. So I think we can close this.

          Show
          Christian Schneider added a comment - Added a link to the issue that handles the better solution. So I think we can close this.

            People

            • Assignee:
              Christian Schneider
              Reporter:
              Christian Schneider
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development