-
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
Add a CXF extension #5538
Add a CXF extension #5538
Conversation
Hi @dufoli thanks for the PR. I did a quick look and noticed that you have files that are not supposed to be here. Can you please delete this folder - https://github.com/quarkusio/quarkus/tree/261673fd90672f1e4647d8caae1a811ee83fda7f/docs/src/main/asciidoc/generated and also squash the commits? Thanks |
Hi, Can you please rebase onto master to pick up a fix for CI? Thanks |
@geoand I have rebase but I have still an issue of namespace on test. I have try to fix it with
|
@dufoli that seems related to your PR. The rebase was mostly about some failing security tests |
@dufoli note to myself try to create one class by producer method with same name space than webservice |
5209eea
to
8e3eab4
Compare
it seems that we need few files in test project to make it working: |
locally I have mode impl and SEi (interface) in same folder it fix an issue. |
cc601df
to
9f43353
Compare
Many thanks lolo :) |
I have error but that I do not understand:
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message: |
it seems to be a pom issue to remove dependancy but it do not work when I add exclude dependency tag on pom file. |
I don't see it in dependency:tree. I think I fix it, there: You can get it or activate pull request on your repo and i will push it to your repo ;o) |
@Dufgui still failing ;-( |
d19765c
to
eeb638f
Compare
I have try to add to extensions/cxf/deployment/pom.xml
but I still get: |
ok I get the issue. |
I haven't followed the jakarta stuff much, I just know we aren't going back :). @gsmet any suggestions for the above? |
73daf99
to
3447679
Compare
hello, code need a review now that all tests pass. I have just squash and rebase. |
@famod I have added client support quickly. Thanks for the tips, I discover this helper too. When I see your comment It help me to choose the way to do it. Just need to debug it because unit test do not worked. |
@famod if you can test client. It is ready to work. I have not test native for client. But it must be ok. |
The error in the build is from kubernetes. So it's not related to CXF. KubernetesWithConfigMapCustomModeTest � Runtime java.lang.RuntimeException: io... |
We need a test on integration side. |
* | ||
*/ | ||
private void generateCxfClientProducer(BuildProducer<GeneratedBeanBuildItem> generatedBean, | ||
String cxfClientProducerClassName, String endpointAddress, String sei, String wsdlUrl) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does that mean the endpointAddress
has to be known at "build time"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@famod crap, ou are absolutly right, I need to change endpointAddress and wsdlUrl to runtime config and pass it to producer thanks to generatedBeanListener... like done on agroal.
That's what I'm trying to figure out as well |
I think that initially we'll probably have the docs here, right @gsmet @aloubyansky ? |
This is something we should discuss. We could pick up the guides in |
@aloubyansky Kogito and Camel documentation are still inside the Quarkus main repository documentation folder. Maybe we can host the documentation of CXF here also. This will be easier to maintain the website. @dufoli maybe it's a silly proposal but CXF maintain it's Spring integration maybe they will be interesting by hosting the Quarkus extension ? |
For now maybe. But, you know, having docs in one repo and the code in another one is not a good recipe. |
I agree, but the site is the way people discover what technologies Quarkus support, and as SOAP support is one of the most wanted extension it must be listed in the website. |
@loicmathieu So we agree it should be listed but the way it's integrated isn't a proper one. The root isssue is that the web site is taking guides from the Quarkus repo, while the extension list and other info from the platform repo. It should be pulling all the data from the platform in some uniform way instead. |
any news about quarkus-cxf-client? |
any updates about quarkus-cxf-client? |
client is supported : #4005 (comment) But this merge request will not be merged. Quarkus team change the rule during development (around 3 months, more 100 hours) and don't want it in core repository. They ask us, to publish and maintain it in a separate repo. My brother and me do it to contribute on Quarkus, not to use it, so we don't want to maintain it. So we don't do it, even if code (client and server) works. So if you want it you can take the code and put it in a repository and maintain it. So, sorry, we will not do it. We propose this code to community without any warranty. So I let you choose the license, but my advice is it to take the same as Quarkus : Apache 2. Have a nice day |
I totally agree for license. I do not care about it. So feel free to take it and change license to apache 2 or other |
@geoand |
@xumk subsequent development will happen on the https://github.com/shumonsharif/quarkus-cxf repository. I'll close this issue to avoid conflicts since the same content is already there. Thank you! |
@xumk you might not be aware but we are setting up an org to host community contributed extensions https://github.com/quarkiverse |
@aloubyansky I think will be better add guide like a camel guide @gastaldi @loicmathieu what are you think about this? |
@xumk that's ok. We want to support external repos too. If that's OK for you, we'll want to setup a few github actions in your repo to test compatibility with new Quarkus versions automatically to keep the catalog of extensions up-to-date. This is something we are figuring out atm. I'll ping you when I have news for you. |
rebase and fix cxf branch for quarkusio#4005