-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension for CXF #4005
Comments
I work in banking environment where SOAP+XML is the de facto standard and still will be standard for the years to come. |
Thanks for creating this proposal Emmanuel . It will definitely help people working in the insurance and financial services industries who are still on SOAP web services due to existing electronic data interchanges with their B2B customers . |
I start a work on it. Now I must test to see if it's do the job.... |
Even on a modern stack wil often deals with SOAP WS. |
please assign to me |
Add cxf server side extension Docs Unit tests fix quarkusio#4005
Add cxf server side extension Docs Unit tests fix quarkusio#4005
Add cxf server side extension Docs Unit tests fix quarkusio#4005
Add cxf server side extension Docs Unit tests fix quarkusio#4005
Pretty interested in this extension as well. Any chance to get some traction on it? |
Sorry I have too much works to continue until December.
Le ven. 1 nov. 2019 à 12:40, blaghed <notifications@github.com> a écrit :
… Pretty interested in this extension as well. Any chance to get some
traction on it?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#4005?email_source=notifications&email_token=AABZ5G7I2XSCAOFZ26YJH63QRQIULA5CNFSM4IWODFZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC2WM3A#issuecomment-548759148>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABZ5GZ3QORHBEZM7T7JDZDQRQIULANCNFSM4IWODFZA>
.
|
Add cxf server side extension Docs Unit tests fix quarkusio#4005
Add cxf server side extension Docs Unit tests fix quarkusio#4005
Add cxf server side extension Docs Unit tests fix quarkusio#4005
Agree with dufgui for licensing |
ok so new TODO:
|
@gastaldi is it the right todo to register extension outside of quarkus ? |
@Dufgui this is still a work in progress (meaning that we'll document these steps properly) and our tools are not aware of it at the moment. You'll also need to declare the released versions, as in https://github.com/gastaldi/quarkus-extension-catalog/blob/master/extensions/jsf.json |
@Dufgui @dufoli I have been looking forward to this extension for some time. My apologies, but I wasn't 100% sure on whether you are working on getting the extension registered outside of quarkus, given the TODO list @dufoli created. I'm happy to try to take on the remaining TODO list items, but wanted to check and confirm with you first. |
is this extension already available for usage? I have been exploring Quarkus as a serious option for migrating an old Java EE application and everything is great with Quarkus, but unfortunately I need to keep exposing SOAP webservices |
I don't think so. We are using CXF as a client via |
My team and I are also looking forward to this extension, although it does work in JVM mode. |
Actually I would think on using the JVM mode in the application that I would be migrating. @AmsterdamFilho have you been able to expose SOAP services by some means in Quarkus? |
No, I am just consuming. |
Thank you for clarifying @AmsterdamFilho and @famod. Let's see if some extension comes out soon. |
I took a stab at making this available as an extension just a few days ago. I am able to both expose and consume SOAP services in JVM mode, though having some (hopefully minor) issues with native mode that I'm trying to work through. Would greatly appreciate any help; please feel free to open issues, and/or submit PRs: https://github.com/shumonsharif/quarkus-cxf |
@shumonsharif Great news, I will definitely have a look at your extension! |
@shumonsharif I could test the extension and indeed I could publish a SOAP service, but I had a problem with dependency injection. Raised the issue shumonsharif/quarkus-cxf#1 for more detail. |
@shumonsharif thank you very much. But many people wait SOAP-clent in quarkus extension, because it more important for interpraise. Alas this repo: not listed on the oficail site (https://quarkus.io/). Unfortunately, i can find it only by reading issues |
@Dufgui When is this extension expected to be released? I am trying to convince Telefonica to start using Quarkus instead of Spring Boot, but they have so many legacy SOAP web services. Maybe work together with @shumonsharif to release this extension sooner? |
@AmsterdamFilho you can use this. It extension is being developed and relesed there |
Closing this issue since the extension already exists and is maintained in https://github.com/shumonsharif/quarkus-cxf/ |
Hello, I need help to fix native on |
good news, I have quarkus cxf extention which work native with java 8. Huge todo remaining but it test is running ! |
@gsmet can it be elligible for quarkiverse ? |
@dufoli definitely, we would love that! But I think @shumonsharif wanted to keep in his own repository? |
I'll get the repository ready for you to push your stuff and give you the necessary permissions. The package and groupId should be renamed to start with |
Repository created in https://github.com/quarkiverse/quarkiverse-cxf and invitation sent. Instructions are in https://github.com/quarkiverse/quarkiverse/wiki. Ping us if you have any questions. Welcome aboard! |
@dufoli done. You can also add other maintainers as you have the Maintainer role for the @quarkiverse/quarkiverse-cxf team |
no I have no access to settings of project. |
Describe the extension
Discuss CXF support via an extension (either partial support or full is TBD).
Interested, please +1 via the emoji/reaction feature of GitHub (top right)
Configuration suggestion
# Add your application.properties here, if applicable. TBD
Additional context
(Add any other context about the proposal here.)
We mainly use SOAP/XML based web services driven by our insurance industry standard formats ( MISMO) . We are currently exploring using quarkus to migrate all our existing camel code .
The text was updated successfully, but these errors were encountered: