incubator-wookie-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WOOKIE-181) Test Release
Date Sun, 03 Apr 2011 19:34:05 GMT

     [ https://issues.apache.org/jira/browse/WOOKIE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ate Douma updated WOOKIE-181:
-----------------------------

    Attachment: rat.log

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
  

> Test Release
> ------------
>
>                 Key: WOOKIE-181
>                 URL: https://issues.apache.org/jira/browse/WOOKIE-181
>             Project: Wookie
>          Issue Type: Task
>    Affects Versions: 0.9.0
>            Reporter: Scott Wilson
>             Fix For: 0.9.0
>
>         Attachments: rat.log
>
>
> 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?:

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message