You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Ali Alhaidary <al...@the5stars.org> on 2020/12/26 16:49:23 UTC

Google Calendar

Still not able to sync with google calendar, any update?


Re: Google Calendar

Posted by GuruCoool Learnings <in...@gurucoool.com>.
I am also facing problems with google calendar sync.

On Sat, 26 Dec 2020 at 22:19, Ali Alhaidary <al...@the5stars.org>
wrote:

> Still not able to sync with google calendar, any update?
>
>

Re: Google Calendar

Posted by Ali Alhaidary <al...@the5stars.org>.
done ...

On 12/28/20 5:23 PM, Maxim Solodovnik wrote:
>
>
> On Mon, 28 Dec 2020 at 17:38, Ali Alhaidary 
> <ali.alhaidary@the5stars.org <ma...@the5stars.org>> wrote:
>
>     ERROR 12-28 10:32:42.382 o.a.w.DefaultExceptionMapper:170
>     [io-5443-exec-10] - Unexpected error occurred
>     org.springframework.dao.InvalidDataAccessApiUsageException:
>     Encountered unmanaged object
>     "org.apache.openmeetings.db.entity.user.User@12b47276" in life
>     cycle state  unmanaged while cascading persistence via field
>     "org.apache.openmeetings.db.entity.calendar.OmCalendar.owner"
>     during flush.  However, this field does not allow cascade persist.
>     You cannot flush unmanaged objects or graphs that have persistent
>     associations to unmanaged objects.
>      Suggested actions: a) Set the cascade attribute for this field to
>     CascadeType.PERSIST or CascadeType.ALL (JPA annotations) or
>     "persist" or "all" (JPA orm.xml),
>      b) enable cascade-persist globally,
>      c) manually persist the related field value prior to flushing.
>      d) if the reference belongs to another context, allow reference
>     to it by setting
>     StoreContext.setAllowReferenceToSiblingContext().; nested
>     exception is <openjpa-3.1.2-r66d2a72 nonfatal user error>
>     org.apache.openjpa.persistence.InvalidStateException: Encountered
>     unmanaged object
>     "org.apache.openmeetings.db.entity.user.User@12b47276" in life
>     cycle state  unmanaged while cascading persistence via field
>     "org.apache.openmeetings.db.entity.calendar.OmCalendar.owner"
>     during flush.  However, this field does not allow cascade persist.
>     You cannot flush unmanaged objects or graphs that have persistent
>     associations to unmanaged objects.
>      Suggested actions: a) Set the cascade attribute for this field to
>     CascadeType.PERSIST or CascadeType.ALL (JPA annotations) or
>     "persist" or "all" (JPA orm.xml),
>      b) enable cascade-persist globally,
>      c) manually persist the related field value prior to flushing.
>      d) if the reference belongs to another context, allow reference
>     to it by setting StoreContext.setAllowReferenceToSiblingContext().
>     FailedObject: org.apache.openmeetings.db.entity.user.User@12b47276
>         at
>     org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:371)
>         at
>     org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:128)
>         at
>     org.springframework.dao.support.DataAccessUtils.translateIfNecessary(DataAccessUtils.java:242)
>         at
>     org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:575)
>         at
>     org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:743)
>
>     *That is when trying to add a google calendar ...*
>
>
> Please file JIRA with this log
> and some steps :)
> I'll try to check :)
>
>
>     On 12/28/20 10:18 AM, Ali Alhaidary wrote:
>>
>>     Does this has anything with the calendar?
>>
>>      INFO 12-28 07:05:03.918 o.a.w.p.h.WebApplication:974 [main] -
>>     [OpenmeetingsApplication] Started Wicket version 9.2.0 in
>>     DEPLOYMENT mode
>>      INFO 12-28 07:05:05.563 o.a.c.e.ServerImpl:94 [main] - Setting
>>     the server's publish address to be /
>>      INFO 12-28 07:05:05.865
>>     o.a.c.w.s.f.ReflectionServiceFactoryBean:436 [main] - Creating
>>     Service
>>     {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.CalendarWebService
>>     from class org.apache.openmeetings.webservice.CalendarWebService
>>      INFO 12-28 07:05:07.959 o.a.c.e.ServerImpl:94 [main] - Setting
>>     the server's publish address to be /CalendarService
>>      INFO 12-28 07:05:07.992
>>     o.a.c.w.s.f.ReflectionServiceFactoryBean:436 [main] - Creating
>>     Service
>>     {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.ErrorWebService
>>     from class org.apache.openmeetings.webservice.ErrorWebService
>>      INFO 12-28 07:05:08.050 o.a.c.e.ServerImpl:94 [main] - Setting
>>     the server's publish address to be /ErrorService
>>      INFO 12-28 07:05:08.056
>>     o.a.c.w.s.f.ReflectionServiceFactoryBean:436 [main] - Creating
>>     Service
>>     {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.GroupWebService
>>     from class org.apache.openmeetings.webservice.GroupWebService
>>      INFO 12-28 07:05:08.281 o.a.c.e.ServerImpl:94 [main] - Setting
>>     the server's publish address to be /GroupService
>>      INFO 12-28 07:05:08.284
>>     o.a.c.w.s.f.ReflectionServiceFactoryBean:436 [main] - Creating
>>     Service
>>     {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.InfoWebService
>>     from class org.apache.openmeetings.webservice.InfoWebService
>>      INFO 12-28 07:05:08.335 o.a.c.e.ServerImpl:94 [main] - Setting
>>     the server's publish address to be /InfoService
>>      INFO 12-28 07:05:08.342
>>     o.a.c.w.s.f.ReflectionServiceFactoryBean:436 [main] - Creating
>>     Service
>>     {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.FileWebService
>>     from class org.apache.openmeetings.webservice.FileWebService
>>      INFO 12-28 07:05:08.563 o.a.c.e.ServerImpl:94 [main] - Setting
>>     the server's publish address to be /FileService
>>      INFO 12-28 07:05:08.566
>>     o.a.c.w.s.f.ReflectionServiceFactoryBean:436 [main] - Creating
>>     Service
>>     {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RecordingWebService
>>     from class org.apache.openmeetings.webservice.RecordingWebService
>>      INFO 12-28 07:05:08.658 o.a.c.e.ServerImpl:94 [main] - Setting
>>     the server's publish address to be /RecordService
>>      INFO 12-28 07:05:08.662
>>     o.a.c.w.s.f.ReflectionServiceFactoryBean:436 [main] - Creating
>>     Service
>>     {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RoomWebService
>>     from class org.apache.openmeetings.webservice.RoomWebService
>>      INFO 12-28 07:05:08.984 o.a.c.e.ServerImpl:94 [main] - Setting
>>     the server's publish address to be /RoomService
>>      INFO 12-28 07:05:08.988
>>     o.a.c.w.s.f.ReflectionServiceFactoryBean:436 [main] - Creating
>>     Service
>>     {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.UserWebService
>>     from class org.apache.openmeetings.webservice.UserWebService
>>      INFO 12-28 07:05:09.088 o.a.c.e.ServerImpl:94 [main] - Setting
>>     the server's publish address to be /UserService
>>      INFO 12-28 07:05:09.093
>>     o.a.c.w.s.f.ReflectionServiceFactoryBean:436 [main] - Creating
>>     Service
>>     {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.WbWebService
>>     from class org.apache.openmeetings.webservice.WbWebService
>>      INFO 12-28 07:05:09.163 o.a.c.e.ServerImpl:94 [main] - Setting
>>     the server's publish address to be /WbService
>>     DEBUG 12-28 07:05:12.506 o.a.o.u.c.CryptProvider:39
>>     [ean#0_Worker-10] - get:: configKeyCryptClassName:
>>     org.apache.openmeetings.util.crypt.SCryptImplementation
>>     DEBUG 12-28 07:06:30.060 o.a.o.w.a.ClientManager:372
>>     [nio-5443-exec-5] - Cluster:: Checking token null, full list: []
>>
>>     On 12/28/20 9:50 AM, Ali Alhaidary wrote:
>>>
>>>     It is the shortest report, the calendar is added, does not sync,
>>>     and can not find errors in log...
>>>
>>>     Ali
>>>
>>>     On 12/28/20 9:48 AM, Maxim Solodovnik wrote:
>>>>     without detailed report on what is wrong - no :)
>>>>
>>>>     On Mon, 28 Dec 2020 at 12:49, Ali Alhaidary
>>>>     <ali.alhaidary@the5stars.org
>>>>     <ma...@the5stars.org>> wrote:
>>>>
>>>>         Is it going to happen?
>>>>
>>>>         On 12/28/20 8:45 AM, Maxim Solodovnik wrote:
>>>>>
>>>>>
>>>>>         On Sat, 26 Dec 2020 at 23:49, Ali Alhaidary
>>>>>         <ali.alhaidary@the5stars.org
>>>>>         <ma...@the5stars.org>> wrote:
>>>>>
>>>>>             Still not able to sync with google calendar, any update?
>>>>>
>>>>>
>>>>>         I read "still not able" as it was already reported,
>>>>>         I haven't saw any report regarding something is not working
>>>>>
>>>>>         so no update :)
>>>>>
>>>>>
>>>>>         -- 
>>>>>         Best regards,
>>>>>         Maxim
>>>>
>>>>
>>>>
>>>>     -- 
>>>>     Best regards,
>>>>     Maxim
>
>
>
> -- 
> Best regards,
> Maxim

Re: Google Calendar

Posted by Maxim Solodovnik <so...@gmail.com>.
On Mon, 28 Dec 2020 at 17:38, Ali Alhaidary <al...@the5stars.org>
wrote:

> ERROR 12-28 10:32:42.382 o.a.w.DefaultExceptionMapper:170
> [io-5443-exec-10] - Unexpected error occurred
> org.springframework.dao.InvalidDataAccessApiUsageException: Encountered
> unmanaged object "org.apache.openmeetings.db.entity.user.User@12b47276"
> in life cycle state  unmanaged while cascading persistence via field
> "org.apache.openmeetings.db.entity.calendar.OmCalendar.owner" during
> flush.  However, this field does not allow cascade persist. You cannot
> flush unmanaged objects or graphs that have persistent associations to
> unmanaged objects.
>  Suggested actions: a) Set the cascade attribute for this field to
> CascadeType.PERSIST or CascadeType.ALL (JPA annotations) or "persist" or
> "all" (JPA orm.xml),
>  b) enable cascade-persist globally,
>  c) manually persist the related field value prior to flushing.
>  d) if the reference belongs to another context, allow reference to it by
> setting StoreContext.setAllowReferenceToSiblingContext().; nested exception
> is <openjpa-3.1.2-r66d2a72 nonfatal user error>
> org.apache.openjpa.persistence.InvalidStateException: Encountered unmanaged
> object "org.apache.openmeetings.db.entity.user.User@12b47276" in life
> cycle state  unmanaged while cascading persistence via field
> "org.apache.openmeetings.db.entity.calendar.OmCalendar.owner" during
> flush.  However, this field does not allow cascade persist. You cannot
> flush unmanaged objects or graphs that have persistent associations to
> unmanaged objects.
>  Suggested actions: a) Set the cascade attribute for this field to
> CascadeType.PERSIST or CascadeType.ALL (JPA annotations) or "persist" or
> "all" (JPA orm.xml),
>  b) enable cascade-persist globally,
>  c) manually persist the related field value prior to flushing.
>  d) if the reference belongs to another context, allow reference to it by
> setting StoreContext.setAllowReferenceToSiblingContext().
> FailedObject: org.apache.openmeetings.db.entity.user.User@12b47276
>     at
> org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:371)
>     at
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:128)
>     at
> org.springframework.dao.support.DataAccessUtils.translateIfNecessary(DataAccessUtils.java:242)
>     at
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:575)
>     at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:743)
>
> *That is when trying to add a google calendar ...*
>

Please file JIRA with this log
and some steps :)
I'll try to check :)


>
> On 12/28/20 10:18 AM, Ali Alhaidary wrote:
>
> Does this has anything with the calendar?
>
>  INFO 12-28 07:05:03.918 o.a.w.p.h.WebApplication:974 [main] -
> [OpenmeetingsApplication] Started Wicket version 9.2.0 in DEPLOYMENT mode
>  INFO 12-28 07:05:05.563 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /
>  INFO 12-28 07:05:05.865 o.a.c.w.s.f.ReflectionServiceFactoryBean:436
> [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.CalendarWebService
> from class org.apache.openmeetings.webservice.CalendarWebService
>  INFO 12-28 07:05:07.959 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /CalendarService
>  INFO 12-28 07:05:07.992 o.a.c.w.s.f.ReflectionServiceFactoryBean:436
> [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.ErrorWebService
> from class org.apache.openmeetings.webservice.ErrorWebService
>  INFO 12-28 07:05:08.050 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /ErrorService
>  INFO 12-28 07:05:08.056 o.a.c.w.s.f.ReflectionServiceFactoryBean:436
> [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.GroupWebService
> from class org.apache.openmeetings.webservice.GroupWebService
>  INFO 12-28 07:05:08.281 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /GroupService
>  INFO 12-28 07:05:08.284 o.a.c.w.s.f.ReflectionServiceFactoryBean:436
> [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.InfoWebService
> from class org.apache.openmeetings.webservice.InfoWebService
>  INFO 12-28 07:05:08.335 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /InfoService
>  INFO 12-28 07:05:08.342 o.a.c.w.s.f.ReflectionServiceFactoryBean:436
> [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.FileWebService
> from class org.apache.openmeetings.webservice.FileWebService
>  INFO 12-28 07:05:08.563 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /FileService
>  INFO 12-28 07:05:08.566 o.a.c.w.s.f.ReflectionServiceFactoryBean:436
> [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RecordingWebService
> from class org.apache.openmeetings.webservice.RecordingWebService
>  INFO 12-28 07:05:08.658 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /RecordService
>  INFO 12-28 07:05:08.662 o.a.c.w.s.f.ReflectionServiceFactoryBean:436
> [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RoomWebService
> from class org.apache.openmeetings.webservice.RoomWebService
>  INFO 12-28 07:05:08.984 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /RoomService
>  INFO 12-28 07:05:08.988 o.a.c.w.s.f.ReflectionServiceFactoryBean:436
> [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.UserWebService
> from class org.apache.openmeetings.webservice.UserWebService
>  INFO 12-28 07:05:09.088 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /UserService
>  INFO 12-28 07:05:09.093 o.a.c.w.s.f.ReflectionServiceFactoryBean:436
> [main] - Creating Service {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.WbWebService
> from class org.apache.openmeetings.webservice.WbWebService
>  INFO 12-28 07:05:09.163 o.a.c.e.ServerImpl:94 [main] - Setting the
> server's publish address to be /WbService
> DEBUG 12-28 07:05:12.506 o.a.o.u.c.CryptProvider:39 [ean#0_Worker-10] -
> get:: configKeyCryptClassName:
> org.apache.openmeetings.util.crypt.SCryptImplementation
> DEBUG 12-28 07:06:30.060 o.a.o.w.a.ClientManager:372 [nio-5443-exec-5] -
> Cluster:: Checking token null, full list: []
>
> On 12/28/20 9:50 AM, Ali Alhaidary wrote:
>
> It is the shortest report, the calendar is added, does not sync, and can
> not find errors in log...
>
> Ali
> On 12/28/20 9:48 AM, Maxim Solodovnik wrote:
>
> without detailed report on what is wrong - no :)
>
> On Mon, 28 Dec 2020 at 12:49, Ali Alhaidary <al...@the5stars.org>
> wrote:
>
>> Is it going to happen?
>> On 12/28/20 8:45 AM, Maxim Solodovnik wrote:
>>
>>
>>
>> On Sat, 26 Dec 2020 at 23:49, Ali Alhaidary <al...@the5stars.org>
>> wrote:
>>
>>> Still not able to sync with google calendar, any update?
>>>
>>
>> I read "still not able" as it was already reported,
>> I haven't saw any report regarding something is not working
>>
>> so no update :)
>>
>>
>> --
>> Best regards,
>> Maxim
>>
>>
>
> --
> Best regards,
> Maxim
>
>

-- 
Best regards,
Maxim

Re: Google Calendar

Posted by Ali Alhaidary <al...@the5stars.org>.
ERROR 12-28 10:32:42.382 o.a.w.DefaultExceptionMapper:170 
[io-5443-exec-10] - Unexpected error occurred
org.springframework.dao.InvalidDataAccessApiUsageException: Encountered 
unmanaged object "org.apache.openmeetings.db.entity.user.User@12b47276" 
in life cycle state  unmanaged while cascading persistence via field 
"org.apache.openmeetings.db.entity.calendar.OmCalendar.owner" during 
flush.  However, this field does not allow cascade persist. You cannot 
flush unmanaged objects or graphs that have persistent associations to 
unmanaged objects.
  Suggested actions: a) Set the cascade attribute for this field to 
CascadeType.PERSIST or CascadeType.ALL (JPA annotations) or "persist" or 
"all" (JPA orm.xml),
  b) enable cascade-persist globally,
  c) manually persist the related field value prior to flushing.
  d) if the reference belongs to another context, allow reference to it 
by setting StoreContext.setAllowReferenceToSiblingContext().; nested 
exception is <openjpa-3.1.2-r66d2a72 nonfatal user error> 
org.apache.openjpa.persistence.InvalidStateException: Encountered 
unmanaged object "org.apache.openmeetings.db.entity.user.User@12b47276" 
in life cycle state  unmanaged while cascading persistence via field 
"org.apache.openmeetings.db.entity.calendar.OmCalendar.owner" during 
flush.  However, this field does not allow cascade persist. You cannot 
flush unmanaged objects or graphs that have persistent associations to 
unmanaged objects.
  Suggested actions: a) Set the cascade attribute for this field to 
CascadeType.PERSIST or CascadeType.ALL (JPA annotations) or "persist" or 
"all" (JPA orm.xml),
  b) enable cascade-persist globally,
  c) manually persist the related field value prior to flushing.
  d) if the reference belongs to another context, allow reference to it 
by setting StoreContext.setAllowReferenceToSiblingContext().
FailedObject: org.apache.openmeetings.db.entity.user.User@12b47276
     at 
org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:371)
     at 
org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:128)
     at 
org.springframework.dao.support.DataAccessUtils.translateIfNecessary(DataAccessUtils.java:242)
     at 
org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:575)
     at 
org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:743)

*That is when trying to add a google calendar ...*

On 12/28/20 10:18 AM, Ali Alhaidary wrote:
>
> Does this has anything with the calendar?
>
>  INFO 12-28 07:05:03.918 o.a.w.p.h.WebApplication:974 [main] - 
> [OpenmeetingsApplication] Started Wicket version 9.2.0 in DEPLOYMENT mode
>  INFO 12-28 07:05:05.563 o.a.c.e.ServerImpl:94 [main] - Setting the 
> server's publish address to be /
>  INFO 12-28 07:05:05.865 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
> [main] - Creating Service 
> {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.CalendarWebService 
> from class org.apache.openmeetings.webservice.CalendarWebService
>  INFO 12-28 07:05:07.959 o.a.c.e.ServerImpl:94 [main] - Setting the 
> server's publish address to be /CalendarService
>  INFO 12-28 07:05:07.992 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
> [main] - Creating Service 
> {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.ErrorWebService 
> from class org.apache.openmeetings.webservice.ErrorWebService
>  INFO 12-28 07:05:08.050 o.a.c.e.ServerImpl:94 [main] - Setting the 
> server's publish address to be /ErrorService
>  INFO 12-28 07:05:08.056 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
> [main] - Creating Service 
> {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.GroupWebService 
> from class org.apache.openmeetings.webservice.GroupWebService
>  INFO 12-28 07:05:08.281 o.a.c.e.ServerImpl:94 [main] - Setting the 
> server's publish address to be /GroupService
>  INFO 12-28 07:05:08.284 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
> [main] - Creating Service 
> {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.InfoWebService 
> from class org.apache.openmeetings.webservice.InfoWebService
>  INFO 12-28 07:05:08.335 o.a.c.e.ServerImpl:94 [main] - Setting the 
> server's publish address to be /InfoService
>  INFO 12-28 07:05:08.342 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
> [main] - Creating Service 
> {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.FileWebService 
> from class org.apache.openmeetings.webservice.FileWebService
>  INFO 12-28 07:05:08.563 o.a.c.e.ServerImpl:94 [main] - Setting the 
> server's publish address to be /FileService
>  INFO 12-28 07:05:08.566 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
> [main] - Creating Service 
> {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RecordingWebService 
> from class org.apache.openmeetings.webservice.RecordingWebService
>  INFO 12-28 07:05:08.658 o.a.c.e.ServerImpl:94 [main] - Setting the 
> server's publish address to be /RecordService
>  INFO 12-28 07:05:08.662 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
> [main] - Creating Service 
> {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RoomWebService 
> from class org.apache.openmeetings.webservice.RoomWebService
>  INFO 12-28 07:05:08.984 o.a.c.e.ServerImpl:94 [main] - Setting the 
> server's publish address to be /RoomService
>  INFO 12-28 07:05:08.988 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
> [main] - Creating Service 
> {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.UserWebService 
> from class org.apache.openmeetings.webservice.UserWebService
>  INFO 12-28 07:05:09.088 o.a.c.e.ServerImpl:94 [main] - Setting the 
> server's publish address to be /UserService
>  INFO 12-28 07:05:09.093 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
> [main] - Creating Service 
> {http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.WbWebService 
> from class org.apache.openmeetings.webservice.WbWebService
>  INFO 12-28 07:05:09.163 o.a.c.e.ServerImpl:94 [main] - Setting the 
> server's publish address to be /WbService
> DEBUG 12-28 07:05:12.506 o.a.o.u.c.CryptProvider:39 [ean#0_Worker-10] 
> - get:: configKeyCryptClassName: 
> org.apache.openmeetings.util.crypt.SCryptImplementation
> DEBUG 12-28 07:06:30.060 o.a.o.w.a.ClientManager:372 [nio-5443-exec-5] 
> - Cluster:: Checking token null, full list: []
>
> On 12/28/20 9:50 AM, Ali Alhaidary wrote:
>>
>> It is the shortest report, the calendar is added, does not sync, and 
>> can not find errors in log...
>>
>> Ali
>>
>> On 12/28/20 9:48 AM, Maxim Solodovnik wrote:
>>> without detailed report on what is wrong - no :)
>>>
>>> On Mon, 28 Dec 2020 at 12:49, Ali Alhaidary 
>>> <ali.alhaidary@the5stars.org <ma...@the5stars.org>> 
>>> wrote:
>>>
>>>     Is it going to happen?
>>>
>>>     On 12/28/20 8:45 AM, Maxim Solodovnik wrote:
>>>>
>>>>
>>>>     On Sat, 26 Dec 2020 at 23:49, Ali Alhaidary
>>>>     <ali.alhaidary@the5stars.org
>>>>     <ma...@the5stars.org>> wrote:
>>>>
>>>>         Still not able to sync with google calendar, any update?
>>>>
>>>>
>>>>     I read "still not able" as it was already reported,
>>>>     I haven't saw any report regarding something is not working
>>>>
>>>>     so no update :)
>>>>
>>>>
>>>>     -- 
>>>>     Best regards,
>>>>     Maxim
>>>
>>>
>>>
>>> -- 
>>> Best regards,
>>> Maxim

Re: Google Calendar

Posted by Ali Alhaidary <al...@the5stars.org>.
Does this has anything with the calendar?

  INFO 12-28 07:05:03.918 o.a.w.p.h.WebApplication:974 [main] - 
[OpenmeetingsApplication] Started Wicket version 9.2.0 in DEPLOYMENT mode
  INFO 12-28 07:05:05.563 o.a.c.e.ServerImpl:94 [main] - Setting the 
server's publish address to be /
  INFO 12-28 07:05:05.865 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
[main] - Creating Service 
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.CalendarWebService 
from class org.apache.openmeetings.webservice.CalendarWebService
  INFO 12-28 07:05:07.959 o.a.c.e.ServerImpl:94 [main] - Setting the 
server's publish address to be /CalendarService
  INFO 12-28 07:05:07.992 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
[main] - Creating Service 
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.ErrorWebService 
from class org.apache.openmeetings.webservice.ErrorWebService
  INFO 12-28 07:05:08.050 o.a.c.e.ServerImpl:94 [main] - Setting the 
server's publish address to be /ErrorService
  INFO 12-28 07:05:08.056 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
[main] - Creating Service 
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.GroupWebService 
from class org.apache.openmeetings.webservice.GroupWebService
  INFO 12-28 07:05:08.281 o.a.c.e.ServerImpl:94 [main] - Setting the 
server's publish address to be /GroupService
  INFO 12-28 07:05:08.284 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
[main] - Creating Service 
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.InfoWebService 
from class org.apache.openmeetings.webservice.InfoWebService
  INFO 12-28 07:05:08.335 o.a.c.e.ServerImpl:94 [main] - Setting the 
server's publish address to be /InfoService
  INFO 12-28 07:05:08.342 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
[main] - Creating Service 
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.FileWebService 
from class org.apache.openmeetings.webservice.FileWebService
  INFO 12-28 07:05:08.563 o.a.c.e.ServerImpl:94 [main] - Setting the 
server's publish address to be /FileService
  INFO 12-28 07:05:08.566 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
[main] - Creating Service 
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RecordingWebService 
from class org.apache.openmeetings.webservice.RecordingWebService
  INFO 12-28 07:05:08.658 o.a.c.e.ServerImpl:94 [main] - Setting the 
server's publish address to be /RecordService
  INFO 12-28 07:05:08.662 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
[main] - Creating Service 
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.RoomWebService 
from class org.apache.openmeetings.webservice.RoomWebService
  INFO 12-28 07:05:08.984 o.a.c.e.ServerImpl:94 [main] - Setting the 
server's publish address to be /RoomService
  INFO 12-28 07:05:08.988 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
[main] - Creating Service 
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.UserWebService 
from class org.apache.openmeetings.webservice.UserWebService
  INFO 12-28 07:05:09.088 o.a.c.e.ServerImpl:94 [main] - Setting the 
server's publish address to be /UserService
  INFO 12-28 07:05:09.093 o.a.c.w.s.f.ReflectionServiceFactoryBean:436 
[main] - Creating Service 
{http://webservice.openmeetings.apache.org/}org.apache.openmeetings.webservice.WbWebService 
from class org.apache.openmeetings.webservice.WbWebService
  INFO 12-28 07:05:09.163 o.a.c.e.ServerImpl:94 [main] - Setting the 
server's publish address to be /WbService
DEBUG 12-28 07:05:12.506 o.a.o.u.c.CryptProvider:39 [ean#0_Worker-10] - 
get:: configKeyCryptClassName: 
org.apache.openmeetings.util.crypt.SCryptImplementation
DEBUG 12-28 07:06:30.060 o.a.o.w.a.ClientManager:372 [nio-5443-exec-5] - 
Cluster:: Checking token null, full list: []

On 12/28/20 9:50 AM, Ali Alhaidary wrote:
>
> It is the shortest report, the calendar is added, does not sync, and 
> can not find errors in log...
>
> Ali
>
> On 12/28/20 9:48 AM, Maxim Solodovnik wrote:
>> without detailed report on what is wrong - no :)
>>
>> On Mon, 28 Dec 2020 at 12:49, Ali Alhaidary 
>> <ali.alhaidary@the5stars.org <ma...@the5stars.org>> wrote:
>>
>>     Is it going to happen?
>>
>>     On 12/28/20 8:45 AM, Maxim Solodovnik wrote:
>>>
>>>
>>>     On Sat, 26 Dec 2020 at 23:49, Ali Alhaidary
>>>     <ali.alhaidary@the5stars.org
>>>     <ma...@the5stars.org>> wrote:
>>>
>>>         Still not able to sync with google calendar, any update?
>>>
>>>
>>>     I read "still not able" as it was already reported,
>>>     I haven't saw any report regarding something is not working
>>>
>>>     so no update :)
>>>
>>>
>>>     -- 
>>>     Best regards,
>>>     Maxim
>>
>>
>>
>> -- 
>> Best regards,
>> Maxim

Re: Google Calendar

Posted by Ali Alhaidary <al...@the5stars.org>.
It is the shortest report, the calendar is added, does not sync, and can 
not find errors in log...

Ali

On 12/28/20 9:48 AM, Maxim Solodovnik wrote:
> without detailed report on what is wrong - no :)
>
> On Mon, 28 Dec 2020 at 12:49, Ali Alhaidary 
> <ali.alhaidary@the5stars.org <ma...@the5stars.org>> wrote:
>
>     Is it going to happen?
>
>     On 12/28/20 8:45 AM, Maxim Solodovnik wrote:
>>
>>
>>     On Sat, 26 Dec 2020 at 23:49, Ali Alhaidary
>>     <ali.alhaidary@the5stars.org
>>     <ma...@the5stars.org>> wrote:
>>
>>         Still not able to sync with google calendar, any update?
>>
>>
>>     I read "still not able" as it was already reported,
>>     I haven't saw any report regarding something is not working
>>
>>     so no update :)
>>
>>
>>     -- 
>>     Best regards,
>>     Maxim
>
>
>
> -- 
> Best regards,
> Maxim

Re: Google Calendar

Posted by Maxim Solodovnik <so...@gmail.com>.
without detailed report on what is wrong - no :)

On Mon, 28 Dec 2020 at 12:49, Ali Alhaidary <al...@the5stars.org>
wrote:

> Is it going to happen?
> On 12/28/20 8:45 AM, Maxim Solodovnik wrote:
>
>
>
> On Sat, 26 Dec 2020 at 23:49, Ali Alhaidary <al...@the5stars.org>
> wrote:
>
>> Still not able to sync with google calendar, any update?
>>
>
> I read "still not able" as it was already reported,
> I haven't saw any report regarding something is not working
>
> so no update :)
>
>
> --
> Best regards,
> Maxim
>
>

-- 
Best regards,
Maxim

Re: Google Calendar

Posted by Ali Alhaidary <al...@the5stars.org>.
Is it going to happen?

On 12/28/20 8:45 AM, Maxim Solodovnik wrote:
>
>
> On Sat, 26 Dec 2020 at 23:49, Ali Alhaidary 
> <ali.alhaidary@the5stars.org <ma...@the5stars.org>> wrote:
>
>     Still not able to sync with google calendar, any update?
>
>
> I read "still not able" as it was already reported,
> I haven't saw any report regarding something is not working
>
> so no update :)
>
>
> -- 
> Best regards,
> Maxim

Re: Google Calendar

Posted by Maxim Solodovnik <so...@gmail.com>.
On Sat, 26 Dec 2020 at 23:49, Ali Alhaidary <al...@the5stars.org>
wrote:

> Still not able to sync with google calendar, any update?
>

I read "still not able" as it was already reported,
I haven't saw any report regarding something is not working

so no update :)


-- 
Best regards,
Maxim