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

Generate client proxy instead of using provided bean implementation #19

Closed
bfitzpat opened this issue Dec 4, 2017 · 2 comments
Closed
Assignees
Labels
Milestone

Comments

@bfitzpat
Copy link
Contributor

bfitzpat commented Dec 4, 2017

This came up during the tooling demo we had on 29-NOV-2017 with Keith.

Currently the utility can use an optional bean input when generating the REST DSL output. It came up during the meeting that we should just require the WSDL and use a generated client proxy (CXF?) to wrap the existing service in REST terms.

From Keith:

  • Only prerequisite should be a WSDL - no other artifacts (beans, etc.) should be required. We should only ask for the location of the WSDL and the SOAP address (defaulted from WSDL) the user wants to use.
  • The utility should automatically generate the client proxy interface and we don't need the bean at all.

Any chance we can get this in for Fuse 7?

@tdiesler
Copy link
Collaborator

tdiesler added a commit that referenced this issue Jan 12, 2018
@tdiesler
Copy link
Collaborator

tdiesler commented Jan 12, 2018

Blocked by [#37] JAXRS message cannot be routed to JAXWS proxy

@tdiesler tdiesler self-assigned this Mar 22, 2018
@tdiesler tdiesler added this to the 0.7 milestone Mar 22, 2018
@tdiesler tdiesler added task and removed blocked labels Mar 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants