Skip to content
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

Better Documentation & support of Client-Mode for JAX-WS-Services that are not hostet, but used (incl. example project) #8

Closed
jonashackt opened this issue Nov 10, 2016 · 5 comments
Milestone

Comments

@jonashackt
Copy link
Member

You can use this starter also not only for serving SOAP services but also for consuming them with Apache CXF. But this is not documented yet and there´s no example-project or test for this feature.

@ePaul
Copy link

ePaul commented Dec 22, 2016

I just wanted to open an issue asking how to do this. I guess I'll have to browse the code, then.

@jonashackt
Copy link
Member Author

@ePaul you´re right - we´ll deliver some kind of example project soon including documentation. Stay tuned :)

@jonashackt jonashackt changed the title Document already supported Client-Mode for JAX-WS-Services that are not hostet, but used (incl. example project) Better Documentation & support of Client-Mode for JAX-WS-Services that are not hostet, but used (incl. example project) Jan 16, 2017
@jonashackt
Copy link
Member Author

We need an integration test for this - not only a system test. We should consider the use of https://github.com/testcontainers/testcontainers-java to run cxf-boot-simple as app inside a Docker container and then integration test onto it.

jonashackt added a commit that referenced this issue Jan 16, 2017
…t only sceanarios (it also helps #8). Renamed the SystemTest from Integration test which it is not.
@jonashackt
Copy link
Member Author

Documented in tests & README. So closing now.

@jonashackt
Copy link
Member Author

I'am developing an example client-only project right now, that will hopefully also address #41 and #47 - AND document much much better, how to do it. As a second benefit, this will provide us with a real integration test - since the sample client will use another sample project, which is live-deployed on Heroku.

@jonashackt jonashackt added this to the 2.1.7.RELEASE milestone Aug 30, 2019
jonashackt added a commit that referenced this issue Aug 30, 2019
…eroku deployment as a counterpart (should help/fix #47, #41 & #8)
@renovate renovate bot mentioned this issue Mar 19, 2022
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants