Thanks Maxim for your answer.
Yes I do. I have tried two scenarios, pass dates without time at all (e.g. 2015-02-04), and pass dates with time ‘zeroed’ (e.g. 2015-02-04T00:00:00+00:00). These two scenarios do not return ZONE_OFFSET error, so I think it makes the workaround for AXIS2-5494 report. But, I get another error informing that the field ‘inserted’ in MeetingMember object can not be readable. Any methods that return a list of Appointments or an Appointment object return this error. Searching in the CalendarWebService code I have seen that the Appointment object has a field called meetingMembers, it is a list of MeetingMember, and the class MeetingMember has a field ‘inserted’. This field is linked to the ‘starttime’ column of the meeting_members table in the database. But, I could not realize why the field is not readable. Any suggestion on that ? Regards, Jose Fernando De: Maxim Solodovnik [mailto:solomax...@gmail.com] Enviada em: quinta-feira, 5 de fevereiro de 2015 12:10 Para: Openmeetings user-list Assunto: Re: Axis fault with zone_offset reason when calling CalendarWebService methods with date argument have you tried to pass dates without time zome? On Thu, Feb 5, 2015 at 7:55 PM, José Fernando <josefs...@gmail.com> wrote: Hi, I have a OpenMeetings 3.0.3 server installed and I am developing an application to communicate with it via REST. I'm getting an error with the axis ZONE_OFFSET reason when I call the getAppointmentByRange method. Searching the internet I found the problem AXIS2-5494 that reports a bug in the conversion of dates with timezone, as described below: -------------------------------------------------------------------------- Description The date format containing seconds and timezone offset as follows generates an exception: yyyy-MM-dd'T'hh:mm:ssZse e.g.: 2013-03-04T15:07:14+11:00 The web service call fails with the exception: Caused by: java.lang.IllegalArgumentException: ZONE_OFFSET at java.util.GregorianCalendar.computeTime(GregorianCalendar.java:2316) at java.util.Calendar.updateTime(Calendar.java:2469) at java.util.Calendar.getTimeInMillis(Calendar.java:1088) at org.apache.axis2.databinding.utils.ConverterUtil.convertToDate(ConverterUtil.java:623) ConvertUtil.java line 596: int hours = Integer.parseInt(restpart.substring(1,3)); int minits = Integer.parseInt(restpart.substring(4,6)); timeZoneOffSet = ((hours * 60) + minits) * 60000; -------------------------------------------------------------------------------------- This is the same problem I'm having. Has anyone had this problem? Is there any fix for it ? Thanks, José Fernando. -- WBR Maxim aka solomax
