Yeah, not unexpected, it's fine to look at this one post-1.0. Just as I figured those issues out and got my service working and successfully posted to mooshup it began to fail again and I spent a long time fiddling around with stubs and other stuff before realizing I had a pre-existing bug in my Javascript due to time zone de-synchronization between the nationalgeographic site and the mashup site. So the service was liable to fail during a small window each day ;-). Easy fix, but took me a while to stop suspecting the Mashup Server/Mooshup.com combination which actually was working fine. In the process I verified some complex behaviors like migrating stubs work fine (thanks to the new localhost parameter.)
Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Tyrell Perera (JIRA) > Sent: Saturday, January 26, 2008 6:18 PM > To: [email protected] > Subject: [mashup-dev] [jira] Updated: (MASHUP-607) Editing a service > with < in the documentation XML fails > > [ http://wso2.org/jira/browse/MASHUP-607?page=all ] > > Tyrell Perera updated MASHUP-607: > --------------------------------- > > Fix Version/s: 1.1 > (was: 1.0) > > > Editing a service with < in the documentation XML fails > > ---------------------------------------------------------- > > > > Key: MASHUP-607 > > URL: http://wso2.org/jira/browse/MASHUP-607 > > Project: WSO2 Mashup Server > > Issue Type: Bug > > Reporter: Jonathan Marsh > > Assigned To: Tyrell Perera > > Priority: Minor > > Fix For: 1.1 > > > > > > Had some issues deploying the nationalgeographic service. First I > deployed the service through the file system, which failed because I > hadn't deployed a local stub which the service depends on. Then I > deployed the stub. I went to the ui for the service to reload it. > Since the service was faulty, the only option was to edit the service. > > Suggestion: Can we have a "redeploy" link as well on this page, for > situations such as this where it makes sense to redeploy the service > without editing the main file? > > Then when I opened up the service to make a trivial edit so I could > save it and redeploy it, I had another failure on a line similar to > this one: > > op.documentation=<div><result></div>; > > When saved by the editor this appeared on disk as <div><result></div> > which is malformed XML. To workaround this I would have had to go > directly to the file system, or in my case I just changed the content > to <div>[result]</div>. > > Bug: should be able to save <. > > This doesn't appear critical to fix prior to the 1.0 release if the > fix is difficult or potentially destabilizing. This could be > documented under known issues and authors can avoid it fairly easily. > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://wso2.org/jira/secure/Administrators.jspa > - > For more information on JIRA, see: > http://www.atlassian.com/software/jira > > > > _______________________________________________ > Mashup-dev mailing list > [email protected] > http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev _______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
