[
https://issues.apache.org/jira/browse/RAMPART-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Detelin Yordanov updated RAMPART-416:
-------------------------------------
Attachment: rampart_jetty.patch
Attaching a patch against Rampart trunk that introduces a JettyServer class
providing support for starting/stopping an embedded Jetty 7 instance. The patch
modifies RampartTest test to use that and re-enables transport binding tests
(scenario .
The patch increases Rampart dependency to servlet API from 2.3 to 2.5 since all
recent Jetty versions (6.x, 7.x) require at least servlet API 2.5 in order to
function. One can keep the original servlet API 2.3 dependency coming from
Axis2, but it would have to be explicitly excluded from Rampart integration
module and it does not make sense to do this, since Rampart only uses
HttpServletRequest.getAttribute() which would work with both servlet API
versions. Also, if Rampart core module preserves the dependency to servlet API
2.3, while the integration module is switched to 2.5, importing and running
Rampart tests from within Eclipse IDE fails as both servlet API versions will
be on the classpath.
> Enable Rampart transport binding integration tests
> --------------------------------------------------
>
> Key: RAMPART-416
> URL: https://issues.apache.org/jira/browse/RAMPART-416
> Project: Rampart
> Issue Type: Improvement
> Components: rampart-integration
> Affects Versions: 1.6.2, 1.7.0
> Reporter: Detelin Yordanov
> Attachments: rampart_jetty.patch
>
>
> Rampart transport binding integration tests are currently disabled since
> https support is not available using Axis2 SimpleHttpServer. These can be
> enabled if SimpleHttpServer is replaced with embedded Jetty server configured
> with SSL support. This would improve the Rampart integration test coverage
> and allow contributing additional integration tests which use transport
> binding policy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
