axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Jayasekara (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RAMPART-334) Unable to set TTL and maxTimeStampSkew values through a rampart callback
Date Tue, 19 Jul 2011 17:02:58 GMT

     [ https://issues.apache.org/jira/browse/RAMPART-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Amila Jayasekara updated RAMPART-334:
-------------------------------------

    Attachment: service.zip

> Unable to set TTL and maxTimeStampSkew values through a rampart callback
> ------------------------------------------------------------------------
>
>                 Key: RAMPART-334
>                 URL: https://issues.apache.org/jira/browse/RAMPART-334
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.5
>         Environment: Ubuntu
>            Reporter: Amila Jayasekara
>         Attachments: service.zip
>
>
> Even though we set timestamp TTL and max timestamp skew values through configuration
or configuration callback, updated values are not read during actual message processing.
> To reproduce the issue follow steps given below,
> 1. Write a rampart configuration callback
> 2. Write a validation callback
> 3. Print TTL and maxTimestampSkew values in the validator
> Updated values should be printed. But as per now only default values are printing.
> Attaching a service code which can be used to reproduce this issue. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message