*Pushpalanka Jayawardhana *Software Engineer WSO2 Lanka (pvt) Ltd +94 779716248 [image: Facebook] <http://www.facebook.com/pushpalanka> [image: LinkedIn]<http://www.linkedin.com/profile/view?id=75175642&trk=tab_pro> [image: Twitter] <http://twitter.com/Pushpalanka> [image: SlideShare]<http://www.slideshare.net/Pushpalanka> [image: Blogger] <http://pushpalankajaya.blogspot.com/>
On Fri, Apr 26, 2013 at 6:06 PM, Matthias Niederhausen (JIRA) < [email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/WOOKIE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642789#comment-13642789] > > Matthias Niederhausen commented on WOOKIE-407: > ---------------------------------------------- > > Thank you for the effort. But still, the problem is not resolved. > I can mostly only reproduce it when re-deploying with a certified widget. > My refined test case is: > > 1) deploy widget without certificate -> works > 2) re-deploy signed widget -> works > 3) re-deploy signed widget -> error > 4) deploy widget without certificate -> error > > These steps now consistently lead to an error. It seems like the > certificate file being in the unpacked folder (thus only after step 2 an > error occurs) is the problem? > Thanks for the detailed feedback Matthias. > > > Can not redeploy signed widgets > > ------------------------------- > > > > Key: WOOKIE-407 > > URL: https://issues.apache.org/jira/browse/WOOKIE-407 > > Project: Wookie > > Issue Type: Bug > > Affects Versions: 0.14.0 > > Environment: Windows 7 x64 > > Reporter: Matthias Niederhausen > > Fix For: 0.15.0 > > > > Attachments: Google Map.wgt, proper_file_release3.patch > > > > > > I have no clue why, but when I try to redeploy a signed widget, I get an > error that the widget has an invalid manifest. > > Use case: > > 1. deploy a .wgt file by dropping it into /deploy folder > > 2. deploy the same .wgt file [works] > > 3. deploy the same .wgt file, but with signature file > author-signature.xml [works] > > 4. deploy the same .wgt file as in step 3 [error] > > 11:23:28,327 ERROR ContextListener:214 - Google Map.wgt:Hot deploy > error: widget has invalid manifest - java.io.IOException: Unable to delete > file: C:\Users\mtni\workspace\Apache > Rave\rave-portal\target\tomcat6x\webapps\wookie\deploy\mms.t-systems.de > \widgets\eventfinder\script\eventfinder.js > > org.apache.wookie.w3c.exceptions.BadManifestException: > java.io.IOException: Unable to delete file: C:\Users\mtni\workspace\Apache > Rave\rave-portal\target\tomcat6x\webapps\wookie\deploy\mms.t-systems.de > \widgets\eventfinder\script\eventfinder.js > > at > org.apache.wookie.w3c.W3CWidgetFactory.processWidgetPackage(W3CWidgetFactory.java:334) > > at > org.apache.wookie.w3c.W3CWidgetFactory.parse(W3CWidgetFactory.java:177) > > at > org.apache.wookie.w3c.W3CWidgetFactory.parse(W3CWidgetFactory.java:162) > > at > org.apache.wookie.server.ContextListener$1$1.fileModified(ContextListener.java:190) > > at org.apache.wookie.util.WgtWatcher.check(WgtWatcher.java:95) > > at > org.apache.wookie.server.ContextListener$1.run(ContextListener.java:230) > > Caused by: java.io.IOException: Unable to delete file: > C:\Users\mtni\workspace\Apache > Rave\rave-portal\target\tomcat6x\webapps\wookie\deploy\mms.t-systems.de > \widgets\eventfinder\script\eventfinder.js > > at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1919) > > at > org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1399) > > at > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1331) > > at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1910) > > at > org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1399) > > at > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1331) > > at > org.apache.wookie.w3c.util.WidgetPackageUtils.unpackZip(WidgetPackageUtils.java:304) > > at > org.apache.wookie.w3c.W3CWidgetFactory.processWidgetPackage(W3CWidgetFactory.java:298) > > ... 5 more > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira >
