http://blog.gmane.org/gmane.org.osaf.cosmo hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.org.osaf.cosmo/6185 <pre>Hi, I downloaded osaf-server-bundle-1.1.0 zip folder and with this run the chandler server on local machine.....http://localhost:81/chandler Then I created on user and in that user created one calendar....through web ui.... Now my requirement is: 1) To access it through caldav4j api, so I changed CaldavCredential.java class accordingly. and changed: home = "/dav/abc/" (abc is my user name) collection = "collection/" But it throws me 403 as response code means forbidden. What more changes it require???????????????? 2) Secondly, I wanna know, whether it is possible to share calendar between two users A and B, so that A can book slot into B's calendar. Please help me out as i'm new to this calendar world........ Thanks and Regards.. _______________________________________________ cosmo-dev mailing list cosmo-dev&lt; at &gt;lists.osafoundation.org http://lists.osafoundation.org/mailman/listinfo/cosmo-dev </pre> Test Test 2011-12-02T12:44:26 http://permalink.gmane.org/gmane.org.osaf.cosmo/6184 <pre>About a year ago it appeared that the Hub server was running some kind of patched snapshot which provided support for CalDAV sync with iOS devices' calendar app. But the Cosmo Server bundle remains at 1.1.0 to date. Any news? Thunderbird Lighting used to work but something is broken after recent updates to the add-on. I wonder if it is also affected by whatever has been troubling the compatibility between Cosmo and iOS. </pre> Andrew Tong 2011-10-19T06:00:36 http://permalink.gmane.org/gmane.org.osaf.cosmo/6183 <pre>Hello! Do you want a more satisfactory future, go up in money earning power, and the recognition of all? Today only: We can assist with Diplomas from prestigious universities based on your present knowledge and work experience. Get a Degree in 4 weeks with our program! ~Our program will let EVERYONE with professional experience get a 100% verified Degree: ~Doctorate ~Bachelors ~Masters - Just think about it... - Follow YOUR Dreams! - Live a much better life by earning or upgrading your degree. This is a best way to make a right move and receive your due benefits... if you are qualified but are lacking that piece of paper. Get one from us in a fraction of the time. If you want to get better - you must Contact Us to start improving your life! ~CALL~ 1-310-205-2502 You must leave us a voice message with your phone number with country code if outside USA and name and we'll contact you as soon as possible. It's your way... Make the right move. Yours sincerely. Do Not Reply to this Email. We do not reply to text inquiries, and our server will reject all response traffic. We apologize for any inconvenience this may have caused you. </pre> cosmo-dev< at >osafoundation.org 2011-04-25T13:57:27 http://permalink.gmane.org/gmane.org.osaf.cosmo/6182 <pre>Hi all, I have the following errors many times! Can I ask your advice on something? I use the following commands. LANG=en_US.UTF-8 mvn -Dmaven.test.skip=true package -e My execution environment is as follows. ubuntu 10.10 Maverick Meerkat Maven 2.2.1-5 [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error adding file to archive: /home/super/calendar/cosmo/snarf/../cosmo/target/cosmo-1.1-SNAPSHOT.war isn't a file. [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error adding file to archive: /home/super/calendar/cosmo/snarf/../cosmo/target/cosmo-1.1-SNAPSHOT.war isn't a file. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error adding file to archive: /home/super/calendar/cosmo/snarf/../cosmo/target/cosmo-1.1-SNAPSHOT.war isn't a file. at org.apache.maven.plugin.assembly.AbstractAssemblyMojo.processFileList(AbstractAssemblyMojo.java:1341) at org.apache.maven.plugin.assembly.AbstractAssemblyMojo.createArchive(AbstractAssemblyMojo.java:325) at org.apache.maven.plugin.assembly.AbstractAssemblyMojo.createAssembly(AbstractAssemblyMojo.java:261) at org.apache.maven.plugin.assembly.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:241) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: org.codehaus.plexus.archiver.ArchiverException: /home/super/calendar/cosmo/snarf/../cosmo/target/cosmo-1.1-SNAPSHOT.war isn't a file. at org.codehaus.plexus.archiver.AbstractArchiver.addFile(AbstractArchiver.java:172) at org.apache.maven.plugin.assembly.AbstractAssemblyMojo.processFileList(AbstractAssemblyMojo.java:1336) ... 22 more [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2 minutes 15 seconds [INFO] Finished at: Wed Jan 12 19:41:17 JST 2011 [INFO] Final Memory: 18M/136M [INFO] ------------------------------------------------------------------------ </pre> waterimp 2011-01-12T11:09:24 http://permalink.gmane.org/gmane.org.osaf.cosmo/6181 <pre> Hi, I'm running an instance of osaf-server-bundle-1.1.0 in my PC. I want to receive notificacion by email about event in a calendar. I set Scheduler Properties in cosmo.properties file (cosmo.scheduler.enabled=true, etc), but it doesn't works. I receive email from server about "Forgot your login" correctly, so emailing is working with the server. Notification by email is enabled in server bundle? I've seen a "Notification Tab" ( in settings option) in Chander Hub but it doesn't appears in my server web page. Hub server version is different from Chandler Server Version 1.1-SNAPSHOT in bundle form download link in chandlerproject? Thanks Christian </pre> christian 2010-11-29T12:49:01 http://permalink.gmane.org/gmane.org.osaf.cosmo/6180 <pre>I understand that the version running on the public chandler hub is newer than the released server bundle. The hub version apparently has been patched to fix the iphone caldav sync issue. </pre> Andrew Tong 2010-10-15T21:20:03 http://permalink.gmane.org/gmane.org.osaf.cosmo/6179 <pre>Hi there, I was wondering whether there's any plan for another Cosmo release? The last 1.1.0 release was two years ago. I also noticed that there's a 1.2.0 tag: http://svn.osafoundation.org/server/cosmo/tags/rel_1.2.0/ Is this an official release? The download page still quotes 1.1.0: http://chandlerproject.org/Developers/DownloadChandlerServer Cheers, Mark </pre> Mark Hobson 2010-10-14T17:03:05 http://permalink.gmane.org/gmane.org.osaf.cosmo/6178 <pre> I am trying to setup iCal 4.0 / iPhone access using OSAF Server Bundle 1.1, but am encountering issues related to PROPFIND URL mismatches (missing calendars, etc). Is there a 1.2 build of the server bundle? Or, is there a newer chandler.war that I could drop-in to the 1.1 bundle (or at least try to drop-in)? </pre> Justin Vallon 2010-10-11T18:50:26 http://permalink.gmane.org/gmane.org.osaf.cosmo/6177 <pre>Hi all, today I released caldav4j 0.6.1. It contains a minor but useful improvement: use ehcache 1.2 instead of 1.2beta. The modification is only in the pom.xml but it appears to improve significantly the troubleshooting when using cache in real world. You can upgrade your old app simply updating your pom: the code of caldav4j is *unchanged*, only the pom.xml is changed! Instead, if you're developing new apps, the switch to 0.7-SNAPSHOT is strongly suggested, as many 0.6* classes will be deprecated or renamed. Peace, R. </pre> Roberto Polli 2010-08-03T11:20:12 http://permalink.gmane.org/gmane.org.osaf.cosmo/6176 <pre>I tried Tim's shortened URL on iOS4 on iPhone 3GS and it passed the initial set-up test. But no collection shows in the calendar app. I have multiple collections under my account on the Cosmo 1.1.0 server. ----- Original Message ---- Date: Wed, 21 Jul 2010 09:39:22 -0700 From: Tim White &lt;tim.white&lt; at &gt;zulius.com&gt; Subject: [cosmo-dev] iPhone/iPad Calendar CalDAV support? To: cosmo-dev&lt; at &gt;lists.osafoundation.org Woohoo! I was able to get my iPhone client to sync. It was necessary to use the following url structure (as opposed to the previous url to a specific collection): https://my.domain.com:51115/chandler/dav/users/timwhite </pre> Andrew Tong 2010-07-22T06:25:33 http://permalink.gmane.org/gmane.org.osaf.cosmo/6175 <pre>Woohoo! I was able to get my iPhone client to sync. It was necessary to use the following url structure (as opposed to the previous url to a specific collection): https://my.domain.com:51115/chandler/dav/users/timwhite Still no joy with the iPad however, even using the above url. My server's logs/osafsrv.log reports the following error (after a bunch of DEBUG messages) when I start the iPad's calendar app: 2010-07-21 09:28:18,801 INFO [StandardRequestHandler] Client error (403): CALDAV:comp-filter time-range requires an end time So maybe a problem with the iPad client? </pre> Tim White 2010-07-21T16:39:22 http://permalink.gmane.org/gmane.org.osaf.cosmo/6174 <pre>_______________________________________________ cosmo-dev mailing list cosmo-dev&lt; at &gt;lists.osafoundation.org http://lists.osafoundation.org/mailman/listinfo/cosmo-dev </pre> Tim White 2010-07-21T15:55:18 http://permalink.gmane.org/gmane.org.osaf.cosmo/6173 <pre> In response to your question I have just tidied up my code and uploaded it to google code - http://code.google.com/p/cosmo-atom-integration/ In the project blurb I have "The cosmo calendar provides an atom interface to communicate with it. We have implemented this using httpclient4 code and provided simple interfaces for your code to call. It is the hope that this project saves many people many hours, and that people contribute back to it in order to give the fantastic cosmo new life by making it easy in becoming a part of other people's projects." Whilst it may not directly answer your question, it does provide the ability to create new users. Hopefully you are able to use this code and feedback any problems. Whilst it is no longer in use here we believe it could still be used by many and am willing to make it work for you to help us get the module more widely usable and help get instructions right (for which there are none at present - its a simple maven svn project). Regards, adam </pre> adam hamer 2010-06-28T10:29:56 http://permalink.gmane.org/gmane.org.osaf.cosmo/6172 <pre>Hello everyone! I am trying to enable my java calendaring application to create new users on the cosmo server. I am using the apache http-client library. However, executing the PUT-method gives me "HTTP/1.1 403 Forbidden" and I cannout figure out why. I do have the line "cosmo.service.account.disableSignups=false" in my cosmo.properties file in ./etc/. I am using osaf-server-bundle-1.1.0 for testing. Unfortunately, the logs don't show any hints. So if you have any suggestions or if you need more info, I'd be happy to hear from you. Thanks in advance: Snellius </pre> Cornelius Lilge 2010-06-26T17:29:17 http://permalink.gmane.org/gmane.org.osaf.cosmo/6171 <pre>Jared, I understand that the patches fixes also the iPhone CalDAV issue and are part of public Hub but not yet in the server bundle which is still listed as 1.1.0. I have 5-user production setup with 1.1.0 running as a Windows service, and clients using mostly the web interface (faster than the Chandler Desktop!) and an iPhone on 3.1.3. If the next server bundle version isn't going to be made publicly final imminently can we help to test any near release-quality version? By "test" I mean we'll simply use it day-to-day for real. Andrew </pre> Andrew Tong 2010-02-20T13:43:32 http://permalink.gmane.org/gmane.org.osaf.cosmo/6170 <pre>iCal 4.x support has been missing from Cosmo and Hub. A couple patches have been offered, but I'm starting to move forward with the patch attached to bug 12907, contributed by Irina Arkhipets. https://bugzilla.osafoundation.org/show_bug.cgi?id=12907 The patch was tested earlier by Graham Perrin on a fresh (empty database) instance but is now installed on next.osaf.us with snapshotted recent Hub data. If that testing looks good too, I'll update Hub production and apply the patch to trunk. Code reviews of the patch would be welcomed. It's reported that the patch causes iCal 4.x connection problems ("connection closed", "unexpected network error", etc as reported in: https://bugzilla.osafoundation.org/show_bug.cgi?id=12933 https://bugzilla.osafoundation.org/show_bug.cgi?id=12934 I don't have an iCal 4.x installation around, so don't know what's actually going on there. Packet captures would be handy. From Irina's discussion in the ticket: ------ 1. Cosmo does not take into account that collection URL should not contain extra doubled slashes and should end with the slash. Apple iCal 4.0 breaks otherwise during the account creation. That is why there are no any calendars in calendar view after the Cosmo user account creation. 2. Cosmo formats DAV privileges incorrectly. It should be like "&lt;D:privilege&gt;&lt;D:read-current-user-privilege-set/&gt;&lt;/D:privilege&gt;" – but Cosmo omits &lt;privelege&gt; tags. It is unable to edit the events in Snow Leopard calendar view because of this reason. 3. MM CalDav Servlet sends supported calendar component set property in incorrect format. It is unable to create new events in iCal Client 4 because of this reason. ------- </pre> Jared Rhine 2010-02-07T09:08:01 http://permalink.gmane.org/gmane.org.osaf.cosmo/6169 <pre>_______________________________________________ cosmo-dev mailing list cosmo-dev&lt; at &gt;lists.osafoundation.org http://lists.osafoundation.org/mailman/listinfo/cosmo-dev </pre> vaibhav 2010-02-04T17:46:59 http://permalink.gmane.org/gmane.org.osaf.cosmo/6168 <pre>_______________________________________________ cosmo-dev mailing list cosmo-dev&lt; at &gt;lists.osafoundation.org http://lists.osafoundation.org/mailman/listinfo/cosmo-dev </pre> vaibhav 2010-02-04T17:46:53 http://permalink.gmane.org/gmane.org.osaf.cosmo/6167 <pre> I do not object. You already have :) http://github.com/travis/cosmo http://github.com/ashanan/cosmo Github has publicly griped that it's super expensive for them to support open- source-for-free on their service but even if they trim service, moving's not too hard. Frankly, I'm not sure. I suspect git makes it easier to change the right answer later if needed. I'm not sure how the various approaches impact things other than what devs set as their origin.master. In terms of the project, is the only difference whether we put "fork from github.com/travis/cosmo" or "fork from github.com/osaf/cosmo" on the dev page? How big is our repo now? I'm sure it's as tiny as git allows, but did we check in any binaries or anything that makes the 300MB free open-source account a problem? (Though github will increase the limit if we actually need it.) Other probable todo items: * committer's vote? * run that svn-to-git pattern that fixes up the author strings * i'd really kinda like to keep the cosmo-commits list; dunno if github provides or i'd need to hack something on top of github's authenticated watch/rss services * chandlerproject.org wiki update for dev access/contributing * update or kill the cia.vc account? </pre> Jared Rhine 2010-01-31T20:10:04 http://permalink.gmane.org/gmane.org.osaf.cosmo/6166 <pre> Interesting -- I was able to build the current Cosmo trunk without applying your build patch. We should proceed anyway, but I'll switch from verifying that your patch fixes something specific to just verifying that it doesn't cause problems. For reference, my build output is here: http://people.osafoundation.org/jared/cosmo-build-2010-01-31A.txt You can see an outdated POM like spring-security-core-tiger-2.0.2 came from: http://repo1.maven.org/maven2/org/springframework/security/spring-security- core-tiger/2.0.2/spring-security-core-tiger-2.0.2.pom and that my Maven repo is rm -rf'ed at the beginning of the build. </pre> Jared Rhine 2010-01-31T19:13:21 http://permalink.gmane.org/gmane.org.osaf.cosmo/6165 <pre>_______________________________________________ cosmo-dev mailing list cosmo-dev&lt; at &gt;lists.osafoundation.org http://lists.osafoundation.org/mailman/listinfo/cosmo-dev </pre> adam hamer 2010-01-30T11:44:35 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.org.osaf.cosmo