You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Scott Wilson (JIRA)" <ji...@apache.org> on 2011/02/11 13:10:01 UTC
[jira] Created: (WOOKIE-181) Test 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
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
[jira] Updated: (WOOKIE-181) Test Release
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Wilson updated WOOKIE-181:
--------------------------------
Fix Version/s: 0.9.0
> 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
>
>
> 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
[jira] Commented: (WOOKIE-181) Test Release
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993467#comment-12993467 ]
Scott Wilson commented on WOOKIE-181:
-------------------------------------
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.
> 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
>
> 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
Re: [jira] [Updated] (WOOKIE-181) Test Release
Posted by Scott Wilson <sc...@gmail.com>.
On 4 Apr 2011, at 09:47, Scott Wilson wrote:
> On 4 Apr 2011, at 08:21, Ate Douma wrote:
>
>> On 04/04/2011 01:12 AM, Ross Gardler wrote:
>>> Replying to list so we can decide whether we want to fix or open a new issues
>>> for each item (thanks for being more thorough than me Ate - seems I was lax
>>> because I'm hacking on Wookie).
>>>
>>> On 03/04/2011 20:34, Ate Douma (JIRA) wrote:
>>>> * 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)
>>>
>>> I'm not sure about this one.
>> Do you mean you nor anyone else has seen this? Its been consistently wrong for me.
>
> I can confirm this; the issue is that i18n text is being returned in styled rather than encoded format. This has been fixed in trunk.
Or rather, I fixed it on Friday but haven't checked it in yet! I'll create a new issue and check in the fix against it.
> NB I've started work in trunk on properly passing the full suite of W3C Widget Interface tests including i18n; the API Test widget provides a basic sanity check.
>
Re: [jira] [Updated] (WOOKIE-181) Test Release
Posted by Scott Wilson <sc...@gmail.com>.
On 4 Apr 2011, at 08:21, Ate Douma wrote:
> On 04/04/2011 01:12 AM, Ross Gardler wrote:
>> Replying to list so we can decide whether we want to fix or open a new issues
>> for each item (thanks for being more thorough than me Ate - seems I was lax
>> because I'm hacking on Wookie).
>>
>> On 03/04/2011 20:34, Ate Douma (JIRA) wrote:
>>> * 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)
>>
>> I'm not sure about this one.
> Do you mean you nor anyone else has seen this? Its been consistently wrong for me.
I can confirm this; the issue is that i18n text is being returned in styled rather than encoded format. This has been fixed in trunk.
NB I've started work in trunk on properly passing the full suite of W3C Widget Interface tests including i18n; the API Test widget provides a basic sanity check.
Re: [jira] [Updated] (WOOKIE-181) Test Release
Posted by Ate Douma <at...@douma.nu>.
On 04/04/2011 01:12 AM, Ross Gardler wrote:
> Replying to list so we can decide whether we want to fix or open a new issues
> for each item (thanks for being more thorough than me Ate - seems I was lax
> because I'm hacking on Wookie).
>
> On 03/04/2011 20:34, Ate Douma (JIRA) wrote:
>> * 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)
>
> I'm not sure about this one.
Do you mean you nor anyone else has seen this? Its been consistently wrong for me.
>
>> - 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
>>
>
> I beleive this is a known issue: https://issues.apache.org/jira/browse/WOOKIE-145
>
> This is an intermittent problem introduced with the JPA conversion. It has been
> resolved in trunk. The fix is currently turned off by default pending code
> review and thorough testing under load.
>
> Since the team seem to want to continue with the 0.9 release and follow quickly
> with a 0.9.1 release I'd suggest we can probably leave this in the release. It
> only affects widgets that setPreferences, and even then only intermittently.
Seems not so intermittently to me, but if its a known issue and regarded as less
critical for *this* release, I'm fine if it is only marked as a known issue.
>
>> - stopping standalone and run ./startup.sh again: all previously deployed
>> widgets are "gone" except the "unsupported widget" widget
>> -> standalone is not repeatable runnable
>
> That sounds like we have initDB set to true (which is the default in src). We
> probably want this to be false in the release. I've opened an issue for this one
> and added a test to our test script. Good catch Ate.
>
> https://issues.apache.org/jira/browse/WOOKIE-196
>
> http://wookie.staging.apache.org/wookie/docs/developer/releaseTesting.html
>
> (committer only, CMS is not yet live site)
>
>> * 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
>
> Added as https://issues.apache.org/jira/browse/WOOKIE-197
>
>
>> - 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
>
> I've not test the WAR version, but we certainly don't want people to downlaod
> mySQL when there is no need to (or have I misunderstood something?)
The packaged README only specifically describes installing on Tomcat with MySQL,
and the provided Tomcat context descriptor (wookie.xml) also is preconfigured to
use the MySQL JDBC driver.
>
>> - 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
>
> Can someone look into this?
AFAIK this is caused by the same JPA error (WOOKIE-145) but on Tomcat with MySQL
it displays a different error dialog to the user.
>
>> - 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
>
> Hmmm... that doesn't sound good.
No it doesn't.
Might be something with further hardened request/session (cookie?) protections
by Tomcat 7x, or possibly a Tomcat 7x specific problem.
>
>> 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
>
> Sounds like a badly configured build file or something strange on the build
> machine.
As these dist folders also contain maven poms, which I could not find in the
svn, I suspect these might be an "artifact" from the build machine?
>
> Added as https://issues.apache.org/jira/browse/WOOKIE-199
>
>> - 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've not done a licence check yet, other than to look at RAT
>
>> - 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
>
> RAT is already configured and run regularly -
> http://ci.apache.org/projects/wookie/rat-output.html Cheking this report is
> already part of the documented release process - see
> http://wookie.staging.apache.org/wookie/docs/developer/release.html
>
> It would make sense to incorporate in the build, but the above page should have
> caught any errors before the RC was built.
Ah, I wasn't aware of that yet. Thanks for pointing that out.
Note though the above report only runs on trunk, not this 0.9.x branch.
>
>> - NOTICE file seems pretty good maintained although I haven't yet
>> checked/validated all and every additional external license usage
>
> I also need to check this.
>
>> - 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?
>
> Added to Wookie-199 9above)
>
>> - 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
>
> Good spot, technically these are separate releases and need to be handled
> appropriately. SNAPSHOT in this context is the same as in Maven world (IVY uses
> Maven repos).
>
> Added as https://issues.apache.org/jira/browse/WOOKIE-202
>
>> - the war artifact within the war distribution itself also should have the
>> required NOTICE and LICENSE files
>
> Added to https://issues.apache.org/jira/browse/WOOKIE-195
>
>> - all:
>> - An Incubator disclaimer is required to be provided in every distribution, in
>> the README or RELEASE_NOTES DISCLAIMER
>
> Already noted by Luciano in https://issues.apache.org/jira/browse/WOOKIE-195
>
>> - Preferably also a RELEASE_NOTES is provided, detailing the version of the
>> release, issues fixed and possible known issues pertaining this release
>
> Yes, this is in the release process, not sure why that's missing.
>
> Added to https://issues.apache.org/jira/browse/WOOKIE-195
>
>
> So, in summary there is quite a bit to do on this release before we have checked
> the legal stuff.
>
> Do you still want to do this one and follow quickly with a 0.9.1 or rebuild from
> trunk for 0.9.0?
>
> The disadvantage of doing a 0.9.0 from trunk is that we will need to wait for
> people to find time to test again, if we fix these issues and backport to the
> 0.9.0 branch then testing will be quicker and thus the release will be out sooner.
I'd be in favor of seeing the 0.9.x (!) branch fixed, through backporting.
If that produces a 0.9.0 or 0.9.1 version doesn't really matter, does it?
However, if too many of these issues above and possibly others cause too many
changes needed also on trunk, there will be a cut-off moment where simply
branching trunk again might become more efficient.
Ate
>
> Ross
>
>>
>>
>>> 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
>
Re: [jira] [Updated] (WOOKIE-181) Test Release
Posted by Ross Gardler <rg...@apache.org>.
Replying to list so we can decide whether we want to fix or open a new
issues for each item (thanks for being more thorough than me Ate - seems
I was lax because I'm hacking on Wookie).
On 03/04/2011 20:34, Ate Douma (JIRA) wrote:
> * 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)
I'm not sure about this one.
> - 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
I beleive this is a known issue:
https://issues.apache.org/jira/browse/WOOKIE-145
This is an intermittent problem introduced with the JPA conversion. It
has been resolved in trunk. The fix is currently turned off by default
pending code review and thorough testing under load.
Since the team seem to want to continue with the 0.9 release and follow
quickly with a 0.9.1 release I'd suggest we can probably leave this in
the release. It only affects widgets that setPreferences, and even then
only intermittently.
> - stopping standalone and run ./startup.sh again: all previously deployed widgets are "gone" except the "unsupported widget" widget
> -> standalone is not repeatable runnable
That sounds like we have initDB set to true (which is the default in
src). We probably want this to be false in the release. I've opened an
issue for this one and added a test to our test script. Good catch Ate.
https://issues.apache.org/jira/browse/WOOKIE-196
http://wookie.staging.apache.org/wookie/docs/developer/releaseTesting.html
(committer only, CMS is not yet live site)
> * 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
Added as https://issues.apache.org/jira/browse/WOOKIE-197
> - 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
I've not test the WAR version, but we certainly don't want people to
downlaod mySQL when there is no need to (or have I misunderstood something?)
> - 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
Can someone look into this?
> - 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
Hmmm... that doesn't sound good.
> 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
Sounds like a badly configured build file or something strange on the
build machine.
Added as https://issues.apache.org/jira/browse/WOOKIE-199
> - 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've not done a licence check yet, other than to look at RAT
> - 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
RAT is already configured and run regularly -
http://ci.apache.org/projects/wookie/rat-output.html Cheking this report
is already part of the documented release process - see
http://wookie.staging.apache.org/wookie/docs/developer/release.html
It would make sense to incorporate in the build, but the above page
should have caught any errors before the RC was built.
> - NOTICE file seems pretty good maintained although I haven't yet checked/validated all and every additional external license usage
I also need to check this.
> - 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?
Added to Wookie-199 9above)
> - 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
Good spot, technically these are separate releases and need to be
handled appropriately. SNAPSHOT in this context is the same as in Maven
world (IVY uses Maven repos).
Added as https://issues.apache.org/jira/browse/WOOKIE-202
> - the war artifact within the war distribution itself also should have the required NOTICE and LICENSE files
Added to https://issues.apache.org/jira/browse/WOOKIE-195
> - all:
> - An Incubator disclaimer is required to be provided in every distribution, in the README or RELEASE_NOTES DISCLAIMER
Already noted by Luciano in https://issues.apache.org/jira/browse/WOOKIE-195
> - Preferably also a RELEASE_NOTES is provided, detailing the version of the release, issues fixed and possible known issues pertaining this release
Yes, this is in the release process, not sure why that's missing.
Added to https://issues.apache.org/jira/browse/WOOKIE-195
So, in summary there is quite a bit to do on this release before we have
checked the legal stuff.
Do you still want to do this one and follow quickly with a 0.9.1 or
rebuild from trunk for 0.9.0?
The disadvantage of doing a 0.9.0 from trunk is that we will need to
wait for people to find time to test again, if we fix these issues and
backport to the 0.9.0 branch then testing will be quicker and thus the
release will be out sooner.
Ross
>
>
>> 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
[jira] [Updated] (WOOKIE-181) Test Release
Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (WOOKIE-181) Test Release
Posted by "David Sherlock (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995227#comment-12995227 ]
David Sherlock commented on WOOKIE-181:
---------------------------------------
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
> 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
>
>
> 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
[jira] Commented: (WOOKIE-181) Test Release
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997215#comment-12997215 ]
Scott Wilson commented on WOOKIE-181:
-------------------------------------
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.
> 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
>
>
> 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
[jira] [Commented] (WOOKIE-181) Test Release
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045318#comment-13045318 ]
Scott Wilson commented on WOOKIE-181:
-------------------------------------
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
> 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
> Assignee: Paul Sharples
> 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
[jira] [Commented] (WOOKIE-181) Test Release
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014829#comment-13014829 ]
Ross Gardler commented on WOOKIE-181:
-------------------------------------
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
> 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
>
>
> 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
[jira] [Commented] (WOOKIE-181) Test Release
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014835#comment-13014835 ]
Ross Gardler commented on WOOKIE-181:
-------------------------------------
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)
> 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
>
>
> 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
[jira] [Commented] (WOOKIE-181) Test Release
Posted by "Paul Sharples (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010740#comment-13010740 ]
Paul Sharples commented on WOOKIE-181:
--------------------------------------
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.
> 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
>
>
> 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
[jira] Commented: (WOOKIE-181) Test Release
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997218#comment-12997218 ]
Scott Wilson commented on WOOKIE-181:
-------------------------------------
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.
> 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
>
>
> 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