I hope we will be able to release next week

I'll check these methods

WBR, Maxim
(from mobile, sorry for the typos)
On Feb 6, 2015 12:42 AM, "José Fernando" <[email protected]> wrote:

> Thanks so much Maxim,
>
>
>
> I'll take the time to test it because I have to download and install it.
> Is this build you created stable ? Can it  be used in production?
>
>
>
> I'm having another problem with getNextAppointment methods,
> getNextAppointmentForUserId ang searchAppointmentByName. They always return
> null, although the appointments are created. I run a sql query directly in
> the database and return the meetings, but OpenMeetings only returns null.
> Could you check for any problem in OpenMeetings code?
>
>
>
> Thanks in advance,
>
>
>
> José Fernando.
>
>
>
> *De:* Maxim Solodovnik [mailto:[email protected]]
> *Enviada em:* quinta-feira, 5 de fevereiro de 2015 16:05
> *Para:* Openmeetings user-list
> *Assunto:* Re: Axis fault with zone_offset reason when calling
> CalendarWebService methods with date argument
>
>
>
> https://issues.apache.org/jira/browse/OPENMEETINGS-1157
>
>
>
> fixed :)
>
>
>
> you can test using build 114+ from here
> https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.0.x/
>
>
>
> On Thu, Feb 5, 2015 at 10:55 PM, José Fernando da Silva <
> [email protected]> wrote:
>
> I am using Ruby to send request to openmeetings server. But, you can
> reproduce the same error using a browser, I used chrome to do it:
>
>
>
> 1) First get an authenticated sid;
>
> 2) Send the request below to the openmeetings ( The openmeetings in a VM
> with ip 10.3.3.25):
>
>
>
>
> http://10.3.3.25:5080/openmeetings/services/CalendarService/getAppointmentByRange?SID=62b959dabd61ad0565139b941c725f61&starttime=2015-02-05T10:25:13-02:00&endtime=2015-02-05T18:25:13-02:00
>
>
>
>
>     The server returns this answer:
>
>
>
>        <soapenv:Reason xmlns:soapenv="
> http://www.w3.org/2003/05/soap-envelope";>
>
>               <soapenv:Text xml:lang="en-US">ZONE_OFFSET</soapenv:Text>
>
>        </soapenv:Reason>
>
>
>
> 3) Change the time and zone portion of the url in item 2 and resubmit:
>
>
>
>
> http://10.3.3.25:5080/openmeetings/services/CalendarService/getAppointmentByRange?SID=62b959dabd61ad0565139b941c725f61&starttime=2015-02-05T10:25:13-02:00&endtime=2015-02-05T00:00:00-00:00
>
>
>
>     The server returns this answer:
>
>
>
>      <soapenv:Reason xmlns:soapenv="
> http://www.w3.org/2003/05/soap-envelope";>
>
>          <soapenv:Text xml:lang="en-US">
>
>               org.apache.axis2.AxisFault: Property 'inserted' in bean
> class 'org.apache.openmeetings.db.entity.calendar.MeetingMember'is not
> readable.
>
>          </soapenv:Text>
>
>      </soapenv:Reason>
>
>
>
> The method saveAppointment works perfectly. It think it is because it uses
> Calendar as type for appointmentstart and appointmentend parameters instead
> of Date.
>
>
>
> Regards,
>
>
>
> Jose Fernando.
>
>
>
> 2015-02-05 13:03 GMT-02:00 Maxim Solodovnik <[email protected]>:
>
>
>
> could you please send me the example of the request so I can check?
>
>
>
> On Thu, Feb 5, 2015 at 9:00 PM, José Fernando <[email protected]> wrote:
>
> 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:[email protected]]
> *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 <[email protected]> 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
>
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>
>
>
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>

Reply via email to