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

How to start single services/ports based on configuration? #68

Open
RobertZenz opened this issue Dec 31, 2019 · 0 comments
Open

How to start single services/ports based on configuration? #68

RobertZenz opened this issue Dec 31, 2019 · 0 comments

Comments

@RobertZenz
Copy link

RobertZenz commented Dec 31, 2019

I have the following situation at hand: The goal is to develop a contract-first application with a given WSDL file (changes to the definition/schema/requirements are out of the question, close to impossible I might even say). The WSDL is defining one service with two ports and is structured like this:

<service name="SomeService">
    <port name="PortA" binding="ns:ABinding">
        <soap12:address location="http://nobodycares" />
    </port>
    <port name="PortB" binding="ns:BBinding">
        <soap12:address location="http://nobodycares" />
    </port>
</service>

Generating classes from this definition/schema is all set and working, the problem arises when wanting to start these ports. The requirements make it necessary to only start one port at a time or to start them on different network ports (to make sure that they are reachable only from different parts of the network).

Is that somehow possible with the automatic wiring of cxf-spring or is the easiest way to deactivate the automatic initialization and create the EndpointImpl instances manually?

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

1 participant