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
ISPN-3950 Allow deployment of event filters and converters in server #2742
Conversation
|
||
@Override | ||
public void undeploy(DeploymentUnit context) { | ||
// TODO: Customise this generated block |
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.
Customise it by removing it :)
Needs rebase |
Rebased |
context.addStep(new AbstractDeploymentChainStep() { | ||
protected void execute(DeploymentProcessorTarget processorTarget) { | ||
processorTarget.addDeploymentProcessor(Constants.SUBSYSTEM_NAME, | ||
Phase.INSTALL, Constants.INSTALL_FILTER_FACTORY, new FilterFactoryExtensionProcessor(hotRodServerServiceName)); |
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.
If you have multiple endpoints enabled, this fails with
java.lang.IllegalStateException: JBAS018786: Multiple deployment unit processors registered with priority 6145 and class class org.infinispan.server.endpoint.deployments.FilterFactoryExtensionProcessor
So probably the deployer should be installed independently and added as a dependency.
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 is not straightforward to solve.
* Moved to core/ to make it easier for users to implement factory instances and avoid leaking server/hotrod components.
* Adding filters and converters done dynamically now, to make it easier to deal with deployments of these. * Servlet deployment disabled for HotRod tests in server because it forces deployment jars to be included within war. Instead, use JMX deployment. * Updated documentation to reflect how filter and converter instances are plugging into Infinispan Server.
Closing for the time being. |
New PR: #2782 |
https://issues.jboss.org/browse/ISPN-3950
A long awaited PR completing functionality in Hot Rod event (barring some small fixes) by allowing filter and converter instances to be deployed in Infinispan Servers. Adding filters and converters is a dynamic process now to make it easier to fit into the deployment model.
This PR also includes refactoring of filter and converter factory classes to
core
module, as agreed on a dev discussion.