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.

Sign up for GitHub

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

Jump to bottom

Use qualified name of interface when exporting a service #28

Closed
lukaszPulawski opened this issue Apr 14, 2015 · 0 comments
Closed

Use qualified name of interface when exporting a service #28

lukaszPulawski opened this issue Apr 14, 2015 · 0 comments

Comments

@lukaszPulawski
Copy link
Contributor

Right now, when service is exported, the endpoint path is build only with use of local name of the interface class (without package). It yields a risk of collision.
This issue is about changing a strategy of building service path so that it is more unique
piotrromanski pushed a commit that referenced this issue Apr 30, 2015
[#28] Use qualified name of interface in service address
ebe3a1d
piotrromanski pushed a commit that referenced this issue Apr 30, 2015
[#28] Use qualified name of interface in service address
7a55a36
lukaszPulawski added a commit that referenced this issue Apr 30, 2015
@lukaszPulawski
Merge pull request #37 from PayU-Tech/issue-28
1730b77 
[#28] Use qualified name of interface in service address
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lukaszPulawski @piotrromanski