| Hi Dirk, 
 we have an alternative implementation of the JaxRs  Whiteboard that uses Jersey. 
 We currently working on making this implementation fully spec compliant. In addition to that we working on using this implementation with the upcoming Jakarta renaming changes. 
 This implementation will then move to the OSGi technology project at the Eclipse Foundation. Currently you find the latest version at maven central og.geckoprojects.rest:org.gecko.rest.jersey:4.0.11 
 The project is currently located at Gitlab https://gitlab.com/geck.io/geckoREST. This version will not further developed. Instead we work on a spec compliant version that will move to Eclipse/OSGi Technology. The Gitlab Version is not fully spec compliant! The plan is to have everything done within this year. 
 If you have further question, just contact us. 
 Regards, 
 Mark Hoffmann  M.A. Dipl.-Betriebswirt (FH)  CEO/CTO  
 
 
 Data In Motion Consulting GmbH  Kahlaische Strasse 4  07745 Jena  Germany  
 Geschäftsführer/CEO  Mark Hoffmann  Jürgen Albert  
 Jena HRB 513025  Steuernummer 162/107/05779  USt-Id DE310002614
 
 -------- Ursprüngliche Nachricht -------- Von: "Fauth Dirk (ETAS/ENA) via osgi-users" <osgi-users@xxxxxxxxxxx>  Datum: 08.06.22  10:40  (GMT+01:00)  An: Tim Ward <timothyjward.oss@xxxxxxxxx>, "This is a community mail list for OSGi technology. Any OSGi technical discussion or questions are acceptable here." <osgi-users@xxxxxxxxxxx>  Cc: "Fauth Dirk (ETAS/ENA)" <dirk.fauth@xxxxxxxxxxxx>  Betreff: Re: [osgi-users] JAX-RS Whiteboard update question  
Hi Tim,   Yes you are right. I was talking about the Apache Aries JAX-RS Whiteboard reference implementation. Sorry for missing this detail in the
 question. Is there an alternative implementation available anywhere? I only know this one.   Anyhow, thanks for the explanation. That makes it clear. I was simply confused by the naming then. I just noticed that after the update
 (Aries JAX-RS Whiteboard AND required Java version) the size of the executable JAR increased from 12 MB to 17 MB. And I was wondering if this is mainly caused by the Java update (8 -> 11) or if there are jars included that shouldn’t be there.   Mit freundlichen Grüßen / Best regards
 Dirk Fauth
 ETAS Advance Engineering
 
 T +49 711 3423-2174
 Dirk.Fauth@xxxxxxxx
 
 ETAS GmbH, ETAS/ENA
 Borsigstraße 24, 70469 Stuttgart, Germany
 www.etas.com
 
 ETAS – Empowering Tomorrow’s Automotive Software
 
 Managing Directors: Christoph Hartung, Günter Gromeier, Götz Nigge
 Chairman of the Supervisory Board: Dr. Walter Schirm
 Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB: 19033
 
 
Von: Tim Ward <timothyjward.oss@xxxxxxxxx> Gesendet: Mittwoch, 8. Juni 2022 10:27
 An: This is a community mail list for OSGi technology. Any OSGi technical discussion or questions are acceptable here. <osgi-users@xxxxxxxxxxx>
 Cc: Fauth Dirk (ETAS/ENA) <dirk.fauth@xxxxxxxxxxxx>
 Betreff: Re: [osgi-users] JAX-RS Whiteboard update question
   Hi Dirk, 
At a guess you have updated to the latest release of Apache Aries JAX-RS Whiteboard? The implementation used to repackage CXF as an implementation detail, making it easer to deploy. Over time, however, it became a significant maintenance
 problem trying to keep pace with CXF’s releases (there are quite a few CVEs raised against CXF). Aries JAX-RS users indicated that they would prefer to be able to update CXF to pick up these security fixes without having to rebuild Aries JAX-RS, so Aries JAX-RS
 stopped bundling CXF and started using it as a “normal” dependency. 
As you can see it has nothing to do with the specification, and is just an implementation choice. I hope this helps to answer your question. 
The CXF client is needed - the OSGi JAX-RS whiteboard requires the implementation to register a ClientBuilder so that users can access a JAX-RS client. The CXF JAX-RS client implementation lives in this bundle.
The CXF JAX-RS frontend is needed - this is the bundle that provides CXF’s server side JAX-RS support. It is a JAX-RS “frontend” to CXF’s internal runtime, not a UI. 
 
 
  
I updated my JAX-RS Whiteboard example from enRoute OSGi R7 (created via archetypes) to OSGi R8 and Java 11. 
I have some questions related to the update: 
1. Are there any plans to provide enRoute archetypes for R8? Or is the archetype approach dropped? It was quite hard to gather all the necessary dependencies manually.
 It worked out at the end and there are quite some examples to have a look, but for a new start the archetypes where quite helpful. 
2. I realized an increase of the size of the executable jar after updating to R8, the newest libraries and Java 11. Of course there is an increase because of the
 XML stuff. One of the reasons why I wanted to update to Java 11 to see the effects. But one thing I didn't get is that now several CXF bundles are required and included in the resulting jar. They weren't necessary before (which was a 1.0.1). 
I'm just curious why they are included now. There is no indication in the change log, and it feels strange that for example the CXF JAX-RS Client API and the CXF
 JAX-RS Frontend are now a required part of a runtime that provides a REST service. Is this by intention or maybe a mistake and they should be optional? 
Mit freundlichen Grüßen / Best regards
 Dirk Fauth
 ETAS Advance Engineering
 
 T +49 711 3423-2174
 Dirk.Fauth@xxxxxxxx
 
 ETAS GmbH, ETAS/ENA
 Borsigstraße 24, 70469 Stuttgart, Germany
 www.etas.com
 
 ETAS – Empowering Tomorrow’s Automotive Software
 
 Managing Directors: Christoph Hartung, Günter Gromeier, Götz Nigge
 Chairman of the Supervisory Board: Dr. Walter Schirm
 Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB: 19033
 
 _______________________________________________osgi-users mailing list
 osgi-users@xxxxxxxxxxx
 To change your delivery options, retrieve your password, or unsubscribe from this list, visit
 https://dev.eclipse.org/mailman/listinfo/osgi-users
   |