- 
	I fixed format of timestamp by changing yyyy-MM-dd'T'HH:mm:ssZtoyyyy-MM-dd'T'HH:mm:ssXXXand @yyyy-MM-dd'T'HH:mm:ssXX@.First one properly handles timestamps like 2016-02-24T16:52:13+01:00and2016-02-24T16:52:13Z@, while second one handles @2016-02-24T16:52:13+0100anf @2016-02-24T16:52:13Z@. This way Tigase Message Archiving component will properly handle format described at http://xmpp.org/extensions/xep-0082.html#sect-idp621488 and format which was handled until now (for backward compatibility).From now on Tigase Message Archiving component will return timestamps in following form 2016-02-24T16:52:13ZUsage of format string suggested in task description is not possible. yyyy-MM-dd'T'HH:mm:ss'Z'will result in formatting time properly however will lead to timezone information being lost (especially as in some cases this formatter is also used for parsing timestamps!)
- 
	官方阿迪达斯新店开张大促销了,三折呀,还有情侣款,我卖了两双,去验过是正品,很满意~!http://st.zzaa.org This is an automatic reply, confirming that your e-mail was received.Thank you 邮箱使用小提示 想让对方更及时看到你的邮件,可以试试发到"对方手机号@163.com"。 无需事先开通,还有短信提醒。了解网易手机邮箱详情
| Type | Bug | 
| Priority | Major | 
| Assignee | |
| RedmineID | 4188 | 
 
	
				 
		 
	
			
"yyyy-MM-dd'T'HH:mm:ssZ" will format date to string like "2016-02-24T16:52:13+0000"
but "yyyy-MM-dd'T'HH:mm:ss'Z'" will format date to string like "2016-02-24T16:52:13+00:00", as is protocoled in
http://xmpp.org/extensions/xep-0136.html#manage-list
http://xmpp.org/extensions/xep-0082.html#sect-idp621488
TZD Time Zone Definition (either "Z" for UTC or "(+|-)hh:mm" for a specific time zone)