[ http://issues.apache.org/jira/browse/AXIS2C-274?page=comments#action_12433779 ] Malinda Kaushalye Kapuruge commented on AXIS2C-274: ---------------------------------------------------
TRUE. It's much better to use the axis2_date_time_* for this purpose. But when I develop timestamps there was no such support for the date time serialization in the axis2 util. Hence I had to write my own code to generate the time. But thanks for raising the issue. Doing this, we have to introduce a new create function to the axis2_data_time_* to create a time which has a different value to the current time. The existing function always generate axis2_date_time based on the current time. I'd prefer to have a function like AXIS2_EXTERN axis2_date_time_t * AXIS2_CALL axis2_date_time_create_with_offset(const axis2_env_t *env, int offset); and then the existing function axis2_date_time_create() can call this function with offset=0 > rampart_generate_time should use date time stuff from util > ---------------------------------------------------------- > > Key: AXIS2C-274 > URL: http://issues.apache.org/jira/browse/AXIS2C-274 > Project: Axis2-C > Issue Type: Improvement > Components: util > Affects Versions: Current (Nightly) > Reporter: James Clark > Assigned To: Malinda Kaushalye Kapuruge > Priority: Minor > > rampart_generate_time looks suspicious to me. It shouldn't be calling system > functions directly. This sort of thing belongs in util. Why isn't it using > axis2_date_time_*? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
