-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
WFLY-2422 Remoting profiles #6835
Conversation
Linux with security manager Build 263 outcome was FAILURE using a merge of f3d5922 Build problems:Failed tests detected Failed tests
|
Linux Build 5264 is now running using a merge of f3d5922 |
Windows Build 380 outcome was FAILURE using a merge of f3d5922 Build problems:Failed tests detected Failed tests
|
Linux Build 5264 outcome was FAILURE using a merge of f3d5922 Build problems:Failed tests detected Failed tests
|
Linux Build 5284 is now running using a merge of a58951b |
Windows Build 391 outcome was FAILURE using a merge of a58951b Build problems:Failed tests detected Failed tests
|
Linux Build 5284 outcome was FAILURE using a merge of a58951b Build problems:Failed tests detected Failed tests
|
Linux Build 5289 is now running using a merge of 0eb48b5 |
Linux Build 5289 outcome was SUCCESS using a merge of 0eb48b5 |
There shouldn't be a need for a new xsd version for this. I don't see the current 3.0 version used in any 8.x release, so the changes here are just further work on the non-yet-final 3.0. |
serviceBuilder.addDependency(TCCLEJBClientContextSelectorService.TCCL_BASED_EJB_CLIENT_CONTEXT_SELECTOR_SERVICE_NAME); | ||
// install the service | ||
serviceBuilder.install(); | ||
logger.debug("Deployment unit " + deploymentUnit + " will use " + ejbClientContextServiceName |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should use debugf rather that doing string concatenation, although this is not really performance sensitve code so I guess it does not matter that much
This looks ok from an EE point of view, but as Brian said all the references to 3.1 schema (and related model version bumps) need to be removed, and the changes put in the 3.0 schema. |
Linux Build 5652 is now running using a merge of 03601c4 |
Windows Build 763 outcome was FAILURE using a merge of 03601c4 Build problems:Failed tests detected Failed tests
|
Linux Build 5652 outcome was FAILURE using a merge of 03601c4 Build problems:Failed tests detected Failed tests
|
Linux Build 5653 is now running using a merge of 8dac2a8 |
Linux Build 5653 outcome was SUCCESS using a merge of 98b5eb0 |
Linux Build 5654 is now running using a merge of 98b5eb0 |
Linux Build 5654 outcome was FAILURE using a merge of 98b5eb0 Build problems:Failed tests detected Failed tests
|
WFLY-2422 Remoting profiles
Adds remoting profiles to ejb3 subsystem. Profiles consist of remote ejb receivers and local ejb receiver. Profile is represented by RemotingProfileService which depends on all connection services that ejb receivers need to connect to. If client wants to use remoting profile it can configure it in jboss-ejb-client.xml.
To provide backward compatibility client can still define remoting ejb receivers directly in jboss-ejb-client.xml. In this case during application deployment internal profile service, which consist of those receivers, is created. Remoting-profiles are responsive to cli operations: each time profile resource (or any of it's children resources) changes profile service is being restarted with new configuration. In case of invalid configuration update (f.e. non-existent connection dependency) operation is being rolled back and profile is restored to it's last correct configuration.