Arquillian provides a component model for integration tests, which includes dependency injection and container life cycle management. Instead of managing a runtime in your test, Arquillian brings your test to the runtime.
When a DeploymentPackager is called there is knowledge of the target DeployableContainer
and a ProtocolDefinition which contains the default protocol configuration. This is not provided to the DeploymentPackager via the DeploymentDescription available from the TestDeployment argument to DeploymentPackager#generateDeployment()..
The DeployableContainer is also capable of overriding the protocol and configuration, so that value is what needs to be first looked at, and then fallback to the default ProtocolDefinition if none was specified at the container level. This needs
to be specified on the TestDeployment.
Expected Behaviour
The TestDeployment should have the target protocol information available.
Current Behaviour
This information, while available at the time the DeploymentPackager is called, is not provided via the TestDeployment argument.
Issue Overview
When a
DeploymentPackageris called there is knowledge of the targetDeployableContainerand aProtocolDefinitionwhich contains the default protocol configuration. This is not provided to theDeploymentPackagervia theDeploymentDescriptionavailable from theTestDeploymentargument toDeploymentPackager#generateDeployment()..The
DeployableContaineris also capable of overriding the protocol and configuration, so that value is what needs to be first looked at, and then fallback to the defaultProtocolDefinitionif none was specified at the container level. This needs to be specified on theTestDeployment.Expected Behaviour
The
TestDeploymentshould have the target protocol information available.Current Behaviour
This information, while available at the time the
DeploymentPackageris called, is not provided via theTestDeploymentargument.