Skip to content

Conversation

stuartwdouglas
Copy link
Contributor

No description provided.

@stuartwdouglas stuartwdouglas force-pushed the remote-naming-permissiong branch 2 times, most recently from f9408a2 to 51015b3 Compare February 28, 2017 03:45

try (MessageInputStream mis = message) {
if(!channel.getConnection().getLocalIdentity().implies(RemoteNamingPermission.getInstance())) {
throw Messages.log.noPermission(channel.getConnection().getLocalIdentity().getPrincipal().getName(), RemoteNamingPermission.getInstance());
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should use writeExceptionResponse() to write the naming exception. Throwing before reading the inv ID means the response won't be correlated.

@stuartwdouglas stuartwdouglas force-pushed the remote-naming-permissiong branch from 51015b3 to 176c0bc Compare February 28, 2017 21:16
spyrkob pushed a commit to spyrkob/wildfly-naming-client that referenced this pull request Nov 27, 2018
Add licence file and pom information
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

Successfully merging this pull request may close these issues.

2 participants