On 17 Apr 2012, at 06:34, Pushpalanka Jayawardhana wrote: > Hi Scott, > > I went through this > documentation<http://incubator.apache.org/wookie/docs/developer/parser.html> > on > using parser as a standalone jar. So it seemed to me that it will be a > better to just introduce a variable in 'W3CWidgetFactory' class rather than > going for a configuration file to point to the trusted key store, which > will guide to tight cohesion, which is beneficial.
Yes, that should make it more portable. > > In documentation aspects, I could identify that following points need > updates after project completion. > > - Wookie web site - Documentation:Server administration, Development: > W3C widget parser Yes. > - Wookie docs - widget_dev_guide. Thats a legacy doc so I wouldn't worry about updating that. Instead you could add a page on the site under "docs" e.g. "Using Digital Signatures". > > Also I'm glad to mention that, I will be able to work about 40hours per > week on the project. > - 5 hours in week days and 8 hours each in Saturday and Sunday. At that rate I think you'd finish the project very quickly :) > > On Thu, Apr 12, 2012 at 11:25 PM, Scott Wilson < > [email protected]> wrote: > >> On 12 Apr 2012, at 17:46, Pushpalanka Jayawardhana wrote: >> >>> Hi Scott, >>> >>> Thought it will be better to keep this thread updated on the progress I >>> made. >> >> >> Great! Thanks for the updates - it makes sense to keep the thread going. >> >>> >>> Meanwhile I looked into the widget code and possible implementation of >>> verifying function. I placed a sample signature file inside a .wgt and >>> tried to access it inside Wookie. Inside W3CWidgetFactory class of parser >>> could get into the signature file with >>> *unzippedWidgetDirectory.getCanonicalPath() + File.separator + >>> "signature.xml".* Identification can be done,considering the naming >>> conventions in the spec for authors and distributors, when more >> signatures >>> are present. >>> * >>> * >>> As next step, I hope to look at how the decision of verification function >>> can take effect in deploying the .wgt at Wookie and taken into >>> other higher levels. Working on this is becoming more interesting now. >> >> Yes, as W3CWidgetFactory is the front API for the parser lib - for both >> the Wookie server and other W3C implementations reusing it - so it needs to >> have easy to understand/well documented method signatures so poses more of >> a design challenge. >> >>> >>> -- >>> Pushpalanka Jayawardhana | Undergraduate | Computer Science and >> Engineering >>> University of Moratuwa >>> >>> +94779716248 | http://pushpalankajaya.blogspot.com >>> >>> Twitter: http://twitter.com/Pushpalanka | Slideshare: >>> http://www.slideshare.net/Pushpalanka >> >> > > Thank you and Best Regards, > -- > Pushpalanka Jayawardhana | Undergraduate | Computer Science and Engineering > University of Moratuwa > > +94779716248 | http://pushpalankajaya.blogspot.com > > Twitter: http://twitter.com/Pushpalanka | Slideshare: > http://www.slideshare.net/Pushpalanka
