I have alfresco 4.2.b running (will test soon with 4.2.d/4.2.e). I'm testing on a dev instance with content/db/indexes from our production instance. Server is Ubuntu 12.04.3 with a PPA for tomcat-7.0.42.
On the same machine I also have the 4.2.b bundle installed in /opt/alfresco-4.2.b. Only one of these tomcat instances runs at any given time. Normally I have an apache reverse proxy in front of both for SSL (with proxy_ajp to tomcat) and I've tested with and without the apache reverse proxy.
I have a difference in behavior between the bundle and the distribution and am requesting insights into what might be causing this (so I can fix it and have bundle and distribution tomcat work the same way).
I test CMIS functionality in Libreoffice 4.0.2 and 4.1.3.2
I've made the bundle and distribution configurations as close as possible (using the same WAR files, configuration in shared/classes is identical, configuration in [tomcat]/conf is as close to identical as is practical (any differences in distribution tomcat config has to do with customisations as per: http://wiki.alfresco.com/wiki/Install_Tomcat6).
As noted above I usually run with an apache reverse proxy for SSL but for testing this I just hit tomcat directly at port 8080 and see the same results so it's not the reverse proxy or AJP causing the difference in behavior (I don't see why it would anyway since cmisatom works and cmisws doesn't, if it were the reverse proxy I'd expect both to fail).
Again this is 4.2.b. I expect to run into CSRF issues with the reverse proxy when I test against 4.2.d and 4.2.e. That's not the issue here though.
As in the subject, no need to resolve this. After more testing, I've decied to just wait for libreoffice 4.2 to come out. There are enough usability and performance issues with libreoffice 4.0 and 4.1 and CMIS access to alfresco (libreoffice bugs) that I don't think it's worth training my colleagues on libreoffice CMIS until 4.2 is out.
The cmisws vs cmisatom difference on my dev instance is clearly a configuration error. I'm not clear on what the error is, but I now have cmisws working with https, apache reverse proxy and distribution tomcat on our test instance but not working on my dev instance with the same configuration. Looks like I'm missing something in my test instance's configuration.