Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.9.0
    • Fix Version/s: 0.9.0
    • Component/s: None
    • Labels:
      None

      Description

      Report test results below in the comments for release candidates for 0.9.0. See https://cwiki.apache.org/confluence/display/WOOKIE/Testing+a+Release

      Please include:

      Server OS:
      Client OS:
      Server and Client separate machines?:
      Servlet Engine:
      Java version:
      Browser:
      Browser version:
      Tested with Shindig integration?:

      1. rat.log
        520 kB
        Ate Douma

        Issue Links

          Activity

          Hide
          Scott Wilson added a comment -

          Server OS: Mac OS X
          Client OS: Mac OS X
          Server and Client separate machines?: No
          Servlet Engine: Standalone (Jetty)
          Java version: 1.6
          Browser: Safari
          Browser version: 5.0.3
          Tested with Shindig integration?: No

          The only issue I had was that the startup.sh file did not have execute permission set when I unzipped the package - I had to chmod it before I could run it.

          Show
          Scott Wilson added a comment - Server OS: Mac OS X Client OS: Mac OS X Server and Client separate machines?: No Servlet Engine: Standalone (Jetty) Java version: 1.6 Browser: Safari Browser version: 5.0.3 Tested with Shindig integration?: No The only issue I had was that the startup.sh file did not have execute permission set when I unzipped the package - I had to chmod it before I could run it.
          Hide
          David Sherlock added a comment -

          Server OS: OS X
          Client OS: OS X
          Server and Client separate machines?: NO
          Servlet Engine: Standalone
          Java version: 1.6
          Browser: Firefox
          Browser version: 3.6.13
          Tested with Shindig integration?:

          Didn't get chance to test gadget deployment.

          Also had to chmod startup. Otherwise everything was fine

          Show
          David Sherlock added a comment - Server OS: OS X Client OS: OS X Server and Client separate machines?: NO Servlet Engine: Standalone Java version: 1.6 Browser: Firefox Browser version: 3.6.13 Tested with Shindig integration?: Didn't get chance to test gadget deployment. Also had to chmod startup. Otherwise everything was fine
          Hide
          Scott Wilson added a comment -

          Server OS: Mac OS X
          Client OS: Mac OS X
          Server and Client separate machines?: No
          Servlet Engine: WAR (Tomcat 7.0.2)
          Java version: 1.6
          Browser: Safari
          Browser version: 5.0.3
          Tested with Shindig integration?: No

          I keep getting this problem trying to start it up:

          SEVERE: The web application [/wookie] registered the JBDC driver [org.apache.derby.jdbc.AutoloadedDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

          Show
          Scott Wilson added a comment - Server OS: Mac OS X Client OS: Mac OS X Server and Client separate machines?: No Servlet Engine: WAR (Tomcat 7.0.2) Java version: 1.6 Browser: Safari Browser version: 5.0.3 Tested with Shindig integration?: No I keep getting this problem trying to start it up: SEVERE: The web application [/wookie] registered the JBDC driver [org.apache.derby.jdbc.AutoloadedDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
          Hide
          Scott Wilson added a comment -

          Server OS: Mac OS X
          Client OS: Mac OS X
          Server and Client separate machines?: No
          Servlet Engine: WAR (Tomcat 6.0.20)
          Java version: 1.6
          Browser: Safari
          Browser version: 5.0.3
          Tested with Shindig integration?: No

          Worked absolutely fine on Tomcat 6.0.20.

          Show
          Scott Wilson added a comment - Server OS: Mac OS X Client OS: Mac OS X Server and Client separate machines?: No Servlet Engine: WAR (Tomcat 6.0.20) Java version: 1.6 Browser: Safari Browser version: 5.0.3 Tested with Shindig integration?: No Worked absolutely fine on Tomcat 6.0.20.
          Hide
          Paul Sharples added a comment -

          Server OS: Windows 7 x64
          Client OS: Windows 7 x64
          Server and Client separate machines?: No
          Servlet Engine: applies to both standalone & war build with tomcat 6.0.32
          Java version: 1.6
          Browser: n/a
          Browser version: n/a
          Tested with Shindig integration?: No

          Re-testing the builds, specifically setting/getting the preferences and there's a (v)minor bug. Some browsers complain when a preference name or value contains the '-' character

          for example....
          Error: invalid assignment left-hand side Source File: http://localhost:8080/wookie/shared/js/wookie-wrapper.js Line: 72, Column: 34
          Source Code: Widget.preferences.wookie-test-key='defaultvalue'

          Affected browsers
          ----------------------------
          Firefox 3.6.16
          Safari for windows 5.0.4

          Works okay in
          -------------------------
          IE8
          Google Chrome 10.0.648.151

          Resolution
          ----------------
          We could just document not to use '-' character in this release for preferences. Or the wookie-wrapper.js in the the main trunk does not suffer with this problem and runs okay in all browsers. We could replace the js wrapper in the 0.9.0 branch with the one in the main trunk.

          Show
          Paul Sharples added a comment - Server OS: Windows 7 x64 Client OS: Windows 7 x64 Server and Client separate machines?: No Servlet Engine: applies to both standalone & war build with tomcat 6.0.32 Java version: 1.6 Browser: n/a Browser version: n/a Tested with Shindig integration?: No Re-testing the builds, specifically setting/getting the preferences and there's a (v)minor bug. Some browsers complain when a preference name or value contains the '-' character for example.... Error: invalid assignment left-hand side Source File: http://localhost:8080/wookie/shared/js/wookie-wrapper.js Line: 72, Column: 34 Source Code: Widget.preferences.wookie-test-key='defaultvalue' Affected browsers ---------------------------- Firefox 3.6.16 Safari for windows 5.0.4 Works okay in ------------------------- IE8 Google Chrome 10.0.648.151 Resolution ---------------- We could just document not to use '-' character in this release for preferences. Or the wookie-wrapper.js in the the main trunk does not suffer with this problem and runs okay in all browsers. We could replace the js wrapper in the 0.9.0 branch with the one in the main trunk.
          Hide
          Ross Gardler added a comment -

          Release versions tested: Source and Standalone
          Server OSs: Windows
          Server and browser separate machines?: Yes (virtual machines)
          Servlet Engine: embedded
          Java version: 1.6.0_17
          Browsers tested: Firefox
          Browser versions: 3.6.10
          Tested with Shindig integration?: No
          Results: All tests passed

          Show
          Ross Gardler added a comment - Release versions tested: Source and Standalone Server OSs: Windows Server and browser separate machines?: Yes (virtual machines) Servlet Engine: embedded Java version: 1.6.0_17 Browsers tested: Firefox Browser versions: 3.6.10 Tested with Shindig integration?: No Results: All tests passed
          Hide
          Ross Gardler added a comment -

          One minor issue which can easily be resolved in the final build...

          The zips unpack to the same directory as the zip rather than a subdirectory. It should really extract to "/Apache Wookie" (or similar)

          Show
          Ross Gardler added a comment - One minor issue which can easily be resolved in the final build... The zips unpack to the same directory as the zip rather than a subdirectory. It should really extract to "/Apache Wookie" (or similar)
          Hide
          Ate Douma added a comment -

          Tested: RC-0.9.0-20110203 downloads (source, standalone and war)
          Server OSs: Ubuntu 11.04
          Server and browser separate machines?: No
          Servlet Engine: embedded, Tomcat 6.0.32, Tomcat 7.0.11
          Java version: 1.6.0_24 (64-bit)
          Browsers tested: Firefox 4.0
          Tested with Shindig integration?: No

          Results:

          • Standalone (embedded Jetty + Derby) using ./startup.sh (after $chmod +x *.sh):
          • Most interaction tests pass, but Widget API Tester fails on "access attribute:name" and "access attribute:description" (marked red)
          • Refreshing the Widget API Tester causes the following error displayed in the browser:

          Persistence_commit_exception_caught_for_transaction_orgapachewookiebeansutilPersistenceCommitException_Transaction_commit_exception_openjpa200r422266935683_fatal_store_error_orgapacheopenjpapersistenceRollbackException_The_transaction_has_been_rolled_back__See_the_nested_exceptions_for_details_on_the_errors_that_occurred_FailedObject_orgapachewookiebeansjpaimplPreferenceImpl6815a68d

          and the following stack trace in the console:

          org.apache.openjpa.lib.jdbc.ReportingSQLException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'UNPREFERENCE1' defined on 'PREFERENCE'.

          {prepstmnt 61964785 INSERT INTO JAVA.Preference (ID, JPA_VERSION, WIDGET_INSTANCE_ID, DKEY, DVALUE, READONLY) VALUES (?, ?, ?, ?, ?, ?) [params=(int) 907, (int) 1, (int) 734, (String) nice, (Reader) java.io.StringReader@7baca5ae, (String) ]}

          [code=20000, state=23505]
          at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:257)
          at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:233)
          at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:70)
          at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:1079)
          at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:285)
          at org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1722)
          at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:267)
          at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:118)
          ... 36 more

          • stopping standalone and run ./startup.sh again: all previously deployed widgets are "gone" except the "unsupported widget" widget
            -> standalone is not repeatable runnable
          • Building distributions from source using ant/ivy build-release-src, build-release-war, build-release-standalone targets: works OK
          • Running war distribution in own container:
          • README.txt is incomplete:
          • it doesn't explain a local.widgetserver.properties is auto-created (in my case under $CATALINA_HOME/bin) which needs to be updated to specify widget.persistence.manager.dbtype=mysql5 (if using mysql)
            without the above, wookie won't start up
          • I would prefer it if a derby configuration could be provided without having to download/configure mysql first like as with the standalone package, or at least provide instructions how to do so
          • running in tomcat 6.0.32:
          • works mostly fine like with the standalone but again with same failures on the API Test widget:
          • refresh now causes "Internal Server Error" to be displayed
          • similar type jpa stack trace concerning duplicate key entries
          • running in tomcat 7.0.11:
          • causes a "Session Error" dialog to be displayed for each widget on the page during loading, repeated after a page refresh
          • interactions works mostly fine after above, except with API Test widget which causes much more "Session Error" messages and most test fail with output "null" or empty (marked red)

          Concerning the release distributions:

          • source distribution:
          • connector/java and parser/java folders:
          • contain both build and dist folders not contained in the svn source tree
          • build folders contain (duplicated) .java src files as well as corresponding .class
          • dist folders contain maven project files (poms) not in svn as well as pre-build jars
          • many files don't have the required license-headers, especially most .js and .xml files
            the rules from http://www.apache.org/legal/src-headers.html needs to be followed
          • I ran apache-rat-0.7 in the source distribution root folder using $java -jar /opt/apache-rat-0.7/apache-rat-0.7.jar . > rat.log
            The attached rat.log file shows all files which do not yet have an appropriate license-header or otherwise should be (explicitly) excluded from reporting upon
            My suggestion is to incorporate apache-rat in the ant/ivy build configuration using the apache-rat ant-tasks so the appropriate configuration and exclusions can be setup and managed from the build
          • NOTICE file seems pretty good maintained although I haven't yet checked/validated all and every additional external license usage
          • several duplicate jar artifacts are bundled in the source distribution under /ant/lib and /parser/java/ant/lib: maybe only one /ant/lib folder should suffice?
          • standalone and war distribution:
          • both contain a pre-build wookieJavaConnector-0.1.0-SNAPSHOT.jar and wookieW3CParser-0.1.0-SNAPSHOT.jar
          • neither of these artifacts contain the required NOTICE and LICENSE files
          • how is version management for these two artifacts "managed" and related to the whole of the Wookie release
          • although this is not a maven based release, -SNAPSHOT versioned artifacts are considered unreliable by definition
          • the war artifact within the war distribution itself also should have the required NOTICE and LICENSE files
          • all:
          • An Incubator disclaimer is required to be provided in every distribution, in the README or RELEASE_NOTES DISCLAIMER
          • Preferably also a RELEASE_NOTES is provided, detailing the version of the release, issues fixed and possible known issues pertaining this release
          Show
          Ate Douma added a comment - Tested: RC-0.9.0-20110203 downloads (source, standalone and war) Server OSs: Ubuntu 11.04 Server and browser separate machines?: No Servlet Engine: embedded, Tomcat 6.0.32, Tomcat 7.0.11 Java version: 1.6.0_24 (64-bit) Browsers tested: Firefox 4.0 Tested with Shindig integration?: No Results: Standalone (embedded Jetty + Derby) using ./startup.sh (after $chmod +x *.sh): Most interaction tests pass, but Widget API Tester fails on "access attribute:name" and "access attribute:description" (marked red) Refreshing the Widget API Tester causes the following error displayed in the browser: Persistence_commit_exception_caught_for_transaction_orgapachewookiebeansutilPersistenceCommitException_Transaction_commit_exception_openjpa200r422266935683_fatal_store_error_orgapacheopenjpapersistenceRollbackException_The_transaction_has_been_rolled_back__See_the_nested_exceptions_for_details_on_the_errors_that_occurred_FailedObject_orgapachewookiebeansjpaimplPreferenceImpl6815a68d and the following stack trace in the console: org.apache.openjpa.lib.jdbc.ReportingSQLException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'UNPREFERENCE1' defined on 'PREFERENCE'. {prepstmnt 61964785 INSERT INTO JAVA.Preference (ID, JPA_VERSION, WIDGET_INSTANCE_ID, DKEY, DVALUE, READONLY) VALUES (?, ?, ?, ?, ?, ?) [params=(int) 907, (int) 1, (int) 734, (String) nice, (Reader) java.io.StringReader@7baca5ae, (String) ]} [code=20000, state=23505] at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:257) at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:233) at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:70) at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:1079) at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:285) at org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1722) at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:267) at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:118) ... 36 more stopping standalone and run ./startup.sh again: all previously deployed widgets are "gone" except the "unsupported widget" widget -> standalone is not repeatable runnable Building distributions from source using ant/ivy build-release-src, build-release-war, build-release-standalone targets: works OK Running war distribution in own container: README.txt is incomplete: it doesn't explain a local.widgetserver.properties is auto-created (in my case under $CATALINA_HOME/bin) which needs to be updated to specify widget.persistence.manager.dbtype=mysql5 (if using mysql) without the above, wookie won't start up I would prefer it if a derby configuration could be provided without having to download/configure mysql first like as with the standalone package, or at least provide instructions how to do so running in tomcat 6.0.32: works mostly fine like with the standalone but again with same failures on the API Test widget: refresh now causes "Internal Server Error" to be displayed similar type jpa stack trace concerning duplicate key entries running in tomcat 7.0.11: causes a "Session Error" dialog to be displayed for each widget on the page during loading, repeated after a page refresh interactions works mostly fine after above, except with API Test widget which causes much more "Session Error" messages and most test fail with output "null" or empty (marked red) Concerning the release distributions: source distribution: connector/java and parser/java folders: contain both build and dist folders not contained in the svn source tree build folders contain (duplicated) .java src files as well as corresponding .class dist folders contain maven project files (poms) not in svn as well as pre-build jars many files don't have the required license-headers, especially most .js and .xml files the rules from http://www.apache.org/legal/src-headers.html needs to be followed I ran apache-rat-0.7 in the source distribution root folder using $java -jar /opt/apache-rat-0.7/apache-rat-0.7.jar . > rat.log The attached rat.log file shows all files which do not yet have an appropriate license-header or otherwise should be (explicitly) excluded from reporting upon My suggestion is to incorporate apache-rat in the ant/ivy build configuration using the apache-rat ant-tasks so the appropriate configuration and exclusions can be setup and managed from the build NOTICE file seems pretty good maintained although I haven't yet checked/validated all and every additional external license usage several duplicate jar artifacts are bundled in the source distribution under /ant/lib and /parser/java/ant/lib: maybe only one /ant/lib folder should suffice? standalone and war distribution: both contain a pre-build wookieJavaConnector-0.1.0-SNAPSHOT.jar and wookieW3CParser-0.1.0-SNAPSHOT.jar neither of these artifacts contain the required NOTICE and LICENSE files how is version management for these two artifacts "managed" and related to the whole of the Wookie release although this is not a maven based release, -SNAPSHOT versioned artifacts are considered unreliable by definition the war artifact within the war distribution itself also should have the required NOTICE and LICENSE files all: An Incubator disclaimer is required to be provided in every distribution, in the README or RELEASE_NOTES DISCLAIMER Preferably also a RELEASE_NOTES is provided, detailing the version of the release, issues fixed and possible known issues pertaining this release
          Hide
          Scott Wilson added a comment -

          RC2 WAR version

          Server OS: Mac OS X 10.6.7
          Client OS: Mac OS X 10.6.7
          Server and Client separate machines?: No
          Servlet Engine: Tomcat 6.0.20
          Java version: 1.6
          Browser: Safari, Opera 11
          Browser version:
          Tested with Shindig integration?: Yes, 1.1b5

          Deployed WAR successfully. Shindig integration worked with 1.1b5 but couldn't work with 2.0.0 - adding the Gadget resulted in:

          java.lang.Exception: Invalid gadget - Shindig error
          at org.apache.wookie.util.gadgets.GadgetAdapter.<init>(GadgetAdapter.java:63)
          at org.apache.wookie.util.gadgets.GadgetUtils.getWidget(GadgetUtils.java:171)
          at org.apache.wookie.util.gadgets.GadgetUtils.createWidget(GadgetUtils.java:91)
          at org.apache.wookie.util.gadgets.GadgetUtils.createWidget(GadgetUtils.java:80)
          at org.apache.wookie.WidgetAdminServlet.registerOperation(WidgetAdminServlet.java:435)
          at org.apache.wookie.WidgetAdminServlet.doGet(WidgetAdminServlet.java:276)
          at org.apache.wookie.WidgetAdminServlet.doPost(WidgetAdminServlet.java:310)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
          at org.apache.wookie.server.CharSetFilter.doFilter(CharSetFilter.java:34)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
          at org.apache.wookie.server.MainFilter.doFilter(MainFilter.java:63)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
          at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
          at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
          at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
          at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
          at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
          at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
          at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
          at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
          at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
          at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
          at java.lang.Thread.run(Thread.java:680)

          This is due to some changes in the metadata request. Note this was fixed in trunk - we can either backport the fix (its trivial - change "wookie" to "default" when setting CONTAINER_ID in GadgetUtils), or add an entry in the release notes for it.

          RC2 Standalone Version

          Server OS: Mac OS X 10.6.7
          Client OS: Mac OS X 10.6.7
          Server and Client separate machines?: No
          Servlet Engine:
          Java version: 1.6
          Browser: Safari, Opera 11
          Browser version:
          Tested with Shindig integration?: No

          Still have to chmod +x startup.sh to run, otherwise no problems

          Show
          Scott Wilson added a comment - RC2 WAR version Server OS: Mac OS X 10.6.7 Client OS: Mac OS X 10.6.7 Server and Client separate machines?: No Servlet Engine: Tomcat 6.0.20 Java version: 1.6 Browser: Safari, Opera 11 Browser version: Tested with Shindig integration?: Yes, 1.1b5 Deployed WAR successfully. Shindig integration worked with 1.1b5 but couldn't work with 2.0.0 - adding the Gadget resulted in: java.lang.Exception: Invalid gadget - Shindig error at org.apache.wookie.util.gadgets.GadgetAdapter.<init>(GadgetAdapter.java:63) at org.apache.wookie.util.gadgets.GadgetUtils.getWidget(GadgetUtils.java:171) at org.apache.wookie.util.gadgets.GadgetUtils.createWidget(GadgetUtils.java:91) at org.apache.wookie.util.gadgets.GadgetUtils.createWidget(GadgetUtils.java:80) at org.apache.wookie.WidgetAdminServlet.registerOperation(WidgetAdminServlet.java:435) at org.apache.wookie.WidgetAdminServlet.doGet(WidgetAdminServlet.java:276) at org.apache.wookie.WidgetAdminServlet.doPost(WidgetAdminServlet.java:310) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.wookie.server.CharSetFilter.doFilter(CharSetFilter.java:34) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.wookie.server.MainFilter.doFilter(MainFilter.java:63) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454) at java.lang.Thread.run(Thread.java:680) This is due to some changes in the metadata request. Note this was fixed in trunk - we can either backport the fix (its trivial - change "wookie" to "default" when setting CONTAINER_ID in GadgetUtils), or add an entry in the release notes for it. RC2 Standalone Version Server OS: Mac OS X 10.6.7 Client OS: Mac OS X 10.6.7 Server and Client separate machines?: No Servlet Engine: Java version: 1.6 Browser: Safari, Opera 11 Browser version: Tested with Shindig integration?: No Still have to chmod +x startup.sh to run, otherwise no problems
          Hide
          Paul Sharples added a comment -

          Marking as closed - 0.9.0 issues resolved

          Show
          Paul Sharples added a comment - Marking as closed - 0.9.0 issues resolved

            People

            • Assignee:
              Paul Sharples
              Reporter:
              Scott Wilson
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development