From jits at cs.man.ac.uk Wed Oct 1 08:03:05 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Wed, 01 Oct 2008 13:03:05 +0100 Subject: [BioCatalogue-developers] soap_services submission In-Reply-To: <48DA662C.9010802@cs.man.ac.uk> References: <48CFBF1A.4000704@ebi.ac.uk> <48CFD467.5090205@cs.man.ac.uk> <48D0FCBF.7040309@ebi.ac.uk> <48D0FF3F.901@cs.man.ac.uk> <48D79277.1060307@ebi.ac.uk> <48D7A4F1.30308@cs.man.ac.uk> <48D7AACF.8050407@ebi.ac.uk> <48D7ACE4.2030909@cs.man.ac.uk> <48D7B34D.50005@ebi.ac.uk> <48D7B5AE.90603@ebi.ac.uk> <48DA06AA.2010107@ebi.ac.uk> <48DA1189.2070501@cs.man.ac.uk> <48DA14AB.9010509@ebi.ac.uk> <48DA1563.80403@cs.man.ac.uk> <48DA1646.4030403@ebi.ac.uk> <48DA16E3.8090403@cs.man.ac.uk> <48DA17D1.5030206@ebi.ac.uk> <48DA1B21.1060805@ebi.ac.uk> <48DA1F97.6090000@ebi.ac.uk> <48DA202F.8020306@cs.man.ac.uk> <48DA57F6.6050902@ebi.ac.uk> <48DA5929.4050209@cs.man.ac.uk> <48DA6124.8070002@ebi.ac.uk> <48DA662C.9010802@cs.man.ac.uk> Message-ID: <48E366F9.3010701@cs.man.ac.uk> Hi Thomas, Found out more about setting routes that only respond to particular HTTP verbs... http://guides.rails.info/routing/routing_outside_in.html#_route_conditions Cheers, Jits Jiten Bhagat wrote: > No, you're absolutely right. Maybe I'm over thinking this particular > problem :-) > > Jits > > > Thomas Laurent wrote: >> I don't follow you... >> If a search engine hit the link <%= link_to 'Logout', logout_url, >> :method => :delete -%> , it'll do like with any other "Destroy" link, >> e.g. not follow it as it's in fact a POST. >> >> By "people hitting the link directly", do you mean typing the URL >> directly ? If this is the case, I don't see much of a problem, it'll >> send a GET request because that's the only thing a browser can do >> from an URL typed in, but that'll still log them out >> >> I think I'm not understanding what you mean very well... >> >> Thomas >> >> Jiten Bhagat wrote: >>> Hi Thomas, >>> >>> Comments below... >>> >>> Thomas Laurent wrote: >>>> I don't know, that's an interesting question... >>>> >>>> I thought that the HTTP verb was defined in the link itself, as >>>> the "logout" link should really be coded like that: >>>> <%= link_to 'Logout', logout_url, :method => :delete -%> >>> >>> Yes, that can be done. My concern is people hitting the link >>> directly or possibly a search engine. Though it doesn't sound like >>> much harm can be done. >>> >>>> >>>> I didn't find a way to specify the link to use HTTP DELETE directly >>>> in the route, but if there was, it'd be great and I'd gladly add it >>>> to the route. >>> >>> Ok, I'll check and see. I'm sure I read somewhere about this (since >>> Resourceful Routes do it, and they just translate to named routes at >>> 'runtime' anyways). >>> >>> Cheers, >>> Jits >>> >>>> >>>> Thomas >>>> >>>> Jiten Bhagat wrote: >>>>> Hi Thomas, >>>>> >>>>> Just something I've noticed in routes... >>>>> >>>>> map.logout '/logout', :controller => 'sessions', :action => 'destroy' >>>>> >>>>> I like that idea! My only concern is that "http://.../logout" will >>>>> make a GET request instead of a DELETE as it should. Is this a >>>>> valid concern? >>>>> >>>>> Jits >>>>> >>>>> >>>>> >>>>> Thomas Laurent wrote: >>>>>> I didn't link up the pages at all for the moment, that'll be done >>>>>> now that I can work on the layout/look and feel. >>>>>> >>>>>> In the meantime, /register would lead you to the "new user" page. >>>>>> >>>>>> Cheers, >>>>>> Thomas >>>>>> >>>>>> >>>>>> Eric Nzuobontane wrote: >>>>>>> Feature request ... Thomas could you add a link to the new user >>>>>>> from the login page? >>>>>>> Thanks! >>>>>>> >>>>>>> Eric >>>>>>> >>>>>>> >>>>>>> Thomas Laurent wrote: >>>>>>>> Sorry again, I'm not used to use plugins, so I didn't see I had >>>>>>>> something to check in from inside the "vendor" directory. I >>>>>>>> just noticed it when checking out the changes from Eric, as he >>>>>>>> had also some new plugins... >>>>>>>> >>>>>>>> >>>>>>>> Jiten Bhagat wrote: >>>>>>>>> Great, thanks, and no worries... we'll no doubt run into many >>>>>>>>> times when we forget small pieces, especially when we use >>>>>>>>> Ctrl-C and Ctrl-V a lot ;-) >>>>>>>>> >>>>>>>>> Jits >>>>>>>>> >>>>>>>>> >>>>>>>>> Thomas Laurent wrote: >>>>>>>>>> Jits, I've just added the files 5-10 minutes ago when I >>>>>>>>>> realised I forgot to check them in. Sorry about that. >>>>>>>>>> >>>>>>>>>> Thomas >>>>>>>>>> >>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>> Was just drafting an email about this :-) >>>>>>>>>>> >>>>>>>>>>> Have been testing it but I got an error that >>>>>>>>>>> "validates_email_veracity_of" couldn't be found. This was >>>>>>>>>>> from the User model and requires a plugin to work... I'll >>>>>>>>>>> add this plugin to make it work :-) >>>>>>>>>>> >>>>>>>>>>> Jits >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thomas Laurent wrote: >>>>>>>>>>>> Jits, when are you planning to add the css stuff ? >>>>>>>>>>>> >>>>>>>>>>>> Thomas >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>>>> Sounds good Eric. Will check out the model code in a bit. >>>>>>>>>>>>> >>>>>>>>>>>>> Cheers, >>>>>>>>>>>>> Jits >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Eric Nzuobontane wrote: >>>>>>>>>>>>>> Hi Guys, >>>>>>>>>>>>>> I have just committed coded to submit a soap_service. I >>>>>>>>>>>>>> do not expect it to break anything Thomas did but you >>>>>>>>>>>>>> never know. It will be wise for Thomas especially to >>>>>>>>>>>>>> check that everything he did is still fine with my >>>>>>>>>>>>>> updates. I guess we should start writing tests!!! >>>>>>>>>>>>>> >>>>>>>>>>>>>> That said, what the code does is take a wsdl file, >>>>>>>>>>>>>> extract the relevant information on operations and inputs >>>>>>>>>>>>>> and outputs with their types and store these >>>>>>>>>>>>>> transactionally in the database. I have also added some >>>>>>>>>>>>>> migrations (adding some fields to the input/output tables). >>>>>>>>>>>>>> >>>>>>>>>>>>>> The work on soaplab servers is ongoing, but I decided to >>>>>>>>>>>>>> check it in as I will be in Manchester during the next >>>>>>>>>>>>>> two days and would want to bring it to a usable standard... >>>>>>>>>>>>>> >>>>>>>>>>>>>> Jits, could you please look at the soap_service model in >>>>>>>>>>>>>> particular and get back to me? You were interested in >>>>>>>>>>>>>> knowing how I did it from the last chat..... >>>>>>>>>>>>>> >>>>>>>>>>>>>> cheers, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Eric >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>> _______________________________________________ >>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>> _______________________________________________ >>>>>>>> BioCatalogue-developers mailing list >>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>> >>>>>> _______________________________________________ >>>>>> BioCatalogue-developers mailing list >>>>>> BioCatalogue-developers at rubyforge.org >>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From jits at cs.man.ac.uk Wed Oct 1 08:07:02 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Wed, 01 Oct 2008 13:07:02 +0100 Subject: [BioCatalogue-developers] soap_services submission In-Reply-To: <48E366F9.3010701@cs.man.ac.uk> References: <48CFBF1A.4000704@ebi.ac.uk> <48CFD467.5090205@cs.man.ac.uk> <48D0FCBF.7040309@ebi.ac.uk> <48D0FF3F.901@cs.man.ac.uk> <48D79277.1060307@ebi.ac.uk> <48D7A4F1.30308@cs.man.ac.uk> <48D7AACF.8050407@ebi.ac.uk> <48D7ACE4.2030909@cs.man.ac.uk> <48D7B34D.50005@ebi.ac.uk> <48D7B5AE.90603@ebi.ac.uk> <48DA06AA.2010107@ebi.ac.uk> <48DA1189.2070501@cs.man.ac.uk> <48DA14AB.9010509@ebi.ac.uk> <48DA1563.80403@cs.man.ac.uk> <48DA1646.4030403@ebi.ac.uk> <48DA16E3.8090403@cs.man.ac.uk> <48DA17D1.5030206@ebi.ac.uk> <48DA1B21.1060805@ebi.ac.uk> <48DA1F97.6090000@ebi.ac.uk> <48DA202F.8020306@cs.man.ac.uk> <48DA57F6.6050902@ebi.ac.uk> <48DA5929.4050209@cs.man.ac.uk> <48DA6124.8070002@ebi.ac.uk> <48DA662C.9010802@cs.man.ac.uk> <48E366F9.3010701@cs.man.ac.uk> Message-ID: <48E367E6.2020803@cs.man.ac.uk> Also, the logout thing I brought up earlier is an example of a potential cross-site request forgery (CSRF) attack, albeit not a severe one (and not one we need to worry about too much), but important enough for us to be aware of atleast. More info: http://www.theregister.co.uk/2008/09/30/web_bug_bites_sites/ Excerpt: "Cross-site request forgery (CSRF) vulnerabilities occur when a website carries out an action without first confirming it was requested by the authenticated user. Miscreants can exploit this shortcoming by including code on an attack site that causes the user's browser to send commands to a site such as ING.com. ING.com then carries out the command under the mistaken notion that because it was requested by the browser, it was invoked by the user." Jits Jiten Bhagat wrote: > Hi Thomas, > > Found out more about setting routes that only respond to particular > HTTP verbs... > > http://guides.rails.info/routing/routing_outside_in.html#_route_conditions > > > Cheers, > Jits > > > Jiten Bhagat wrote: >> No, you're absolutely right. Maybe I'm over thinking this particular >> problem :-) >> >> Jits >> >> >> Thomas Laurent wrote: >>> I don't follow you... >>> If a search engine hit the link <%= link_to 'Logout', logout_url, >>> :method => :delete -%> , it'll do like with any other "Destroy" >>> link, e.g. not follow it as it's in fact a POST. >>> >>> By "people hitting the link directly", do you mean typing the URL >>> directly ? If this is the case, I don't see much of a problem, it'll >>> send a GET request because that's the only thing a browser can do >>> from an URL typed in, but that'll still log them out >>> >>> I think I'm not understanding what you mean very well... >>> >>> Thomas >>> >>> Jiten Bhagat wrote: >>>> Hi Thomas, >>>> >>>> Comments below... >>>> >>>> Thomas Laurent wrote: >>>>> I don't know, that's an interesting question... >>>>> >>>>> I thought that the HTTP verb was defined in the link itself, as >>>>> the "logout" link should really be coded like that: >>>>> <%= link_to 'Logout', logout_url, :method => :delete -%> >>>> >>>> Yes, that can be done. My concern is people hitting the link >>>> directly or possibly a search engine. Though it doesn't sound like >>>> much harm can be done. >>>> >>>>> >>>>> I didn't find a way to specify the link to use HTTP DELETE >>>>> directly in the route, but if there was, it'd be great and I'd >>>>> gladly add it to the route. >>>> >>>> Ok, I'll check and see. I'm sure I read somewhere about this (since >>>> Resourceful Routes do it, and they just translate to named routes >>>> at 'runtime' anyways). >>>> >>>> Cheers, >>>> Jits >>>> >>>>> >>>>> Thomas >>>>> >>>>> Jiten Bhagat wrote: >>>>>> Hi Thomas, >>>>>> >>>>>> Just something I've noticed in routes... >>>>>> >>>>>> map.logout '/logout', :controller => 'sessions', :action => >>>>>> 'destroy' >>>>>> >>>>>> I like that idea! My only concern is that "http://.../logout" >>>>>> will make a GET request instead of a DELETE as it should. Is this >>>>>> a valid concern? >>>>>> >>>>>> Jits >>>>>> >>>>>> >>>>>> >>>>>> Thomas Laurent wrote: >>>>>>> I didn't link up the pages at all for the moment, that'll be >>>>>>> done now that I can work on the layout/look and feel. >>>>>>> >>>>>>> In the meantime, /register would lead you to the "new user" page. >>>>>>> >>>>>>> Cheers, >>>>>>> Thomas >>>>>>> >>>>>>> >>>>>>> Eric Nzuobontane wrote: >>>>>>>> Feature request ... Thomas could you add a link to the new user >>>>>>>> from the login page? >>>>>>>> Thanks! >>>>>>>> >>>>>>>> Eric >>>>>>>> >>>>>>>> >>>>>>>> Thomas Laurent wrote: >>>>>>>>> Sorry again, I'm not used to use plugins, so I didn't see I >>>>>>>>> had something to check in from inside the "vendor" directory. >>>>>>>>> I just noticed it when checking out the changes from Eric, as >>>>>>>>> he had also some new plugins... >>>>>>>>> >>>>>>>>> >>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>> Great, thanks, and no worries... we'll no doubt run into many >>>>>>>>>> times when we forget small pieces, especially when we use >>>>>>>>>> Ctrl-C and Ctrl-V a lot ;-) >>>>>>>>>> >>>>>>>>>> Jits >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Thomas Laurent wrote: >>>>>>>>>>> Jits, I've just added the files 5-10 minutes ago when I >>>>>>>>>>> realised I forgot to check them in. Sorry about that. >>>>>>>>>>> >>>>>>>>>>> Thomas >>>>>>>>>>> >>>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>>> Was just drafting an email about this :-) >>>>>>>>>>>> >>>>>>>>>>>> Have been testing it but I got an error that >>>>>>>>>>>> "validates_email_veracity_of" couldn't be found. This was >>>>>>>>>>>> from the User model and requires a plugin to work... I'll >>>>>>>>>>>> add this plugin to make it work :-) >>>>>>>>>>>> >>>>>>>>>>>> Jits >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thomas Laurent wrote: >>>>>>>>>>>>> Jits, when are you planning to add the css stuff ? >>>>>>>>>>>>> >>>>>>>>>>>>> Thomas >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>>>>> Sounds good Eric. Will check out the model code in a bit. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>> Jits >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Eric Nzuobontane wrote: >>>>>>>>>>>>>>> Hi Guys, >>>>>>>>>>>>>>> I have just committed coded to submit a soap_service. I >>>>>>>>>>>>>>> do not expect it to break anything Thomas did but you >>>>>>>>>>>>>>> never know. It will be wise for Thomas especially to >>>>>>>>>>>>>>> check that everything he did is still fine with my >>>>>>>>>>>>>>> updates. I guess we should start writing tests!!! >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> That said, what the code does is take a wsdl file, >>>>>>>>>>>>>>> extract the relevant information on operations and >>>>>>>>>>>>>>> inputs and outputs with their types and store these >>>>>>>>>>>>>>> transactionally in the database. I have also added some >>>>>>>>>>>>>>> migrations (adding some fields to the input/output tables). >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The work on soaplab servers is ongoing, but I decided to >>>>>>>>>>>>>>> check it in as I will be in Manchester during the next >>>>>>>>>>>>>>> two days and would want to bring it to a usable standard... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Jits, could you please look at the soap_service model in >>>>>>>>>>>>>>> particular and get back to me? You were interested in >>>>>>>>>>>>>>> knowing how I did it from the last chat..... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> cheers, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Eric >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>> _______________________________________________ >>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> BioCatalogue-developers mailing list >>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>> _______________________________________________ >>>>> BioCatalogue-developers mailing list >>>>> BioCatalogue-developers at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From tlaurent at ebi.ac.uk Wed Oct 1 09:22:51 2008 From: tlaurent at ebi.ac.uk (Thomas Laurent) Date: Wed, 01 Oct 2008 14:22:51 +0100 Subject: [BioCatalogue-developers] soap_services submission In-Reply-To: <48E366F9.3010701@cs.man.ac.uk> References: <48CFBF1A.4000704@ebi.ac.uk> <48CFD467.5090205@cs.man.ac.uk> <48D0FCBF.7040309@ebi.ac.uk> <48D0FF3F.901@cs.man.ac.uk> <48D79277.1060307@ebi.ac.uk> <48D7A4F1.30308@cs.man.ac.uk> <48D7AACF.8050407@ebi.ac.uk> <48D7ACE4.2030909@cs.man.ac.uk> <48D7B34D.50005@ebi.ac.uk> <48D7B5AE.90603@ebi.ac.uk> <48DA06AA.2010107@ebi.ac.uk> <48DA1189.2070501@cs.man.ac.uk> <48DA14AB.9010509@ebi.ac.uk> <48DA1563.80403@cs.man.ac.uk> <48DA1646.4030403@ebi.ac.uk> <48DA16E3.8090403@cs.man.ac.uk> <48DA17D1.5030206@ebi.ac.uk> <48DA1B21.1060805@ebi.ac.uk> <48DA1F97.6090000@ebi.ac.uk> <48DA202F.8020306@cs.man.ac.uk> <48DA57F6.6050902@ebi.ac.uk> <48DA5929.4050209@cs.man.ac.uk> <48DA6124.8070002@ebi.ac.uk> <48DA662C.9010802@cs.man.ac.uk> <48E366F9.3010701@cs.man.ac.uk> Message-ID: <48E379AB.3030404@ebi.ac.uk> Hi Jits, I saw this one, but that's not setting the route to the verb, that's restricting it to this verb, which is completely different. It'll throw an error if your request is not DELETE, but it won't make the link send a DELETE request. You still have to use :method => :delete in the link to make it use DELETE instead of GET. But I don't see anything wrong in adding this extra condition to the route. I'll do it later. Thomas Jiten Bhagat wrote: > Hi Thomas, > > Found out more about setting routes that only respond to particular HTTP > verbs... > > http://guides.rails.info/routing/routing_outside_in.html#_route_conditions > > Cheers, > Jits > > > Jiten Bhagat wrote: >> No, you're absolutely right. Maybe I'm over thinking this particular >> problem :-) >> >> Jits >> >> >> Thomas Laurent wrote: >>> I don't follow you... >>> If a search engine hit the link <%= link_to 'Logout', logout_url, >>> :method => :delete -%> , it'll do like with any other "Destroy" link, >>> e.g. not follow it as it's in fact a POST. >>> >>> By "people hitting the link directly", do you mean typing the URL >>> directly ? If this is the case, I don't see much of a problem, it'll >>> send a GET request because that's the only thing a browser can do >>> from an URL typed in, but that'll still log them out >>> >>> I think I'm not understanding what you mean very well... >>> >>> Thomas >>> >>> Jiten Bhagat wrote: >>>> Hi Thomas, >>>> >>>> Comments below... >>>> >>>> Thomas Laurent wrote: >>>>> I don't know, that's an interesting question... >>>>> >>>>> I thought that the HTTP verb was defined in the link itself, as >>>>> the "logout" link should really be coded like that: >>>>> <%= link_to 'Logout', logout_url, :method => :delete -%> >>>> >>>> Yes, that can be done. My concern is people hitting the link >>>> directly or possibly a search engine. Though it doesn't sound like >>>> much harm can be done. >>>> >>>>> >>>>> I didn't find a way to specify the link to use HTTP DELETE directly >>>>> in the route, but if there was, it'd be great and I'd gladly add it >>>>> to the route. >>>> >>>> Ok, I'll check and see. I'm sure I read somewhere about this (since >>>> Resourceful Routes do it, and they just translate to named routes at >>>> 'runtime' anyways). >>>> >>>> Cheers, >>>> Jits >>>> >>>>> >>>>> Thomas >>>>> >>>>> Jiten Bhagat wrote: >>>>>> Hi Thomas, >>>>>> >>>>>> Just something I've noticed in routes... >>>>>> >>>>>> map.logout '/logout', :controller => 'sessions', :action => 'destroy' >>>>>> >>>>>> I like that idea! My only concern is that "http://.../logout" will >>>>>> make a GET request instead of a DELETE as it should. Is this a >>>>>> valid concern? >>>>>> >>>>>> Jits >>>>>> >>>>>> >>>>>> >>>>>> Thomas Laurent wrote: >>>>>>> I didn't link up the pages at all for the moment, that'll be done >>>>>>> now that I can work on the layout/look and feel. >>>>>>> >>>>>>> In the meantime, /register would lead you to the "new user" page. >>>>>>> >>>>>>> Cheers, >>>>>>> Thomas >>>>>>> >>>>>>> >>>>>>> Eric Nzuobontane wrote: >>>>>>>> Feature request ... Thomas could you add a link to the new user >>>>>>>> from the login page? >>>>>>>> Thanks! >>>>>>>> >>>>>>>> Eric >>>>>>>> >>>>>>>> >>>>>>>> Thomas Laurent wrote: >>>>>>>>> Sorry again, I'm not used to use plugins, so I didn't see I had >>>>>>>>> something to check in from inside the "vendor" directory. I >>>>>>>>> just noticed it when checking out the changes from Eric, as he >>>>>>>>> had also some new plugins... >>>>>>>>> >>>>>>>>> >>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>> Great, thanks, and no worries... we'll no doubt run into many >>>>>>>>>> times when we forget small pieces, especially when we use >>>>>>>>>> Ctrl-C and Ctrl-V a lot ;-) >>>>>>>>>> >>>>>>>>>> Jits >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Thomas Laurent wrote: >>>>>>>>>>> Jits, I've just added the files 5-10 minutes ago when I >>>>>>>>>>> realised I forgot to check them in. Sorry about that. >>>>>>>>>>> >>>>>>>>>>> Thomas >>>>>>>>>>> >>>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>>> Was just drafting an email about this :-) >>>>>>>>>>>> >>>>>>>>>>>> Have been testing it but I got an error that >>>>>>>>>>>> "validates_email_veracity_of" couldn't be found. This was >>>>>>>>>>>> from the User model and requires a plugin to work... I'll >>>>>>>>>>>> add this plugin to make it work :-) >>>>>>>>>>>> >>>>>>>>>>>> Jits >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thomas Laurent wrote: >>>>>>>>>>>>> Jits, when are you planning to add the css stuff ? >>>>>>>>>>>>> >>>>>>>>>>>>> Thomas >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>>>>> Sounds good Eric. Will check out the model code in a bit. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>> Jits >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Eric Nzuobontane wrote: >>>>>>>>>>>>>>> Hi Guys, >>>>>>>>>>>>>>> I have just committed coded to submit a soap_service. I >>>>>>>>>>>>>>> do not expect it to break anything Thomas did but you >>>>>>>>>>>>>>> never know. It will be wise for Thomas especially to >>>>>>>>>>>>>>> check that everything he did is still fine with my >>>>>>>>>>>>>>> updates. I guess we should start writing tests!!! >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> That said, what the code does is take a wsdl file, >>>>>>>>>>>>>>> extract the relevant information on operations and inputs >>>>>>>>>>>>>>> and outputs with their types and store these >>>>>>>>>>>>>>> transactionally in the database. I have also added some >>>>>>>>>>>>>>> migrations (adding some fields to the input/output tables). >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The work on soaplab servers is ongoing, but I decided to >>>>>>>>>>>>>>> check it in as I will be in Manchester during the next >>>>>>>>>>>>>>> two days and would want to bring it to a usable standard... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Jits, could you please look at the soap_service model in >>>>>>>>>>>>>>> particular and get back to me? You were interested in >>>>>>>>>>>>>>> knowing how I did it from the last chat..... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> cheers, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Eric >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>> _______________________________________________ >>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> BioCatalogue-developers mailing list >>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>> _______________________________________________ >>>>> BioCatalogue-developers mailing list >>>>> BioCatalogue-developers at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers From tlaurent at ebi.ac.uk Wed Oct 1 09:24:35 2008 From: tlaurent at ebi.ac.uk (Thomas Laurent) Date: Wed, 01 Oct 2008 14:24:35 +0100 Subject: [BioCatalogue-developers] soap_services submission In-Reply-To: <48E367E6.2020803@cs.man.ac.uk> References: <48CFBF1A.4000704@ebi.ac.uk> <48CFD467.5090205@cs.man.ac.uk> <48D0FCBF.7040309@ebi.ac.uk> <48D0FF3F.901@cs.man.ac.uk> <48D79277.1060307@ebi.ac.uk> <48D7A4F1.30308@cs.man.ac.uk> <48D7AACF.8050407@ebi.ac.uk> <48D7ACE4.2030909@cs.man.ac.uk> <48D7B34D.50005@ebi.ac.uk> <48D7B5AE.90603@ebi.ac.uk> <48DA06AA.2010107@ebi.ac.uk> <48DA1189.2070501@cs.man.ac.uk> <48DA14AB.9010509@ebi.ac.uk> <48DA1563.80403@cs.man.ac.uk> <48DA1646.4030403@ebi.ac.uk> <48DA16E3.8090403@cs.man.ac.uk> <48DA17D1.5030206@ebi.ac.uk> <48DA1B21.1060805@ebi.ac.uk> <48DA1F97.6090000@ebi.ac.uk> <48DA202F.8020306@cs.man.ac.uk> <48DA57F6.6050902@ebi.ac.uk> <48DA5929.4050209@cs.man.ac.uk> <48DA6124.8070002@ebi.ac.uk> <48DA662C.9010802@cs.man.ac.uk> <48E366F9.3010701@cs.man.ac.uk> <48E367E6.2020803@cs.man.ac.uk> Message-ID: <48E37A13.4010904@ebi.ac.uk> Yeah, deleting the session is not really a pb, but we'll have to be careful with the other resources. Thomas Jiten Bhagat wrote: > Also, the logout thing I brought up earlier is an example of a potential > cross-site request forgery (CSRF) attack, albeit not a severe one (and > not one we need to worry about too much), but important enough for us to > be aware of atleast. > > More info: http://www.theregister.co.uk/2008/09/30/web_bug_bites_sites/ > > Excerpt: > > "Cross-site request forgery (CSRF) vulnerabilities occur when a website > carries out an action without first confirming it was requested by the > authenticated user. Miscreants can exploit this shortcoming by including > code on an attack site that causes the user's browser to send commands > to a site such as ING.com. ING.com then carries out the command under > the mistaken notion that because it was requested by the browser, it was > invoked by the user." > > Jits > > > Jiten Bhagat wrote: >> Hi Thomas, >> >> Found out more about setting routes that only respond to particular >> HTTP verbs... >> >> http://guides.rails.info/routing/routing_outside_in.html#_route_conditions >> >> >> Cheers, >> Jits >> >> >> Jiten Bhagat wrote: >>> No, you're absolutely right. Maybe I'm over thinking this particular >>> problem :-) >>> >>> Jits >>> >>> >>> Thomas Laurent wrote: >>>> I don't follow you... >>>> If a search engine hit the link <%= link_to 'Logout', logout_url, >>>> :method => :delete -%> , it'll do like with any other "Destroy" >>>> link, e.g. not follow it as it's in fact a POST. >>>> >>>> By "people hitting the link directly", do you mean typing the URL >>>> directly ? If this is the case, I don't see much of a problem, it'll >>>> send a GET request because that's the only thing a browser can do >>>> from an URL typed in, but that'll still log them out >>>> >>>> I think I'm not understanding what you mean very well... >>>> >>>> Thomas >>>> >>>> Jiten Bhagat wrote: >>>>> Hi Thomas, >>>>> >>>>> Comments below... >>>>> >>>>> Thomas Laurent wrote: >>>>>> I don't know, that's an interesting question... >>>>>> >>>>>> I thought that the HTTP verb was defined in the link itself, as >>>>>> the "logout" link should really be coded like that: >>>>>> <%= link_to 'Logout', logout_url, :method => :delete -%> >>>>> >>>>> Yes, that can be done. My concern is people hitting the link >>>>> directly or possibly a search engine. Though it doesn't sound like >>>>> much harm can be done. >>>>> >>>>>> >>>>>> I didn't find a way to specify the link to use HTTP DELETE >>>>>> directly in the route, but if there was, it'd be great and I'd >>>>>> gladly add it to the route. >>>>> >>>>> Ok, I'll check and see. I'm sure I read somewhere about this (since >>>>> Resourceful Routes do it, and they just translate to named routes >>>>> at 'runtime' anyways). >>>>> >>>>> Cheers, >>>>> Jits >>>>> >>>>>> >>>>>> Thomas >>>>>> >>>>>> Jiten Bhagat wrote: >>>>>>> Hi Thomas, >>>>>>> >>>>>>> Just something I've noticed in routes... >>>>>>> >>>>>>> map.logout '/logout', :controller => 'sessions', :action => >>>>>>> 'destroy' >>>>>>> >>>>>>> I like that idea! My only concern is that "http://.../logout" >>>>>>> will make a GET request instead of a DELETE as it should. Is this >>>>>>> a valid concern? >>>>>>> >>>>>>> Jits >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thomas Laurent wrote: >>>>>>>> I didn't link up the pages at all for the moment, that'll be >>>>>>>> done now that I can work on the layout/look and feel. >>>>>>>> >>>>>>>> In the meantime, /register would lead you to the "new user" page. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Thomas >>>>>>>> >>>>>>>> >>>>>>>> Eric Nzuobontane wrote: >>>>>>>>> Feature request ... Thomas could you add a link to the new user >>>>>>>>> from the login page? >>>>>>>>> Thanks! >>>>>>>>> >>>>>>>>> Eric >>>>>>>>> >>>>>>>>> >>>>>>>>> Thomas Laurent wrote: >>>>>>>>>> Sorry again, I'm not used to use plugins, so I didn't see I >>>>>>>>>> had something to check in from inside the "vendor" directory. >>>>>>>>>> I just noticed it when checking out the changes from Eric, as >>>>>>>>>> he had also some new plugins... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>> Great, thanks, and no worries... we'll no doubt run into many >>>>>>>>>>> times when we forget small pieces, especially when we use >>>>>>>>>>> Ctrl-C and Ctrl-V a lot ;-) >>>>>>>>>>> >>>>>>>>>>> Jits >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thomas Laurent wrote: >>>>>>>>>>>> Jits, I've just added the files 5-10 minutes ago when I >>>>>>>>>>>> realised I forgot to check them in. Sorry about that. >>>>>>>>>>>> >>>>>>>>>>>> Thomas >>>>>>>>>>>> >>>>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>>>> Was just drafting an email about this :-) >>>>>>>>>>>>> >>>>>>>>>>>>> Have been testing it but I got an error that >>>>>>>>>>>>> "validates_email_veracity_of" couldn't be found. This was >>>>>>>>>>>>> from the User model and requires a plugin to work... I'll >>>>>>>>>>>>> add this plugin to make it work :-) >>>>>>>>>>>>> >>>>>>>>>>>>> Jits >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Thomas Laurent wrote: >>>>>>>>>>>>>> Jits, when are you planning to add the css stuff ? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thomas >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>>>>>> Sounds good Eric. Will check out the model code in a bit. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>> Jits >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Eric Nzuobontane wrote: >>>>>>>>>>>>>>>> Hi Guys, >>>>>>>>>>>>>>>> I have just committed coded to submit a soap_service. I >>>>>>>>>>>>>>>> do not expect it to break anything Thomas did but you >>>>>>>>>>>>>>>> never know. It will be wise for Thomas especially to >>>>>>>>>>>>>>>> check that everything he did is still fine with my >>>>>>>>>>>>>>>> updates. I guess we should start writing tests!!! >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> That said, what the code does is take a wsdl file, >>>>>>>>>>>>>>>> extract the relevant information on operations and >>>>>>>>>>>>>>>> inputs and outputs with their types and store these >>>>>>>>>>>>>>>> transactionally in the database. I have also added some >>>>>>>>>>>>>>>> migrations (adding some fields to the input/output tables). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> The work on soaplab servers is ongoing, but I decided to >>>>>>>>>>>>>>>> check it in as I will be in Manchester during the next >>>>>>>>>>>>>>>> two days and would want to bring it to a usable standard... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Jits, could you please look at the soap_service model in >>>>>>>>>>>>>>>> particular and get back to me? You were interested in >>>>>>>>>>>>>>>> knowing how I did it from the last chat..... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> cheers, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Eric >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>> _______________________________________________ >>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> BioCatalogue-developers mailing list >>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>> _______________________________________________ >>>>>> BioCatalogue-developers mailing list >>>>>> BioCatalogue-developers at rubyforge.org >>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers From jits at cs.man.ac.uk Wed Oct 1 09:25:02 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Wed, 01 Oct 2008 14:25:02 +0100 Subject: [BioCatalogue-developers] soap_services submission In-Reply-To: <48E379AB.3030404@ebi.ac.uk> References: <48CFBF1A.4000704@ebi.ac.uk> <48CFD467.5090205@cs.man.ac.uk> <48D0FCBF.7040309@ebi.ac.uk> <48D0FF3F.901@cs.man.ac.uk> <48D79277.1060307@ebi.ac.uk> <48D7A4F1.30308@cs.man.ac.uk> <48D7AACF.8050407@ebi.ac.uk> <48D7ACE4.2030909@cs.man.ac.uk> <48D7B34D.50005@ebi.ac.uk> <48D7B5AE.90603@ebi.ac.uk> <48DA06AA.2010107@ebi.ac.uk> <48DA1189.2070501@cs.man.ac.uk> <48DA14AB.9010509@ebi.ac.uk> <48DA1563.80403@cs.man.ac.uk> <48DA1646.4030403@ebi.ac.uk> <48DA16E3.8090403@cs.man.ac.uk> <48DA17D1.5030206@ebi.ac.uk> <48DA1B21.1060805@ebi.ac.uk> <48DA1F97.6090000@ebi.ac.uk> <48DA202F.8020306@cs.man.ac.uk> <48DA57F6.6050902@ebi.ac.uk> <48DA5929.4050209@cs.man.ac.uk> <48DA6124.8070002@ebi.ac.uk> <48DA662C.9010802@cs.man.ac.uk> <48E366F9.3010701@cs.man.ac.uk> <48E379AB.3030404@ebi.ac.uk> Message-ID: <48E37A2E.6060101@cs.man.ac.uk> Ok cool, thanks Thomas :-) Jits Thomas Laurent wrote: > Hi Jits, > > I saw this one, but that's not setting the route to the verb, that's > restricting it to this verb, which is completely different. It'll > throw an error if your request is not DELETE, but it won't make the > link send a DELETE request. > You still have to use :method => :delete in the link to make it use > DELETE instead of GET. > > But I don't see anything wrong in adding this extra condition to the > route. I'll do it later. > > Thomas > > Jiten Bhagat wrote: >> Hi Thomas, >> >> Found out more about setting routes that only respond to particular >> HTTP verbs... >> >> http://guides.rails.info/routing/routing_outside_in.html#_route_conditions >> >> >> Cheers, >> Jits >> >> >> Jiten Bhagat wrote: >>> No, you're absolutely right. Maybe I'm over thinking this particular >>> problem :-) >>> >>> Jits >>> >>> >>> Thomas Laurent wrote: >>>> I don't follow you... >>>> If a search engine hit the link <%= link_to 'Logout', logout_url, >>>> :method => :delete -%> , it'll do like with any other "Destroy" >>>> link, e.g. not follow it as it's in fact a POST. >>>> >>>> By "people hitting the link directly", do you mean typing the URL >>>> directly ? If this is the case, I don't see much of a problem, >>>> it'll send a GET request because that's the only thing a browser >>>> can do from an URL typed in, but that'll still log them out >>>> >>>> I think I'm not understanding what you mean very well... >>>> >>>> Thomas >>>> >>>> Jiten Bhagat wrote: >>>>> Hi Thomas, >>>>> >>>>> Comments below... >>>>> >>>>> Thomas Laurent wrote: >>>>>> I don't know, that's an interesting question... >>>>>> >>>>>> I thought that the HTTP verb was defined in the link itself, as >>>>>> the "logout" link should really be coded like that: >>>>>> <%= link_to 'Logout', logout_url, :method => :delete -%> >>>>> >>>>> Yes, that can be done. My concern is people hitting the link >>>>> directly or possibly a search engine. Though it doesn't sound like >>>>> much harm can be done. >>>>> >>>>>> >>>>>> I didn't find a way to specify the link to use HTTP DELETE >>>>>> directly in the route, but if there was, it'd be great and I'd >>>>>> gladly add it to the route. >>>>> >>>>> Ok, I'll check and see. I'm sure I read somewhere about this >>>>> (since Resourceful Routes do it, and they just translate to named >>>>> routes at 'runtime' anyways). >>>>> >>>>> Cheers, >>>>> Jits >>>>> >>>>>> >>>>>> Thomas >>>>>> >>>>>> Jiten Bhagat wrote: >>>>>>> Hi Thomas, >>>>>>> >>>>>>> Just something I've noticed in routes... >>>>>>> >>>>>>> map.logout '/logout', :controller => 'sessions', :action => >>>>>>> 'destroy' >>>>>>> >>>>>>> I like that idea! My only concern is that "http://.../logout" >>>>>>> will make a GET request instead of a DELETE as it should. Is >>>>>>> this a valid concern? >>>>>>> >>>>>>> Jits >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thomas Laurent wrote: >>>>>>>> I didn't link up the pages at all for the moment, that'll be >>>>>>>> done now that I can work on the layout/look and feel. >>>>>>>> >>>>>>>> In the meantime, /register would lead you to the "new user" page. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Thomas >>>>>>>> >>>>>>>> >>>>>>>> Eric Nzuobontane wrote: >>>>>>>>> Feature request ... Thomas could you add a link to the new >>>>>>>>> user from the login page? >>>>>>>>> Thanks! >>>>>>>>> >>>>>>>>> Eric >>>>>>>>> >>>>>>>>> >>>>>>>>> Thomas Laurent wrote: >>>>>>>>>> Sorry again, I'm not used to use plugins, so I didn't see I >>>>>>>>>> had something to check in from inside the "vendor" directory. >>>>>>>>>> I just noticed it when checking out the changes from Eric, as >>>>>>>>>> he had also some new plugins... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>> Great, thanks, and no worries... we'll no doubt run into >>>>>>>>>>> many times when we forget small pieces, especially when we >>>>>>>>>>> use Ctrl-C and Ctrl-V a lot ;-) >>>>>>>>>>> >>>>>>>>>>> Jits >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thomas Laurent wrote: >>>>>>>>>>>> Jits, I've just added the files 5-10 minutes ago when I >>>>>>>>>>>> realised I forgot to check them in. Sorry about that. >>>>>>>>>>>> >>>>>>>>>>>> Thomas >>>>>>>>>>>> >>>>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>>>> Was just drafting an email about this :-) >>>>>>>>>>>>> >>>>>>>>>>>>> Have been testing it but I got an error that >>>>>>>>>>>>> "validates_email_veracity_of" couldn't be found. This was >>>>>>>>>>>>> from the User model and requires a plugin to work... I'll >>>>>>>>>>>>> add this plugin to make it work :-) >>>>>>>>>>>>> >>>>>>>>>>>>> Jits >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Thomas Laurent wrote: >>>>>>>>>>>>>> Jits, when are you planning to add the css stuff ? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thomas >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>>>>>> Sounds good Eric. Will check out the model code in a bit. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>> Jits >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Eric Nzuobontane wrote: >>>>>>>>>>>>>>>> Hi Guys, >>>>>>>>>>>>>>>> I have just committed coded to submit a soap_service. I >>>>>>>>>>>>>>>> do not expect it to break anything Thomas did but you >>>>>>>>>>>>>>>> never know. It will be wise for Thomas especially to >>>>>>>>>>>>>>>> check that everything he did is still fine with my >>>>>>>>>>>>>>>> updates. I guess we should start writing tests!!! >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> That said, what the code does is take a wsdl file, >>>>>>>>>>>>>>>> extract the relevant information on operations and >>>>>>>>>>>>>>>> inputs and outputs with their types and store these >>>>>>>>>>>>>>>> transactionally in the database. I have also added some >>>>>>>>>>>>>>>> migrations (adding some fields to the input/output >>>>>>>>>>>>>>>> tables). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> The work on soaplab servers is ongoing, but I decided >>>>>>>>>>>>>>>> to check it in as I will be in Manchester during the >>>>>>>>>>>>>>>> next two days and would want to bring it to a usable >>>>>>>>>>>>>>>> standard... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Jits, could you please look at the soap_service model >>>>>>>>>>>>>>>> in particular and get back to me? You were interested >>>>>>>>>>>>>>>> in knowing how I did it from the last chat..... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> cheers, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Eric >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>> _______________________________________________ >>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> BioCatalogue-developers mailing list >>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>> _______________________________________________ >>>>>> BioCatalogue-developers mailing list >>>>>> BioCatalogue-developers at rubyforge.org >>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers From jits at cs.man.ac.uk Wed Oct 1 17:32:07 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Wed, 01 Oct 2008 22:32:07 +0100 Subject: [BioCatalogue-developers] Latest changes to data model Message-ID: <48E3EC57.5030109@cs.man.ac.uk> Hi guys, So Eric and I had a long chat today about how we could incorporate the notion of "service instances" together with service versions into our data model, since the same service could be deployed in various places. This is following on from the hackathon last week. As a result, we've updated the data model we are doing for the pilot. Latest here: http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot You'll notice there is a bit crossed out under Service Instance - a table for "Service Deployments". This was a mapping table between service instances and service versions (ie: a many to many relationship), so we could track over time what versions were deployed at what instances. However, earlier Eric raised the issue of making the model too perfect and complex for the pilot, so I crossed this out for now and collapsed the version relationship to the service instance directly (thus making it a one to many relationship). This should be ok for the pilot. I have done the necessary db changes via migration scripts, and have also created the necessary model classes together with controller stubs (with Resourceful REST actions in them). I'll do all the ActiveRecord model associations in the morning tomorrow before the myExp hackathon and commit this all. Let me know if you have any comments etc Cheers, Jits From ericnzuo at ebi.ac.uk Thu Oct 2 04:44:54 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Thu, 02 Oct 2008 09:44:54 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E3EC57.5030109@cs.man.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> Message-ID: <48E48A06.7050904@ebi.ac.uk> The first comment I have is to rename 'service instance' to 'service deployment'. In my opinion it is easier to understand. So speaking in singular, a service versions, a version has deployments... Jiten Bhagat wrote: > Hi guys, > > So Eric and I had a long chat today about how we could incorporate the > notion of "service instances" together with service versions into our > data model, since the same service could be deployed in various > places. This is following on from the hackathon last week. > > As a result, we've updated the data model we are doing for the pilot. > Latest here: > http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot > > > You'll notice there is a bit crossed out under Service Instance - a > table for "Service Deployments". This was a mapping table between > service instances and service versions (ie: a many to many > relationship), so we could track over time what versions were deployed > at what instances. However, earlier Eric raised the issue of making > the model too perfect and complex for the pilot, so I crossed this out > for now and collapsed the version relationship to the service instance > directly (thus making it a one to many relationship). This should be > ok for the pilot. > > I have done the necessary db changes via migration scripts, and have > also created the necessary model classes together with controller > stubs (with Resourceful REST actions in them). I'll do all the > ActiveRecord model associations in the morning tomorrow before the > myExp hackathon and commit this all. > > Let me know if you have any comments etc > > Cheers, > Jits > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Thu Oct 2 05:18:13 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Thu, 02 Oct 2008 10:18:13 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E48A06.7050904@ebi.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> <48E48A06.7050904@ebi.ac.uk> Message-ID: <48E491D5.7030609@cs.man.ac.uk> Okay, I'll do that. Jits Eric Nzuobontane wrote: > The first comment I have is to rename 'service instance' to 'service > deployment'. In my opinion it is easier to understand. So speaking in > singular, a service versions, a version has deployments... > > > Jiten Bhagat wrote: >> Hi guys, >> >> So Eric and I had a long chat today about how we could incorporate >> the notion of "service instances" together with service versions into >> our data model, since the same service could be deployed in various >> places. This is following on from the hackathon last week. >> >> As a result, we've updated the data model we are doing for the pilot. >> Latest here: >> http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot >> >> >> You'll notice there is a bit crossed out under Service Instance - a >> table for "Service Deployments". This was a mapping table between >> service instances and service versions (ie: a many to many >> relationship), so we could track over time what versions were >> deployed at what instances. However, earlier Eric raised the issue of >> making the model too perfect and complex for the pilot, so I crossed >> this out for now and collapsed the version relationship to the >> service instance directly (thus making it a one to many >> relationship). This should be ok for the pilot. >> >> I have done the necessary db changes via migration scripts, and have >> also created the necessary model classes together with controller >> stubs (with Resourceful REST actions in them). I'll do all the >> ActiveRecord model associations in the morning tomorrow before the >> myExp hackathon and commit this all. >> >> Let me know if you have any comments etc >> >> Cheers, >> Jits >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > From jits at cs.man.ac.uk Thu Oct 2 05:35:33 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Thu, 02 Oct 2008 10:35:33 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E491D5.7030609@cs.man.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> <48E48A06.7050904@ebi.ac.uk> <48E491D5.7030609@cs.man.ac.uk> Message-ID: <48E495E5.1090608@cs.man.ac.uk> Though I'm assuming that's not necessarily what we will use in the UI and URLs... because I think "service deployment" is too techy for most of our users. Jits Jiten Bhagat wrote: > Okay, I'll do that. > > Jits > > > Eric Nzuobontane wrote: >> The first comment I have is to rename 'service instance' to 'service >> deployment'. In my opinion it is easier to understand. So speaking in >> singular, a service versions, a version has deployments... >> >> >> Jiten Bhagat wrote: >>> Hi guys, >>> >>> So Eric and I had a long chat today about how we could incorporate >>> the notion of "service instances" together with service versions >>> into our data model, since the same service could be deployed in >>> various places. This is following on from the hackathon last week. >>> >>> As a result, we've updated the data model we are doing for the >>> pilot. Latest here: >>> http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot >>> >>> >>> You'll notice there is a bit crossed out under Service Instance - a >>> table for "Service Deployments". This was a mapping table between >>> service instances and service versions (ie: a many to many >>> relationship), so we could track over time what versions were >>> deployed at what instances. However, earlier Eric raised the issue >>> of making the model too perfect and complex for the pilot, so I >>> crossed this out for now and collapsed the version relationship to >>> the service instance directly (thus making it a one to many >>> relationship). This should be ok for the pilot. >>> >>> I have done the necessary db changes via migration scripts, and have >>> also created the necessary model classes together with controller >>> stubs (with Resourceful REST actions in them). I'll do all the >>> ActiveRecord model associations in the morning tomorrow before the >>> myExp hackathon and commit this all. >>> >>> Let me know if you have any comments etc >>> >>> Cheers, >>> Jits >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From jits at cs.man.ac.uk Thu Oct 2 07:35:14 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Thu, 02 Oct 2008 12:35:14 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E3EC57.5030109@cs.man.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> Message-ID: <48E4B1F2.8070004@cs.man.ac.uk> Hi guys, Just made the commits for this (please see commit logs). Note that although I have generated the Resourceful views, we don't have to use these! Jits Jiten Bhagat wrote: > Hi guys, > > So Eric and I had a long chat today about how we could incorporate the > notion of "service instances" together with service versions into our > data model, since the same service could be deployed in various > places. This is following on from the hackathon last week. > > As a result, we've updated the data model we are doing for the pilot. > Latest here: > http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot > > > You'll notice there is a bit crossed out under Service Instance - a > table for "Service Deployments". This was a mapping table between > service instances and service versions (ie: a many to many > relationship), so we could track over time what versions were deployed > at what instances. However, earlier Eric raised the issue of making > the model too perfect and complex for the pilot, so I crossed this out > for now and collapsed the version relationship to the service instance > directly (thus making it a one to many relationship). This should be > ok for the pilot. > > I have done the necessary db changes via migration scripts, and have > also created the necessary model classes together with controller > stubs (with Resourceful REST actions in them). I'll do all the > ActiveRecord model associations in the morning tomorrow before the > myExp hackathon and commit this all. > > Let me know if you have any comments etc > > Cheers, > Jits > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From ericnzuo at ebi.ac.uk Fri Oct 3 06:51:19 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Fri, 03 Oct 2008 11:51:19 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E495E5.1090608@cs.man.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> <48E48A06.7050904@ebi.ac.uk> <48E491D5.7030609@cs.man.ac.uk> <48E495E5.1090608@cs.man.ac.uk> Message-ID: <48E5F927.2040405@ebi.ac.uk> Hi Guys, One thing I think we should should consider doing now is tagging the repository, or maybe that is done automatically? I am new to subversion but I know that with cvs one needs to run cvs-tag 'blah' to build a tag. I have just updated my local code with Jits changes. Thanks for the changes, especially to some of the field names and migrations which I made... I have not had a look yet at how 'acts_as_service_versionified' works but one thing I noticed was that a 'require' was needed in the models that use it, which was missing for soap_service model. Another thing is that the 'service_type ' table was removed but the 'service_type ' model still seems to be in the repository. I would think that that should go as well. For my part, I have stripped out the wsdl parsing function that were in soap_model and put them in a module now in libs. That removes the cluttering of the model which I was unhappy with... I hope to check this in today. Should we have a developer chat on Monday, to evaluate where we are? Eric Jiten Bhagat wrote: > Though I'm assuming that's not necessarily what we will use in the UI > and URLs... because I think "service deployment" is too techy for most > of our users. > > Jits > > > Jiten Bhagat wrote: >> Okay, I'll do that. >> >> Jits >> >> >> Eric Nzuobontane wrote: >>> The first comment I have is to rename 'service instance' to 'service >>> deployment'. In my opinion it is easier to understand. So speaking >>> in singular, a service versions, a version has deployments... >>> >>> >>> Jiten Bhagat wrote: >>>> Hi guys, >>>> >>>> So Eric and I had a long chat today about how we could incorporate >>>> the notion of "service instances" together with service versions >>>> into our data model, since the same service could be deployed in >>>> various places. This is following on from the hackathon last week. >>>> >>>> As a result, we've updated the data model we are doing for the >>>> pilot. Latest here: >>>> http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot >>>> >>>> >>>> You'll notice there is a bit crossed out under Service Instance - a >>>> table for "Service Deployments". This was a mapping table between >>>> service instances and service versions (ie: a many to many >>>> relationship), so we could track over time what versions were >>>> deployed at what instances. However, earlier Eric raised the issue >>>> of making the model too perfect and complex for the pilot, so I >>>> crossed this out for now and collapsed the version relationship to >>>> the service instance directly (thus making it a one to many >>>> relationship). This should be ok for the pilot. >>>> >>>> I have done the necessary db changes via migration scripts, and >>>> have also created the necessary model classes together with >>>> controller stubs (with Resourceful REST actions in them). I'll do >>>> all the ActiveRecord model associations in the morning tomorrow >>>> before the myExp hackathon and commit this all. >>>> >>>> Let me know if you have any comments etc >>>> >>>> Cheers, >>>> Jits >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Fri Oct 3 07:15:18 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Fri, 03 Oct 2008 12:15:18 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E5F927.2040405@ebi.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> <48E48A06.7050904@ebi.ac.uk> <48E491D5.7030609@cs.man.ac.uk> <48E495E5.1090608@cs.man.ac.uk> <48E5F927.2040405@ebi.ac.uk> Message-ID: <48E5FEC6.8020907@cs.man.ac.uk> Hi Eric, > One thing I think we should should consider doing now is tagging the > repository, or maybe that is done automatically? I am new to > subversion but I know that with cvs one needs to run cvs-tag 'blah' to > build a tag. At this stage when do we need to tag the repository? If we need to in the future it is very simple to do with SVN. > ... but one thing I noticed was that a 'require' was needed in the > models that use it, which was missing for soap_service model. Ahh yes, thanks. I take it you've added this in? > Should we have a developer chat on Monday, to evaluate where we are? Sounds good! Say 11am-12pm skype text chat? Cheers, Jits Eric Nzuobontane wrote: > Hi Guys, > One thing I think we should should consider doing now is tagging the > repository, or maybe that is done automatically? I am new to > subversion but I know that with cvs one needs to run cvs-tag 'blah' to > build a tag. > I have just updated my local code with Jits changes. Thanks for the > changes, especially to some of the field names and migrations which I > made... I have not had a look yet at how > 'acts_as_service_versionified' works but one thing I noticed was that > a 'require' was needed in the models that use it, which was missing > for soap_service model. Another thing is that the 'service_type ' > table was removed but the 'service_type ' model still seems to be in > the repository. I would think that that should go as well. For my > part, I have stripped out the wsdl parsing function that were in > soap_model and put them in a module now in libs. That removes the > cluttering of the model which I was unhappy with... I hope to check > this in today. > > Should we have a developer chat on Monday, to evaluate where we are? > > Eric > > > > Jiten Bhagat wrote: >> Though I'm assuming that's not necessarily what we will use in the UI >> and URLs... because I think "service deployment" is too techy for >> most of our users. >> >> Jits >> >> >> Jiten Bhagat wrote: >>> Okay, I'll do that. >>> >>> Jits >>> >>> >>> Eric Nzuobontane wrote: >>>> The first comment I have is to rename 'service instance' to >>>> 'service deployment'. In my opinion it is easier to understand. So >>>> speaking in singular, a service versions, a version has >>>> deployments... >>>> >>>> >>>> Jiten Bhagat wrote: >>>>> Hi guys, >>>>> >>>>> So Eric and I had a long chat today about how we could incorporate >>>>> the notion of "service instances" together with service versions >>>>> into our data model, since the same service could be deployed in >>>>> various places. This is following on from the hackathon last week. >>>>> >>>>> As a result, we've updated the data model we are doing for the >>>>> pilot. Latest here: >>>>> http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot >>>>> >>>>> >>>>> You'll notice there is a bit crossed out under Service Instance - >>>>> a table for "Service Deployments". This was a mapping table >>>>> between service instances and service versions (ie: a many to many >>>>> relationship), so we could track over time what versions were >>>>> deployed at what instances. However, earlier Eric raised the issue >>>>> of making the model too perfect and complex for the pilot, so I >>>>> crossed this out for now and collapsed the version relationship to >>>>> the service instance directly (thus making it a one to many >>>>> relationship). This should be ok for the pilot. >>>>> >>>>> I have done the necessary db changes via migration scripts, and >>>>> have also created the necessary model classes together with >>>>> controller stubs (with Resourceful REST actions in them). I'll do >>>>> all the ActiveRecord model associations in the morning tomorrow >>>>> before the myExp hackathon and commit this all. >>>>> >>>>> Let me know if you have any comments etc >>>>> >>>>> Cheers, >>>>> Jits >>>>> _______________________________________________ >>>>> BioCatalogue-developers mailing list >>>>> BioCatalogue-developers at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > From ericnzuo at ebi.ac.uk Fri Oct 3 07:44:27 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Fri, 03 Oct 2008 12:44:27 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E5FEC6.8020907@cs.man.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> <48E48A06.7050904@ebi.ac.uk> <48E491D5.7030609@cs.man.ac.uk> <48E495E5.1090608@cs.man.ac.uk> <48E5F927.2040405@ebi.ac.uk> <48E5FEC6.8020907@cs.man.ac.uk> Message-ID: <48E6059B.7060509@ebi.ac.uk> > > At this stage when do we need to tag the repository? If we need to in > the future it is very simple to do with SVN. > I suppose this is why? Well if you need to show anything to somebody out of the developer team, it is always nice to be sure that you are showing what you think you are showing. A tag would give that kind of assurance. Are tags expensive in svn? We do not have to tag if people think it is unnecessary... >> ... but one thing I noticed was that a 'require' was needed in the >> models that use it, which was missing for soap_service model. > > Ahh yes, thanks. I take it you've added this in? yes > >> Should we have a developer chat on Monday, to evaluate where we are? > > Sounds good! Say 11am-12pm skype text chat? fine by me... > > > > > Eric Nzuobontane wrote: >> Hi Guys, >> One thing I think we should should consider doing now is tagging the >> repository, or maybe that is done automatically? I am new to >> subversion but I know that with cvs one needs to run cvs-tag 'blah' >> to build a tag. >> I have just updated my local code with Jits changes. Thanks for the >> changes, especially to some of the field names and migrations which I >> made... I have not had a look yet at how >> 'acts_as_service_versionified' works but one thing I noticed was that >> a 'require' was needed in the models that use it, which was >> missing for soap_service model. Another thing is that the >> 'service_type ' table was removed but the 'service_type ' model still >> seems to be in the repository. I would think that that should go as >> well. For my part, I have stripped out the wsdl parsing function that >> were in soap_model and put them in a module now in libs. That removes >> the cluttering of the model which I was unhappy with... I hope to >> check this in today. >> >> Should we have a developer chat on Monday, to evaluate where we are? >> >> Eric >> >> >> >> Jiten Bhagat wrote: >>> Though I'm assuming that's not necessarily what we will use in the >>> UI and URLs... because I think "service deployment" is too techy for >>> most of our users. >>> >>> Jits >>> >>> >>> Jiten Bhagat wrote: >>>> Okay, I'll do that. >>>> >>>> Jits >>>> >>>> >>>> Eric Nzuobontane wrote: >>>>> The first comment I have is to rename 'service instance' to >>>>> 'service deployment'. In my opinion it is easier to understand. So >>>>> speaking in singular, a service versions, a version has >>>>> deployments... >>>>> >>>>> >>>>> Jiten Bhagat wrote: >>>>>> Hi guys, >>>>>> >>>>>> So Eric and I had a long chat today about how we could >>>>>> incorporate the notion of "service instances" together with >>>>>> service versions into our data model, since the same service >>>>>> could be deployed in various places. This is following on from >>>>>> the hackathon last week. >>>>>> >>>>>> As a result, we've updated the data model we are doing for the >>>>>> pilot. Latest here: >>>>>> http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot >>>>>> >>>>>> >>>>>> You'll notice there is a bit crossed out under Service Instance - >>>>>> a table for "Service Deployments". This was a mapping table >>>>>> between service instances and service versions (ie: a many to >>>>>> many relationship), so we could track over time what versions >>>>>> were deployed at what instances. However, earlier Eric raised the >>>>>> issue of making the model too perfect and complex for the pilot, >>>>>> so I crossed this out for now and collapsed the version >>>>>> relationship to the service instance directly (thus making it a >>>>>> one to many relationship). This should be ok for the pilot. >>>>>> >>>>>> I have done the necessary db changes via migration scripts, and >>>>>> have also created the necessary model classes together with >>>>>> controller stubs (with Resourceful REST actions in them). I'll do >>>>>> all the ActiveRecord model associations in the morning tomorrow >>>>>> before the myExp hackathon and commit this all. >>>>>> >>>>>> Let me know if you have any comments etc >>>>>> >>>>>> Cheers, >>>>>> Jits >>>>>> _______________________________________________ >>>>>> BioCatalogue-developers mailing list >>>>>> BioCatalogue-developers at rubyforge.org >>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>> >>>> >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Fri Oct 3 08:08:27 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Fri, 03 Oct 2008 13:08:27 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E6059B.7060509@ebi.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> <48E48A06.7050904@ebi.ac.uk> <48E491D5.7030609@cs.man.ac.uk> <48E495E5.1090608@cs.man.ac.uk> <48E5F927.2040405@ebi.ac.uk> <48E5FEC6.8020907@cs.man.ac.uk> <48E6059B.7060509@ebi.ac.uk> Message-ID: <48E60B3B.7010803@cs.man.ac.uk> Hi Eric, Eric Nzuobontane wrote: > >> >> At this stage when do we need to tag the repository? If we need to in >> the future it is very simple to do with SVN. >> > I suppose this is why? Well if you need to show anything to somebody > out of the developer team, it is always nice to be sure that you are > showing what you think you are showing. A tag would give that kind of > assurance. Are tags expensive in svn? We do not have to tag if people > think it is unnecessary... Ah yes, when it comes to deployment we should tag every single "release". Tags are very cheap in SVN as it doesn't actually copy anything. >>> ... but one thing I noticed was that a 'require' was needed in the >>> models that use it, which was missing for soap_service model. >> >> Ahh yes, thanks. I take it you've added this in? > yes >> >>> Should we have a developer chat on Monday, to evaluate where we are? >> >> Sounds good! Say 11am-12pm skype text chat? > fine by me... Great, speak to you then. Jits > >> >> >> >> >> Eric Nzuobontane wrote: >>> Hi Guys, >>> One thing I think we should should consider doing now is tagging the >>> repository, or maybe that is done automatically? I am new to >>> subversion but I know that with cvs one needs to run cvs-tag 'blah' >>> to build a tag. >>> I have just updated my local code with Jits changes. Thanks for the >>> changes, especially to some of the field names and migrations which >>> I made... I have not had a look yet at how >>> 'acts_as_service_versionified' works but one thing I noticed was >>> that a 'require' was needed in the models that use it, which was >>> missing for soap_service model. Another thing is that the >>> 'service_type ' table was removed but the 'service_type ' model >>> still seems to be in the repository. I would think that that >>> should go as well. For my part, I have stripped out the wsdl >>> parsing function that were in soap_model and put them in a module >>> now in libs. That removes the cluttering of the model which I was >>> unhappy with... I hope to check this in today. >>> >>> Should we have a developer chat on Monday, to evaluate where we are? >>> >>> Eric >>> >>> >>> >>> Jiten Bhagat wrote: >>>> Though I'm assuming that's not necessarily what we will use in the >>>> UI and URLs... because I think "service deployment" is too techy >>>> for most of our users. >>>> >>>> Jits >>>> >>>> >>>> Jiten Bhagat wrote: >>>>> Okay, I'll do that. >>>>> >>>>> Jits >>>>> >>>>> >>>>> Eric Nzuobontane wrote: >>>>>> The first comment I have is to rename 'service instance' to >>>>>> 'service deployment'. In my opinion it is easier to understand. >>>>>> So speaking in singular, a service versions, a version has >>>>>> deployments... >>>>>> >>>>>> >>>>>> Jiten Bhagat wrote: >>>>>>> Hi guys, >>>>>>> >>>>>>> So Eric and I had a long chat today about how we could >>>>>>> incorporate the notion of "service instances" together with >>>>>>> service versions into our data model, since the same service >>>>>>> could be deployed in various places. This is following on from >>>>>>> the hackathon last week. >>>>>>> >>>>>>> As a result, we've updated the data model we are doing for the >>>>>>> pilot. Latest here: >>>>>>> http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot >>>>>>> >>>>>>> >>>>>>> You'll notice there is a bit crossed out under Service Instance >>>>>>> - a table for "Service Deployments". This was a mapping table >>>>>>> between service instances and service versions (ie: a many to >>>>>>> many relationship), so we could track over time what versions >>>>>>> were deployed at what instances. However, earlier Eric raised >>>>>>> the issue of making the model too perfect and complex for the >>>>>>> pilot, so I crossed this out for now and collapsed the version >>>>>>> relationship to the service instance directly (thus making it a >>>>>>> one to many relationship). This should be ok for the pilot. >>>>>>> >>>>>>> I have done the necessary db changes via migration scripts, and >>>>>>> have also created the necessary model classes together with >>>>>>> controller stubs (with Resourceful REST actions in them). I'll >>>>>>> do all the ActiveRecord model associations in the morning >>>>>>> tomorrow before the myExp hackathon and commit this all. >>>>>>> >>>>>>> Let me know if you have any comments etc >>>>>>> >>>>>>> Cheers, >>>>>>> Jits >>>>>>> _______________________________________________ >>>>>>> BioCatalogue-developers mailing list >>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>> >>>>> >>>>> _______________________________________________ >>>>> BioCatalogue-developers mailing list >>>>> BioCatalogue-developers at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> > From ericnzuo at ebi.ac.uk Fri Oct 3 08:46:55 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Fri, 03 Oct 2008 13:46:55 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E60B3B.7010803@cs.man.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> <48E48A06.7050904@ebi.ac.uk> <48E491D5.7030609@cs.man.ac.uk> <48E495E5.1090608@cs.man.ac.uk> <48E5F927.2040405@ebi.ac.uk> <48E5FEC6.8020907@cs.man.ac.uk> <48E6059B.7060509@ebi.ac.uk> <48E60B3B.7010803@cs.man.ac.uk> Message-ID: <48E6143F.1090208@ebi.ac.uk> Hi Jits, What effect is acts_as_service_versionified supposed to have on the db when I create a soap_service? Eric Jiten Bhagat wrote: > Hi Eric, > > Eric Nzuobontane wrote: >> >>> >>> At this stage when do we need to tag the repository? If we need to >>> in the future it is very simple to do with SVN. >>> >> I suppose this is why? Well if you need to show anything to somebody >> out of the developer team, it is always nice to be sure that you are >> showing what you think you are showing. A tag would give that kind of >> assurance. Are tags expensive in svn? We do not have to tag if people >> think it is unnecessary... > > Ah yes, when it comes to deployment we should tag every single > "release". Tags are very cheap in SVN as it doesn't actually copy > anything. > >>>> ... but one thing I noticed was that a 'require' was needed in >>>> the models that use it, which was missing for soap_service model. >>> >>> Ahh yes, thanks. I take it you've added this in? >> yes >>> >>>> Should we have a developer chat on Monday, to evaluate where we are? >>> >>> Sounds good! Say 11am-12pm skype text chat? >> fine by me... > > Great, speak to you then. > > Jits > >> >>> >>> >>> >>> >>> Eric Nzuobontane wrote: >>>> Hi Guys, >>>> One thing I think we should should consider doing now is tagging >>>> the repository, or maybe that is done automatically? I am new to >>>> subversion but I know that with cvs one needs to run cvs-tag 'blah' >>>> to build a tag. >>>> I have just updated my local code with Jits changes. Thanks for the >>>> changes, especially to some of the field names and migrations which >>>> I made... I have not had a look yet at how >>>> 'acts_as_service_versionified' works but one thing I noticed was >>>> that a 'require' was needed in the models that use it, which was >>>> missing for soap_service model. Another thing is that the >>>> 'service_type ' table was removed but the 'service_type ' model >>>> still seems to be in the repository. I would think that that >>>> should go as well. For my part, I have stripped out the wsdl >>>> parsing function that were in soap_model and put them in a module >>>> now in libs. That removes the cluttering of the model which I was >>>> unhappy with... I hope to check this in today. >>>> >>>> Should we have a developer chat on Monday, to evaluate where we are? >>>> >>>> Eric >>>> >>>> >>>> >>>> Jiten Bhagat wrote: >>>>> Though I'm assuming that's not necessarily what we will use in the >>>>> UI and URLs... because I think "service deployment" is too techy >>>>> for most of our users. >>>>> >>>>> Jits >>>>> >>>>> >>>>> Jiten Bhagat wrote: >>>>>> Okay, I'll do that. >>>>>> >>>>>> Jits >>>>>> >>>>>> >>>>>> Eric Nzuobontane wrote: >>>>>>> The first comment I have is to rename 'service instance' to >>>>>>> 'service deployment'. In my opinion it is easier to understand. >>>>>>> So speaking in singular, a service versions, a version has >>>>>>> deployments... >>>>>>> >>>>>>> >>>>>>> Jiten Bhagat wrote: >>>>>>>> Hi guys, >>>>>>>> >>>>>>>> So Eric and I had a long chat today about how we could >>>>>>>> incorporate the notion of "service instances" together with >>>>>>>> service versions into our data model, since the same service >>>>>>>> could be deployed in various places. This is following on from >>>>>>>> the hackathon last week. >>>>>>>> >>>>>>>> As a result, we've updated the data model we are doing for the >>>>>>>> pilot. Latest here: >>>>>>>> http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot >>>>>>>> >>>>>>>> >>>>>>>> You'll notice there is a bit crossed out under Service Instance >>>>>>>> - a table for "Service Deployments". This was a mapping table >>>>>>>> between service instances and service versions (ie: a many to >>>>>>>> many relationship), so we could track over time what versions >>>>>>>> were deployed at what instances. However, earlier Eric raised >>>>>>>> the issue of making the model too perfect and complex for the >>>>>>>> pilot, so I crossed this out for now and collapsed the version >>>>>>>> relationship to the service instance directly (thus making it a >>>>>>>> one to many relationship). This should be ok for the pilot. >>>>>>>> >>>>>>>> I have done the necessary db changes via migration scripts, and >>>>>>>> have also created the necessary model classes together with >>>>>>>> controller stubs (with Resourceful REST actions in them). I'll >>>>>>>> do all the ActiveRecord model associations in the morning >>>>>>>> tomorrow before the myExp hackathon and commit this all. >>>>>>>> >>>>>>>> Let me know if you have any comments etc >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Jits >>>>>>>> _______________________________________________ >>>>>>>> BioCatalogue-developers mailing list >>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> BioCatalogue-developers mailing list >>>>>> BioCatalogue-developers at rubyforge.org >>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> >> -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Fri Oct 3 09:15:38 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Fri, 03 Oct 2008 14:15:38 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E6143F.1090208@ebi.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> <48E48A06.7050904@ebi.ac.uk> <48E491D5.7030609@cs.man.ac.uk> <48E495E5.1090608@cs.man.ac.uk> <48E5F927.2040405@ebi.ac.uk> <48E5FEC6.8020907@cs.man.ac.uk> <48E6059B.7060509@ebi.ac.uk> <48E60B3B.7010803@cs.man.ac.uk> <48E6143F.1090208@ebi.ac.uk> Message-ID: <48E61AFA.9000502@cs.man.ac.uk> Hi Eric, It shouldn't have any effect on *create* and on an *update* it just updates the parent ServiceVersion so that it's updated_at time is updated accordingly. Note you will need to create the parent ServiceVersion model object when creating any new service type object (eg: soap service). I wanted to have this done automatically in the acts_as_service_versionified but the version info needs to be provided manually. Cheers, Jits Eric Nzuobontane wrote: > Hi Jits, > What effect is acts_as_service_versionified supposed to have on the db > when I create a soap_service? > > Eric > > > Jiten Bhagat wrote: >> Hi Eric, >> >> Eric Nzuobontane wrote: >>> >>>> >>>> At this stage when do we need to tag the repository? If we need to >>>> in the future it is very simple to do with SVN. >>>> >>> I suppose this is why? Well if you need to show anything to somebody >>> out of the developer team, it is always nice to be sure that you are >>> showing what you think you are showing. A tag would give that kind >>> of assurance. Are tags expensive in svn? We do not have to tag if >>> people think it is unnecessary... >> >> Ah yes, when it comes to deployment we should tag every single >> "release". Tags are very cheap in SVN as it doesn't actually copy >> anything. >> >>>>> ... but one thing I noticed was that a 'require' was needed in >>>>> the models that use it, which was missing for soap_service model. >>>> >>>> Ahh yes, thanks. I take it you've added this in? >>> yes >>>> >>>>> Should we have a developer chat on Monday, to evaluate where we are? >>>> >>>> Sounds good! Say 11am-12pm skype text chat? >>> fine by me... >> >> Great, speak to you then. >> >> Jits >> >>> >>>> >>>> >>>> >>>> >>>> Eric Nzuobontane wrote: >>>>> Hi Guys, >>>>> One thing I think we should should consider doing now is tagging >>>>> the repository, or maybe that is done automatically? I am new to >>>>> subversion but I know that with cvs one needs to run cvs-tag >>>>> 'blah' to build a tag. >>>>> I have just updated my local code with Jits changes. Thanks for >>>>> the changes, especially to some of the field names and migrations >>>>> which I made... I have not had a look yet at how >>>>> 'acts_as_service_versionified' works but one thing I noticed was >>>>> that a 'require' was needed in the models that use it, which >>>>> was missing for soap_service model. Another thing is that the >>>>> 'service_type ' table was removed but the 'service_type ' model >>>>> still seems to be in the repository. I would think that that >>>>> should go as well. For my part, I have stripped out the wsdl >>>>> parsing function that were in soap_model and put them in a module >>>>> now in libs. That removes the cluttering of the model which I was >>>>> unhappy with... I hope to check this in today. >>>>> >>>>> Should we have a developer chat on Monday, to evaluate where we are? >>>>> >>>>> Eric >>>>> >>>>> >>>>> >>>>> Jiten Bhagat wrote: >>>>>> Though I'm assuming that's not necessarily what we will use in >>>>>> the UI and URLs... because I think "service deployment" is too >>>>>> techy for most of our users. >>>>>> >>>>>> Jits >>>>>> >>>>>> >>>>>> Jiten Bhagat wrote: >>>>>>> Okay, I'll do that. >>>>>>> >>>>>>> Jits >>>>>>> >>>>>>> >>>>>>> Eric Nzuobontane wrote: >>>>>>>> The first comment I have is to rename 'service instance' to >>>>>>>> 'service deployment'. In my opinion it is easier to understand. >>>>>>>> So speaking in singular, a service versions, a version has >>>>>>>> deployments... >>>>>>>> >>>>>>>> >>>>>>>> Jiten Bhagat wrote: >>>>>>>>> Hi guys, >>>>>>>>> >>>>>>>>> So Eric and I had a long chat today about how we could >>>>>>>>> incorporate the notion of "service instances" together with >>>>>>>>> service versions into our data model, since the same service >>>>>>>>> could be deployed in various places. This is following on from >>>>>>>>> the hackathon last week. >>>>>>>>> >>>>>>>>> As a result, we've updated the data model we are doing for the >>>>>>>>> pilot. Latest here: >>>>>>>>> http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot >>>>>>>>> >>>>>>>>> >>>>>>>>> You'll notice there is a bit crossed out under Service >>>>>>>>> Instance - a table for "Service Deployments". This was a >>>>>>>>> mapping table between service instances and service versions >>>>>>>>> (ie: a many to many relationship), so we could track over time >>>>>>>>> what versions were deployed at what instances. However, >>>>>>>>> earlier Eric raised the issue of making the model too perfect >>>>>>>>> and complex for the pilot, so I crossed this out for now and >>>>>>>>> collapsed the version relationship to the service instance >>>>>>>>> directly (thus making it a one to many relationship). This >>>>>>>>> should be ok for the pilot. >>>>>>>>> >>>>>>>>> I have done the necessary db changes via migration scripts, >>>>>>>>> and have also created the necessary model classes together >>>>>>>>> with controller stubs (with Resourceful REST actions in them). >>>>>>>>> I'll do all the ActiveRecord model associations in the morning >>>>>>>>> tomorrow before the myExp hackathon and commit this all. >>>>>>>>> >>>>>>>>> Let me know if you have any comments etc >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Jits >>>>>>>>> _______________________________________________ >>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> BioCatalogue-developers mailing list >>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>> >>> > From jits at cs.man.ac.uk Fri Oct 3 10:03:24 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Fri, 03 Oct 2008 15:03:24 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E61AFA.9000502@cs.man.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> <48E48A06.7050904@ebi.ac.uk> <48E491D5.7030609@cs.man.ac.uk> <48E495E5.1090608@cs.man.ac.uk> <48E5F927.2040405@ebi.ac.uk> <48E5FEC6.8020907@cs.man.ac.uk> <48E6059B.7060509@ebi.ac.uk> <48E60B3B.7010803@cs.man.ac.uk> <48E6143F.1090208@ebi.ac.uk> <48E61AFA.9000502@cs.man.ac.uk> Message-ID: <48E6262C.9080907@cs.man.ac.uk> > Note you will need to create the parent ServiceVersion model object > when creating any new service type object (eg: soap service). I wanted > to have this done automatically in the acts_as_service_versionified > but the version info needs to be provided manually. To elaborate on this... Due to the acts_as_service_versionified, you can do something like this: new_soap_service = SoapService.new(params) new_soap_service.service_version = ServiceVersion.new(params) new_soap_service.save # Should save both objects transactionally Note (1): if the .save fails due to validation errors in the model, the assignment of the ServiceVersion to the SoapService. Note (2): we need to also create a new Service container object if this is the first version, and do something like: s = Service.create(params) # Automatically creates AND saves the object to the db. s.service_versions << new_soap_service.service_version # This will save the association to the db (and set the foreign key appropriately); Will return false if this fails. Note (3): I'm in the process of adding all the necessary ActiveRecord validations in the models. Jits Jiten Bhagat wrote: > Hi Eric, > > It shouldn't have any effect on *create* and on an *update* it just > updates the parent ServiceVersion so that it's updated_at time is > updated accordingly. > > Note you will need to create the parent ServiceVersion model object > when creating any new service type object (eg: soap service). I wanted > to have this done automatically in the acts_as_service_versionified > but the version info needs to be provided manually. > > Cheers, > Jits > > > > > Eric Nzuobontane wrote: >> Hi Jits, >> What effect is acts_as_service_versionified supposed to have on the >> db when I create a soap_service? >> >> Eric >> >> >> Jiten Bhagat wrote: >>> Hi Eric, >>> >>> Eric Nzuobontane wrote: >>>> >>>>> >>>>> At this stage when do we need to tag the repository? If we need to >>>>> in the future it is very simple to do with SVN. >>>>> >>>> I suppose this is why? Well if you need to show anything to >>>> somebody out of the developer team, it is always nice to be sure >>>> that you are showing what you think you are showing. A tag would >>>> give that kind of assurance. Are tags expensive in svn? We do not >>>> have to tag if people think it is unnecessary... >>> >>> Ah yes, when it comes to deployment we should tag every single >>> "release". Tags are very cheap in SVN as it doesn't actually copy >>> anything. >>> >>>>>> ... but one thing I noticed was that a 'require' was needed in >>>>>> the models that use it, which was missing for soap_service model. >>>>> >>>>> Ahh yes, thanks. I take it you've added this in? >>>> yes >>>>> >>>>>> Should we have a developer chat on Monday, to evaluate where we are? >>>>> >>>>> Sounds good! Say 11am-12pm skype text chat? >>>> fine by me... >>> >>> Great, speak to you then. >>> >>> Jits >>> >>>> >>>>> >>>>> >>>>> >>>>> >>>>> Eric Nzuobontane wrote: >>>>>> Hi Guys, >>>>>> One thing I think we should should consider doing now is tagging >>>>>> the repository, or maybe that is done automatically? I am new to >>>>>> subversion but I know that with cvs one needs to run cvs-tag >>>>>> 'blah' to build a tag. >>>>>> I have just updated my local code with Jits changes. Thanks for >>>>>> the changes, especially to some of the field names and migrations >>>>>> which I made... I have not had a look yet at how >>>>>> 'acts_as_service_versionified' works but one thing I noticed was >>>>>> that a 'require' was needed in the models that use it, which >>>>>> was missing for soap_service model. Another thing is that the >>>>>> 'service_type ' table was removed but the 'service_type ' model >>>>>> still seems to be in the repository. I would think that that >>>>>> should go as well. For my part, I have stripped out the wsdl >>>>>> parsing function that were in soap_model and put them in a module >>>>>> now in libs. That removes the cluttering of the model which I was >>>>>> unhappy with... I hope to check this in today. >>>>>> >>>>>> Should we have a developer chat on Monday, to evaluate where we are? >>>>>> >>>>>> Eric >>>>>> >>>>>> >>>>>> >>>>>> Jiten Bhagat wrote: >>>>>>> Though I'm assuming that's not necessarily what we will use in >>>>>>> the UI and URLs... because I think "service deployment" is too >>>>>>> techy for most of our users. >>>>>>> >>>>>>> Jits >>>>>>> >>>>>>> >>>>>>> Jiten Bhagat wrote: >>>>>>>> Okay, I'll do that. >>>>>>>> >>>>>>>> Jits >>>>>>>> >>>>>>>> >>>>>>>> Eric Nzuobontane wrote: >>>>>>>>> The first comment I have is to rename 'service instance' to >>>>>>>>> 'service deployment'. In my opinion it is easier to >>>>>>>>> understand. So speaking in singular, a service versions, a >>>>>>>>> version has deployments... >>>>>>>>> >>>>>>>>> >>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>> Hi guys, >>>>>>>>>> >>>>>>>>>> So Eric and I had a long chat today about how we could >>>>>>>>>> incorporate the notion of "service instances" together with >>>>>>>>>> service versions into our data model, since the same service >>>>>>>>>> could be deployed in various places. This is following on >>>>>>>>>> from the hackathon last week. >>>>>>>>>> >>>>>>>>>> As a result, we've updated the data model we are doing for >>>>>>>>>> the pilot. Latest here: >>>>>>>>>> http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> You'll notice there is a bit crossed out under Service >>>>>>>>>> Instance - a table for "Service Deployments". This was a >>>>>>>>>> mapping table between service instances and service versions >>>>>>>>>> (ie: a many to many relationship), so we could track over >>>>>>>>>> time what versions were deployed at what instances. However, >>>>>>>>>> earlier Eric raised the issue of making the model too perfect >>>>>>>>>> and complex for the pilot, so I crossed this out for now and >>>>>>>>>> collapsed the version relationship to the service instance >>>>>>>>>> directly (thus making it a one to many relationship). This >>>>>>>>>> should be ok for the pilot. >>>>>>>>>> >>>>>>>>>> I have done the necessary db changes via migration scripts, >>>>>>>>>> and have also created the necessary model classes together >>>>>>>>>> with controller stubs (with Resourceful REST actions in >>>>>>>>>> them). I'll do all the ActiveRecord model associations in the >>>>>>>>>> morning tomorrow before the myExp hackathon and commit this all. >>>>>>>>>> >>>>>>>>>> Let me know if you have any comments etc >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Jits >>>>>>>>>> _______________________________________________ >>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> BioCatalogue-developers mailing list >>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>> >>>> >> > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From ericnzuo at ebi.ac.uk Fri Oct 3 10:26:07 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Fri, 03 Oct 2008 15:26:07 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E6262C.9080907@cs.man.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> <48E48A06.7050904@ebi.ac.uk> <48E491D5.7030609@cs.man.ac.uk> <48E495E5.1090608@cs.man.ac.uk> <48E5F927.2040405@ebi.ac.uk> <48E5FEC6.8020907@cs.man.ac.uk> <48E6059B.7060509@ebi.ac.uk> <48E60B3B.7010803@cs.man.ac.uk> <48E6143F.1090208@ebi.ac.uk> <48E61AFA.9000502@cs.man.ac.uk> <48E6262C.9080907@cs.man.ac.uk> Message-ID: <48E62B7F.8070706@ebi.ac.uk> Hi Jits, Thanks for the elaboration. I have committed my recent changes and hope I have not broken anything... O:-) . I believe the soap_service controller still needs to change to take into account the versioning and deployments. Eric Jiten Bhagat wrote: >> Note you will need to create the parent ServiceVersion model object >> when creating any new service type object (eg: soap service). I >> wanted to have this done automatically in the >> acts_as_service_versionified but the version info needs to be >> provided manually. > > To elaborate on this... > > Due to the acts_as_service_versionified, you can do something like this: > > new_soap_service = SoapService.new(params) > new_soap_service.service_version = ServiceVersion.new(params) > new_soap_service.save # Should save both objects transactionally > > Note (1): if the .save fails due to validation errors in the model, > the assignment of the ServiceVersion to the SoapService. > > Note (2): we need to also create a new Service container object if > this is the first version, and do something like: > > s = Service.create(params) # Automatically creates AND saves the > object to the db. > s.service_versions << new_soap_service.service_version # This will > save the association to the db (and set the foreign key > appropriately); Will return false if this fails. > > Note (3): I'm in the process of adding all the necessary ActiveRecord > validations in the models. > > Jits > > > > Jiten Bhagat wrote: >> Hi Eric, >> >> It shouldn't have any effect on *create* and on an *update* it just >> updates the parent ServiceVersion so that it's updated_at time is >> updated accordingly. >> >> Note you will need to create the parent ServiceVersion model object >> when creating any new service type object (eg: soap service). I >> wanted to have this done automatically in the >> acts_as_service_versionified but the version info needs to be >> provided manually. >> >> Cheers, >> Jits >> >> >> >> >> Eric Nzuobontane wrote: >>> Hi Jits, >>> What effect is acts_as_service_versionified supposed to have on the >>> db when I create a soap_service? >>> >>> Eric >>> >>> >>> Jiten Bhagat wrote: >>>> Hi Eric, >>>> >>>> Eric Nzuobontane wrote: >>>>> >>>>>> >>>>>> At this stage when do we need to tag the repository? If we need >>>>>> to in the future it is very simple to do with SVN. >>>>>> >>>>> I suppose this is why? Well if you need to show anything to >>>>> somebody out of the developer team, it is always nice to be sure >>>>> that you are showing what you think you are showing. A tag would >>>>> give that kind of assurance. Are tags expensive in svn? We do not >>>>> have to tag if people think it is unnecessary... >>>> >>>> Ah yes, when it comes to deployment we should tag every single >>>> "release". Tags are very cheap in SVN as it doesn't actually copy >>>> anything. >>>> >>>>>>> ... but one thing I noticed was that a 'require' was needed in >>>>>>> the models that use it, which was missing for soap_service model. >>>>>> >>>>>> Ahh yes, thanks. I take it you've added this in? >>>>> yes >>>>>> >>>>>>> Should we have a developer chat on Monday, to evaluate where we >>>>>>> are? >>>>>> >>>>>> Sounds good! Say 11am-12pm skype text chat? >>>>> fine by me... >>>> >>>> Great, speak to you then. >>>> >>>> Jits >>>> >>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Eric Nzuobontane wrote: >>>>>>> Hi Guys, >>>>>>> One thing I think we should should consider doing now is tagging >>>>>>> the repository, or maybe that is done automatically? I am new to >>>>>>> subversion but I know that with cvs one needs to run cvs-tag >>>>>>> 'blah' to build a tag. >>>>>>> I have just updated my local code with Jits changes. Thanks for >>>>>>> the changes, especially to some of the field names and >>>>>>> migrations which I made... I have not had a look yet at how >>>>>>> 'acts_as_service_versionified' works but one thing I noticed was >>>>>>> that a 'require' was needed in the models that use it, which >>>>>>> was missing for soap_service model. Another thing is that the >>>>>>> 'service_type ' table was removed but the 'service_type ' model >>>>>>> still seems to be in the repository. I would think that that >>>>>>> should go as well. For my part, I have stripped out the wsdl >>>>>>> parsing function that were in soap_model and put them in a >>>>>>> module now in libs. That removes the cluttering of the model >>>>>>> which I was unhappy with... I hope to check this in today. >>>>>>> >>>>>>> Should we have a developer chat on Monday, to evaluate where we >>>>>>> are? >>>>>>> >>>>>>> Eric >>>>>>> >>>>>>> >>>>>>> >>>>>>> Jiten Bhagat wrote: >>>>>>>> Though I'm assuming that's not necessarily what we will use in >>>>>>>> the UI and URLs... because I think "service deployment" is too >>>>>>>> techy for most of our users. >>>>>>>> >>>>>>>> Jits >>>>>>>> >>>>>>>> >>>>>>>> Jiten Bhagat wrote: >>>>>>>>> Okay, I'll do that. >>>>>>>>> >>>>>>>>> Jits >>>>>>>>> >>>>>>>>> >>>>>>>>> Eric Nzuobontane wrote: >>>>>>>>>> The first comment I have is to rename 'service instance' to >>>>>>>>>> 'service deployment'. In my opinion it is easier to >>>>>>>>>> understand. So speaking in singular, a service versions, a >>>>>>>>>> version has deployments... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>> Hi guys, >>>>>>>>>>> >>>>>>>>>>> So Eric and I had a long chat today about how we could >>>>>>>>>>> incorporate the notion of "service instances" together with >>>>>>>>>>> service versions into our data model, since the same service >>>>>>>>>>> could be deployed in various places. This is following on >>>>>>>>>>> from the hackathon last week. >>>>>>>>>>> >>>>>>>>>>> As a result, we've updated the data model we are doing for >>>>>>>>>>> the pilot. Latest here: >>>>>>>>>>> http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> You'll notice there is a bit crossed out under Service >>>>>>>>>>> Instance - a table for "Service Deployments". This was a >>>>>>>>>>> mapping table between service instances and service versions >>>>>>>>>>> (ie: a many to many relationship), so we could track over >>>>>>>>>>> time what versions were deployed at what instances. However, >>>>>>>>>>> earlier Eric raised the issue of making the model too >>>>>>>>>>> perfect and complex for the pilot, so I crossed this out for >>>>>>>>>>> now and collapsed the version relationship to the service >>>>>>>>>>> instance directly (thus making it a one to many >>>>>>>>>>> relationship). This should be ok for the pilot. >>>>>>>>>>> >>>>>>>>>>> I have done the necessary db changes via migration scripts, >>>>>>>>>>> and have also created the necessary model classes together >>>>>>>>>>> with controller stubs (with Resourceful REST actions in >>>>>>>>>>> them). I'll do all the ActiveRecord model associations in >>>>>>>>>>> the morning tomorrow before the myExp hackathon and commit >>>>>>>>>>> this all. >>>>>>>>>>> >>>>>>>>>>> Let me know if you have any comments etc >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> Jits >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>> >>>>> >>> >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Fri Oct 3 10:28:01 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Fri, 03 Oct 2008 15:28:01 +0100 Subject: [BioCatalogue-developers] Latest changes to data model In-Reply-To: <48E62B7F.8070706@ebi.ac.uk> References: <48E3EC57.5030109@cs.man.ac.uk> <48E48A06.7050904@ebi.ac.uk> <48E491D5.7030609@cs.man.ac.uk> <48E495E5.1090608@cs.man.ac.uk> <48E5F927.2040405@ebi.ac.uk> <48E5FEC6.8020907@cs.man.ac.uk> <48E6059B.7060509@ebi.ac.uk> <48E60B3B.7010803@cs.man.ac.uk> <48E6143F.1090208@ebi.ac.uk> <48E61AFA.9000502@cs.man.ac.uk> <48E6262C.9080907@cs.man.ac.uk> <48E62B7F.8070706@ebi.ac.uk> Message-ID: <48E62BF1.5060004@cs.man.ac.uk> Hi Eric, Ok thanks! We'll tackle the controllers early next week. Cheers and have a good weekend! Jits Eric Nzuobontane wrote: > Hi Jits, > Thanks for the elaboration. I have committed my recent changes and > hope I have not broken anything... O:-) . I believe the soap_service > controller still needs to change to take into account the versioning > and deployments. > > Eric > > Jiten Bhagat wrote: >>> Note you will need to create the parent ServiceVersion model object >>> when creating any new service type object (eg: soap service). I >>> wanted to have this done automatically in the >>> acts_as_service_versionified but the version info needs to be >>> provided manually. >> >> To elaborate on this... >> >> Due to the acts_as_service_versionified, you can do something like this: >> >> new_soap_service = SoapService.new(params) >> new_soap_service.service_version = ServiceVersion.new(params) >> new_soap_service.save # Should save both objects transactionally >> >> Note (1): if the .save fails due to validation errors in the model, >> the assignment of the ServiceVersion to the SoapService. >> >> Note (2): we need to also create a new Service container object if >> this is the first version, and do something like: >> >> s = Service.create(params) # Automatically creates AND saves the >> object to the db. >> s.service_versions << new_soap_service.service_version # This will >> save the association to the db (and set the foreign key >> appropriately); Will return false if this fails. >> >> Note (3): I'm in the process of adding all the necessary ActiveRecord >> validations in the models. >> >> Jits >> >> >> >> Jiten Bhagat wrote: >>> Hi Eric, >>> >>> It shouldn't have any effect on *create* and on an *update* it just >>> updates the parent ServiceVersion so that it's updated_at time is >>> updated accordingly. >>> >>> Note you will need to create the parent ServiceVersion model object >>> when creating any new service type object (eg: soap service). I >>> wanted to have this done automatically in the >>> acts_as_service_versionified but the version info needs to be >>> provided manually. >>> >>> Cheers, >>> Jits >>> >>> >>> >>> >>> Eric Nzuobontane wrote: >>>> Hi Jits, >>>> What effect is acts_as_service_versionified supposed to have on the >>>> db when I create a soap_service? >>>> >>>> Eric >>>> >>>> >>>> Jiten Bhagat wrote: >>>>> Hi Eric, >>>>> >>>>> Eric Nzuobontane wrote: >>>>>> >>>>>>> >>>>>>> At this stage when do we need to tag the repository? If we need >>>>>>> to in the future it is very simple to do with SVN. >>>>>>> >>>>>> I suppose this is why? Well if you need to show anything to >>>>>> somebody out of the developer team, it is always nice to be sure >>>>>> that you are showing what you think you are showing. A tag would >>>>>> give that kind of assurance. Are tags expensive in svn? We do not >>>>>> have to tag if people think it is unnecessary... >>>>> >>>>> Ah yes, when it comes to deployment we should tag every single >>>>> "release". Tags are very cheap in SVN as it doesn't actually copy >>>>> anything. >>>>> >>>>>>>> ... but one thing I noticed was that a 'require' was needed in >>>>>>>> the models that use it, which was missing for soap_service >>>>>>>> model. >>>>>>> >>>>>>> Ahh yes, thanks. I take it you've added this in? >>>>>> yes >>>>>>> >>>>>>>> Should we have a developer chat on Monday, to evaluate where we >>>>>>>> are? >>>>>>> >>>>>>> Sounds good! Say 11am-12pm skype text chat? >>>>>> fine by me... >>>>> >>>>> Great, speak to you then. >>>>> >>>>> Jits >>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Eric Nzuobontane wrote: >>>>>>>> Hi Guys, >>>>>>>> One thing I think we should should consider doing now is >>>>>>>> tagging the repository, or maybe that is done automatically? I >>>>>>>> am new to subversion but I know that with cvs one needs to run >>>>>>>> cvs-tag 'blah' to build a tag. >>>>>>>> I have just updated my local code with Jits changes. Thanks for >>>>>>>> the changes, especially to some of the field names and >>>>>>>> migrations which I made... I have not had a look yet at how >>>>>>>> 'acts_as_service_versionified' works but one thing I noticed >>>>>>>> was that a 'require' was needed in the models that use it, >>>>>>>> which was missing for soap_service model. Another thing is >>>>>>>> that the 'service_type ' table was removed but the >>>>>>>> 'service_type ' model still seems to be in the repository. I >>>>>>>> would think that that should go as well. For my part, I have >>>>>>>> stripped out the wsdl parsing function that were in soap_model >>>>>>>> and put them in a module now in libs. That removes the >>>>>>>> cluttering of the model which I was unhappy with... I hope to >>>>>>>> check this in today. >>>>>>>> >>>>>>>> Should we have a developer chat on Monday, to evaluate where we >>>>>>>> are? >>>>>>>> >>>>>>>> Eric >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Jiten Bhagat wrote: >>>>>>>>> Though I'm assuming that's not necessarily what we will use in >>>>>>>>> the UI and URLs... because I think "service deployment" is too >>>>>>>>> techy for most of our users. >>>>>>>>> >>>>>>>>> Jits >>>>>>>>> >>>>>>>>> >>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>> Okay, I'll do that. >>>>>>>>>> >>>>>>>>>> Jits >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Eric Nzuobontane wrote: >>>>>>>>>>> The first comment I have is to rename 'service instance' to >>>>>>>>>>> 'service deployment'. In my opinion it is easier to >>>>>>>>>>> understand. So speaking in singular, a service versions, a >>>>>>>>>>> version has deployments... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Jiten Bhagat wrote: >>>>>>>>>>>> Hi guys, >>>>>>>>>>>> >>>>>>>>>>>> So Eric and I had a long chat today about how we could >>>>>>>>>>>> incorporate the notion of "service instances" together with >>>>>>>>>>>> service versions into our data model, since the same >>>>>>>>>>>> service could be deployed in various places. This is >>>>>>>>>>>> following on from the hackathon last week. >>>>>>>>>>>> >>>>>>>>>>>> As a result, we've updated the data model we are doing for >>>>>>>>>>>> the pilot. Latest here: >>>>>>>>>>>> http://www.ebi.ac.uk/ebiwiki/biocatalogue/doku.php?id=development:data_model_pilot >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> You'll notice there is a bit crossed out under Service >>>>>>>>>>>> Instance - a table for "Service Deployments". This was a >>>>>>>>>>>> mapping table between service instances and service >>>>>>>>>>>> versions (ie: a many to many relationship), so we could >>>>>>>>>>>> track over time what versions were deployed at what >>>>>>>>>>>> instances. However, earlier Eric raised the issue of making >>>>>>>>>>>> the model too perfect and complex for the pilot, so I >>>>>>>>>>>> crossed this out for now and collapsed the version >>>>>>>>>>>> relationship to the service instance directly (thus making >>>>>>>>>>>> it a one to many relationship). This should be ok for the >>>>>>>>>>>> pilot. >>>>>>>>>>>> >>>>>>>>>>>> I have done the necessary db changes via migration scripts, >>>>>>>>>>>> and have also created the necessary model classes together >>>>>>>>>>>> with controller stubs (with Resourceful REST actions in >>>>>>>>>>>> them). I'll do all the ActiveRecord model associations in >>>>>>>>>>>> the morning tomorrow before the myExp hackathon and commit >>>>>>>>>>>> this all. >>>>>>>>>>>> >>>>>>>>>>>> Let me know if you have any comments etc >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> Jits >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> BioCatalogue-developers mailing list >>>>>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>>>> >>>>>> >>>> >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > From jits at cs.man.ac.uk Tue Oct 7 08:02:52 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Tue, 07 Oct 2008 13:02:52 +0100 Subject: [BioCatalogue-developers] "Soft delete" functionality Message-ID: <48EB4FEC.9090509@cs.man.ac.uk> Hi guys, I was planning on using the acts_as_soft_deletable rails plugin so that we can have "soft deletes" in our system (ie: where things aren't actually deleted but do get filtered out from a UI and API). However, this plugin is GPL licensed, which would go against our BSD license, so we can't use it :-( I'll try and find another plugin or something else we could use. Cheers, Jits From ericnzuo at ebi.ac.uk Tue Oct 7 09:38:45 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Tue, 07 Oct 2008 14:38:45 +0100 Subject: [BioCatalogue-developers] "Soft delete" functionality In-Reply-To: <48EB4FEC.9090509@cs.man.ac.uk> References: <48EB4FEC.9090509@cs.man.ac.uk> Message-ID: <48EB6665.2090702@ebi.ac.uk> Too bad!! Jiten Bhagat wrote: > Hi guys, > > I was planning on using the acts_as_soft_deletable rails plugin so > that we can have "soft deletes" in our system (ie: where things aren't > actually deleted but do get filtered out from a UI and API). However, > this plugin is GPL licensed, which would go against our BSD license, > so we can't use it :-( > > I'll try and find another plugin or something else we could use. > > Cheers, > Jits > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Thu Oct 9 07:01:28 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Thu, 09 Oct 2008 12:01:28 +0100 Subject: [BioCatalogue-developers] New private settings file Message-ID: <48EDE488.3080507@cs.man.ac.uk> Hi guys, Btw, a while back I disabled anonymous access to the BioCat repo on rubyforge (so that people don't download pilot code just yet). Hope this is ok :-) So I have checked in a new private settings template file in \config\initializers\ called biocat.rb.pre. The idea being, similar to how we do database.pre right now and also how we do environment_private in myExperiment. So for each individual deployment of BioCatalogue (whether its our local dev ones, test ones, or live ones) we would need to copy this file and rename it to biocat.rb and configure anything inside specifically for that deployment. I've attached the myExperiment environment_private.rb to give you an idea of how we can set up base settings that can be set at "deployment time". Remember never to commit actual biocat.rb or database.yml files to the repo. Cheers, Jits -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: environment_private.rb.pre URL: From jits at cs.man.ac.uk Thu Oct 9 10:59:53 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Thu, 09 Oct 2008 15:59:53 +0100 Subject: [BioCatalogue-developers] New private settings file In-Reply-To: <48EDE488.3080507@cs.man.ac.uk> References: <48EDE488.3080507@cs.man.ac.uk> Message-ID: <48EE1C69.8060404@cs.man.ac.uk> Hi guys, I've just made a change to this, commit message: --- Renamed the private config template to biocat_private.rb.pre and added a new biocat.rb config file that will be used to initialise non-private settings required by the system (such as service types to service classes mappings). --- Jits Jiten Bhagat wrote: > Hi guys, > > Btw, a while back I disabled anonymous access to the BioCat repo on > rubyforge (so that people don't download pilot code just yet). Hope > this is ok :-) > > So I have checked in a new private settings template file in > \config\initializers\ called biocat.rb.pre. The idea being, similar to > how we do database.pre right now and also how we do > environment_private in myExperiment. So for each individual deployment > of BioCatalogue (whether its our local dev ones, test ones, or live > ones) we would need to copy this file and rename it to biocat.rb and > configure anything inside specifically for that deployment. I've > attached the myExperiment environment_private.rb to give you an idea > of how we can set up base settings that can be set at "deployment time". > > Remember never to commit actual biocat.rb or database.yml files to the > repo. > > Cheers, > Jits > ------------------------------------------------------------------------ > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From ericnzuo at ebi.ac.uk Fri Oct 10 10:10:26 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Fri, 10 Oct 2008 15:10:26 +0100 Subject: [BioCatalogue-developers] response formats In-Reply-To: <48EE1C69.8060404@cs.man.ac.uk> References: <48EDE488.3080507@cs.man.ac.uk> <48EE1C69.8060404@cs.man.ac.uk> Message-ID: <48EF6252.7060601@ebi.ac.uk> Hi Guys, there is something I learnt today... It is that with 2.+ the ' respond_to do |format| ' block is no longer necessary in the controllers to render different formats from the same action. The controller actions we have at the moment do all have these blocks. Should we go the current rails way and remove them? The advantage is that if we are adding feeds for example, we do not need to add that format to the controllers. All that is needed is to name the rendered templates appropriately. I do not know yet what the downside is... Eric Jiten Bhagat wrote: > Hi guys, > > I've just made a change to this, commit message: > > --- > Renamed the private config template to biocat_private.rb.pre and added > a new biocat.rb config file that will be used to initialise > non-private settings required by the system (such as service types to > service classes mappings). > --- > > Jits > > > > Jiten Bhagat wrote: >> Hi guys, >> >> Btw, a while back I disabled anonymous access to the BioCat repo on >> rubyforge (so that people don't download pilot code just yet). Hope >> this is ok :-) >> >> So I have checked in a new private settings template file in >> \config\initializers\ called biocat.rb.pre. The idea being, similar >> to how we do database.pre right now and also how we do >> environment_private in myExperiment. So for each individual >> deployment of BioCatalogue (whether its our local dev ones, test >> ones, or live ones) we would need to copy this file and rename it to >> biocat.rb and configure anything inside specifically for that >> deployment. I've attached the myExperiment environment_private.rb to >> give you an idea of how we can set up base settings that can be set >> at "deployment time". >> >> Remember never to commit actual biocat.rb or database.yml files to >> the repo. >> >> Cheers, >> Jits >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Fri Oct 10 11:06:10 2008 From: jits at cs.man.ac.uk (jits at cs.man.ac.uk) Date: Fri, 10 Oct 2008 16:06:10 +0100 (BST) Subject: [BioCatalogue-developers] response formats In-Reply-To: <48EF6252.7060601@ebi.ac.uk> References: <48EDE488.3080507@cs.man.ac.uk> <48EE1C69.8060404@cs.man.ac.uk> <48EF6252.7060601@ebi.ac.uk> Message-ID: <428bac345f76574b4917cf5b1bc82d8e.squirrel@webmail.cs.man.ac.uk> Hi Eric, Interesting, didn't know they had made this a convention in Rails 2.0. I'd still want to explicitly do respond_to for 2 reasons: 1) This way we can temporarily "switch off" certain formats if need be (ASSUMING that formats you don't specify within the respond_to don't get rendered automatically; alternatively we could cause a 404 to be generated in the format.xxx { }). 2) In some cases we need to take different actions than rendering (eg: in error cases. A good example is the create action of the services controller that I did the other day... # POST /services # POST /services.xml def create # Creation of a Service resource is not allowed. Must be created as part of the creation of a specific service type resource. flash[:error] = 'Select the type of service you would like to submit' respond_to do |format| format.html { redirect_to(new_service_url) } format.xml { render :xml => '', :status => 406 } end end .. in this case we could have also removed the format.xml (I think) which would hopefully cause a 404, but a 406 is more descriptive (action not authorised i think). In general, having the formats explicitly shown may be useful info for long term maintenance? Cheers, Jits > Hi Guys, > there is something I learnt today... It is that with 2.+ the ' > respond_to do |format| ' block is no longer necessary in the > controllers to render different formats from the same action. The > controller actions we have at the moment do all have these blocks. > Should we go the current rails way and remove them? The advantage is > that if we are adding feeds for example, we do not need to add that > format to the controllers. All that is needed is to name the rendered > templates appropriately. I do not know yet what the downside is... > > Eric > > > > Jiten Bhagat wrote: >> Hi guys, >> >> I've just made a change to this, commit message: >> >> --- >> Renamed the private config template to biocat_private.rb.pre and added >> a new biocat.rb config file that will be used to initialise >> non-private settings required by the system (such as service types to >> service classes mappings). >> --- >> >> Jits >> >> >> >> Jiten Bhagat wrote: >>> Hi guys, >>> >>> Btw, a while back I disabled anonymous access to the BioCat repo on >>> rubyforge (so that people don't download pilot code just yet). Hope >>> this is ok :-) >>> >>> So I have checked in a new private settings template file in >>> \config\initializers\ called biocat.rb.pre. The idea being, similar >>> to how we do database.pre right now and also how we do >>> environment_private in myExperiment. So for each individual >>> deployment of BioCatalogue (whether its our local dev ones, test >>> ones, or live ones) we would need to copy this file and rename it to >>> biocat.rb and configure anything inside specifically for that >>> deployment. I've attached the myExperiment environment_private.rb to >>> give you an idea of how we can set up base settings that can be set >>> at "deployment time". >>> >>> Remember never to commit actual biocat.rb or database.yml files to >>> the repo. >>> >>> Cheers, >>> Jits >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > > From noreply at rubyforge.org Sat Oct 11 18:10:50 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 11 Oct 2008 18:10:50 -0400 (EDT) Subject: [BioCatalogue-developers] [Task #2412] Catch mail send exception Message-ID: <20081011221050.BBF2E185818C@rubyforge.org> Task #2412 has been updated. Project: BioCatalogue Subproject: Pilot Summary: Catch mail send exception Complete: 0% Status: Open Description: When sending the account activation email, if the mail sending fails then an exception is thrown and the user will get a generic error. We need to catch this exception and take appropriate action (such as logging the error so that the mail can be sent manually later). The user shouldn't need to know that the exception was ever raised. ------------------------------------------------------- For more info, visit: http://rubyforge.org/pm/task.php?func=detailtask&project_task_id=2412&group_id=6901&group_project_id=12540 From ericnzuo at ebi.ac.uk Mon Oct 13 04:59:27 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 13 Oct 2008 09:59:27 +0100 Subject: [BioCatalogue-developers] response formats In-Reply-To: <428bac345f76574b4917cf5b1bc82d8e.squirrel@webmail.cs.man.ac.uk> References: <48EDE488.3080507@cs.man.ac.uk> <48EE1C69.8060404@cs.man.ac.uk> <48EF6252.7060601@ebi.ac.uk> <428bac345f76574b4917cf5b1bc82d8e.squirrel@webmail.cs.man.ac.uk> Message-ID: <48F30DEF.9090402@ebi.ac.uk> Hi Jits, I see your point and I agree with you, that from a maintenance point of view, it is better to have the response blocks in the actions. And as you said, we can better control the behavior of our actions rather than open them up to all sorts of formats we may not be handling properly... Eric jits at cs.man.ac.uk wrote: > Hi Eric, > > Interesting, didn't know they had made this a convention in Rails 2.0. > > I'd still want to explicitly do respond_to for 2 reasons: > > 1) This way we can temporarily "switch off" certain formats if need be > (ASSUMING that formats you don't specify within the respond_to don't get > rendered automatically; alternatively we could cause a 404 to be generated > in the format.xxx { }). > > 2) In some cases we need to take different actions than rendering (eg: in > error cases. A good example is the create action of the services > controller that I did the other day... > > # POST /services > # POST /services.xml > def create > # Creation of a Service resource is not allowed. Must be created as > part of the creation of a specific service type resource. > flash[:error] = 'Select the type of service you would like to submit' > respond_to do |format| > format.html { redirect_to(new_service_url) } > format.xml { render :xml => '', :status => 406 } > end > end > > .. in this case we could have also removed the format.xml (I think) which > would hopefully cause a 404, but a 406 is more descriptive (action not > authorised i think). > > In general, having the formats explicitly shown may be useful info for > long term maintenance? > > Cheers, > Jits > > >> Hi Guys, >> there is something I learnt today... It is that with 2.+ the ' >> respond_to do |format| ' block is no longer necessary in the >> controllers to render different formats from the same action. The >> controller actions we have at the moment do all have these blocks. >> Should we go the current rails way and remove them? The advantage is >> that if we are adding feeds for example, we do not need to add that >> format to the controllers. All that is needed is to name the rendered >> templates appropriately. I do not know yet what the downside is... >> >> Eric >> >> >> >> Jiten Bhagat wrote: >> >>> Hi guys, >>> >>> I've just made a change to this, commit message: >>> >>> --- >>> Renamed the private config template to biocat_private.rb.pre and added >>> a new biocat.rb config file that will be used to initialise >>> non-private settings required by the system (such as service types to >>> service classes mappings). >>> --- >>> >>> Jits >>> >>> >>> >>> Jiten Bhagat wrote: >>> >>>> Hi guys, >>>> >>>> Btw, a while back I disabled anonymous access to the BioCat repo on >>>> rubyforge (so that people don't download pilot code just yet). Hope >>>> this is ok :-) >>>> >>>> So I have checked in a new private settings template file in >>>> \config\initializers\ called biocat.rb.pre. The idea being, similar >>>> to how we do database.pre right now and also how we do >>>> environment_private in myExperiment. So for each individual >>>> deployment of BioCatalogue (whether its our local dev ones, test >>>> ones, or live ones) we would need to copy this file and rename it to >>>> biocat.rb and configure anything inside specifically for that >>>> deployment. I've attached the myExperiment environment_private.rb to >>>> give you an idea of how we can set up base settings that can be set >>>> at "deployment time". >>>> >>>> Remember never to commit actual biocat.rb or database.yml files to >>>> the repo. >>>> >>>> Cheers, >>>> Jits >>>> ------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >> > > -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From ericnzuo at ebi.ac.uk Mon Oct 13 06:44:43 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 13 Oct 2008 11:44:43 +0100 Subject: [BioCatalogue-developers] will_paginate gem Message-ID: <48F3269B.9050107@ebi.ac.uk> Hi Guys, For pagination I installed the will_paginate gem locally. I will like to commit this but would require that u both install the gem otherwise the code will break. I want to add this to the wiki page where we are documenting the plugins and gems used. http://github.com/mislav/will_paginate/wikis Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From tlaurent at ebi.ac.uk Mon Oct 13 06:48:53 2008 From: tlaurent at ebi.ac.uk (Thomas Laurent) Date: Mon, 13 Oct 2008 11:48:53 +0100 Subject: [BioCatalogue-developers] will_paginate gem In-Reply-To: <48F3269B.9050107@ebi.ac.uk> References: <48F3269B.9050107@ebi.ac.uk> Message-ID: <48F32795.6060506@ebi.ac.uk> I've used will_paginate in another project, that's a must have for a Rails 2.x application. Good one Eric. Thomas Eric Nzuobontane wrote: > Hi Guys, > For pagination I installed the will_paginate gem locally. I will like to > commit this but would require that u both install the gem otherwise the > code will break. I want to add this to the wiki page where we are > documenting the plugins and gems used. > > http://github.com/mislav/will_paginate/wikis > > Eric > > > ------------------------------------------------------------------------ > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From tlaurent at ebi.ac.uk Mon Oct 13 06:51:49 2008 From: tlaurent at ebi.ac.uk (Thomas Laurent) Date: Mon, 13 Oct 2008 11:51:49 +0100 Subject: [BioCatalogue-developers] will_paginate gem In-Reply-To: <48F32795.6060506@ebi.ac.uk> References: <48F3269B.9050107@ebi.ac.uk> <48F32795.6060506@ebi.ac.uk> Message-ID: <48F32845.1030304@ebi.ac.uk> ...oups, I forgot why I was replying in the 1st place :-( Eric, if you install the plug-in, it should then be in /vendor/plugins, so if you check it in, we can check it out next time we check out some code. Thomas Thomas Laurent wrote: > I've used will_paginate in another project, that's a must have for a > Rails 2.x application. Good one Eric. > > Thomas > > Eric Nzuobontane wrote: >> Hi Guys, >> For pagination I installed the will_paginate gem locally. I will like >> to commit this but would require that u both install the gem otherwise >> the code will break. I want to add this to the wiki page where we are >> documenting the plugins and gems used. >> >> http://github.com/mislav/will_paginate/wikis >> >> Eric >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > From ericnzuo at ebi.ac.uk Mon Oct 13 06:52:55 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 13 Oct 2008 11:52:55 +0100 Subject: [BioCatalogue-developers] will_paginate gem In-Reply-To: <48F32795.6060506@ebi.ac.uk> References: <48F3269B.9050107@ebi.ac.uk> <48F32795.6060506@ebi.ac.uk> Message-ID: <48F32887.4010203@ebi.ac.uk> great! :) Thomas Laurent wrote: > I've used will_paginate in another project, that's a must have for a > Rails 2.x application. Good one Eric. > > Thomas > > Eric Nzuobontane wrote: >> Hi Guys, >> For pagination I installed the will_paginate gem locally. I will like >> to commit this but would require that u both install the gem >> otherwise the code will break. I want to add this to the wiki page >> where we are documenting the plugins and gems used. >> >> http://github.com/mislav/will_paginate/wikis >> >> Eric >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Mon Oct 13 06:59:56 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 11:59:56 +0100 Subject: [BioCatalogue-developers] will_paginate gem In-Reply-To: <48F32845.1030304@ebi.ac.uk> References: <48F3269B.9050107@ebi.ac.uk> <48F32795.6060506@ebi.ac.uk> <48F32845.1030304@ebi.ac.uk> Message-ID: <48F32A2C.3080204@cs.man.ac.uk> Hi Eric, Nice one! If it's the gem version then this *can* be committed to the codebase by adding it under /vendor/gems/ in which case the app will use that instead of looking in the machine's gem repository (might need to do some configuration in environment.rb though). If it's the plugin version then... what Thomas said..... :-) Jits Thomas Laurent wrote: > ...oups, I forgot why I was replying in the 1st place :-( > Eric, if you install the plug-in, it should then be in > /vendor/plugins, so if you check it in, we can check it out next time > we check out some code. > > Thomas > > Thomas Laurent wrote: >> I've used will_paginate in another project, that's a must have for a >> Rails 2.x application. Good one Eric. >> >> Thomas >> >> Eric Nzuobontane wrote: >>> Hi Guys, >>> For pagination I installed the will_paginate gem locally. I will >>> like to commit this but would require that u both install the gem >>> otherwise the code will break. I want to add this to the wiki page >>> where we are documenting the plugins and gems used. >>> >>> http://github.com/mislav/will_paginate/wikis >>> >>> Eric >>> >>> >>> ------------------------------------------------------------------------ >>> >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From ericnzuo at ebi.ac.uk Mon Oct 13 07:08:03 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 13 Oct 2008 12:08:03 +0100 Subject: [BioCatalogue-developers] will_paginate gem In-Reply-To: <48F32A2C.3080204@cs.man.ac.uk> References: <48F3269B.9050107@ebi.ac.uk> <48F32795.6060506@ebi.ac.uk> <48F32845.1030304@ebi.ac.uk> <48F32A2C.3080204@cs.man.ac.uk> Message-ID: <48F32C13.7060306@ebi.ac.uk> It is the gem version. For the plugins, I understood what Thomas said. But for the gems, I was not sure. I see that in myExperiment, there is only the Taverna gem in the vendor/gem directory. I am sure it is not the only gem used. Why are you doing it both ways there? I did not quite understand how to install the gem in /vendor/gem. Eric Jiten Bhagat wrote: > Hi Eric, > > Nice one! > > If it's the gem version then this *can* be committed to the codebase > by adding it under /vendor/gems/ in which case the app will use that > instead of looking in the machine's gem repository (might need to do > some configuration in environment.rb though). > > If it's the plugin version then... what Thomas said..... :-) > > Jits > > > > Thomas Laurent wrote: >> ...oups, I forgot why I was replying in the 1st place :-( >> Eric, if you install the plug-in, it should then be in >> /vendor/plugins, so if you check it in, we can check it out next time >> we check out some code. >> >> Thomas >> >> Thomas Laurent wrote: >>> I've used will_paginate in another project, that's a must have for a >>> Rails 2.x application. Good one Eric. >>> >>> Thomas >>> >>> Eric Nzuobontane wrote: >>>> Hi Guys, >>>> For pagination I installed the will_paginate gem locally. I will >>>> like to commit this but would require that u both install the gem >>>> otherwise the code will break. I want to add this to the wiki page >>>> where we are documenting the plugins and gems used. >>>> >>>> http://github.com/mislav/will_paginate/wikis >>>> >>>> Eric >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Mon Oct 13 07:29:59 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 12:29:59 +0100 Subject: [BioCatalogue-developers] will_paginate gem In-Reply-To: <48F32C13.7060306@ebi.ac.uk> References: <48F3269B.9050107@ebi.ac.uk> <48F32795.6060506@ebi.ac.uk> <48F32845.1030304@ebi.ac.uk> <48F32A2C.3080204@cs.man.ac.uk> <48F32C13.7060306@ebi.ac.uk> Message-ID: <48F33137.3040500@cs.man.ac.uk> Hi Eric, Eric Nzuobontane wrote: > It is the gem version. For the plugins, I understood what Thomas said. > But for the gems, I was not sure. I see that in myExperiment, there is > only the Taverna gem in the vendor/gem directory. I am sure it is not > the only gem used. Why are you doing it both ways there? Good question. In myExperiment we have been planning on "snapshotting" all gems we use into the vendor folder but part of the reason for not doing it is that it really bulks up the codebase. So we only do this for gems that either cant be obtained from the net, or for gems that we need specific versions of. When someone "installs" myExperiment we get them to install the dependant gems (see: http://wiki.myexperiment.org/index.php/Developer:Installation). > > I did not quite understand how to install the gem in /vendor/gem. Sounds like we don't need to install any gems in /vendor/gems/... we can just set it as a dependency... see here: http://ryandaigle.com/articles/2008/4/1/what-s-new-in-edge-rails-gem-dependencies. This reduces the bulk on the codebase so might be a better way of doing things. Jits > > Eric > > > Jiten Bhagat wrote: >> Hi Eric, >> >> Nice one! >> >> If it's the gem version then this *can* be committed to the codebase >> by adding it under /vendor/gems/ in which case the app will use that >> instead of looking in the machine's gem repository (might need to do >> some configuration in environment.rb though). >> >> If it's the plugin version then... what Thomas said..... :-) >> >> Jits >> >> >> >> Thomas Laurent wrote: >>> ...oups, I forgot why I was replying in the 1st place :-( >>> Eric, if you install the plug-in, it should then be in >>> /vendor/plugins, so if you check it in, we can check it out next >>> time we check out some code. >>> >>> Thomas >>> >>> Thomas Laurent wrote: >>>> I've used will_paginate in another project, that's a must have for >>>> a Rails 2.x application. Good one Eric. >>>> >>>> Thomas >>>> >>>> Eric Nzuobontane wrote: >>>>> Hi Guys, >>>>> For pagination I installed the will_paginate gem locally. I will >>>>> like to commit this but would require that u both install the gem >>>>> otherwise the code will break. I want to add this to the wiki page >>>>> where we are documenting the plugins and gems used. >>>>> >>>>> http://github.com/mislav/will_paginate/wikis >>>>> >>>>> Eric >>>>> >>>>> >>>>> ------------------------------------------------------------------------ >>>>> >>>>> >>>>> _______________________________________________ >>>>> BioCatalogue-developers mailing list >>>>> BioCatalogue-developers at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > From jits at cs.man.ac.uk Mon Oct 13 07:33:47 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 12:33:47 +0100 Subject: [BioCatalogue-developers] will_paginate gem In-Reply-To: <48F33137.3040500@cs.man.ac.uk> References: <48F3269B.9050107@ebi.ac.uk> <48F32795.6060506@ebi.ac.uk> <48F32845.1030304@ebi.ac.uk> <48F32A2C.3080204@cs.man.ac.uk> <48F32C13.7060306@ebi.ac.uk> <48F33137.3040500@cs.man.ac.uk> Message-ID: <48F3321B.2050400@cs.man.ac.uk> Alternatively, if using gem dependencies is over kill for now then you can just unpack the will_paginate gem into vendor/gems and the app should automatically be able to use it (as rails will initialise it automatically I think). Jits Jiten Bhagat wrote: > Hi Eric, > > Eric Nzuobontane wrote: >> It is the gem version. For the plugins, I understood what Thomas >> said. But for the gems, I was not sure. I see that in myExperiment, >> there is only the Taverna gem in the vendor/gem directory. I am sure >> it is not the only gem used. Why are you doing it both ways there? > > Good question. In myExperiment we have been planning on "snapshotting" > all gems we use into the vendor folder but part of the reason for not > doing it is that it really bulks up the codebase. So we only do this > for gems that either cant be obtained from the net, or for gems that > we need specific versions of. > > When someone "installs" myExperiment we get them to install the > dependant gems (see: > http://wiki.myexperiment.org/index.php/Developer:Installation). > >> >> I did not quite understand how to install the gem in /vendor/gem. > > Sounds like we don't need to install any gems in /vendor/gems/... we > can just set it as a dependency... see here: > http://ryandaigle.com/articles/2008/4/1/what-s-new-in-edge-rails-gem-dependencies. > This reduces the bulk on the codebase so might be a better way of > doing things. > > Jits > >> >> Eric >> >> >> Jiten Bhagat wrote: >>> Hi Eric, >>> >>> Nice one! >>> >>> If it's the gem version then this *can* be committed to the codebase >>> by adding it under /vendor/gems/ in which case the app will use that >>> instead of looking in the machine's gem repository (might need to do >>> some configuration in environment.rb though). >>> >>> If it's the plugin version then... what Thomas said..... :-) >>> >>> Jits >>> >>> >>> >>> Thomas Laurent wrote: >>>> ...oups, I forgot why I was replying in the 1st place :-( >>>> Eric, if you install the plug-in, it should then be in >>>> /vendor/plugins, so if you check it in, we can check it out next >>>> time we check out some code. >>>> >>>> Thomas >>>> >>>> Thomas Laurent wrote: >>>>> I've used will_paginate in another project, that's a must have for >>>>> a Rails 2.x application. Good one Eric. >>>>> >>>>> Thomas >>>>> >>>>> Eric Nzuobontane wrote: >>>>>> Hi Guys, >>>>>> For pagination I installed the will_paginate gem locally. I will >>>>>> like to commit this but would require that u both install the gem >>>>>> otherwise the code will break. I want to add this to the wiki >>>>>> page where we are documenting the plugins and gems used. >>>>>> >>>>>> http://github.com/mislav/will_paginate/wikis >>>>>> >>>>>> Eric >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------ >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> BioCatalogue-developers mailing list >>>>>> BioCatalogue-developers at rubyforge.org >>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>> >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From ericnzuo at ebi.ac.uk Mon Oct 13 08:22:38 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 13 Oct 2008 13:22:38 +0100 Subject: [BioCatalogue-developers] will_paginate gem In-Reply-To: <48F3321B.2050400@cs.man.ac.uk> References: <48F3269B.9050107@ebi.ac.uk> <48F32795.6060506@ebi.ac.uk> <48F32845.1030304@ebi.ac.uk> <48F32A2C.3080204@cs.man.ac.uk> <48F32C13.7060306@ebi.ac.uk> <48F33137.3040500@cs.man.ac.uk> <48F3321B.2050400@cs.man.ac.uk> Message-ID: <48F33D8E.10006@ebi.ac.uk> I am installing the plugin for the code base. I liked the idea for the gem for myself as it meant I only install it once and can use for several projects... Eric Jiten Bhagat wrote: > Alternatively, if using gem dependencies is over kill for now then you > can just unpack the will_paginate gem into vendor/gems and the app > should automatically be able to use it (as rails will initialise it > automatically I think). > > Jits > > > > Jiten Bhagat wrote: >> Hi Eric, >> >> Eric Nzuobontane wrote: >>> It is the gem version. For the plugins, I understood what Thomas >>> said. But for the gems, I was not sure. I see that in myExperiment, >>> there is only the Taverna gem in the vendor/gem directory. I am sure >>> it is not the only gem used. Why are you doing it both ways there? >> >> Good question. In myExperiment we have been planning on >> "snapshotting" all gems we use into the vendor folder but part of the >> reason for not doing it is that it really bulks up the codebase. So >> we only do this for gems that either cant be obtained from the net, >> or for gems that we need specific versions of. >> >> When someone "installs" myExperiment we get them to install the >> dependant gems (see: >> http://wiki.myexperiment.org/index.php/Developer:Installation). >> >>> >>> I did not quite understand how to install the gem in /vendor/gem. >> >> Sounds like we don't need to install any gems in /vendor/gems/... we >> can just set it as a dependency... see here: >> http://ryandaigle.com/articles/2008/4/1/what-s-new-in-edge-rails-gem-dependencies. >> This reduces the bulk on the codebase so might be a better way of >> doing things. >> >> Jits >> >>> >>> Eric >>> >>> >>> Jiten Bhagat wrote: >>>> Hi Eric, >>>> >>>> Nice one! >>>> >>>> If it's the gem version then this *can* be committed to the >>>> codebase by adding it under /vendor/gems/ in which case the app >>>> will use that instead of looking in the machine's gem repository >>>> (might need to do some configuration in environment.rb though). >>>> >>>> If it's the plugin version then... what Thomas said..... :-) >>>> >>>> Jits >>>> >>>> >>>> >>>> Thomas Laurent wrote: >>>>> ...oups, I forgot why I was replying in the 1st place :-( >>>>> Eric, if you install the plug-in, it should then be in >>>>> /vendor/plugins, so if you check it in, we can check it out next >>>>> time we check out some code. >>>>> >>>>> Thomas >>>>> >>>>> Thomas Laurent wrote: >>>>>> I've used will_paginate in another project, that's a must have >>>>>> for a Rails 2.x application. Good one Eric. >>>>>> >>>>>> Thomas >>>>>> >>>>>> Eric Nzuobontane wrote: >>>>>>> Hi Guys, >>>>>>> For pagination I installed the will_paginate gem locally. I will >>>>>>> like to commit this but would require that u both install the >>>>>>> gem otherwise the code will break. I want to add this to the >>>>>>> wiki page where we are documenting the plugins and gems used. >>>>>>> >>>>>>> http://github.com/mislav/will_paginate/wikis >>>>>>> >>>>>>> Eric >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------ >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> BioCatalogue-developers mailing list >>>>>>> BioCatalogue-developers at rubyforge.org >>>>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>>>> >>>>> _______________________________________________ >>>>> BioCatalogue-developers mailing list >>>>> BioCatalogue-developers at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From noreply at rubyforge.org Mon Oct 13 08:18:04 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 13 Oct 2008 08:18:04 -0400 (EDT) Subject: [BioCatalogue-developers] [Task #2413] Secure delete actions Message-ID: <20081013121804.83DB318581AE@rubyforge.org> Task #2413 has been updated. Project: BioCatalogue Subproject: Pilot Summary: Secure delete actions Complete: 0% Status: Open Description: Need to secure/disable all delete actions on resources ------------------------------------------------------- For more info, visit: http://rubyforge.org/pm/task.php?func=detailtask&project_task_id=2413&group_id=6901&group_project_id=12540 From ericnzuo at ebi.ac.uk Mon Oct 13 08:51:11 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 13 Oct 2008 13:51:11 +0100 Subject: [BioCatalogue-developers] trashable error Message-ID: <48F3443F.3060908@ebi.ac.uk> I am hitting this when I try to delete a record. Is this configurable like one could say you actually want to delete? Mysql::Error: Table 'biocatalogue_development.trash_records' doesn't exist: SHOW FIELDS FROM `trash_records` |RAILS_ROOT: C:/Documents and Settings/ericnzuo/My Documents/Aptana Studio/biocatalogue| Application Trace | Framework Trace | Full Trace |C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract_adapter.rb:147:in `log' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/mysql_adapter.rb:302:in `execute' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/mysql_adapter.rb:433:in `columns' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/base.rb:1149:in `columns' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/base.rb:2616:in `attributes_from_column_definition_without_lock' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/locking/optimistic.rb:55:in `attributes_from_column_definition' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/base.rb:2137:in `initialize' vendor/plugins/acts_as_trashable/lib/trash_record.rb:7:in `initialize' vendor/plugins/acts_as_trashable/lib/acts_as_trashable.rb:39:in `new' vendor/plugins/acts_as_trashable/lib/acts_as_trashable.rb:39:in `destroy' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/database_statements.rb:66:in `transaction' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/transactions.rb:79:in `transaction' vendor/plugins/acts_as_trashable/lib/acts_as_trashable.rb:38:in `destroy' app/controllers/soap_services_controller.rb:86:in `destroy' | -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Mon Oct 13 08:53:57 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 13:53:57 +0100 Subject: [BioCatalogue-developers] trashable error In-Reply-To: <48F3443F.3060908@ebi.ac.uk> References: <48F3443F.3060908@ebi.ac.uk> Message-ID: <48F344E5.60701@cs.man.ac.uk> You need to run db:migrate to update your db schema.... Jits Eric Nzuobontane wrote: > I am hitting this when I try to delete a record. Is this configurable > like one could say you actually want to delete? > > Mysql::Error: Table 'biocatalogue_development.trash_records' doesn't exist: SHOW FIELDS FROM `trash_records` > > |RAILS_ROOT: C:/Documents and Settings/ericnzuo/My Documents/Aptana > Studio/biocatalogue| > > Application Trace | > Framework Trace | Full > Trace > |C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract_adapter.rb:147:in `log' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/mysql_adapter.rb:302:in `execute' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/mysql_adapter.rb:433:in `columns' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/base.rb:1149:in `columns' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/base.rb:2616:in `attributes_from_column_definition_without_lock' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/locking/optimistic.rb:55:in `attributes_from_column_definition' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/base.rb:2137:in `initialize' > vendor/plugins/acts_as_trashable/lib/trash_record.rb:7:in `initialize' > vendor/plugins/acts_as_trashable/lib/acts_as_trashable.rb:39:in `new' > vendor/plugins/acts_as_trashable/lib/acts_as_trashable.rb:39:in `destroy' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/database_statements.rb:66:in `transaction' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/transactions.rb:79:in `transaction' > vendor/plugins/acts_as_trashable/lib/acts_as_trashable.rb:38:in `destroy' > app/controllers/soap_services_controller.rb:86:in `destroy' > | > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > From ericnzuo at ebi.ac.uk Mon Oct 13 08:55:28 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 13 Oct 2008 13:55:28 +0100 Subject: [BioCatalogue-developers] trashable error In-Reply-To: <48F3443F.3060908@ebi.ac.uk> References: <48F3443F.3060908@ebi.ac.uk> Message-ID: <48F34540.5080107@ebi.ac.uk> my problem!! I did not run the migrations. Sorry for the spam... Eric Nzuobontane wrote: > I am hitting this when I try to delete a record. Is this configurable > like one could say you actually want to delete? > > Mysql::Error: Table 'biocatalogue_development.trash_records' doesn't exist: SHOW FIELDS FROM `trash_records` > > |RAILS_ROOT: C:/Documents and Settings/ericnzuo/My Documents/Aptana > Studio/biocatalogue| > > Application Trace | > Framework Trace | Full > Trace > |C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract_adapter.rb:147:in `log' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/mysql_adapter.rb:302:in `execute' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/mysql_adapter.rb:433:in `columns' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/base.rb:1149:in `columns' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/base.rb:2616:in `attributes_from_column_definition_without_lock' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/locking/optimistic.rb:55:in `attributes_from_column_definition' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/base.rb:2137:in `initialize' > vendor/plugins/acts_as_trashable/lib/trash_record.rb:7:in `initialize' > vendor/plugins/acts_as_trashable/lib/acts_as_trashable.rb:39:in `new' > vendor/plugins/acts_as_trashable/lib/acts_as_trashable.rb:39:in `destroy' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/database_statements.rb:66:in `transaction' > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/transactions.rb:79:in `transaction' > vendor/plugins/acts_as_trashable/lib/acts_as_trashable.rb:38:in `destroy' > app/controllers/soap_services_controller.rb:86:in `destroy' > | > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From ericnzuo at ebi.ac.uk Mon Oct 13 09:11:11 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 13 Oct 2008 14:11:11 +0100 Subject: [BioCatalogue-developers] I may have broken the code Message-ID: <48F348EF.6030304@ebi.ac.uk> I am getting this error in my output window. It is not a show stopper but I am not too sure where that is comming from Processing SoapServicesController#images (for 127.0.0.1 at 2008-10-13 14:05:09) [GET] Session ID: c7a5dfbe4423b96f784676a3f6a0a36a Parameters: {"format"=>"gif", "action"=>"images", "id"=>"close", "controller"=>"soap_services"} ActionController::UnknownAction (No action responded to images): C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:579:in `call_filters' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:572:in `perform_action_without_benchmark' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' C:/Tools/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/rescue.rb:201:in `perform_action_without_caching' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:13:in `perform_action' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in `cache' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/query_cache.rb:8:in `cache' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:12:in `perform_action' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in `send' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in `process_without_filters' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:568:in `process_without_session_management_support' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/session_management.rb:130:in `process' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:389:in `process' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:149:in `handle_request' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:107:in `dispatch' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in `synchronize' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in `dispatch' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:120:in `dispatch_cgi' C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:35:in `dispatch' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:76:in `process' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in `synchronize' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in `process' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:159:in `process_client' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in `each' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in `process_client' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in `run' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in `initialize' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in `new' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in `run' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in `initialize' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in `new' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in `run' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:282:in `run' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in `each' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in `run' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:128:in `run' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/command.rb:212:in `run' C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281 C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in `load' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in `load' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in `new_constants_in' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in `load' C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/servers/mongrel.rb:64 C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in `require' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in `new_constants_in' C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in `require' C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/server.rb:39 C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' ./script/server:3 -e:2:in `load' -e:2 Rendering C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb (not_found) gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb (not_found) -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From tlaurent at ebi.ac.uk Mon Oct 13 09:15:30 2008 From: tlaurent at ebi.ac.uk (Thomas Laurent) Date: Mon, 13 Oct 2008 14:15:30 +0100 Subject: [BioCatalogue-developers] I may have broken the code In-Reply-To: <48F348EF.6030304@ebi.ac.uk> References: <48F348EF.6030304@ebi.ac.uk> Message-ID: <48F349F2.2030202@ebi.ac.uk> Hum, looks like it's complaining about the "close" button from the login box (unless you've added a similar image somewhere else...). Could you check you have the image close.gif in your /public/images directory ? Eric Nzuobontane wrote: > I am getting this error in my output window. It is not a show stopper > but I am not too sure where that is comming from > > Processing SoapServicesController#images (for 127.0.0.1 at 2008-10-13 > 14:05:09) [GET] > Session ID: c7a5dfbe4423b96f784676a3f6a0a36a > Parameters: {"format"=>"gif", "action"=>"images", "id"=>"close", > "controller"=>"soap_services"} > > > ActionController::UnknownAction (No action responded to images): > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:579:in > `call_filters' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:572:in > `perform_action_without_benchmark' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in > `perform_action_without_rescue' > C:/Tools/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in > `perform_action_without_rescue' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/rescue.rb:201:in > `perform_action_without_caching' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:13:in > `perform_action' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in > `cache' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/query_cache.rb:8:in > `cache' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:12:in > `perform_action' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in > `send' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in > `process_without_filters' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:568:in > `process_without_session_management_support' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/session_management.rb:130:in > `process' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:389:in > `process' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:149:in > `handle_request' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:107:in > `dispatch' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in > `synchronize' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in > `dispatch' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:120:in > `dispatch_cgi' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:35:in > `dispatch' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:76:in > `process' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in > `synchronize' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in > `process' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:159:in > `process_client' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in > `each' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in > `process_client' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in > `run' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in > `initialize' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in > `new' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in > `run' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in > `initialize' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in > `new' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in > `run' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:282:in > `run' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in > `each' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in > `run' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:128:in > `run' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/command.rb:212:in > `run' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281 > > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in > `load' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in > `load' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in > `new_constants_in' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in > `load' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/servers/mongrel.rb:64 > > C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in > `gem_original_require' > C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in > `require' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in > `require' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in > `new_constants_in' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in > `require' > > C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/server.rb:39 > C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in > `gem_original_require' > C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in > `require' > ./script/server:3 > -e:2:in `load' > -e:2 > > Rendering > C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb > (not_found) > gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb > (not_found) > > > ------------------------------------------------------------------------ > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From jits at cs.man.ac.uk Mon Oct 13 09:19:53 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 14:19:53 +0100 Subject: [BioCatalogue-developers] I may have broken the code In-Reply-To: <48F349F2.2030202@ebi.ac.uk> References: <48F348EF.6030304@ebi.ac.uk> <48F349F2.2030202@ebi.ac.uk> Message-ID: <48F34AF9.5010405@cs.man.ac.uk> As an aside.... to render images that reside in /public/images/, you can use something like: <%= image_tag "spinner.gif", :id => "spinner", :style => "display: none; float: right; vertical-align: top;" -%> Jits Thomas Laurent wrote: > Hum, looks like it's complaining about the "close" button from the > login box (unless you've added a similar image somewhere else...). > Could you check you have the image close.gif in your /public/images > directory ? > > > Eric Nzuobontane wrote: >> I am getting this error in my output window. It is not a show >> stopper but I am not too sure where that is comming from >> >> Processing SoapServicesController#images (for 127.0.0.1 at 2008-10-13 >> 14:05:09) [GET] >> Session ID: c7a5dfbe4423b96f784676a3f6a0a36a >> Parameters: {"format"=>"gif", "action"=>"images", "id"=>"close", >> "controller"=>"soap_services"} >> >> >> ActionController::UnknownAction (No action responded to images): >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:579:in >> `call_filters' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:572:in >> `perform_action_without_benchmark' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >> `perform_action_without_rescue' >> C:/Tools/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >> `perform_action_without_rescue' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/rescue.rb:201:in >> `perform_action_without_caching' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:13:in >> `perform_action' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in >> `cache' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/query_cache.rb:8:in >> `cache' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:12:in >> `perform_action' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >> `send' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >> `process_without_filters' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:568:in >> `process_without_session_management_support' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/session_management.rb:130:in >> `process' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:389:in >> `process' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:149:in >> `handle_request' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:107:in >> `dispatch' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >> `synchronize' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >> `dispatch' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:120:in >> `dispatch_cgi' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:35:in >> `dispatch' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:76:in >> `process' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >> `synchronize' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >> `process' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:159:in >> `process_client' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >> `each' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >> `process_client' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >> `initialize' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >> `new' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >> `initialize' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >> `new' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:282:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >> `each' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:128:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/command.rb:212:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281 >> >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >> `load' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >> `load' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >> `new_constants_in' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >> `load' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/servers/mongrel.rb:64 >> >> >> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >> `gem_original_require' >> >> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >> `require' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >> `require' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >> `new_constants_in' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >> `require' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/server.rb:39 >> >> >> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >> `gem_original_require' >> >> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >> `require' >> ./script/server:3 >> -e:2:in `load' >> -e:2 >> >> Rendering >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >> (not_found) >> gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >> (not_found) >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From ericnzuo at ebi.ac.uk Mon Oct 13 09:22:02 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 13 Oct 2008 14:22:02 +0100 Subject: [BioCatalogue-developers] I may have broken the code In-Reply-To: <48F349F2.2030202@ebi.ac.uk> References: <48F348EF.6030304@ebi.ac.uk> <48F349F2.2030202@ebi.ac.uk> Message-ID: <48F34B7A.700@ebi.ac.uk> I do have that file. I have not added any similar image, no... Should the soap_service_controller have an images action? Eric Thomas Laurent wrote: > Hum, looks like it's complaining about the "close" button from the > login box (unless you've added a similar image somewhere else...). > Could you check you have the image close.gif in your /public/images > directory ? > > > Eric Nzuobontane wrote: >> I am getting this error in my output window. It is not a show >> stopper but I am not too sure where that is comming from >> >> Processing SoapServicesController#images (for 127.0.0.1 at 2008-10-13 >> 14:05:09) [GET] >> Session ID: c7a5dfbe4423b96f784676a3f6a0a36a >> Parameters: {"format"=>"gif", "action"=>"images", "id"=>"close", >> "controller"=>"soap_services"} >> >> >> ActionController::UnknownAction (No action responded to images): >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:579:in >> `call_filters' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:572:in >> `perform_action_without_benchmark' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >> `perform_action_without_rescue' >> C:/Tools/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >> `perform_action_without_rescue' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/rescue.rb:201:in >> `perform_action_without_caching' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:13:in >> `perform_action' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in >> `cache' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/query_cache.rb:8:in >> `cache' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:12:in >> `perform_action' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >> `send' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >> `process_without_filters' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:568:in >> `process_without_session_management_support' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/session_management.rb:130:in >> `process' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:389:in >> `process' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:149:in >> `handle_request' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:107:in >> `dispatch' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >> `synchronize' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >> `dispatch' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:120:in >> `dispatch_cgi' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:35:in >> `dispatch' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:76:in >> `process' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >> `synchronize' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >> `process' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:159:in >> `process_client' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >> `each' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >> `process_client' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >> `initialize' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >> `new' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >> `initialize' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >> `new' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:282:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >> `each' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:128:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/command.rb:212:in >> `run' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281 >> >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >> `load' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >> `load' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >> `new_constants_in' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >> `load' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/servers/mongrel.rb:64 >> >> >> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >> `gem_original_require' >> >> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >> `require' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >> `require' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >> `new_constants_in' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >> `require' >> >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/server.rb:39 >> >> >> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >> `gem_original_require' >> >> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >> `require' >> ./script/server:3 >> -e:2:in `load' >> -e:2 >> >> Rendering >> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >> (not_found) >> gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >> (not_found) >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Mon Oct 13 09:24:54 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 14:24:54 +0100 Subject: [BioCatalogue-developers] I may have broken the code In-Reply-To: <48F34B7A.700@ebi.ac.uk> References: <48F348EF.6030304@ebi.ac.uk> <48F349F2.2030202@ebi.ac.uk> <48F34B7A.700@ebi.ac.uk> Message-ID: <48F34C26.9050106@cs.man.ac.uk> Hi Eric, Eric Nzuobontane wrote: > I do have that file. I have not added any similar image, no... Should > the soap_service_controller have an images action? No it shouldn't. This could be caused by bad forming of the URL. Have you done an SVN update as I recall seeing Thomas updating something to do with images, last week. Cheers, Jits > > Eric > > Thomas Laurent wrote: >> Hum, looks like it's complaining about the "close" button from the >> login box (unless you've added a similar image somewhere else...). >> Could you check you have the image close.gif in your /public/images >> directory ? >> >> >> Eric Nzuobontane wrote: >>> I am getting this error in my output window. It is not a show >>> stopper but I am not too sure where that is comming from >>> >>> Processing SoapServicesController#images (for 127.0.0.1 at >>> 2008-10-13 14:05:09) [GET] >>> Session ID: c7a5dfbe4423b96f784676a3f6a0a36a >>> Parameters: {"format"=>"gif", "action"=>"images", "id"=>"close", >>> "controller"=>"soap_services"} >>> >>> >>> ActionController::UnknownAction (No action responded to images): >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:579:in >>> `call_filters' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:572:in >>> `perform_action_without_benchmark' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >>> `perform_action_without_rescue' >>> C:/Tools/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >>> `perform_action_without_rescue' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/rescue.rb:201:in >>> `perform_action_without_caching' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:13:in >>> `perform_action' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in >>> `cache' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/query_cache.rb:8:in >>> `cache' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:12:in >>> `perform_action' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >>> `send' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >>> `process_without_filters' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:568:in >>> `process_without_session_management_support' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/session_management.rb:130:in >>> `process' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:389:in >>> `process' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:149:in >>> `handle_request' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:107:in >>> `dispatch' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >>> `synchronize' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >>> `dispatch' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:120:in >>> `dispatch_cgi' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:35:in >>> `dispatch' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:76:in >>> `process' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >>> `synchronize' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >>> `process' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:159:in >>> `process_client' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >>> `each' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >>> `process_client' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>> `initialize' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>> `new' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>> `initialize' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>> `new' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:282:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >>> `each' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:128:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/command.rb:212:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281 >>> >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>> `load' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>> `load' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >>> `new_constants_in' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>> `load' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/servers/mongrel.rb:64 >>> >>> >>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>> `gem_original_require' >>> >>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>> `require' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >>> `require' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >>> `new_constants_in' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >>> `require' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/server.rb:39 >>> >>> >>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>> `gem_original_require' >>> >>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>> `require' >>> ./script/server:3 >>> -e:2:in `load' >>> -e:2 >>> >>> Rendering >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >>> (not_found) >>> gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >>> (not_found) >>> >>> >>> ------------------------------------------------------------------------ >>> >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > From tlaurent at ebi.ac.uk Mon Oct 13 09:26:53 2008 From: tlaurent at ebi.ac.uk (Thomas Laurent) Date: Mon, 13 Oct 2008 14:26:53 +0100 Subject: [BioCatalogue-developers] I may have broken the code In-Reply-To: <48F34B7A.700@ebi.ac.uk> References: <48F348EF.6030304@ebi.ac.uk> <48F349F2.2030202@ebi.ac.uk> <48F34B7A.700@ebi.ac.uk> Message-ID: <48F34C9D.8040302@ebi.ac.uk> weird error... Do you know what that reminds me ? Restart Aptana... Eric Nzuobontane wrote: > I do have that file. I have not added any similar image, no... Should > the soap_service_controller have an images action? > > Eric > > Thomas Laurent wrote: >> Hum, looks like it's complaining about the "close" button from the >> login box (unless you've added a similar image somewhere else...). >> Could you check you have the image close.gif in your /public/images >> directory ? >> >> >> Eric Nzuobontane wrote: >>> I am getting this error in my output window. It is not a show >>> stopper but I am not too sure where that is comming from >>> >>> Processing SoapServicesController#images (for 127.0.0.1 at 2008-10-13 >>> 14:05:09) [GET] >>> Session ID: c7a5dfbe4423b96f784676a3f6a0a36a >>> Parameters: {"format"=>"gif", "action"=>"images", "id"=>"close", >>> "controller"=>"soap_services"} >>> >>> >>> ActionController::UnknownAction (No action responded to images): >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:579:in >>> `call_filters' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:572:in >>> `perform_action_without_benchmark' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >>> `perform_action_without_rescue' >>> C:/Tools/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >>> `perform_action_without_rescue' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/rescue.rb:201:in >>> `perform_action_without_caching' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:13:in >>> `perform_action' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in >>> `cache' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/query_cache.rb:8:in >>> `cache' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:12:in >>> `perform_action' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >>> `send' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >>> `process_without_filters' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:568:in >>> `process_without_session_management_support' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/session_management.rb:130:in >>> `process' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:389:in >>> `process' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:149:in >>> `handle_request' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:107:in >>> `dispatch' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >>> `synchronize' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >>> `dispatch' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:120:in >>> `dispatch_cgi' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:35:in >>> `dispatch' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:76:in >>> `process' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >>> `synchronize' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >>> `process' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:159:in >>> `process_client' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >>> `each' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >>> `process_client' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>> `initialize' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>> `new' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>> `initialize' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>> `new' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:282:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >>> `each' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:128:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/command.rb:212:in >>> `run' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281 >>> >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>> `load' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>> `load' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >>> `new_constants_in' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>> `load' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/servers/mongrel.rb:64 >>> >>> >>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>> `gem_original_require' >>> >>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>> `require' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >>> `require' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >>> `new_constants_in' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >>> `require' >>> >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/server.rb:39 >>> >>> >>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>> `gem_original_require' >>> >>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>> `require' >>> ./script/server:3 >>> -e:2:in `load' >>> -e:2 >>> >>> Rendering >>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >>> (not_found) >>> gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >>> (not_found) >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > From ericnzuo at ebi.ac.uk Mon Oct 13 09:27:05 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 13 Oct 2008 14:27:05 +0100 Subject: [BioCatalogue-developers] I may have broken the code In-Reply-To: <48F34C26.9050106@cs.man.ac.uk> References: <48F348EF.6030304@ebi.ac.uk> <48F349F2.2030202@ebi.ac.uk> <48F34B7A.700@ebi.ac.uk> <48F34C26.9050106@cs.man.ac.uk> Message-ID: <48F34CA9.7020303@ebi.ac.uk> I always do an update before checking in anything, and generally every morning... Eric Jiten Bhagat wrote: > Hi Eric, > > Eric Nzuobontane wrote: >> I do have that file. I have not added any similar image, no... Should >> the soap_service_controller have an images action? > > No it shouldn't. > > This could be caused by bad forming of the URL. Have you done an SVN > update as I recall seeing Thomas updating something to do with images, > last week. > > Cheers, > Jits > >> >> Eric >> >> Thomas Laurent wrote: >>> Hum, looks like it's complaining about the "close" button from the >>> login box (unless you've added a similar image somewhere else...). >>> Could you check you have the image close.gif in your /public/images >>> directory ? >>> >>> >>> Eric Nzuobontane wrote: >>>> I am getting this error in my output window. It is not a show >>>> stopper but I am not too sure where that is comming from >>>> >>>> Processing SoapServicesController#images (for 127.0.0.1 at >>>> 2008-10-13 14:05:09) [GET] >>>> Session ID: c7a5dfbe4423b96f784676a3f6a0a36a >>>> Parameters: {"format"=>"gif", "action"=>"images", "id"=>"close", >>>> "controller"=>"soap_services"} >>>> >>>> >>>> ActionController::UnknownAction (No action responded to images): >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:579:in >>>> `call_filters' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:572:in >>>> `perform_action_without_benchmark' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >>>> `perform_action_without_rescue' >>>> C:/Tools/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >>>> `perform_action_without_rescue' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/rescue.rb:201:in >>>> `perform_action_without_caching' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:13:in >>>> `perform_action' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in >>>> `cache' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/query_cache.rb:8:in >>>> `cache' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:12:in >>>> `perform_action' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >>>> `send' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >>>> `process_without_filters' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:568:in >>>> `process_without_session_management_support' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/session_management.rb:130:in >>>> `process' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:389:in >>>> `process' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:149:in >>>> `handle_request' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:107:in >>>> `dispatch' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >>>> `synchronize' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >>>> `dispatch' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:120:in >>>> `dispatch_cgi' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:35:in >>>> `dispatch' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:76:in >>>> `process' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >>>> `synchronize' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >>>> `process' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:159:in >>>> `process_client' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >>>> `each' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >>>> `process_client' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>> `initialize' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>> `new' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>>> `initialize' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>>> `new' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:282:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >>>> `each' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:128:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/command.rb:212:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281 >>>> >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>>> `load' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>>> `load' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >>>> `new_constants_in' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>>> `load' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/servers/mongrel.rb:64 >>>> >>>> >>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>> `gem_original_require' >>>> >>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>> `require' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >>>> `require' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >>>> `new_constants_in' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >>>> `require' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/server.rb:39 >>>> >>>> >>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>> `gem_original_require' >>>> >>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>> `require' >>>> ./script/server:3 >>>> -e:2:in `load' >>>> -e:2 >>>> >>>> Rendering >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >>>> (not_found) >>>> gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >>>> (not_found) >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Mon Oct 13 09:34:13 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 14:34:13 +0100 Subject: [BioCatalogue-developers] I may have broken the code In-Reply-To: <48F34CA9.7020303@ebi.ac.uk> References: <48F348EF.6030304@ebi.ac.uk> <48F349F2.2030202@ebi.ac.uk> <48F34B7A.700@ebi.ac.uk> <48F34C26.9050106@cs.man.ac.uk> <48F34CA9.7020303@ebi.ac.uk> Message-ID: <48F34E55.1050803@cs.man.ac.uk> Ok cool :-) Eric Nzuobontane wrote: > I always do an update before checking in anything, and generally every > morning... > > Eric > > > > Jiten Bhagat wrote: >> Hi Eric, >> >> Eric Nzuobontane wrote: >>> I do have that file. I have not added any similar image, no... >>> Should the soap_service_controller have an images action? >> >> No it shouldn't. >> >> This could be caused by bad forming of the URL. Have you done an SVN >> update as I recall seeing Thomas updating something to do with >> images, last week. >> >> Cheers, >> Jits >> >>> >>> Eric >>> >>> Thomas Laurent wrote: >>>> Hum, looks like it's complaining about the "close" button from the >>>> login box (unless you've added a similar image somewhere else...). >>>> Could you check you have the image close.gif in your /public/images >>>> directory ? >>>> >>>> >>>> Eric Nzuobontane wrote: >>>>> I am getting this error in my output window. It is not a show >>>>> stopper but I am not too sure where that is comming from >>>>> >>>>> Processing SoapServicesController#images (for 127.0.0.1 at >>>>> 2008-10-13 14:05:09) [GET] >>>>> Session ID: c7a5dfbe4423b96f784676a3f6a0a36a >>>>> Parameters: {"format"=>"gif", "action"=>"images", "id"=>"close", >>>>> "controller"=>"soap_services"} >>>>> >>>>> >>>>> ActionController::UnknownAction (No action responded to images): >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:579:in >>>>> `call_filters' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:572:in >>>>> `perform_action_without_benchmark' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >>>>> `perform_action_without_rescue' >>>>> C:/Tools/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >>>>> `perform_action_without_rescue' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/rescue.rb:201:in >>>>> `perform_action_without_caching' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:13:in >>>>> `perform_action' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in >>>>> `cache' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/query_cache.rb:8:in >>>>> `cache' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:12:in >>>>> `perform_action' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >>>>> `send' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >>>>> `process_without_filters' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:568:in >>>>> `process_without_session_management_support' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/session_management.rb:130:in >>>>> `process' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:389:in >>>>> `process' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:149:in >>>>> `handle_request' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:107:in >>>>> `dispatch' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >>>>> `synchronize' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >>>>> `dispatch' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:120:in >>>>> `dispatch_cgi' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:35:in >>>>> `dispatch' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:76:in >>>>> `process' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >>>>> `synchronize' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >>>>> `process' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:159:in >>>>> `process_client' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >>>>> `each' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >>>>> `process_client' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>>> `initialize' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>>> `new' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>>>> `initialize' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>>>> `new' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:282:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >>>>> `each' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:128:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/command.rb:212:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281 >>>>> >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>>>> `load' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>>>> `load' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >>>>> `new_constants_in' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>>>> `load' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/servers/mongrel.rb:64 >>>>> >>>>> >>>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>>> `gem_original_require' >>>>> >>>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>>> `require' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >>>>> `require' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >>>>> `new_constants_in' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >>>>> `require' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/server.rb:39 >>>>> >>>>> >>>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>>> `gem_original_require' >>>>> >>>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>>> `require' >>>>> ./script/server:3 >>>>> -e:2:in `load' >>>>> -e:2 >>>>> >>>>> Rendering >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >>>>> (not_found) >>>>> gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >>>>> (not_found) >>>>> >>>>> >>>>> ------------------------------------------------------------------------ >>>>> >>>>> >>>>> _______________________________________________ >>>>> BioCatalogue-developers mailing list >>>>> BioCatalogue-developers at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> > From jits at cs.man.ac.uk Mon Oct 13 09:42:55 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 14:42:55 +0100 Subject: [BioCatalogue-developers] bulk actions Message-ID: <48F3505F.10607@cs.man.ac.uk> Hi Eric, Just noticed the bulk submit actions.... would you like me to register these in the routes as well (together with the current work I am doing)? Jits From ericnzuo at ebi.ac.uk Mon Oct 13 09:46:12 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 13 Oct 2008 14:46:12 +0100 Subject: [BioCatalogue-developers] bulk actions In-Reply-To: <48F3505F.10607@cs.man.ac.uk> References: <48F3505F.10607@cs.man.ac.uk> Message-ID: <48F35124.7090509@ebi.ac.uk> Actually thought, I had taken that out of the repository because it was not working properly. Can you still find that in the repository? Eric Jiten Bhagat wrote: > Hi Eric, > > Just noticed the bulk submit actions.... would you like me to register > these in the routes as well (together with the current work I am doing)? > > Jits > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Mon Oct 13 09:48:45 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 14:48:45 +0100 Subject: [BioCatalogue-developers] bulk actions In-Reply-To: <48F35124.7090509@ebi.ac.uk> References: <48F3505F.10607@cs.man.ac.uk> <48F35124.7090509@ebi.ac.uk> Message-ID: <48F351BD.6000907@cs.man.ac.uk> Ahh, my eyes were playing tricks on me! I was looking at the wrong side of the SVN compare, d'oh!! I think they weren't working before they were declared inside of the create action, rather than declared at the controller level. Jits Eric Nzuobontane wrote: > Actually thought, I had taken that out of the repository because it > was not working properly. Can you still find that in the repository? > > Eric > > Jiten Bhagat wrote: >> Hi Eric, >> >> Just noticed the bulk submit actions.... would you like me to >> register these in the routes as well (together with the current work >> I am doing)? >> >> Jits >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > From ericnzuo at ebi.ac.uk Mon Oct 13 09:57:15 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 13 Oct 2008 14:57:15 +0100 Subject: [BioCatalogue-developers] bulk actions In-Reply-To: <48F351BD.6000907@cs.man.ac.uk> References: <48F3505F.10607@cs.man.ac.uk> <48F35124.7090509@ebi.ac.uk> <48F351BD.6000907@cs.man.ac.uk> Message-ID: <48F353BB.5000905@ebi.ac.uk> apparently yes! :'( But I wanted to check that they were fine before I check them in.... Jiten Bhagat wrote: > Ahh, my eyes were playing tricks on me! > > I was looking at the wrong side of the SVN compare, d'oh!! > > I think they weren't working before they were declared inside of the > create action, rather than declared at the controller level. > > Jits > > > Eric Nzuobontane wrote: >> Actually thought, I had taken that out of the repository because it >> was not working properly. Can you still find that in the repository? >> >> Eric >> >> Jiten Bhagat wrote: >>> Hi Eric, >>> >>> Just noticed the bulk submit actions.... would you like me to >>> register these in the routes as well (together with the current work >>> I am doing)? >>> >>> Jits >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Mon Oct 13 10:02:57 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 15:02:57 +0100 Subject: [BioCatalogue-developers] bulk actions In-Reply-To: <48F353BB.5000905@ebi.ac.uk> References: <48F3505F.10607@cs.man.ac.uk> <48F35124.7090509@ebi.ac.uk> <48F351BD.6000907@cs.man.ac.uk> <48F353BB.5000905@ebi.ac.uk> Message-ID: <48F35511.3050805@cs.man.ac.uk> Makes sense... Eric Nzuobontane wrote: > apparently yes! :'( But I wanted to check that they were fine > before I check them in.... > > Jiten Bhagat wrote: >> Ahh, my eyes were playing tricks on me! >> >> I was looking at the wrong side of the SVN compare, d'oh!! >> >> I think they weren't working before they were declared inside of the >> create action, rather than declared at the controller level. >> >> Jits >> >> >> Eric Nzuobontane wrote: >>> Actually thought, I had taken that out of the repository because it >>> was not working properly. Can you still find that in the repository? >>> >>> Eric >>> >>> Jiten Bhagat wrote: >>>> Hi Eric, >>>> >>>> Just noticed the bulk submit actions.... would you like me to >>>> register these in the routes as well (together with the current >>>> work I am doing)? >>>> >>>> Jits >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> > From jits at cs.man.ac.uk Mon Oct 13 10:13:47 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 15:13:47 +0100 Subject: [BioCatalogue-developers] I may have broken the code In-Reply-To: <48F34C9D.8040302@ebi.ac.uk> References: <48F348EF.6030304@ebi.ac.uk> <48F349F2.2030202@ebi.ac.uk> <48F34B7A.700@ebi.ac.uk> <48F34C9D.8040302@ebi.ac.uk> Message-ID: <48F3579B.4020604@cs.man.ac.uk> I get this error too... In a couple of minutes will commit a fix to this (have to use "image_tag" helper)... I've also moved the login stuff into partials in /app/views/widgets/ Jits Thomas Laurent wrote: > weird error... > Do you know what that reminds me ? Restart Aptana... > > > Eric Nzuobontane wrote: >> I do have that file. I have not added any similar image, no... Should >> the soap_service_controller have an images action? >> >> Eric >> >> Thomas Laurent wrote: >>> Hum, looks like it's complaining about the "close" button from the >>> login box (unless you've added a similar image somewhere else...). >>> Could you check you have the image close.gif in your /public/images >>> directory ? >>> >>> >>> Eric Nzuobontane wrote: >>>> I am getting this error in my output window. It is not a show >>>> stopper but I am not too sure where that is comming from >>>> >>>> Processing SoapServicesController#images (for 127.0.0.1 at >>>> 2008-10-13 14:05:09) [GET] >>>> Session ID: c7a5dfbe4423b96f784676a3f6a0a36a >>>> Parameters: {"format"=>"gif", "action"=>"images", "id"=>"close", >>>> "controller"=>"soap_services"} >>>> >>>> >>>> ActionController::UnknownAction (No action responded to images): >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:579:in >>>> `call_filters' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:572:in >>>> `perform_action_without_benchmark' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >>>> `perform_action_without_rescue' >>>> C:/Tools/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >>>> `perform_action_without_rescue' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/rescue.rb:201:in >>>> `perform_action_without_caching' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:13:in >>>> `perform_action' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in >>>> `cache' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/query_cache.rb:8:in >>>> `cache' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:12:in >>>> `perform_action' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >>>> `send' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >>>> `process_without_filters' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:568:in >>>> `process_without_session_management_support' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/session_management.rb:130:in >>>> `process' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:389:in >>>> `process' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:149:in >>>> `handle_request' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:107:in >>>> `dispatch' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >>>> `synchronize' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >>>> `dispatch' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:120:in >>>> `dispatch_cgi' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:35:in >>>> `dispatch' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:76:in >>>> `process' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >>>> `synchronize' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >>>> `process' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:159:in >>>> `process_client' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >>>> `each' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >>>> `process_client' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>> `initialize' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>> `new' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>>> `initialize' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>>> `new' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:282:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >>>> `each' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:128:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/command.rb:212:in >>>> `run' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281 >>>> >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>>> `load' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>>> `load' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >>>> `new_constants_in' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>>> `load' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/servers/mongrel.rb:64 >>>> >>>> >>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>> `gem_original_require' >>>> >>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>> `require' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >>>> `require' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >>>> `new_constants_in' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >>>> `require' >>>> >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/server.rb:39 >>>> >>>> >>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>> `gem_original_require' >>>> >>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>> `require' >>>> ./script/server:3 >>>> -e:2:in `load' >>>> -e:2 >>>> >>>> Rendering >>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >>>> (not_found) >>>> gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >>>> (not_found) >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From noreply at rubyforge.org Mon Oct 13 10:14:24 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 13 Oct 2008 10:14:24 -0400 (EDT) Subject: [BioCatalogue-developers] [Task #2415] Login shouldn't redirect to users index page Message-ID: <20081013141424.BF54518581B8@rubyforge.org> Task #2415 has been updated. Project: BioCatalogue Subproject: Pilot Summary: Login shouldn't redirect to users index page Complete: 0% Status: Open Description: When you login using the login widget at the top of the page, it should take you back to the page you were on. ------------------------------------------------------- For more info, visit: http://rubyforge.org/pm/task.php?func=detailtask&project_task_id=2415&group_id=6901&group_project_id=12540 From jits at cs.man.ac.uk Mon Oct 13 10:20:26 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 15:20:26 +0100 Subject: [BioCatalogue-developers] I may have broken the code In-Reply-To: <48F3579B.4020604@cs.man.ac.uk> References: <48F348EF.6030304@ebi.ac.uk> <48F349F2.2030202@ebi.ac.uk> <48F34B7A.700@ebi.ac.uk> <48F34C9D.8040302@ebi.ac.uk> <48F3579B.4020604@cs.man.ac.uk> Message-ID: <48F3592A.4040908@cs.man.ac.uk> Committed... Jiten Bhagat wrote: > I get this error too... > > In a couple of minutes will commit a fix to this (have to use > "image_tag" helper)... I've also moved the login stuff into partials > in /app/views/widgets/ > > Jits > > > > Thomas Laurent wrote: >> weird error... >> Do you know what that reminds me ? Restart Aptana... >> >> >> Eric Nzuobontane wrote: >>> I do have that file. I have not added any similar image, no... >>> Should the soap_service_controller have an images action? >>> >>> Eric >>> >>> Thomas Laurent wrote: >>>> Hum, looks like it's complaining about the "close" button from the >>>> login box (unless you've added a similar image somewhere else...). >>>> Could you check you have the image close.gif in your /public/images >>>> directory ? >>>> >>>> >>>> Eric Nzuobontane wrote: >>>>> I am getting this error in my output window. It is not a show >>>>> stopper but I am not too sure where that is comming from >>>>> >>>>> Processing SoapServicesController#images (for 127.0.0.1 at >>>>> 2008-10-13 14:05:09) [GET] >>>>> Session ID: c7a5dfbe4423b96f784676a3f6a0a36a >>>>> Parameters: {"format"=>"gif", "action"=>"images", "id"=>"close", >>>>> "controller"=>"soap_services"} >>>>> >>>>> >>>>> ActionController::UnknownAction (No action responded to images): >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:579:in >>>>> `call_filters' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:572:in >>>>> `perform_action_without_benchmark' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >>>>> `perform_action_without_rescue' >>>>> C:/Tools/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/benchmarking.rb:68:in >>>>> `perform_action_without_rescue' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/rescue.rb:201:in >>>>> `perform_action_without_caching' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:13:in >>>>> `perform_action' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in >>>>> `cache' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activerecord-2.1.1/lib/active_record/query_cache.rb:8:in >>>>> `cache' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/caching/sql_cache.rb:12:in >>>>> `perform_action' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >>>>> `send' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:529:in >>>>> `process_without_filters' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/filters.rb:568:in >>>>> `process_without_session_management_support' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/session_management.rb:130:in >>>>> `process' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/base.rb:389:in >>>>> `process' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:149:in >>>>> `handle_request' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:107:in >>>>> `dispatch' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >>>>> `synchronize' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:104:in >>>>> `dispatch' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:120:in >>>>> `dispatch_cgi' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/dispatcher.rb:35:in >>>>> `dispatch' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:76:in >>>>> `process' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >>>>> `synchronize' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:74:in >>>>> `process' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:159:in >>>>> `process_client' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >>>>> `each' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in >>>>> `process_client' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>>> `initialize' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>>> `new' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>>>> `initialize' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>>>> `new' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:282:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >>>>> `each' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:128:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/command.rb:212:in >>>>> `run' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281 >>>>> >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>>>> `load' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>>>> `load' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >>>>> `new_constants_in' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:503:in >>>>> `load' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/servers/mongrel.rb:64 >>>>> >>>>> >>>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>>> `gem_original_require' >>>>> >>>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>>> `require' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >>>>> `require' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:355:in >>>>> `new_constants_in' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.1/lib/active_support/dependencies.rb:510:in >>>>> `require' >>>>> >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/rails-2.1.1/lib/commands/server.rb:39 >>>>> >>>>> >>>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>>> `gem_original_require' >>>>> >>>>> C:/Tools/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in >>>>> `require' >>>>> ./script/server:3 >>>>> -e:2:in `load' >>>>> -e:2 >>>>> >>>>> Rendering >>>>> C:/Tools/ruby/lib/ruby/gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >>>>> (not_found) >>>>> gems/1.8/gems/actionpack-2.1.1/lib/action_controller/templates/rescues/layout.erb >>>>> (not_found) >>>>> >>>>> >>>>> ------------------------------------------------------------------------ >>>>> >>>>> >>>>> _______________________________________________ >>>>> BioCatalogue-developers mailing list >>>>> BioCatalogue-developers at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From noreply at rubyforge.org Mon Oct 13 10:42:15 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 13 Oct 2008 10:42:15 -0400 (EDT) Subject: [BioCatalogue-developers] [Task #2416] Refactor out the wsdl_file from soap_services Message-ID: <20081013144215.B155F15B801C@rubyforge.org> Task #2416 has been updated. Project: BioCatalogue Subproject: Pilot Summary: Refactor out the wsdl_file from soap_services Complete: 0% Status: Open Description: ... use a similar mechanism to the content_blobs in myExperiment. ------------------------------------------------------- For more info, visit: http://rubyforge.org/pm/task.php?func=detailtask&project_task_id=2416&group_id=6901&group_project_id=12540 From jits at cs.man.ac.uk Mon Oct 13 10:54:08 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 15:54:08 +0100 Subject: [BioCatalogue-developers] Initial work on service submission UI Message-ID: <48F36110.8010309@cs.man.ac.uk> Hi guys, I've just committed some intial work on the service submission UI. Commit message: --- Initial work on the UI (and subsequent controller actions) for service submission, mainly SOAP service submission. Still to do is getting the load_wsdl action to populate an @soap_service object and then populate the web form accordingly. After which the create process needs to be done. --- I decided to commit this early so that you could see the approach being taken and I will now need to work with Eric on hooking up the WSDL parsing and then the service creation (that's a hint for you to log onto skype Eric ;-)) Cheers, Jits From jits at cs.man.ac.uk Mon Oct 13 12:20:12 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Mon, 13 Oct 2008 17:20:12 +0100 Subject: [BioCatalogue-developers] Initial work on service submission UI In-Reply-To: <48F36110.8010309@cs.man.ac.uk> References: <48F36110.8010309@cs.man.ac.uk> Message-ID: <48F3753C.6050204@cs.man.ac.uk> Forgot to add a screenshot.. now attached... Jits Jiten Bhagat wrote: > Hi guys, > > I've just committed some intial work on the service submission UI. > Commit message: > > --- > Initial work on the UI (and subsequent controller actions) for service > submission, mainly SOAP service submission. Still to do is getting the > load_wsdl action to populate an @soap_service object and then populate > the web form accordingly. After which the create process needs to be > done. > --- > > I decided to commit this early so that you could see the approach > being taken and I will now need to work with Eric on hooking up the > WSDL parsing and then the service creation (that's a hint for you to > log onto skype Eric ;-)) > > Cheers, > Jits > > -------------- next part -------------- A non-text attachment was scrubbed... Name: 20081013-1548.png Type: image/png Size: 23436 bytes Desc: not available URL: From noreply at rubyforge.org Mon Oct 13 19:21:18 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 13 Oct 2008 19:21:18 -0400 (EDT) Subject: [BioCatalogue-developers] [68] trunk/config/routes.rb: Test commit to check if email notification on commits is working. Message-ID: <20081013232118.3300D18585B4@rubyforge.org> An HTML attachment was scrubbed... URL: From jits at cs.man.ac.uk Mon Oct 13 19:35:03 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Tue, 14 Oct 2008 00:35:03 +0100 Subject: [BioCatalogue-developers] [68] trunk/config/routes.rb: Test commit to check if email notification on commits is working. In-Reply-To: <20081013232118.3300D18585B4@rubyforge.org> References: <20081013232118.3300D18585B4@rubyforge.org> Message-ID: <48F3DB27.6080305@cs.man.ac.uk> Hi guys, As you can see, I finally got post commit emails working for our codebase :-) :-) :-) For future reference... http://rubyforge.org/docman/view.php/5/460/faq.html#syncmail .. BUT, you need to ensure you have line continuation characters, eg: svnnotify --repos-path "$REPOS" --revision "$REV" --svnlook /usr/local/bin/svnlook vs svnnotify --repos-path "$REPOS" --revision "$REV" \ --svnlook /usr/local/bin/svnlook Jits noreply at rubyforge.org wrote: > > Revision > 68 > Author > jits > Date > 2008-10-13 19:21:17 -0400 (Mon, 13 Oct 2008) > > > Log Message > > Test commit to check if email notification on commits is working. > > > Modified Paths > > * trunk/config/routes.rb <#trunkconfigroutesrb> > > > Diff > > > Modified: trunk/config/routes.rb (67 => 68) > > > --- trunk/config/routes.rb 2008-10-13 14:50:45 UTC (rev 67) > +++ trunk/config/routes.rb 2008-10-13 23:21:17 UTC (rev 68) > @@ -2,7 +2,7 @@ > map.resources :service_deployments > > map.resources :service_versions > - > + > map.resources :users, :collection => { :activate_account => :get } > map.resource :session > > ------------------------------------------------------------------------ > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > From ericnzuo at ebi.ac.uk Tue Oct 14 04:50:32 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Tue, 14 Oct 2008 09:50:32 +0100 Subject: [BioCatalogue-developers] demo today? Message-ID: <48F45D58.8080907@ebi.ac.uk> Hi Guys, Rodrigo is working from home today, meaning he will not be able to see the demo should we decide to have one. Thomas and I had a chat earlier and we think it is better to do any demo when both Rodrigo and Carole are available. The suggestion is that we should try to show something to them at the end of this week. Anyone has anything against us moving the meeting to Friday then? Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Tue Oct 14 05:14:50 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Tue, 14 Oct 2008 10:14:50 +0100 Subject: [BioCatalogue-developers] demo today? In-Reply-To: <48F45D58.8080907@ebi.ac.uk> References: <48F45D58.8080907@ebi.ac.uk> Message-ID: <48F4630A.4070403@cs.man.ac.uk> This is fine (and convenient) for me. Just need to let Franck know about a potential rescheduling. Jits Eric Nzuobontane wrote: > Hi Guys, > Rodrigo is working from home today, meaning he will not be able to see > the demo should we decide to have one. Thomas and I had a chat earlier > and we think it is better to do any demo when both Rodrigo and Carole > are available. The suggestion is that we should try to show something > to them at the end of this week. Anyone has anything against us moving > the meeting to Friday then? > > Eric > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > From noreply at rubyforge.org Tue Oct 14 06:32:23 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 14 Oct 2008 06:32:23 -0400 (EDT) Subject: [BioCatalogue-developers] [69] trunk/public/stylesheets/styles_2.css: styles for new design Message-ID: <20081014103223.CCE3518585AD@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 14 06:33:52 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 14 Oct 2008 06:33:52 -0400 (EDT) Subject: [BioCatalogue-developers] [70] trunk/public/javascripts/application.js: changed the open/ close js for the login box for the new design Message-ID: <20081014103352.D612318585B4@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 14 06:39:19 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 14 Oct 2008 06:39:19 -0400 (EDT) Subject: [BioCatalogue-developers] [71] trunk/public/images: images for new design Message-ID: <20081014103919.66C9C18585AD@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 14 06:40:54 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 14 Oct 2008 06:40:54 -0400 (EDT) Subject: [BioCatalogue-developers] [72] trunk/config/routes.rb: put a condition on the /logout route, only DELETE request Message-ID: <20081014104054.8733618585AD@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 14 06:42:42 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 14 Oct 2008 06:42:42 -0400 (EDT) Subject: [BioCatalogue-developers] [73] trunk/app/views/services/index.html.erb: changed "new service" link to use "new_service_path" instead of just "service_path" as it was generating errors Message-ID: <20081014104242.E173718585B4@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 14 06:43:37 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 14 Oct 2008 06:43:37 -0400 (EDT) Subject: [BioCatalogue-developers] [74] trunk/app/views/layouts/application_wide.html.erb: new layout for new design Message-ID: <20081014104337.5696118585B4@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 14 06:44:40 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 14 Oct 2008 06:44:40 -0400 (EDT) Subject: [BioCatalogue-developers] [75] trunk/app/controllers/application.rb: use new layout Message-ID: <20081014104440.90B3318585AD@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 14 07:16:21 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 14 Oct 2008 07:16:21 -0400 (EDT) Subject: [BioCatalogue-developers] [76] trunk/app/views/widgets: small changes for the new design Message-ID: <20081014111621.6719C18585B2@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 14 07:18:29 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 14 Oct 2008 07:18:29 -0400 (EDT) Subject: [BioCatalogue-developers] [77] trunk/app/views/layouts/application_wide.html.erb: using partials for login_links and login_box Message-ID: <20081014111829.6BC6518585B2@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 14 19:00:11 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 14 Oct 2008 19:00:11 -0400 (EDT) Subject: [BioCatalogue-developers] [78] trunk: Added the "Widgets" plugin (see http://www.seesaw.it/en/toolbox /widgets/). Message-ID: <20081014230012.0DC6C18585AB@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 14 19:24:27 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 14 Oct 2008 19:24:27 -0400 (EDT) Subject: [BioCatalogue-developers] [79] trunk: Latest work on the Service Submission UI, based on discussions with Franck. Message-ID: <20081014232427.ECDEC16780D7@rubyforge.org> An HTML attachment was scrubbed... URL: From jits at cs.man.ac.uk Tue Oct 14 19:29:13 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Wed, 15 Oct 2008 00:29:13 +0100 Subject: [BioCatalogue-developers] [79] trunk: Latest work on the Service Submission UI, based on discussions with Franck. In-Reply-To: <20081014232427.ECDEC16780D7@rubyforge.org> References: <20081014232427.ECDEC16780D7@rubyforge.org> Message-ID: <48F52B49.3060205@cs.man.ac.uk> Hi guys, Attached is a screenshot showing latest service submission UI... Note that the "Add new.." boxes all start collapsed so all users see are the links. Jits noreply at rubyforge.org wrote: > > Revision > 79 > Author > jits > Date > 2008-10-14 19:24:27 -0400 (Tue, 14 Oct 2008) > > > Log Message > > Latest work on the Service Submission UI, based on discussions with Franck. > > > Modified Paths > > * trunk/app/controllers/soap_services_controller.rb > <#trunkappcontrollerssoap_services_controllerrb> > * trunk/app/helpers/application_helper.rb > <#trunkapphelpersapplication_helperrb> > * trunk/app/models/soap_service.rb <#trunkappmodelssoap_servicerb> > * trunk/app/views/soap_services/_after_wsdl_load.html.erb > <#trunkappviewssoap_services_after_wsdl_loadhtmlerb> > * trunk/app/views/soap_services/new.html.erb > <#trunkappviewssoap_servicesnewhtmlerb> > * trunk/public/stylesheets/styles.css > <#trunkpublicstylesheetsstylescss> > * trunk/public/stylesheets/styles_2.css > <#trunkpublicstylesheetsstyles_2css> > > > Added Paths > > * trunk/app/views/soap_services/_new_form.html.erb > <#trunkappviewssoap_services_new_formhtmlerb> > > > Removed Paths > > * trunk/app/views/soap_services/_form.html.erb > <#trunkappviewssoap_services_formhtmlerb> > > > Diff > > > Modified: trunk/app/controllers/soap_services_controller.rb > (78 => 79) > > > --- trunk/app/controllers/soap_services_controller.rb 2008-10-14 23:00:10 UTC (rev 78) > +++ trunk/app/controllers/soap_services_controller.rb 2008-10-14 23:24:27 UTC (rev 79) > @@ -31,7 +31,6 @@ > # GET /soap_services/new.xml > def new > @soap_service = SoapService.new > - @error_message = "Enter a WSDL URL to load up first" > > respond_to do |format| > format.html # new.html.erb > @@ -96,7 +95,16 @@ > if params[:wsdl_url].blank? > @error_message = "Please provide a valid WSDL URL" > else > + @soap_service = SoapService.new(:wsdl_location => params[:wsdl_url].strip) > > + begin > + @wsdl_info = @soap_service.get_service_attributes > + @error_message = nil > + rescue Exception => ex > + @error_message = "Failed to load the WSDL location provided." > + logger.info("ERROR: failed to load WSDL from location - #{params[:wsdl_url]}. Exception:") > + logger.info(ex) > + end > end > respond_to do |format| > format.html { render :partial => "after_wsdl_load" } > > > Modified: trunk/app/helpers/application_helper.rb (78 => 79) > > > --- trunk/app/helpers/application_helper.rb 2008-10-14 23:00:10 UTC (rev 78) > +++ trunk/app/helpers/application_helper.rb 2008-10-14 23:24:27 UTC (rev 79) > @@ -2,7 +2,7 @@ > module ApplicationHelper > > def controller_visible_name(controller_name) > - controller_name.humanize > + controller_name.humanize.titleize > end > > end > > > Modified: trunk/app/models/soap_service.rb (78 => 79) > > > --- trunk/app/models/soap_service.rb 2008-10-14 23:00:10 UTC (rev 78) > +++ trunk/app/models/soap_service.rb 2008-10-14 23:24:27 UTC (rev 79) > @@ -1,8 +1,8 @@ > > require 'open-uri' > require 'rexml/document' > -require 'lib/biocat_wsdl_parser' > -require 'lib/acts_as_service_versionified' > +require 'biocat_wsdl_parser' > +require 'acts_as_service_versionified' > > > class SoapService < ActiveRecord::Base > @@ -47,7 +47,6 @@ > # > # data structure : > # > - protected > #------------------------------------------------ > # get the service attributes from a wsdl url > # supplied in the web form > @@ -85,6 +84,8 @@ > return the_operations > end > > +protected > + > def check_duplicates > wsdls =[] > SoapService.find(:all).each{|s| wsdls << s.wsdl_location} > > > Modified: > trunk/app/views/soap_services/_after_wsdl_load.html.erb (78 => 79) > > > --- trunk/app/views/soap_services/_after_wsdl_load.html.erb 2008-10-14 23:00:10 UTC (rev 78) > +++ trunk/app/views/soap_services/_after_wsdl_load.html.erb 2008-10-14 23:24:27 UTC (rev 79) > @@ -2,6 +2,6 @@ > <% if !@error_message.blank? -%> >

<%= h @error_message -%>

> <% else %> > - <%= render :partial => "form" %> > + <%= render :partial => "new_form" %> > <% end -%> > > > > Deleted: trunk/app/views/soap_services/_form.html.erb (78 => 79) > > > --- trunk/app/views/soap_services/_form.html.erb 2008-10-14 23:00:10 UTC (rev 78) > +++ trunk/app/views/soap_services/_form.html.erb 2008-10-14 23:24:27 UTC (rev 79) > @@ -1,19 +0,0 @@ > -<% form_for(@soap_service) do |f| %> > - <%= f.error_messages %> > - > -

Name:
> - <%= f.text_field :name %> > -

> - > -

location:
> - <%= f.text_field :wsdl_location %> > -

> - > -

Description:
> - <%= f.text_area :description %> > -

> - > -

> - <%= f.submit "Submit" %> > -

> -<% end %> > > > Copied: trunk/app/views/soap_services/_new_form.html.erb (from > rev 67, trunk/app/views/soap_services/_form.html.erb) (0 => 79) > > > --- trunk/app/views/soap_services/_new_form.html.erb (rev 0) > +++ trunk/app/views/soap_services/_new_form.html.erb 2008-10-14 23:24:27 UTC (rev 79) > @@ -0,0 +1,100 @@ > +<% form_for(@soap_service) do |f| %> > + <%= f.error_messages %> > + > + > + > + > + > + > +
> + > + > + <%= f.hidden_field :name -%> > +
> + Name:
> + <% unless @soap_service.name.blank? %> > +

<%= h @soap_service.name -%>

> + <% else %> > +

Not available

> + <% end %> > +
> + > + > + <%= f.hidden_field :wsdl_location -%> > +
> + WSDL Location:
> + <% unless @soap_service.wsdl_location.blank? %> > +

<%= h @soap_service.wsdl_location -%>

> + <% else %> > +

Not available

> + <% end %> > +
> + > + > + <%= f.hidden_field :description -%> > +
> + Description:
> + <% unless @soap_service.description.blank? %> > +

<%= h @soap_service.description -%>

> + <% else %> > +

Not available

> + <% end %> > +
> + > + > + <%= f.hidden_field :documentation_url -%> > +
> + Documentation URL:
> + <% unless @soap_service.documentation_url.blank? %> > +

<%= h @soap_service.documentation_url -%>

> + <% else %> > +

Not available

> + <% end %> > +
> + > +
> + > + > + <% unless @wsdl_info.blank? %> > +
> +

This service has the following operations:

> + > +
> +
    > + <% @wsdl_info.each do |item| -%> > +
  • <%= "#{h item['operation']['name']} (#{item['inputs'].length} inputs, #{item['outputs'].length} outputs)" -%>
    • > + <% end -%> > +
> +
> +
> + <% end -%> > + 		> + > +

> + <%= link_to_function "Add new name alias...", visual_effect(:toggle_blind, "new_name_box", :duration => 0.3) %> > +

> + > + > + > +

> + <%= link_to_function "Add new description...", visual_effect(:toggle_blind, "new_description_box", :duration => 0.3) %> > +

> + > + > + > +

> + <%= link_to_function "Add new documentation URL...", visual_effect(:toggle_blind, "new_doc_url_box", :duration => 0.3) %> > +

> + > +
> + > +

> + <%= f.submit "Submit" %> > +

> +<% end %> > > > Modified: trunk/app/views/soap_services/new.html.erb (78 => 79) > > > --- trunk/app/views/soap_services/new.html.erb 2008-10-14 23:00:10 UTC (rev 78) > +++ trunk/app/views/soap_services/new.html.erb 2008-10-14 23:24:27 UTC (rev 79) > @@ -4,24 +4,27 @@ > > <%= error_messages_for :soap_service %> > > +

1. Specify the URL to the WSDL of the service, then preview...

> + > <% form_remote_tag(:url => load_wsdl_soap_services_url, > :update => 'soap_service_form', > :success => "new Effect.Highlight('soap_service_form', { duration: 1.5 });", > :loading => "Element.show('spinner')", > :complete => "Element.hide('spinner')") do -%> > - > -

1. Specify the URL to the WSDL of the service, then load...

> > -
> -

> - <%= image_tag "spinner.gif", :id => "spinner", :style => "display: none; float: right; vertical-align: top;" -%> > - <%= text_field_tag "wsdl_url", params[:wsdl_url], :size => 100, :style => "vertical-align: middle;" -%> > - <%= submit_tag "Load", :style => "vertical-align: middle;" -%> > +

> +

> + <%= text_field_tag "wsdl_url", params[:wsdl_url], :size => 60, :style => "vertical-align: middle;" -%> > + <%= submit_tag "Preview", :style => "vertical-align: middle;" -%> > + <%= image_tag "spinner.gif", :id => "spinner", :style => "display: none; vertical-align: middle;" -%> >

>
> > <% end -%> > > +

2. Check the details, then submit...

> +

After submission you will be able to provide more information

> + >
> <%= render :partial => "after_wsdl_load" %> >
> > > Modified: trunk/public/stylesheets/styles.css (78 => 79) > > > --- trunk/public/stylesheets/styles.css 2008-10-14 23:00:10 UTC (rev 78) > +++ trunk/public/stylesheets/styles.css 2008-10-14 23:24:27 UTC (rev 79) > @@ -30,7 +30,6 @@ > (see: http://developer.yahoo.com/yui/fonts/) */ > font-family: "Trebuchet MS"; > background-color: #8e8e8e; > - > line-height: 1.0; > } > > @@ -41,6 +40,10 @@ > margin-bottom: 0em; > } > > +form p { > + margin-top: 1em; > +} > + > #doc4 { > background-color: #FFFFFF; > } > @@ -70,6 +73,7 @@ > padding-left: 0.5em; > margin-top: 1em; > margin-bottom: 3em; > + min-height: 800px; > } > > #error_flash { > > > Modified: trunk/public/stylesheets/styles_2.css (78 => 79) > > > --- trunk/public/stylesheets/styles_2.css 2008-10-14 23:00:10 UTC (rev 78) > +++ trunk/public/stylesheets/styles_2.css 2008-10-14 23:24:27 UTC (rev 79) > @@ -174,6 +174,10 @@ > border: none; > } > > +td { > + vertical-align: top; > +} > + > /** > * Layout > */ > @@ -613,3 +617,31 @@ > > /* END Login box styles */ > > +.step_text { > + font-weight: bold; > + margin-top: 1.2em; > + color: #333333; > +} > + > +.none_text { > + font-style: italic; > + color: #666666; > +} > + > +.error_text { > + color: red; > + font-weight: bold; > +} > + > +#soap_service_form { > + margin: 1.5em 0; > + border: 1px dotted #999999; > + padding: 0.8em 1.3em; > + background-color: #F5F5F5; > +} > + > +.field { > + border: 1px dotted #DDDDDD; > + background-color: #FFFFCC; > + padding: 0.2em 0.5em; > +} > ------------------------------------------------------------------------ > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 20081015-0023.png Type: image/png Size: 78787 bytes Desc: not available URL: From tlaurent at ebi.ac.uk Wed Oct 15 04:50:19 2008 From: tlaurent at ebi.ac.uk (Thomas Laurent) Date: Wed, 15 Oct 2008 09:50:19 +0100 Subject: [BioCatalogue-developers] [79] trunk: Latest work on the Service Submission UI, based on discussions with Franck. In-Reply-To: <48F52B49.3060205@cs.man.ac.uk> References: <20081014232427.ECDEC16780D7@rubyforge.org> <48F52B49.3060205@cs.man.ac.uk> Message-ID: <48F5AECB.1030600@ebi.ac.uk> This looks very nice Jits, well done ! Jiten Bhagat wrote: > Hi guys, > > Attached is a screenshot showing latest service submission UI... > > Note that the "Add new.." boxes all start collapsed so all users see are > the links. > > Jits > > > > noreply at rubyforge.org wrote: >> >> Revision >> 79 >> Author >> jits >> Date >> 2008-10-14 19:24:27 -0400 (Tue, 14 Oct 2008) >> >> >> Log Message >> >> Latest work on the Service Submission UI, based on discussions with Franck. >> >> >> Modified Paths >> >> * trunk/app/controllers/soap_services_controller.rb >> <#trunkappcontrollerssoap_services_controllerrb> >> * trunk/app/helpers/application_helper.rb >> <#trunkapphelpersapplication_helperrb> >> * trunk/app/models/soap_service.rb <#trunkappmodelssoap_servicerb> >> * trunk/app/views/soap_services/_after_wsdl_load.html.erb >> <#trunkappviewssoap_services_after_wsdl_loadhtmlerb> >> * trunk/app/views/soap_services/new.html.erb >> <#trunkappviewssoap_servicesnewhtmlerb> >> * trunk/public/stylesheets/styles.css >> <#trunkpublicstylesheetsstylescss> >> * trunk/public/stylesheets/styles_2.css >> <#trunkpublicstylesheetsstyles_2css> >> >> >> Added Paths >> >> * trunk/app/views/soap_services/_new_form.html.erb >> <#trunkappviewssoap_services_new_formhtmlerb> >> >> >> Removed Paths >> >> * trunk/app/views/soap_services/_form.html.erb >> <#trunkappviewssoap_services_formhtmlerb> >> >> >> Diff >> >> >> Modified: trunk/app/controllers/soap_services_controller.rb >> (78 => 79) >> >> >> --- trunk/app/controllers/soap_services_controller.rb 2008-10-14 23:00:10 UTC (rev 78) >> +++ trunk/app/controllers/soap_services_controller.rb 2008-10-14 23:24:27 UTC (rev 79) >> @@ -31,7 +31,6 @@ >> # GET /soap_services/new.xml >> def new >> @soap_service = SoapService.new >> - @error_message = "Enter a WSDL URL to load up first" >> >> respond_to do |format| >> format.html # new.html.erb >> @@ -96,7 +95,16 @@ >> if params[:wsdl_url].blank? >> @error_message = "Please provide a valid WSDL URL" >> else >> + @soap_service = SoapService.new(:wsdl_location => params[:wsdl_url].strip) >> >> + begin >> + @wsdl_info = @soap_service.get_service_attributes >> + @error_message = nil >> + rescue Exception => ex >> + @error_message = "Failed to load the WSDL location provided." >> + logger.info("ERROR: failed to load WSDL from location - #{params[:wsdl_url]}. Exception:") >> + logger.info(ex) >> + end >> end >> respond_to do |format| >> format.html { render :partial => "after_wsdl_load" } >> >> >> Modified: trunk/app/helpers/application_helper.rb (78 => 79) >> >> >> --- trunk/app/helpers/application_helper.rb 2008-10-14 23:00:10 UTC (rev 78) >> +++ trunk/app/helpers/application_helper.rb 2008-10-14 23:24:27 UTC (rev 79) >> @@ -2,7 +2,7 @@ >> module ApplicationHelper >> >> def controller_visible_name(controller_name) >> - controller_name.humanize >> + controller_name.humanize.titleize >> end >> >> end >> >> >> Modified: trunk/app/models/soap_service.rb (78 => 79) >> >> >> --- trunk/app/models/soap_service.rb 2008-10-14 23:00:10 UTC (rev 78) >> +++ trunk/app/models/soap_service.rb 2008-10-14 23:24:27 UTC (rev 79) >> @@ -1,8 +1,8 @@ >> >> require 'open-uri' >> require 'rexml/document' >> -require 'lib/biocat_wsdl_parser' >> -require 'lib/acts_as_service_versionified' >> +require 'biocat_wsdl_parser' >> +require 'acts_as_service_versionified' >> >> >> class SoapService < ActiveRecord::Base >> @@ -47,7 +47,6 @@ >> # >> # data structure : >> # >> - protected >> #------------------------------------------------ >> # get the service attributes from a wsdl url >> # supplied in the web form >> @@ -85,6 +84,8 @@ >> return the_operations >> end >> >> +protected >> + >> def check_duplicates >> wsdls =[] >> SoapService.find(:all).each{|s| wsdls << s.wsdl_location} >> >> >> Modified: >> trunk/app/views/soap_services/_after_wsdl_load.html.erb (78 => 79) >> >> >> --- trunk/app/views/soap_services/_after_wsdl_load.html.erb 2008-10-14 23:00:10 UTC (rev 78) >> +++ trunk/app/views/soap_services/_after_wsdl_load.html.erb 2008-10-14 23:24:27 UTC (rev 79) >> @@ -2,6 +2,6 @@ >> <% if !@error_message.blank? -%> >>

<%= h @error_message -%>

>> <% else %> >> - <%= render :partial => "form" %> >> + <%= render :partial => "new_form" %> >> <% end -%> >>
>> >> >> Deleted: trunk/app/views/soap_services/_form.html.erb (78 => 79) >> >> >> --- trunk/app/views/soap_services/_form.html.erb 2008-10-14 23:00:10 UTC (rev 78) >> +++ trunk/app/views/soap_services/_form.html.erb 2008-10-14 23:24:27 UTC (rev 79) >> @@ -1,19 +0,0 @@ >> -<% form_for(@soap_service) do |f| %> >> - <%= f.error_messages %> >> - >> -

Name:
>> - <%= f.text_field :name %> >> -

>> - >> -

location:
>> - <%= f.text_field :wsdl_location %> >> -

>> - >> -

Description:
>> - <%= f.text_area :description %> >> -

>> - >> -

>> - <%= f.submit "Submit" %> >> -

>> -<% end %> >> >> >> Copied: trunk/app/views/soap_services/_new_form.html.erb (from >> rev 67, trunk/app/views/soap_services/_form.html.erb) (0 => 79) >> >> >> --- trunk/app/views/soap_services/_new_form.html.erb (rev 0) >> +++ trunk/app/views/soap_services/_new_form.html.erb 2008-10-14 23:24:27 UTC (rev 79) >> @@ -0,0 +1,100 @@ >> +<% form_for(@soap_service) do |f| %> >> + <%= f.error_messages %> >> + >> + >> + >> + >> + >> + >> +
>> + >> + >> + <%= f.hidden_field :name -%> >> +
>> + Name:
>> + <% unless @soap_service.name.blank? %> >> +

<%= h @soap_service.name -%>

>> + <% else %> >> +

Not available

>> + <% end %> >> +
>> + >> + >> + <%= f.hidden_field :wsdl_location -%> >> +
>> + WSDL Location:
>> + <% unless @soap_service.wsdl_location.blank? %> >> +

<%= h @soap_service.wsdl_location -%>

>> + <% else %> >> +

Not available

>> + <% end %> >> +
>> + >> + >> + <%= f.hidden_field :description -%> >> +
>> + Description:
>> + <% unless @soap_service.description.blank? %> >> +

<%= h @soap_service.description -%>

>> + <% else %> >> +

Not available

>> + <% end %> >> +
>> + >> + >> + <%= f.hidden_field :documentation_url -%> >> +
>> + Documentation URL:
>> + <% unless @soap_service.documentation_url.blank? %> >> +

<%= h @soap_service.documentation_url -%>

>> + <% else %> >> +

Not available

>> + <% end %> >> +
>> + >> +
>> + >> + >> + <% unless @wsdl_info.blank? %> >> +
>> +

This service has the following operations:

>> + >> +
>> +
    >> + <% @wsdl_info.each do |item| -%> >> +
  • <%= "#{h item['operation']['name']} (#{item['inputs'].length} inputs, #{item['outputs'].length} outputs)" -%>
    • >> + <% end -%> >> +
>> +
>> +
>> + <% end -%> >> + 		>> + >> +

>> + <%= link_to_function "Add new name alias...", visual_effect(:toggle_blind, "new_name_box", :duration => 0.3) %> >> +

>> + >> + >> + >> +

>> + <%= link_to_function "Add new description...", visual_effect(:toggle_blind, "new_description_box", :duration => 0.3) %> >> +

>> + >> + >> + >> +

>> + <%= link_to_function "Add new documentation URL...", visual_effect(:toggle_blind, "new_doc_url_box", :duration => 0.3) %> >> +

>> + >> +
>> + >> +

>> + <%= f.submit "Submit" %> >> +

>> +<% end %> >> >> >> Modified: trunk/app/views/soap_services/new.html.erb (78 => 79) >> >> >> --- trunk/app/views/soap_services/new.html.erb 2008-10-14 23:00:10 UTC (rev 78) >> +++ trunk/app/views/soap_services/new.html.erb 2008-10-14 23:24:27 UTC (rev 79) >> @@ -4,24 +4,27 @@ >> >> <%= error_messages_for :soap_service %> >> >> +

1. Specify the URL to the WSDL of the service, then preview...

>> + >> <% form_remote_tag(:url => load_wsdl_soap_services_url, >> :update => 'soap_service_form', >> :success => "new Effect.Highlight('soap_service_form', { duration: 1.5 });", >> :loading => "Element.show('spinner')", >> :complete => "Element.hide('spinner')") do -%> >> - >> -

1. Specify the URL to the WSDL of the service, then load...

>> >> -
>> -

>> - <%= image_tag "spinner.gif", :id => "spinner", :style => "display: none; float: right; vertical-align: top;" -%> >> - <%= text_field_tag "wsdl_url", params[:wsdl_url], :size => 100, :style => "vertical-align: middle;" -%> >> - <%= submit_tag "Load", :style => "vertical-align: middle;" -%> >> +

>> +

>> + <%= text_field_tag "wsdl_url", params[:wsdl_url], :size => 60, :style => "vertical-align: middle;" -%> >> + <%= submit_tag "Preview", :style => "vertical-align: middle;" -%> >> + <%= image_tag "spinner.gif", :id => "spinner", :style => "display: none; vertical-align: middle;" -%> >>

>>
>> >> <% end -%> >> >> +

2. Check the details, then submit...

>> +

After submission you will be able to provide more information

>> + >>
>> <%= render :partial => "after_wsdl_load" %> >>
>> >> >> Modified: trunk/public/stylesheets/styles.css (78 => 79) >> >> >> --- trunk/public/stylesheets/styles.css 2008-10-14 23:00:10 UTC (rev 78) >> +++ trunk/public/stylesheets/styles.css 2008-10-14 23:24:27 UTC (rev 79) >> @@ -30,7 +30,6 @@ >> (see: http://developer.yahoo.com/yui/fonts/) */ >> font-family: "Trebuchet MS"; >> background-color: #8e8e8e; >> - >> line-height: 1.0; >> } >> >> @@ -41,6 +40,10 @@ >> margin-bottom: 0em; >> } >> >> +form p { >> + margin-top: 1em; >> +} >> + >> #doc4 { >> background-color: #FFFFFF; >> } >> @@ -70,6 +73,7 @@ >> padding-left: 0.5em; >> margin-top: 1em; >> margin-bottom: 3em; >> + min-height: 800px; >> } >> >> #error_flash { >> >> >> Modified: trunk/public/stylesheets/styles_2.css (78 => 79) >> >> >> --- trunk/public/stylesheets/styles_2.css 2008-10-14 23:00:10 UTC (rev 78) >> +++ trunk/public/stylesheets/styles_2.css 2008-10-14 23:24:27 UTC (rev 79) >> @@ -174,6 +174,10 @@ >> border: none; >> } >> >> +td { >> + vertical-align: top; >> +} >> + >> /** >> * Layout >> */ >> @@ -613,3 +617,31 @@ >> >> /* END Login box styles */ >> >> +.step_text { >> + font-weight: bold; >> + margin-top: 1.2em; >> + color: #333333; >> +} >> + >> +.none_text { >> + font-style: italic; >> + color: #666666; >> +} >> + >> +.error_text { >> + color: red; >> + font-weight: bold; >> +} >> + >> +#soap_service_form { >> + margin: 1.5em 0; >> + border: 1px dotted #999999; >> + padding: 0.8em 1.3em; >> + background-color: #F5F5F5; >> +} >> + >> +.field { >> + border: 1px dotted #DDDDDD; >> + background-color: #FFFFCC; >> + padding: 0.2em 0.5em; >> +} >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> > > > ------------------------------------------------------------------------ > > This body part will be downloaded on demand. From tlaurent at ebi.ac.uk Wed Oct 15 04:53:38 2008 From: tlaurent at ebi.ac.uk (Thomas Laurent) Date: Wed, 15 Oct 2008 09:53:38 +0100 Subject: [BioCatalogue-developers] password protection of beta.biocatalogue.org Message-ID: <48F5AF92.5060509@ebi.ac.uk> Hi guys, I've added a very simple htaccess-like authentication to the beta site. username: biocat password: biodog Cheers, Thomas From jits at cs.man.ac.uk Wed Oct 15 05:06:05 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Wed, 15 Oct 2008 10:06:05 +0100 Subject: [BioCatalogue-developers] password protection of beta.biocatalogue.org In-Reply-To: <48F5AF92.5060509@ebi.ac.uk> References: <48F5AF92.5060509@ebi.ac.uk> Message-ID: <48F5B27D.7030000@cs.man.ac.uk> Nice one! Thanks Thomas. Any minute now.......... :-) Jits Thomas Laurent wrote: > Hi guys, > > I've added a very simple htaccess-like authentication to the beta site. > username: biocat > password: biodog > > Cheers, > Thomas > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers From ericnzuo at ebi.ac.uk Wed Oct 15 05:08:38 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Wed, 15 Oct 2008 10:08:38 +0100 Subject: [BioCatalogue-developers] [79] trunk: Latest work on the Service Submission UI, based on discussions with Franck. In-Reply-To: <48F5AECB.1030600@ebi.ac.uk> References: <20081014232427.ECDEC16780D7@rubyforge.org> <48F52B49.3060205@cs.man.ac.uk> <48F5AECB.1030600@ebi.ac.uk> Message-ID: <48F5B316.4000103@ebi.ac.uk> Hi Jits, It is very very nice. I should hire you for private work! Well done... Eric Thomas Laurent wrote: > This looks very nice Jits, well done ! > > Jiten Bhagat wrote: >> Hi guys, >> >> Attached is a screenshot showing latest service submission UI... >> >> Note that the "Add new.." boxes all start collapsed so all users see >> are the links. >> >> Jits >> >> >> >> noreply at rubyforge.org wrote: >>> >>> Revision >>> 79 >>> Author >>> jits >>> Date >>> 2008-10-14 19:24:27 -0400 (Tue, 14 Oct 2008) >>> >>> >>> Log Message >>> >>> Latest work on the Service Submission UI, based on discussions with >>> Franck. >>> >>> >>> Modified Paths >>> >>> * trunk/app/controllers/soap_services_controller.rb >>> <#trunkappcontrollerssoap_services_controllerrb> >>> * trunk/app/helpers/application_helper.rb >>> <#trunkapphelpersapplication_helperrb> >>> * trunk/app/models/soap_service.rb <#trunkappmodelssoap_servicerb> >>> * trunk/app/views/soap_services/_after_wsdl_load.html.erb >>> <#trunkappviewssoap_services_after_wsdl_loadhtmlerb> >>> * trunk/app/views/soap_services/new.html.erb >>> <#trunkappviewssoap_servicesnewhtmlerb> >>> * trunk/public/stylesheets/styles.css >>> <#trunkpublicstylesheetsstylescss> >>> * trunk/public/stylesheets/styles_2.css >>> <#trunkpublicstylesheetsstyles_2css> >>> >>> >>> Added Paths >>> >>> * trunk/app/views/soap_services/_new_form.html.erb >>> <#trunkappviewssoap_services_new_formhtmlerb> >>> >>> >>> Removed Paths >>> >>> * trunk/app/views/soap_services/_form.html.erb >>> <#trunkappviewssoap_services_formhtmlerb> >>> >>> >>> Diff >>> >>> >>> Modified: trunk/app/controllers/soap_services_controller.rb >>> (78 => 79) >>> >>> >>> --- trunk/app/controllers/soap_services_controller.rb 2008-10-14 >>> 23:00:10 UTC (rev 78) >>> +++ trunk/app/controllers/soap_services_controller.rb 2008-10-14 >>> 23:24:27 UTC (rev 79) >>> @@ -31,7 +31,6 @@ >>> # GET /soap_services/new.xml >>> def new >>> @soap_service = SoapService.new >>> - @error_message = "Enter a WSDL URL to load up first" >>> >>> respond_to do |format| >>> format.html # new.html.erb >>> @@ -96,7 +95,16 @@ >>> if params[:wsdl_url].blank? >>> @error_message = "Please provide a valid WSDL URL" >>> else >>> + @soap_service = SoapService.new(:wsdl_location => >>> params[:wsdl_url].strip) >>> + begin >>> + @wsdl_info = @soap_service.get_service_attributes >>> + @error_message = nil >>> + rescue Exception => ex >>> + @error_message = "Failed to load the WSDL location provided." >>> + logger.info("ERROR: failed to load WSDL from location - >>> #{params[:wsdl_url]}. Exception:") >>> + logger.info(ex) >>> + end >>> end >>> respond_to do |format| >>> format.html { render :partial => "after_wsdl_load" } >>> >>> >>> Modified: trunk/app/helpers/application_helper.rb (78 => 79) >>> >>> >>> --- trunk/app/helpers/application_helper.rb 2008-10-14 23:00:10 >>> UTC (rev 78) >>> +++ trunk/app/helpers/application_helper.rb 2008-10-14 23:24:27 >>> UTC (rev 79) >>> @@ -2,7 +2,7 @@ >>> module ApplicationHelper >>> def controller_visible_name(controller_name) >>> - controller_name.humanize >>> + controller_name.humanize.titleize >>> end >>> end >>> >>> >>> Modified: trunk/app/models/soap_service.rb (78 => 79) >>> >>> >>> --- trunk/app/models/soap_service.rb 2008-10-14 23:00:10 UTC (rev >>> 78) >>> +++ trunk/app/models/soap_service.rb 2008-10-14 23:24:27 UTC (rev >>> 79) >>> @@ -1,8 +1,8 @@ >>> >>> require 'open-uri' >>> require 'rexml/document' >>> -require 'lib/biocat_wsdl_parser' >>> -require 'lib/acts_as_service_versionified' >>> +require 'biocat_wsdl_parser' >>> +require 'acts_as_service_versionified' >>> >>> >>> class SoapService < ActiveRecord::Base >>> @@ -47,7 +47,6 @@ >>> # >>> # data structure : >>> # >>> - protected >>> #------------------------------------------------ >>> # get the service attributes from a wsdl url >>> # supplied in the web form >>> @@ -85,6 +84,8 @@ >>> return the_operations >>> end >>> +protected >>> + def check_duplicates >>> wsdls =[] SoapService.find(:all).each{|s| wsdls << >>> s.wsdl_location} >>> >>> >>> Modified: >>> trunk/app/views/soap_services/_after_wsdl_load.html.erb (78 >>> => 79) >>> >>> >>> --- trunk/app/views/soap_services/_after_wsdl_load.html.erb >>> 2008-10-14 23:00:10 UTC (rev 78) >>> +++ trunk/app/views/soap_services/_after_wsdl_load.html.erb >>> 2008-10-14 23:24:27 UTC (rev 79) >>> @@ -2,6 +2,6 @@ >>> <% if !@error_message.blank? -%> >>>

<%= h @error_message -%>

>>> <% else %> >>> - <%= render :partial => "form" %> >>> + <%= render :partial => "new_form" %> >>> <% end -%> >>>
>>> >>> >>> Deleted: trunk/app/views/soap_services/_form.html.erb (78 => >>> 79) >>> >>> >>> --- trunk/app/views/soap_services/_form.html.erb 2008-10-14 >>> 23:00:10 UTC (rev 78) >>> +++ trunk/app/views/soap_services/_form.html.erb 2008-10-14 >>> 23:24:27 UTC (rev 79) >>> @@ -1,19 +0,0 @@ >>> -<% form_for(@soap_service) do |f| %> >>> - <%= f.error_messages %> >>> - >>> -

Name:
>>> - <%= f.text_field :name %> >>> -

>>> - -

location:
>>> - <%= f.text_field :wsdl_location %> >>> -

>>> - -

Description:
>>> - <%= f.text_area :description %> >>> -

>>> - -

>>> - <%= f.submit "Submit" %> >>> -

>>> -<% end %> >>> >>> >>> Copied: trunk/app/views/soap_services/_new_form.html.erb (from >>> rev 67, trunk/app/views/soap_services/_form.html.erb) (0 => 79) >>> >>> >>> --- >>> trunk/app/views/soap_services/_new_form.html.erb >>> (rev 0) >>> +++ trunk/app/views/soap_services/_new_form.html.erb 2008-10-14 >>> 23:24:27 UTC (rev 79) >>> @@ -0,0 +1,100 @@ >>> +<% form_for(@soap_service) do |f| %> >>> + <%= f.error_messages %> >>> + >>> + >>> + >>> + >>> + >>> + >>> +
>>> + >>> + >>> + <%= f.hidden_field :name -%> >>> +
>>> + Name:
>>> + <% unless @soap_service.name.blank? %> >>> +

<%= h @soap_service.name >>> -%>

>>> + <% else %> >>> +

Not available

>>> + <% end %> >>> +
>>> + >>> + >>> + <%= f.hidden_field :wsdl_location -%> >>> +
>>> + WSDL Location:
>>> + <% unless @soap_service.wsdl_location.blank? %> >>> +

<%= h >>> @soap_service.wsdl_location -%>

>>> + <% else %> >>> +

Not available

>>> + <% end %> >>> +
>>> + >>> + >>> + <%= f.hidden_field :description -%> >>> +
>>> + Description:
>>> + <% unless @soap_service.description.blank? %> >>> +

<%= h >>> @soap_service.description -%>

>>> + <% else %> >>> +

Not available

>>> + <% end %> >>> +
>>> + >>> + >>> + <%= f.hidden_field :documentation_url -%> >>> +
>>> + Documentation URL:
>>> + <% unless >>> @soap_service.documentation_url.blank? %> >>> +

<%= h >>> @soap_service.documentation_url -%>

>>> + <% else %> >>> +

Not available

>>> + <% end %> >>> +
>>> + >>> +
>>> + >>> + >>> + <% unless @wsdl_info.blank? %> >>> +
>>> +

This service has the following >>> operations:

>>> + >>> +
>>> +
    >>> + <% @wsdl_info.each do |item| -%> >>> +
  • <%= "#{h >>> item['operation']['name']} (#{item['inputs'].length} inputs, >>> #{item['outputs'].length} outputs)" -%>
    • >>> + <% end -%> >>> +
>>> +
>>> +
>>> + <% end -%> >>> + 		>>> + >>> +

>>> + <%= link_to_function "Add new name alias...", >>> visual_effect(:toggle_blind, "new_name_box", :duration => 0.3) %> >>> +

>>> + >>> + >>> + >>> +

>>> + <%= link_to_function "Add new description...", >>> visual_effect(:toggle_blind, "new_description_box", :duration => >>> 0.3) %> >>> +

>>> + >>> + >>> + >>> +

>>> + <%= link_to_function "Add new documentation >>> URL...", visual_effect(:toggle_blind, "new_doc_url_box", :duration >>> => 0.3) %> >>> +

>>> + >>> +
>>> + >>> +

>>> + <%= f.submit "Submit" %> >>> +

>>> +<% end %> >>> >>> >>> Modified: trunk/app/views/soap_services/new.html.erb (78 => 79) >>> >>> >>> --- trunk/app/views/soap_services/new.html.erb 2008-10-14 >>> 23:00:10 UTC (rev 78) >>> +++ trunk/app/views/soap_services/new.html.erb 2008-10-14 >>> 23:24:27 UTC (rev 79) >>> @@ -4,24 +4,27 @@ >>> >>> <%= error_messages_for :soap_service %> >>> >>> +

1. Specify the URL to the WSDL of the service, >>> then preview...

>>> + >>> <% form_remote_tag(:url => load_wsdl_soap_services_url, >>> :update => 'soap_service_form', >>> :success => "new >>> Effect.Highlight('soap_service_form', { duration: 1.5 });", >>> :loading => >>> "Element.show('spinner')", >>> :complete => "Element.hide('spinner')") do -%> >>> - >>> -

1. Specify the URL to the WSDL of the >>> service, then load...

>>> >>> -
>>> -

>>> - <%= image_tag "spinner.gif", :id => "spinner", :style >>> => "display: none; float: right; vertical-align: top;" -%> >>> - <%= text_field_tag "wsdl_url", params[:wsdl_url], :size >>> => 100, :style => "vertical-align: middle;" -%> >>> - <%= submit_tag "Load", :style => "vertical-align: >>> middle;" -%> >>> +

>>> +

>>> + <%= text_field_tag "wsdl_url", params[:wsdl_url], :size >>> => 60, :style => "vertical-align: middle;" -%> >>> + <%= submit_tag "Preview", :style => "vertical-align: >>> middle;" -%> >>> + <%= image_tag "spinner.gif", :id => "spinner", :style >>> => "display: none; vertical-align: middle;" -%> >>>

>>>
>>> >>> <% end -%> >>> >>> +

2. Check the details, then submit...

>>> +

After submission you will be able to >>> provide more information

>>> + >>>
>>> <%= render :partial => "after_wsdl_load" %> >>>
>>> >>> >>> Modified: trunk/public/stylesheets/styles.css (78 => 79) >>> >>> >>> --- trunk/public/stylesheets/styles.css 2008-10-14 23:00:10 UTC >>> (rev 78) >>> +++ trunk/public/stylesheets/styles.css 2008-10-14 23:24:27 UTC >>> (rev 79) >>> @@ -30,7 +30,6 @@ >>> (see: http://developer.yahoo.com/yui/fonts/) */ >>> font-family: "Trebuchet MS"; >>> background-color: #8e8e8e; >>> - >>> line-height: 1.0; >>> } >>> >>> @@ -41,6 +40,10 @@ >>> margin-bottom: 0em; >>> } >>> >>> +form p { >>> + margin-top: 1em; >>> +} >>> + >>> #doc4 { >>> background-color: #FFFFFF; >>> } >>> @@ -70,6 +73,7 @@ >>> padding-left: 0.5em; >>> margin-top: 1em; >>> margin-bottom: 3em; >>> + min-height: 800px; >>> } >>> >>> #error_flash { >>> >>> >>> Modified: trunk/public/stylesheets/styles_2.css (78 => 79) >>> >>> >>> --- trunk/public/stylesheets/styles_2.css 2008-10-14 23:00:10 UTC >>> (rev 78) >>> +++ trunk/public/stylesheets/styles_2.css 2008-10-14 23:24:27 UTC >>> (rev 79) >>> @@ -174,6 +174,10 @@ >>> border: none; >>> } >>> >>> +td { >>> + vertical-align: top; >>> +} >>> + >>> /** >>> * Layout >>> */ >>> @@ -613,3 +617,31 @@ >>> >>> /* END Login box styles */ >>> >>> +.step_text { >>> + font-weight: bold; >>> + margin-top: 1.2em; >>> + color: #333333; >>> +} >>> + >>> +.none_text { >>> + font-style: italic; >>> + color: #666666; >>> +} >>> + >>> +.error_text { >>> + color: red; >>> + font-weight: bold; >>> +} >>> + >>> +#soap_service_form { >>> + margin: 1.5em 0; >>> + border: 1px dotted #999999; >>> + padding: 0.8em 1.3em; >>> + background-color: #F5F5F5; >>> +} >>> + >>> +.field { >>> + border: 1px dotted #DDDDDD; >>> + background-color: #FFFFCC; >>> + padding: 0.2em 0.5em; >>> +} >>> ------------------------------------------------------------------------ >>> >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >> >> >> ------------------------------------------------------------------------ >> >> This body part will be downloaded on demand. > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Wed Oct 15 05:09:59 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Wed, 15 Oct 2008 10:09:59 +0100 Subject: [BioCatalogue-developers] [79] trunk: Latest work on the Service Submission UI, based on discussions with Franck. In-Reply-To: <48F5B316.4000103@ebi.ac.uk> References: <20081014232427.ECDEC16780D7@rubyforge.org> <48F52B49.3060205@cs.man.ac.uk> <48F5AECB.1030600@ebi.ac.uk> <48F5B316.4000103@ebi.ac.uk> Message-ID: <48F5B367.3020109@cs.man.ac.uk> HEHEHEHEHEHE.... thanks guys, you're too kind :-) Jits Eric Nzuobontane wrote: > Hi Jits, > It is very very nice. I should hire you for private work! Well done... > Eric > > > Thomas Laurent wrote: >> This looks very nice Jits, well done ! >> >> Jiten Bhagat wrote: >>> Hi guys, >>> >>> Attached is a screenshot showing latest service submission UI... >>> >>> Note that the "Add new.." boxes all start collapsed so all users see >>> are the links. >>> >>> Jits >>> >>> >>> >>> noreply at rubyforge.org wrote: >>>> >>>> Revision >>>> 79 >>>> Author >>>> jits >>>> Date >>>> 2008-10-14 19:24:27 -0400 (Tue, 14 Oct 2008) >>>> >>>> >>>> Log Message >>>> >>>> Latest work on the Service Submission UI, based on discussions with >>>> Franck. >>>> >>>> >>>> Modified Paths >>>> >>>> * trunk/app/controllers/soap_services_controller.rb >>>> <#trunkappcontrollerssoap_services_controllerrb> >>>> * trunk/app/helpers/application_helper.rb >>>> <#trunkapphelpersapplication_helperrb> >>>> * trunk/app/models/soap_service.rb <#trunkappmodelssoap_servicerb> >>>> * trunk/app/views/soap_services/_after_wsdl_load.html.erb >>>> <#trunkappviewssoap_services_after_wsdl_loadhtmlerb> >>>> * trunk/app/views/soap_services/new.html.erb >>>> <#trunkappviewssoap_servicesnewhtmlerb> >>>> * trunk/public/stylesheets/styles.css >>>> <#trunkpublicstylesheetsstylescss> >>>> * trunk/public/stylesheets/styles_2.css >>>> <#trunkpublicstylesheetsstyles_2css> >>>> >>>> >>>> Added Paths >>>> >>>> * trunk/app/views/soap_services/_new_form.html.erb >>>> <#trunkappviewssoap_services_new_formhtmlerb> >>>> >>>> >>>> Removed Paths >>>> >>>> * trunk/app/views/soap_services/_form.html.erb >>>> <#trunkappviewssoap_services_formhtmlerb> >>>> >>>> >>>> Diff >>>> >>>> >>>> Modified: trunk/app/controllers/soap_services_controller.rb >>>> (78 => 79) >>>> >>>> >>>> --- trunk/app/controllers/soap_services_controller.rb 2008-10-14 >>>> 23:00:10 UTC (rev 78) >>>> +++ trunk/app/controllers/soap_services_controller.rb 2008-10-14 >>>> 23:24:27 UTC (rev 79) >>>> @@ -31,7 +31,6 @@ >>>> # GET /soap_services/new.xml >>>> def new >>>> @soap_service = SoapService.new >>>> - @error_message = "Enter a WSDL URL to load up first" >>>> >>>> respond_to do |format| >>>> format.html # new.html.erb >>>> @@ -96,7 +95,16 @@ >>>> if params[:wsdl_url].blank? >>>> @error_message = "Please provide a valid WSDL URL" >>>> else >>>> + @soap_service = SoapService.new(:wsdl_location => >>>> params[:wsdl_url].strip) >>>> + begin >>>> + @wsdl_info = @soap_service.get_service_attributes >>>> + @error_message = nil >>>> + rescue Exception => ex >>>> + @error_message = "Failed to load the WSDL location provided." >>>> + logger.info("ERROR: failed to load WSDL from location - >>>> #{params[:wsdl_url]}. Exception:") >>>> + logger.info(ex) >>>> + end >>>> end >>>> respond_to do |format| >>>> format.html { render :partial => "after_wsdl_load" } >>>> >>>> >>>> Modified: trunk/app/helpers/application_helper.rb (78 => 79) >>>> >>>> >>>> --- trunk/app/helpers/application_helper.rb 2008-10-14 23:00:10 >>>> UTC (rev 78) >>>> +++ trunk/app/helpers/application_helper.rb 2008-10-14 23:24:27 >>>> UTC (rev 79) >>>> @@ -2,7 +2,7 @@ >>>> module ApplicationHelper >>>> def controller_visible_name(controller_name) >>>> - controller_name.humanize >>>> + controller_name.humanize.titleize >>>> end >>>> end >>>> >>>> >>>> Modified: trunk/app/models/soap_service.rb (78 => 79) >>>> >>>> >>>> --- trunk/app/models/soap_service.rb 2008-10-14 23:00:10 UTC >>>> (rev 78) >>>> +++ trunk/app/models/soap_service.rb 2008-10-14 23:24:27 UTC >>>> (rev 79) >>>> @@ -1,8 +1,8 @@ >>>> >>>> require 'open-uri' >>>> require 'rexml/document' >>>> -require 'lib/biocat_wsdl_parser' >>>> -require 'lib/acts_as_service_versionified' >>>> +require 'biocat_wsdl_parser' >>>> +require 'acts_as_service_versionified' >>>> >>>> >>>> class SoapService < ActiveRecord::Base >>>> @@ -47,7 +47,6 @@ >>>> # >>>> # data structure : >>>> # >>>> - protected >>>> #------------------------------------------------ >>>> # get the service attributes from a wsdl url >>>> # supplied in the web form >>>> @@ -85,6 +84,8 @@ >>>> return the_operations >>>> end >>>> +protected >>>> + def check_duplicates >>>> wsdls =[] SoapService.find(:all).each{|s| wsdls << >>>> s.wsdl_location} >>>> >>>> >>>> Modified: >>>> trunk/app/views/soap_services/_after_wsdl_load.html.erb (78 >>>> => 79) >>>> >>>> >>>> --- trunk/app/views/soap_services/_after_wsdl_load.html.erb >>>> 2008-10-14 23:00:10 UTC (rev 78) >>>> +++ trunk/app/views/soap_services/_after_wsdl_load.html.erb >>>> 2008-10-14 23:24:27 UTC (rev 79) >>>> @@ -2,6 +2,6 @@ >>>> <% if !@error_message.blank? -%> >>>>

<%= h @error_message -%>

>>>> <% else %> >>>> - <%= render :partial => "form" %> + <%= render >>>> :partial => "new_form" %> <% end -%> >>>>
>>>> >>>> >>>> Deleted: trunk/app/views/soap_services/_form.html.erb (78 >>>> => 79) >>>> >>>> >>>> --- trunk/app/views/soap_services/_form.html.erb 2008-10-14 >>>> 23:00:10 UTC (rev 78) >>>> +++ trunk/app/views/soap_services/_form.html.erb 2008-10-14 >>>> 23:24:27 UTC (rev 79) >>>> @@ -1,19 +0,0 @@ >>>> -<% form_for(@soap_service) do |f| %> >>>> - <%= f.error_messages %> >>>> - -

Name:
>>>> - <%= f.text_field :name %> >>>> -

>>>> - -

location:
>>>> - <%= f.text_field :wsdl_location %> >>>> -

>>>> - -

Description:
>>>> - <%= f.text_area :description %> >>>> -

>>>> - -

>>>> - <%= f.submit "Submit" %> >>>> -

>>>> -<% end %> >>>> >>>> >>>> Copied: trunk/app/views/soap_services/_new_form.html.erb (from >>>> rev 67, trunk/app/views/soap_services/_form.html.erb) (0 => >>>> 79) >>>> >>>> >>>> --- >>>> trunk/app/views/soap_services/_new_form.html.erb >>>> (rev 0) >>>> +++ trunk/app/views/soap_services/_new_form.html.erb 2008-10-14 >>>> 23:24:27 UTC (rev 79) >>>> @@ -0,0 +1,100 @@ >>>> +<% form_for(@soap_service) do |f| %> >>>> + <%= f.error_messages %> >>>> + + >>>> + >>>> + >>>> + >>>> + >>>> +
>>>> + >>>> + >>>> + <%= f.hidden_field :name -%> >>>> +
>>>> + Name:
>>>> + <% unless @soap_service.name.blank? %> >>>> +

<%= h @soap_service.name >>>> -%>

>>>> + <% else %> >>>> +

Not available

>>>> + <% end %> >>>> +
>>>> + + >>>> + <%= f.hidden_field :wsdl_location -%> >>>> +
>>>> + WSDL Location:
>>>> + <% unless @soap_service.wsdl_location.blank? %> >>>> +

<%= h >>>> @soap_service.wsdl_location -%>

>>>> + <% else %> >>>> +

Not available

>>>> + <% end %> >>>> +
>>>> + + >>>> + <%= f.hidden_field :description -%> >>>> +
>>>> + Description:
>>>> + <% unless @soap_service.description.blank? %> >>>> +

<%= h >>>> @soap_service.description -%>

>>>> + <% else %> >>>> +

Not available

>>>> + <% end %> >>>> +
>>>> + + >>>> + <%= f.hidden_field :documentation_url -%> >>>> +
>>>> + Documentation URL:
>>>> + <% unless >>>> @soap_service.documentation_url.blank? %> >>>> +

<%= h >>>> @soap_service.documentation_url -%>

>>>> + <% else %> >>>> +

Not available

>>>> + <% end %> >>>> +
>>>> + +
>>>> + + >>>> + <% unless @wsdl_info.blank? %> >>>> +
>>>> +

This service has the following >>>> operations:

>>>> + +
>>>> +
    >>>> + <% @wsdl_info.each do |item| -%> >>>> +
  • <%= "#{h >>>> item['operation']['name']} (#{item['inputs'].length} inputs, >>>> #{item['outputs'].length} outputs)" -%>
    • >>>> + <% end -%> >>>> +
>>>> +
>>>> +
>>>> + <% end -%> >>>> + 		>>>> + >>>> +

>>>> + <%= link_to_function "Add new name alias...", >>>> visual_effect(:toggle_blind, "new_name_box", :duration => 0.3) %> >>>> +

>>>> + >>>> + + >>>> +

>>>> + <%= link_to_function "Add new description...", >>>> visual_effect(:toggle_blind, "new_description_box", :duration => >>>> 0.3) %> >>>> +

>>>> + >>>> + + >>>> +

>>>> + <%= link_to_function "Add new documentation >>>> URL...", visual_effect(:toggle_blind, "new_doc_url_box", :duration >>>> => 0.3) %> >>>> +

>>>> + >>>> +
>>>> + +

>>>> + <%= f.submit "Submit" %> >>>> +

>>>> +<% end %> >>>> >>>> >>>> Modified: trunk/app/views/soap_services/new.html.erb (78 => >>>> 79) >>>> >>>> >>>> --- trunk/app/views/soap_services/new.html.erb 2008-10-14 >>>> 23:00:10 UTC (rev 78) >>>> +++ trunk/app/views/soap_services/new.html.erb 2008-10-14 >>>> 23:24:27 UTC (rev 79) >>>> @@ -4,24 +4,27 @@ >>>> >>>> <%= error_messages_for :soap_service %> >>>> >>>> +

1. Specify the URL to the WSDL of the >>>> service, then preview...

>>>> + >>>> <% form_remote_tag(:url => load_wsdl_soap_services_url, >>>> :update => 'soap_service_form', >>>> :success => "new >>>> Effect.Highlight('soap_service_form', { duration: 1.5 });", >>>> :loading => >>>> "Element.show('spinner')", >>>> :complete => "Element.hide('spinner')") do -%> >>>> - >>>> -

1. Specify the URL to the WSDL of the >>>> service, then load...

>>>> -
>>>> -

>>>> - <%= image_tag "spinner.gif", :id => "spinner", :style >>>> => "display: none; float: right; vertical-align: top;" -%> >>>> - <%= text_field_tag "wsdl_url", params[:wsdl_url], >>>> :size => 100, :style => "vertical-align: middle;" -%> >>>> - <%= submit_tag "Load", :style => "vertical-align: >>>> middle;" -%> >>>> +

>>>> +

>>>> + <%= text_field_tag "wsdl_url", params[:wsdl_url], >>>> :size => 60, :style => "vertical-align: middle;" -%> >>>> + <%= submit_tag "Preview", :style => "vertical-align: >>>> middle;" -%> >>>> + <%= image_tag "spinner.gif", :id => "spinner", :style >>>> => "display: none; vertical-align: middle;" -%> >>>>

>>>>
>>>> >>>> <% end -%> >>>> >>>> +

2. Check the details, then submit...

>>>> +

After submission you will be able to >>>> provide more information

>>>> + >>>>
>>>> <%= render :partial => "after_wsdl_load" %> >>>>
>>>> >>>> >>>> Modified: trunk/public/stylesheets/styles.css (78 => 79) >>>> >>>> >>>> --- trunk/public/stylesheets/styles.css 2008-10-14 23:00:10 UTC >>>> (rev 78) >>>> +++ trunk/public/stylesheets/styles.css 2008-10-14 23:24:27 UTC >>>> (rev 79) >>>> @@ -30,7 +30,6 @@ >>>> (see: http://developer.yahoo.com/yui/fonts/) */ >>>> font-family: "Trebuchet MS"; >>>> background-color: #8e8e8e; >>>> - line-height: 1.0; >>>> } >>>> >>>> @@ -41,6 +40,10 @@ >>>> margin-bottom: 0em; >>>> } >>>> >>>> +form p { >>>> + margin-top: 1em; >>>> +} >>>> + >>>> #doc4 { >>>> background-color: #FFFFFF; >>>> } >>>> @@ -70,6 +73,7 @@ >>>> padding-left: 0.5em; >>>> margin-top: 1em; >>>> margin-bottom: 3em; >>>> + min-height: 800px; >>>> } >>>> >>>> #error_flash { >>>> >>>> >>>> Modified: trunk/public/stylesheets/styles_2.css (78 => 79) >>>> >>>> >>>> --- trunk/public/stylesheets/styles_2.css 2008-10-14 23:00:10 >>>> UTC (rev 78) >>>> +++ trunk/public/stylesheets/styles_2.css 2008-10-14 23:24:27 >>>> UTC (rev 79) >>>> @@ -174,6 +174,10 @@ >>>> border: none; >>>> } >>>> >>>> +td { >>>> + vertical-align: top; >>>> +} >>>> + >>>> /** >>>> * Layout >>>> */ >>>> @@ -613,3 +617,31 @@ >>>> >>>> /* END Login box styles */ >>>> >>>> +.step_text { >>>> + font-weight: bold; >>>> + margin-top: 1.2em; >>>> + color: #333333; >>>> +} >>>> + >>>> +.none_text { >>>> + font-style: italic; >>>> + color: #666666; >>>> +} >>>> + >>>> +.error_text { >>>> + color: red; >>>> + font-weight: bold; >>>> +} >>>> + >>>> +#soap_service_form { >>>> + margin: 1.5em 0; >>>> + border: 1px dotted #999999; >>>> + padding: 0.8em 1.3em; >>>> + background-color: #F5F5F5; >>>> +} >>>> + >>>> +.field { >>>> + border: 1px dotted #DDDDDD; >>>> + background-color: #FFFFCC; >>>> + padding: 0.2em 0.5em; >>>> +} >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> >>> This body part will be downloaded on demand. >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > From noreply at rubyforge.org Wed Oct 15 09:40:15 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 15 Oct 2008 09:40:15 -0400 (EDT) Subject: [BioCatalogue-developers] [80] trunk: action to submit list of services Message-ID: <20081015134015.6ADB218585D2@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Wed Oct 15 09:49:15 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 15 Oct 2008 09:49:15 -0400 (EDT) Subject: [BioCatalogue-developers] [81] trunk/app/models/soap_service.rb: removed validation statement for description and default description Message-ID: <20081015134915.965E818585CF@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Wed Oct 15 10:25:58 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 15 Oct 2008 10:25:58 -0400 (EDT) Subject: [BioCatalogue-developers] [82] trunk: added some eye-candy for login box Message-ID: <20081015142558.F04A318585B5@rubyforge.org> An HTML attachment was scrubbed... URL: From tlaurent at ebi.ac.uk Thu Oct 16 04:32:30 2008 From: tlaurent at ebi.ac.uk (Thomas Laurent) Date: Thu, 16 Oct 2008 09:32:30 +0100 Subject: [BioCatalogue-developers] mailer on beta site Message-ID: <48F6FC1E.5010002@ebi.ac.uk> Hi guys, I've fixed the mailer on the beta site, we should now be able to do a normal registration with confirmation email from it. Cheers, Thomas From jits at cs.man.ac.uk Sat Oct 18 16:09:58 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Sat, 18 Oct 2008 21:09:58 +0100 Subject: [BioCatalogue-developers] Soap Service Submission Message-ID: <48FA4296.3040608@cs.man.ac.uk> Hi guys, Before I finalise up the soap submission piece I just want to make sure that no else has any uncommitted work on this... if you do please could you let me know about it and possibly commit it? This includes any versioning and duplication checking code. Thanks, Jits From noreply at rubyforge.org Sat Oct 18 16:50:19 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 18 Oct 2008 16:50:19 -0400 (EDT) Subject: [BioCatalogue-developers] [83] trunk: Removed the unneeded Yahoo base CSS files but added the reset one on it' s own. Message-ID: <20081018205020.B5C6618585B1@rubyforge.org> An HTML attachment was scrubbed... URL: From jits at cs.man.ac.uk Sat Oct 18 16:52:35 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Sat, 18 Oct 2008 21:52:35 +0100 Subject: [BioCatalogue-developers] Soap Service Submission Message-ID: <48FA4C93.6010200@cs.man.ac.uk> Hi guys, Before I finalise up the soap submission piece I just want to make sure that no else has any uncommitted work on this... if you do please could you let me know about it and possibly commit it? This includes any versioning and duplication checking code. Thanks, Jits From noreply at rubyforge.org Sun Oct 19 13:28:43 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sun, 19 Oct 2008 13:28:43 -0400 (EDT) Subject: [BioCatalogue-developers] [84] trunk/public/images/box_title_bkgd_green_12.png: image for the sidebar box title bckgd Message-ID: <20081019172844.AD2A4185818C@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Sun Oct 19 13:30:00 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sun, 19 Oct 2008 13:30:00 -0400 (EDT) Subject: [BioCatalogue-developers] [85] trunk/public/stylesheets/styles_2.css: added styles for sidebar template and sidebar boxes Message-ID: <20081019173000.EC7DE185818C@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Sun Oct 19 13:30:43 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sun, 19 Oct 2008 13:30:43 -0400 (EDT) Subject: [BioCatalogue-developers] [86] trunk/app/views/layouts/application_sidebar.html.erb: template for page with sidebar Message-ID: <20081019173043.60A02185818B@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Sun Oct 19 13:32:19 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sun, 19 Oct 2008 13:32:19 -0400 (EDT) Subject: [BioCatalogue-developers] [87] trunk/app/views/layouts/application_wide.html.erb: moved the location of the login box in the code Message-ID: <20081019173219.F0EC7185818B@rubyforge.org> An HTML attachment was scrubbed... URL: From tlaurent at ebi.ac.uk Sun Oct 19 13:39:06 2008 From: tlaurent at ebi.ac.uk (Thomas Laurent) Date: Sun, 19 Oct 2008 18:39:06 +0100 Subject: [BioCatalogue-developers] Sidebar template Message-ID: <48FB70BA.5020500@ebi.ac.uk> Hi guys, I've committed another template for the pages needing a right sidebar (if you want to use it, you'll need to add: layout "application_sidebar" in your controller using this layout). There's an example of a sidebar box in the code (but commented out) as an example if you want to add one (or more). I'm not very happy with the look of the boxes but it looks like the time is running out for me (my wife is starting to have some contractions...), so that'll do for the time being, I'll modify it later. Hope everything will be ok with my check-in, and that I haven't messed up anything. Cheers, Thomas From jits at cs.man.ac.uk Mon Oct 20 00:54:50 2008 From: jits at cs.man.ac.uk (jits at cs.man.ac.uk) Date: Mon, 20 Oct 2008 05:54:50 +0100 (BST) Subject: [BioCatalogue-developers] Illness Message-ID: <2eb9591ff8d9e19807b481deeb795f0b.squirrel@webmail.cs.man.ac.uk> Hi guys, My plan was to catch up with a lot of BioCatalogue work this weekend but unfortunately the cold that I've had on and off in the last 2.5 months has culminated in a really bad cold and fever this weekend :( :( This also means that I'm going to be bed ridden for atleast the next couple of days. I'll try and get some work done when I can but it sounds like progress on the pilot is being hampered a lot :-( (2 weeks ago my cold had also gone worse, but not as much as now). Sorry about this guys! Jits From ericnzuo at ebi.ac.uk Mon Oct 20 04:29:08 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 20 Oct 2008 09:29:08 +0100 Subject: [BioCatalogue-developers] Sidebar template In-Reply-To: <48FB70BA.5020500@ebi.ac.uk> References: <48FB70BA.5020500@ebi.ac.uk> Message-ID: <48FC4154.10007@ebi.ac.uk> Thanks Thomas and best of luck! Eric Thomas Laurent wrote: > Hi guys, > > I've committed another template for the pages needing a right sidebar > (if you want to use it, you'll need to add: > layout "application_sidebar" > in your controller using this layout). > There's an example of a sidebar box in the code (but commented out) as > an example if you want to add one (or more). > I'm not very happy with the look of the boxes but it looks like the > time is running out for me (my wife is starting to have some > contractions...), so that'll do for the time being, I'll modify it later. > > Hope everything will be ok with my check-in, and that I haven't messed > up anything. > > Cheers, > Thomas > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From ericnzuo at ebi.ac.uk Mon Oct 20 04:33:25 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 20 Oct 2008 09:33:25 +0100 Subject: [BioCatalogue-developers] Soap Service Submission In-Reply-To: <48FA4C93.6010200@cs.man.ac.uk> References: <48FA4C93.6010200@cs.man.ac.uk> Message-ID: <48FC4255.90008@ebi.ac.uk> Hi Jits, Please go ahead. It is one of the things that was on my list but I would rather spend time on biomoby services. cheers! Eric Jiten Bhagat wrote: > Hi guys, > > Before I finalise up the soap submission piece I just want to make sure > that no else has any uncommitted work on this... if you do please could > you let me know about it and possibly commit it? > > This includes any versioning and duplication checking code. > > Thanks, > Jits > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From ericnzuo at ebi.ac.uk Mon Oct 20 04:30:22 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Mon, 20 Oct 2008 09:30:22 +0100 Subject: [BioCatalogue-developers] Illness In-Reply-To: <2eb9591ff8d9e19807b481deeb795f0b.squirrel@webmail.cs.man.ac.uk> References: <2eb9591ff8d9e19807b481deeb795f0b.squirrel@webmail.cs.man.ac.uk> Message-ID: <48FC419E.1060507@ebi.ac.uk> Hope it gets better soon. We can't beat nature. regards, Eric jits at cs.man.ac.uk wrote: > Hi guys, > > My plan was to catch up with a lot of BioCatalogue work this weekend but > unfortunately the cold that I've had on and off in the last 2.5 months has > culminated in a really bad cold and fever this weekend :( :( > > This also means that I'm going to be bed ridden for atleast the next > couple of days. I'll try and get some work done when I can but it sounds > like progress on the pilot is being hampered a lot :-( (2 weeks ago my > cold had also gone worse, but not as much as now). > > Sorry about this guys! > > Jits > > > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From ericnzuo at ebi.ac.uk Thu Oct 23 04:59:29 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Thu, 23 Oct 2008 09:59:29 +0100 Subject: [BioCatalogue-developers] Acts as annotatable plugin In-Reply-To: <48FC4255.90008@ebi.ac.uk> References: <48FA4C93.6010200@cs.man.ac.uk> <48FC4255.90008@ebi.ac.uk> Message-ID: <49003CF1.3050609@ebi.ac.uk> Hi Guys, In my quest to undestand how plugins are written, I ploughed abit into the acts_as_commentable plugin came up with what I called acts_as_annotatable plugin. It does work as I expected it to, ie, can be added to any AR model to make it annotatable. I also made a form partial for adding the annotations and an annotation controller. I have tried them on my test project and it does seem to work fine. One thing that crossed my mind was that we have 'key' and 'value' as field in the annotations table. I have reservations towards such generic names. I would rather it was called 'annotation_key' and 'annotation_value'. I know Jits was going to do this plugin, so I hope this does not enfringe on anything he has done... Maybe Jits will also like to see this, so that if he is fine with it, we can check it in. On the otherhand it may be possible for him to correct any stupid mistakes of mine. cheers Eric >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Thu Oct 23 05:26:08 2008 From: jits at cs.man.ac.uk (jits at cs.man.ac.uk) Date: Thu, 23 Oct 2008 10:26:08 +0100 (BST) Subject: [BioCatalogue-developers] Acts as annotatable plugin In-Reply-To: <49003CF1.3050609@ebi.ac.uk> References: <48FA4C93.6010200@cs.man.ac.uk> <48FC4255.90008@ebi.ac.uk> <49003CF1.3050609@ebi.ac.uk> Message-ID: <03c723e8e288f0c47e097b1a0471c47e.squirrel@webmail.cs.man.ac.uk> Hi Eric, Sounds good! Nice one. Commit this to the repo whenever you can and I can integrate any changes in. I had many ideas for this (eg: setting up automatic routings so you could get at annotation sets easily, such as: /service/12/annotations/availability), but some of these will have to wait till after the pilot. Cheers, Jits > Hi Guys, > In my quest to undestand how plugins are written, I ploughed abit into > the acts_as_commentable plugin came up with what I called > acts_as_annotatable plugin. It does work as I expected it to, ie, can be > added to any AR model to make it annotatable. I also made a form partial > for adding the annotations and an annotation controller. I have tried > them on my test project and it does seem to work fine. One thing that > crossed my mind was that we have 'key' and 'value' as field in the > annotations table. I have reservations towards such generic names. I > would rather it was called 'annotation_key' and 'annotation_value'. > I know Jits was going to do this plugin, so I hope this does not > enfringe on anything he has done... Maybe Jits will also like to see > this, so that if he is fine with it, we can check it in. On the > otherhand it may be possible for him to correct any stupid mistakes of > mine. > > cheers > Eric > >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> > > From noreply at rubyforge.org Thu Oct 23 07:40:07 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 23 Oct 2008 07:40:07 -0400 (EDT) Subject: [BioCatalogue-developers] [88] trunk: added the 'acts_as_annotatable' plugin to enable adding annotations to AR models declaratively. Message-ID: <20081023114008.CEDB418581B0@rubyforge.org> An HTML attachment was scrubbed... URL: From ericnzuo at ebi.ac.uk Thu Oct 23 07:42:35 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Thu, 23 Oct 2008 12:42:35 +0100 Subject: [BioCatalogue-developers] Acts as annotatable plugin In-Reply-To: <49003CF1.3050609@ebi.ac.uk> References: <48FA4C93.6010200@cs.man.ac.uk> <48FC4255.90008@ebi.ac.uk> <49003CF1.3050609@ebi.ac.uk> Message-ID: <4900632B.4060805@ebi.ac.uk> I have just committed the code. Please shout if you find anything weird... Eric Eric Nzuobontane wrote: > Hi Guys, > In my quest to undestand how plugins are written, I ploughed abit into > the acts_as_commentable plugin came up with what I called > acts_as_annotatable plugin. It does work as I expected it to, ie, can > be added to any AR model to make it annotatable. I also made a form > partial for adding the annotations and an annotation controller. I > have tried them on my test project and it does seem to work fine. One > thing that crossed my mind was that we have 'key' and 'value' as field > in the annotations table. I have reservations towards such generic > names. I would rather it was called 'annotation_key' and > 'annotation_value'. > I know Jits was going to do this plugin, so I hope this does not > enfringe on anything he has done... Maybe Jits will also like to see > this, so that if he is fine with it, we can check it in. On the > otherhand it may be possible for him to correct any stupid mistakes of > mine. > > cheers > Eric > >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From ericnzuo at ebi.ac.uk Thu Oct 23 07:46:45 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Thu, 23 Oct 2008 12:46:45 +0100 Subject: [BioCatalogue-developers] Acts as annotatable plugin In-Reply-To: <4900632B.4060805@ebi.ac.uk> References: <48FA4C93.6010200@cs.man.ac.uk> <48FC4255.90008@ebi.ac.uk> <49003CF1.3050609@ebi.ac.uk> <4900632B.4060805@ebi.ac.uk> Message-ID: <49006425.6030408@ebi.ac.uk> replying to my own mail :) ... the views(shared partial) would do with some cosmetics. I trust you will handle that... Eric Eric Nzuobontane wrote: > I have just committed the code. Please shout if you find anything > weird... > Eric > > > Eric Nzuobontane wrote: >> Hi Guys, >> In my quest to undestand how plugins are written, I ploughed abit >> into the acts_as_commentable plugin came up with what I called >> acts_as_annotatable plugin. It does work as I expected it to, ie, can >> be added to any AR model to make it annotatable. I also made a form >> partial for adding the annotations and an annotation controller. I >> have tried them on my test project and it does seem to work fine. One >> thing that crossed my mind was that we have 'key' and 'value' as >> field in the annotations table. I have reservations towards such >> generic names. I would rather it was called 'annotation_key' and >> 'annotation_value'. >> I know Jits was going to do this plugin, so I hope this does not >> enfringe on anything he has done... Maybe Jits will also like to see >> this, so that if he is fine with it, we can check it in. On the >> otherhand it may be possible for him to correct any stupid mistakes >> of mine. >> >> cheers >> Eric >> >>>> >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From jits at cs.man.ac.uk Sun Oct 26 17:30:52 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Sun, 26 Oct 2008 21:30:52 +0000 Subject: [BioCatalogue-developers] Acts as annotatable plugin In-Reply-To: <49006425.6030408@ebi.ac.uk> References: <48FA4C93.6010200@cs.man.ac.uk> <48FC4255.90008@ebi.ac.uk> <49003CF1.3050609@ebi.ac.uk> <4900632B.4060805@ebi.ac.uk> <49006425.6030408@ebi.ac.uk> Message-ID: <4904E18C.7080602@cs.man.ac.uk> Yeap, these will be done in due time :-) Jits Eric Nzuobontane wrote: > replying to my own mail :) ... the views(shared partial) would do with > some cosmetics. I trust you will handle that... > > Eric > > > Eric Nzuobontane wrote: >> I have just committed the code. Please shout if you find anything >> weird... >> Eric >> >> >> Eric Nzuobontane wrote: >>> Hi Guys, >>> In my quest to undestand how plugins are written, I ploughed abit >>> into the acts_as_commentable plugin came up with what I called >>> acts_as_annotatable plugin. It does work as I expected it to, ie, >>> can be added to any AR model to make it annotatable. I also made a >>> form partial for adding the annotations and an annotation >>> controller. I have tried them on my test project and it does seem to >>> work fine. One thing that crossed my mind was that we have 'key' and >>> 'value' as field in the annotations table. I have reservations >>> towards such generic names. I would rather it was called >>> 'annotation_key' and 'annotation_value'. >>> I know Jits was going to do this plugin, so I hope this does not >>> enfringe on anything he has done... Maybe Jits will also like to see >>> this, so that if he is fine with it, we can check it in. On the >>> otherhand it may be possible for him to correct any stupid mistakes >>> of mine. >>> >>> cheers >>> Eric >>> >>>>> >>>>> _______________________________________________ >>>>> BioCatalogue-developers mailing list >>>>> BioCatalogue-developers at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> >>>> _______________________________________________ >>>> BioCatalogue-developers mailing list >>>> BioCatalogue-developers at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>>> >>> >>> _______________________________________________ >>> BioCatalogue-developers mailing list >>> BioCatalogue-developers at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >>> >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> > From noreply at rubyforge.org Sun Oct 26 21:55:38 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sun, 26 Oct 2008 21:55:38 -0400 (EDT) Subject: [BioCatalogue-developers] [89] trunk/app/views/users/new.html.erb: don't ask for display name, this should be only part of the profile (user/edit). Message-ID: <20081027015539.039BD18585AA@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Sun Oct 26 21:55:54 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sun, 26 Oct 2008 21:55:54 -0400 (EDT) Subject: [BioCatalogue-developers] [90] trunk/app/views/users/edit.html.erb: drop-down menu for country selection. Message-ID: <20081027015554.DAC3D16780DC@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Mon Oct 27 09:17:50 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 27 Oct 2008 09:17:50 -0400 (EDT) Subject: [BioCatalogue-developers] [91] trunk: Minor UI tweaks for the soap service submission page. Message-ID: <20081027131750.AFE611858184@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Mon Oct 27 10:55:27 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 27 Oct 2008 10:55:27 -0400 (EDT) Subject: [BioCatalogue-developers] [92] trunk: Added new content blobs mechanism - these are used to store and binary data in a seperate table , so as to reduce the load on the parent tables. Message-ID: <20081027145527.8D9C016780DF@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Mon Oct 27 11:38:30 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 27 Oct 2008 11:38:30 -0400 (EDT) Subject: [BioCatalogue-developers] [93] trunk/config/database.yml: Removed database.yml from codebase ( was added by mistake in last commit). Message-ID: <20081027153830.204B716780E0@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Mon Oct 27 12:44:31 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 27 Oct 2008 12:44:31 -0400 (EDT) Subject: [BioCatalogue-developers] [94] trunk/vendor/plugins: Added GeoKit plugin to provide geocoding and other such capabilities. Message-ID: <20081027164432.339F516780DA@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Mon Oct 27 12:56:24 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 27 Oct 2008 12:56:24 -0400 (EDT) Subject: [BioCatalogue-developers] [95] trunk/config/initializers/geokit_private.rb.pre: Settings template for the GeoKit plugin. Message-ID: <20081027165624.412DA16780D9@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Mon Oct 27 19:49:33 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 27 Oct 2008 19:49:33 -0400 (EDT) Subject: [BioCatalogue-developers] [96] trunk: [Unstable] Initial work on refactoring the WSDL parsing stuff to make it easier for the SOAP Service submission work . Message-ID: <20081027234933.1E732185818B@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 28 07:35:29 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 28 Oct 2008 07:35:29 -0400 (EDT) Subject: [BioCatalogue-developers] [97] trunk: Stabilised work on the WSDL Parsing. Message-ID: <20081028113529.CD962185818F@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 28 07:36:56 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 28 Oct 2008 07:36:56 -0400 (EDT) Subject: [BioCatalogue-developers] [98] trunk/lib/biocat_wsdl_parser.rb: Removed old parser file. Message-ID: <20081028113656.1D0BE185818F@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 28 09:17:10 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 28 Oct 2008 09:17:10 -0400 (EDT) Subject: [BioCatalogue-developers] [99] trunk/config/environment.rb: Updated Rails gem version to 2.1.2. Message-ID: <20081028131710.43E561858192@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Tue Oct 28 09:23:52 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 28 Oct 2008 09:23:52 -0400 (EDT) Subject: [BioCatalogue-developers] [100] trunk: Removed reference to old WSDL Parser file ( which was preventing the server from starting up). Message-ID: <20081028132352.7F70E1858192@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Wed Oct 29 09:16:55 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 29 Oct 2008 09:16:55 -0400 (EDT) Subject: [BioCatalogue-developers] [101] trunk: Initial implementation of the SOAP create action. Message-ID: <20081029131655.20B2F1858184@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Wed Oct 29 13:02:34 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 29 Oct 2008 13:02:34 -0400 (EDT) Subject: [BioCatalogue-developers] [102] trunk/db/migrate/ 20081029165721_add_version_display_text_to_service_versions.rb: Migration script to add 'version_display_text' to service_versions table. Message-ID: <20081029170235.0429918588E4@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Wed Oct 29 14:11:18 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 29 Oct 2008 14:11:18 -0400 (EDT) Subject: [BioCatalogue-developers] [103] trunk/app: Duplication check for the load_wsdl action - this will now show the user the service that has already been submitted . Message-ID: <20081029181118.8C62418588E5@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Wed Oct 29 15:07:55 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 29 Oct 2008 15:07:55 -0400 (EDT) Subject: [BioCatalogue-developers] [104] trunk/app/views/soap_services/show.html.erb: Message-ID: <20081029190755.651DA16780D7@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Wed Oct 29 18:28:47 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 29 Oct 2008 18:28:47 -0400 (EDT) Subject: [BioCatalogue-developers] [105] trunk: Restructured the soap service submission UI to better display information after the wsdl load . Message-ID: <20081029222847.1A8A016780D7@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Wed Oct 29 18:47:58 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 29 Oct 2008 18:47:58 -0400 (EDT) Subject: [BioCatalogue-developers] [106] trunk/app/controllers/soap_services_controller.rb: Added duplicate checking to the create action for soap services. Message-ID: <20081029224758.BC60C18581BB@rubyforge.org> An HTML attachment was scrubbed... URL: From jits at cs.man.ac.uk Mon Oct 27 20:05:53 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Tue, 28 Oct 2008 00:05:53 +0000 Subject: [BioCatalogue-developers] Unstable commit Message-ID: <49065761.2080207@cs.man.ac.uk> Hi guys, I've just committed something marked as [Unstable].. sorry about this recklessness... my laptop is acting weird so I didn't want to lose the work I did this evening. I'll be continuing with it first thing tomorrow morning and should have it all sorted before lunchtime (so he says!). Cheers, Jits From jits at cs.man.ac.uk Thu Oct 30 08:21:19 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Thu, 30 Oct 2008 12:21:19 +0000 Subject: [BioCatalogue-developers] WSDL Parsing In-Reply-To: <4909A60D.6080406@ebi.ac.uk> References: <4908DFF9.40902@cs.man.ac.uk> <49097465.4080706@ebi.ac.uk> <49097512.7030508@cs.man.ac.uk> <49097595.2030009@ebi.ac.uk> <49097629.7060605@cs.man.ac.uk> <4909A60D.6080406@ebi.ac.uk> Message-ID: <4909A6BF.4030808@cs.man.ac.uk> Hi Eric, Ahhh okay! Nice analysis on that :-) Jits PS: biocatalogue-developers is back Eric Nzuobontane wrote: > Hi Jits, > Thanks for spoting the problem with the parsing. On the > parameter_order attribute, it is gotten from the wsdl but apparently > being truncated in the parse function. On the empty hash for certain > inputs/outs, the parser is not processing documentation elements for > inputs/outputs. That empty hash was for those inputs/output messages > with documentation elements...I will fix that now.. > > Eric > > > before parse > > [{"inputs"=> > [{"computational_type"=>"xsd:string", "name"=>"database"}, > {"computational_type"=>"xsd:string", "name"=>"sequence"}, > {"computational_type"=>"xsd:string", "name"=>"email"}], > "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "operation"=> > {"name"=>"blastp", "parameter_order"=>"database sequence email"}}, > {"inputs"=> > [{"computational_type"=>"xsd:string", "name"=>"database"}, > {"computational_type"=>"xsd:string", "name"=>"sequence"}, > {"computational_type"=>"xsd:string", "name"=>"email"}], > "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "operation"=> > {"name"=>"blastn", "parameter_order"=>"database sequence email"}}, > {"inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"result"}], > "operation"=>{"name"=>"getOutput", "parameter_order"=>"jobid"}}, > {"inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"result"}], > "operation"=>{"name"=>"getXML", "parameter_order"=>"jobid"}}, > {"inputs"=> > [{"computational_type"=>"tns:inputParams", "name"=>"params"}, > {"computational_type"=>"tns:WSArrayofData", "name"=>"content"}], > "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "operation"=>{"name"=>"runWUBlast", "parameter_order"=>"params > content"}}, > {"inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"status"}], > "operation"=>{"name"=>"checkStatus", "parameter_order"=>"jobid"}}, > {"inputs"=> > [{"computational_type"=>"xsd:string", "name"=>"jobid"}, > {"computational_type"=>"xsd:string", "name"=>"type"}], > "outputs"=>[{"computational_type"=>"xsd:base64Binary", > "name"=>"result"}], > "operation"=>{"name"=>"poll", "parameter_order"=>"jobid type"}}, > {"inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "outputs"=>[{"computational_type"=>"tns:WSArrayofFile", > "name"=>"results"}], > "operation"=>{"name"=>"getResults", "parameter_order"=>"jobid"}}, > {"inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "outputs"=> > [{"computational_type"=>"tns:ArrayOf_xsd_string", "name"=>"result"}], > "operation"=>{"name"=>"getIds", "parameter_order"=>"jobid"}}, > {"inputs"=> > [{"computational_type"=>"xsd:string", "name"=>"jobid"}, > {"computational_type"=>"xsd:string", "name"=>"outformat"}], > "outputs"=>[{"computational_type"=>"xsd:base64Binary", > "name"=>"result"}], > "operation"=>{"name"=>"polljob", "parameter_order"=>"jobid outformat"}}, > {"inputs"=> > [{"computational_type"=>"tns:inputParams", "name"=>"params"}, > {"computational_type"=>"xsd:base64Binary", "name"=>"content"}], > "outputs"=>[{"computational_type"=>"xsd:base64Binary", > "name"=>"result"}], > "operation"=>{"name"=>"doWUBlast", "parameter_order"=>"params > content"}}] > > > after parse > > [{"name"=>"WSWUBlastService", > "operations"=> > [{"name"=>"blastp", > "inputs"=> > [{"computational_type"=>"xsd:string", "name"=>"database"}, > {"computational_type"=>"xsd:string", "name"=>"sequence"}, > {"computational_type"=>"xsd:string", "name"=>"email"}], > "description"=>nil, > "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}]}, > {"name"=>"blastn", > "inputs"=> > [{"computational_type"=>"xsd:string", "name"=>"database"}, > {"computational_type"=>"xsd:string", "name"=>"sequence"}, > {"computational_type"=>"xsd:string", "name"=>"email"}], > "description"=>nil, > "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}]}, > {"name"=>"getOutput", > "inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "description"=>nil, > "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"result"}]}, > {"name"=>"getXML", > "inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "description"=>nil, > "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"result"}]}, > {"name"=>"runWUBlast", > "inputs"=> > [{"computational_type"=>"tns:inputParams", "name"=>"params"}, > {"computational_type"=>"tns:WSArrayofData", "name"=>"content"}], > "description"=>nil, > "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}]}, > {"name"=>"checkStatus", > "inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "description"=>nil, > "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"status"}]}, > {"name"=>"poll", > "inputs"=> > [{"computational_type"=>"xsd:string", "name"=>"jobid"}, > {"computational_type"=>"xsd:string", "name"=>"type"}], > "description"=>nil, > "outputs"=> > [{"computational_type"=>"xsd:base64Binary", "name"=>"result"}]}, > {"name"=>"getResults", > "inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "description"=>nil, > "outputs"=> > [{"computational_type"=>"tns:WSArrayofFile", "name"=>"results"}]}, > {"name"=>"getIds", > "inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], > "description"=>nil, > "outputs"=> > [{"computational_type"=>"tns:ArrayOf_xsd_string", > "name"=>"result"}]}, > {"name"=>"polljob", > "inputs"=> > [{"computational_type"=>"xsd:string", "name"=>"jobid"}, > {"computational_type"=>"xsd:string", "name"=>"outformat"}], > "description"=>nil, > "outputs"=> > [{"computational_type"=>"xsd:base64Binary", "name"=>"result"}]}, > {"name"=>"doWUBlast", > "inputs"=> > [{"computational_type"=>"tns:inputParams", "name"=>"params"}, > {"computational_type"=>"xsd:base64Binary", "name"=>"content"}], > "description"=>nil, > "outputs"=> > [{"computational_type"=>"xsd:base64Binary", "name"=>"result"}]}], > "description"=> > " Documentation for this service can be found > at\n\t\thttp://www.ebi.ac.uk/Tools/webservices "}, > [], > > Jiten Bhagat wrote: >> Look in the text file i attached in the original email to see a >> better formatted version. >> >> Jits >> >> >> Eric Nzuobontane wrote: >>> I do not understand that... let me check... >>> >>> Eric >>> >>> >>> Jiten Bhagat wrote: >>>> Eric Nzuobontane wrote: >>>>> Jiten Bhagat wrote: >>>>>> Hi Eric, >>>>>> >>>>>> I've attached the service_info structure I get when I use the >>>>>> WSDL parsing on the Blast service you sent me earlier >>>>>> (http://www.ebi.ac.uk/Tools/webservices/wsdl/WSWUBlast.wsdl). >>>>>> >>>>>> If you notice on the 5th, 6th 7th, and 8th operations, empty >>>>>> hashes are being returned for inputs and/or outputs... do you >>>>>> know why? >>>>> probably those operations do not take any inputs or generate outputs. >>>> >>>> Huh? >>>> >>>> An example... >>>> >>>> { >>>> >>>> "name"=>"poll", >>>> >>>> "inputs"=>[ >>>> >>>> {"computational_type"=>"xsd:string", "name"=>"jobid"}, >>>> >>>> {"computational_type"=>"xsd:string", "name"=>"type"}, >>>> >>>> {} ], >>>> >>>> "description"=>nil, >>>> >>>> "outputs"=>[ >>>> >>>> {"computational_type"=>"xsd:base64Binary", "name"=>"result"}, >>>> >>>> {} ] >>>> >>>> }, >>>> >>>> >>>> You can clearly see it has 2 inputs and 1 output, but also empty >>>> hashes for a 3rd input and a 2nd output. >>>> >>>> Just want to make sure it's not outputting this because it failed >>>> to process something and therefore we are losing data from the WSDL! >>>> >>>> Jits >>>> >>>>> >>>>> >>> > From ericnzuo at ebi.ac.uk Thu Oct 30 08:42:26 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Thu, 30 Oct 2008 12:42:26 +0000 Subject: [BioCatalogue-developers] WSDL Parsing In-Reply-To: <4909A6BF.4030808@cs.man.ac.uk> References: <4908DFF9.40902@cs.man.ac.uk> <49097465.4080706@ebi.ac.uk> <49097512.7030508@cs.man.ac.uk> <49097595.2030009@ebi.ac.uk> <49097629.7060605@cs.man.ac.uk> <4909A60D.6080406@ebi.ac.uk> <4909A6BF.4030808@cs.man.ac.uk> Message-ID: <4909ABB2.9010608@ebi.ac.uk> > > > PS: biocatalogue-developers is back I was just going to ask you what the issue was... > > > Eric Nzuobontane wrote: >> Hi Jits, >> Thanks for spoting the problem with the parsing. On the >> parameter_order attribute, it is gotten from the wsdl but apparently >> being truncated in the parse function. On the empty hash for certain >> inputs/outs, the parser is not processing documentation elements for >> inputs/outputs. That empty hash was for those inputs/output messages >> with documentation elements...I will fix that now.. >> >> Eric >> >> >> before parse >> >> [{"inputs"=> >> [{"computational_type"=>"xsd:string", "name"=>"database"}, >> {"computational_type"=>"xsd:string", "name"=>"sequence"}, >> {"computational_type"=>"xsd:string", "name"=>"email"}], >> "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "operation"=> >> {"name"=>"blastp", "parameter_order"=>"database sequence email"}}, >> {"inputs"=> >> [{"computational_type"=>"xsd:string", "name"=>"database"}, >> {"computational_type"=>"xsd:string", "name"=>"sequence"}, >> {"computational_type"=>"xsd:string", "name"=>"email"}], >> "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "operation"=> >> {"name"=>"blastn", "parameter_order"=>"database sequence email"}}, >> {"inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"result"}], >> "operation"=>{"name"=>"getOutput", "parameter_order"=>"jobid"}}, >> {"inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"result"}], >> "operation"=>{"name"=>"getXML", "parameter_order"=>"jobid"}}, >> {"inputs"=> >> [{"computational_type"=>"tns:inputParams", "name"=>"params"}, >> {"computational_type"=>"tns:WSArrayofData", "name"=>"content"}], >> "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "operation"=>{"name"=>"runWUBlast", "parameter_order"=>"params >> content"}}, >> {"inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"status"}], >> "operation"=>{"name"=>"checkStatus", "parameter_order"=>"jobid"}}, >> {"inputs"=> >> [{"computational_type"=>"xsd:string", "name"=>"jobid"}, >> {"computational_type"=>"xsd:string", "name"=>"type"}], >> "outputs"=>[{"computational_type"=>"xsd:base64Binary", >> "name"=>"result"}], >> "operation"=>{"name"=>"poll", "parameter_order"=>"jobid type"}}, >> {"inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "outputs"=>[{"computational_type"=>"tns:WSArrayofFile", >> "name"=>"results"}], >> "operation"=>{"name"=>"getResults", "parameter_order"=>"jobid"}}, >> {"inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "outputs"=> >> [{"computational_type"=>"tns:ArrayOf_xsd_string", "name"=>"result"}], >> "operation"=>{"name"=>"getIds", "parameter_order"=>"jobid"}}, >> {"inputs"=> >> [{"computational_type"=>"xsd:string", "name"=>"jobid"}, >> {"computational_type"=>"xsd:string", "name"=>"outformat"}], >> "outputs"=>[{"computational_type"=>"xsd:base64Binary", >> "name"=>"result"}], >> "operation"=>{"name"=>"polljob", "parameter_order"=>"jobid >> outformat"}}, >> {"inputs"=> >> [{"computational_type"=>"tns:inputParams", "name"=>"params"}, >> {"computational_type"=>"xsd:base64Binary", "name"=>"content"}], >> "outputs"=>[{"computational_type"=>"xsd:base64Binary", >> "name"=>"result"}], >> "operation"=>{"name"=>"doWUBlast", "parameter_order"=>"params >> content"}}] >> >> >> after parse >> >> [{"name"=>"WSWUBlastService", >> "operations"=> >> [{"name"=>"blastp", >> "inputs"=> >> [{"computational_type"=>"xsd:string", "name"=>"database"}, >> {"computational_type"=>"xsd:string", "name"=>"sequence"}, >> {"computational_type"=>"xsd:string", "name"=>"email"}], >> "description"=>nil, >> "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}]}, >> {"name"=>"blastn", >> "inputs"=> >> [{"computational_type"=>"xsd:string", "name"=>"database"}, >> {"computational_type"=>"xsd:string", "name"=>"sequence"}, >> {"computational_type"=>"xsd:string", "name"=>"email"}], >> "description"=>nil, >> "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}]}, >> {"name"=>"getOutput", >> "inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "description"=>nil, >> "outputs"=>[{"computational_type"=>"xsd:string", >> "name"=>"result"}]}, >> {"name"=>"getXML", >> "inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "description"=>nil, >> "outputs"=>[{"computational_type"=>"xsd:string", >> "name"=>"result"}]}, >> {"name"=>"runWUBlast", >> "inputs"=> >> [{"computational_type"=>"tns:inputParams", "name"=>"params"}, >> {"computational_type"=>"tns:WSArrayofData", "name"=>"content"}], >> "description"=>nil, >> "outputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}]}, >> {"name"=>"checkStatus", >> "inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "description"=>nil, >> "outputs"=>[{"computational_type"=>"xsd:string", >> "name"=>"status"}]}, >> {"name"=>"poll", >> "inputs"=> >> [{"computational_type"=>"xsd:string", "name"=>"jobid"}, >> {"computational_type"=>"xsd:string", "name"=>"type"}], >> "description"=>nil, >> "outputs"=> >> [{"computational_type"=>"xsd:base64Binary", "name"=>"result"}]}, >> {"name"=>"getResults", >> "inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "description"=>nil, >> "outputs"=> >> [{"computational_type"=>"tns:WSArrayofFile", "name"=>"results"}]}, >> {"name"=>"getIds", >> "inputs"=>[{"computational_type"=>"xsd:string", "name"=>"jobid"}], >> "description"=>nil, >> "outputs"=> >> [{"computational_type"=>"tns:ArrayOf_xsd_string", >> "name"=>"result"}]}, >> {"name"=>"polljob", >> "inputs"=> >> [{"computational_type"=>"xsd:string", "name"=>"jobid"}, >> {"computational_type"=>"xsd:string", "name"=>"outformat"}], >> "description"=>nil, >> "outputs"=> >> [{"computational_type"=>"xsd:base64Binary", "name"=>"result"}]}, >> {"name"=>"doWUBlast", >> "inputs"=> >> [{"computational_type"=>"tns:inputParams", "name"=>"params"}, >> {"computational_type"=>"xsd:base64Binary", "name"=>"content"}], >> "description"=>nil, >> "outputs"=> >> [{"computational_type"=>"xsd:base64Binary", "name"=>"result"}]}], >> "description"=> >> " Documentation for this service can be found >> at\n\t\thttp://www.ebi.ac.uk/Tools/webservices "}, >> [], >> >> Jiten Bhagat wrote: >>> Look in the text file i attached in the original email to see a >>> better formatted version. >>> >>> Jits >>> >>> >>> Eric Nzuobontane wrote: >>>> I do not understand that... let me check... >>>> >>>> Eric >>>> >>>> >>>> Jiten Bhagat wrote: >>>>> Eric Nzuobontane wrote: >>>>>> Jiten Bhagat wrote: >>>>>>> Hi Eric, >>>>>>> >>>>>>> I've attached the service_info structure I get when I use the >>>>>>> WSDL parsing on the Blast service you sent me earlier >>>>>>> (http://www.ebi.ac.uk/Tools/webservices/wsdl/WSWUBlast.wsdl). >>>>>>> >>>>>>> If you notice on the 5th, 6th 7th, and 8th operations, empty >>>>>>> hashes are being returned for inputs and/or outputs... do you >>>>>>> know why? >>>>>> probably those operations do not take any inputs or generate >>>>>> outputs. >>>>> >>>>> Huh? >>>>> >>>>> An example... >>>>> >>>>> { >>>>> >>>>> "name"=>"poll", >>>>> >>>>> "inputs"=>[ >>>>> >>>>> {"computational_type"=>"xsd:string", "name"=>"jobid"}, >>>>> >>>>> {"computational_type"=>"xsd:string", "name"=>"type"}, >>>>> >>>>> {} ], >>>>> >>>>> "description"=>nil, >>>>> >>>>> "outputs"=>[ >>>>> >>>>> {"computational_type"=>"xsd:base64Binary", "name"=>"result"}, >>>>> >>>>> {} ] >>>>> >>>>> }, >>>>> >>>>> >>>>> You can clearly see it has 2 inputs and 1 output, but also empty >>>>> hashes for a 3rd input and a 2nd output. >>>>> >>>>> Just want to make sure it's not outputting this because it failed >>>>> to process something and therefore we are losing data from the WSDL! >>>>> >>>>> Jits >>>>> >>>>>> >>>>>> >>>> >> -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From noreply at rubyforge.org Thu Oct 30 09:03:51 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 30 Oct 2008 09:03:51 -0400 (EDT) Subject: [BioCatalogue-developers] [107] trunk/lib/wsdl_parser.rb: Fix for the truncated parameter_order attribute and processing of doc tags in messages Message-ID: <20081030130352.0F4741858182@rubyforge.org> An HTML attachment was scrubbed... URL: From jits at cs.man.ac.uk Thu Oct 30 09:17:48 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Thu, 30 Oct 2008 13:17:48 +0000 Subject: [BioCatalogue-developers] [107] trunk/lib/wsdl_parser.rb: Fix for the truncated parameter_order attribute and processing of doc tags in messages In-Reply-To: <20081030130352.0F4741858182@rubyforge.org> References: <20081030130352.0F4741858182@rubyforge.org> Message-ID: <4909B3FC.6080005@cs.man.ac.uk> I'll update the SoapService model to store the parameter_order Cheers, Jits noreply at rubyforge.org wrote: > > Revision > 107 > Author > ebontane > Date > 2008-10-30 09:03:50 -0400 (Thu, 30 Oct 2008) > > > Log Message > > Fix for the truncated parameter_order attribute and processing of doc tags in messages > > > Modified Paths > > * trunk/lib/wsdl_parser.rb <#trunklibwsdl_parserrb> > > > Diff > > > Modified: trunk/lib/wsdl_parser.rb (106 => 107) > > > --- trunk/lib/wsdl_parser.rb 2008-10-29 22:47:57 UTC (rev 106) > +++ trunk/lib/wsdl_parser.rb 2008-10-30 13:03:50 UTC (rev 107) > @@ -78,10 +78,11 @@ > service_attributes.each do |op| > op_hash = { } > > - op_hash["name"] = op["operation"]["name"] > - op_hash["description"] = op["operation"]["description"] > - op_hash["inputs"] = op["inputs"] > - op_hash["outputs"] = op["outputs"] > + op_hash["name"] = op["operation"]["name"] > + op_hash["description"] = op["operation"]["description"] > + op_hash["parameter_order"]= op["operation"]["parameter_order"] > + op_hash["inputs"] = op["inputs"] > + op_hash["outputs"] = op["outputs"] > > service_info["operations"] << op_hash > end > @@ -148,15 +149,18 @@ > my_message_attributes = [] > > root.each_element("//#{prefix}message"){|message| > - my_message = {} > + my_message = {"description" => ""} > my_parts =[] > > my_message["the_message"] = get_hash(message.attributes) > if message.elements["#{prefix}part"] > - message.elements.each{ |part| > + message.elements.each("#{prefix}part"){ |part| > my_parts << get_hash(part.attributes) > - } > + } > end > + if message.elements["#{prefix}documentation"] > + my_message["description"] = message.elements["#{prefix}documentation"].text > + end > my_message["the_parts"]= my_parts > my_message_attributes << my_message > } > ------------------------------------------------------------------------ > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jits at cs.man.ac.uk Thu Oct 30 09:20:36 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Thu, 30 Oct 2008 13:20:36 +0000 Subject: [BioCatalogue-developers] [107] trunk/lib/wsdl_parser.rb: Fix for the truncated parameter_order attribute and processing of doc tags in messages In-Reply-To: <20081030130352.0F4741858182@rubyforge.org> References: <20081030130352.0F4741858182@rubyforge.org> Message-ID: <4909B4A4.3080501@cs.man.ac.uk> Eric, Is there a way of getting the "endpoint" for each operation from the WSDL parsing? Would be useful to have this in the service_info structure if possible. Cheers, Jits noreply at rubyforge.org wrote: > > Revision > 107 > Author > ebontane > Date > 2008-10-30 09:03:50 -0400 (Thu, 30 Oct 2008) > > > Log Message > > Fix for the truncated parameter_order attribute and processing of doc tags in messages > > > Modified Paths > > * trunk/lib/wsdl_parser.rb <#trunklibwsdl_parserrb> > > > Diff > > > Modified: trunk/lib/wsdl_parser.rb (106 => 107) > > > --- trunk/lib/wsdl_parser.rb 2008-10-29 22:47:57 UTC (rev 106) > +++ trunk/lib/wsdl_parser.rb 2008-10-30 13:03:50 UTC (rev 107) > @@ -78,10 +78,11 @@ > service_attributes.each do |op| > op_hash = { } > > - op_hash["name"] = op["operation"]["name"] > - op_hash["description"] = op["operation"]["description"] > - op_hash["inputs"] = op["inputs"] > - op_hash["outputs"] = op["outputs"] > + op_hash["name"] = op["operation"]["name"] > + op_hash["description"] = op["operation"]["description"] > + op_hash["parameter_order"]= op["operation"]["parameter_order"] > + op_hash["inputs"] = op["inputs"] > + op_hash["outputs"] = op["outputs"] > > service_info["operations"] << op_hash > end > @@ -148,15 +149,18 @@ > my_message_attributes = [] > > root.each_element("//#{prefix}message"){|message| > - my_message = {} > + my_message = {"description" => ""} > my_parts =[] > > my_message["the_message"] = get_hash(message.attributes) > if message.elements["#{prefix}part"] > - message.elements.each{ |part| > + message.elements.each("#{prefix}part"){ |part| > my_parts << get_hash(part.attributes) > - } > + } > end > + if message.elements["#{prefix}documentation"] > + my_message["description"] = message.elements["#{prefix}documentation"].text > + end > my_message["the_parts"]= my_parts > my_message_attributes << my_message > } > ------------------------------------------------------------------------ > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ericnzuo at ebi.ac.uk Thu Oct 30 09:40:28 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Thu, 30 Oct 2008 13:40:28 +0000 Subject: [BioCatalogue-developers] [107] trunk/lib/wsdl_parser.rb: Fix for the truncated parameter_order attribute and processing of doc tags in messages In-Reply-To: <4909B3FC.6080005@cs.man.ac.uk> References: <20081030130352.0F4741858182@rubyforge.org> <4909B3FC.6080005@cs.man.ac.uk> Message-ID: <4909B94C.30606@ebi.ac.uk> I believe the operation db table already has this field and so should require no model update. It is just one of the attributes of an operation. But let me check the model and the wiki. Eric Jiten Bhagat wrote: > I'll update the SoapService model to store the parameter_order > > Cheers, > Jits > > > noreply at rubyforge.org wrote: >> >> Revision >> 107 >> Author >> ebontane >> Date >> 2008-10-30 09:03:50 -0400 (Thu, 30 Oct 2008) >> >> >> Log Message >> >> Fix for the truncated parameter_order attribute and processing of doc tags in messages >> >> >> Modified Paths >> >> * trunk/lib/wsdl_parser.rb <#trunklibwsdl_parserrb> >> >> >> Diff >> >> >> Modified: trunk/lib/wsdl_parser.rb (106 => 107) >> >> >> --- trunk/lib/wsdl_parser.rb 2008-10-29 22:47:57 UTC (rev 106) >> +++ trunk/lib/wsdl_parser.rb 2008-10-30 13:03:50 UTC (rev 107) >> @@ -78,10 +78,11 @@ >> service_attributes.each do |op| >> op_hash = { } >> >> - op_hash["name"] = op["operation"]["name"] >> - op_hash["description"] = op["operation"]["description"] >> - op_hash["inputs"] = op["inputs"] >> - op_hash["outputs"] = op["outputs"] >> + op_hash["name"] = op["operation"]["name"] >> + op_hash["description"] = op["operation"]["description"] >> + op_hash["parameter_order"]= op["operation"]["parameter_order"] >> + op_hash["inputs"] = op["inputs"] >> + op_hash["outputs"] = op["outputs"] >> >> service_info["operations"] << op_hash >> end >> @@ -148,15 +149,18 @@ >> my_message_attributes = [] >> >> root.each_element("//#{prefix}message"){|message| >> - my_message = {} >> + my_message = {"description" => ""} >> my_parts =[] >> >> my_message["the_message"] = get_hash(message.attributes) >> if message.elements["#{prefix}part"] >> - message.elements.each{ |part| >> + message.elements.each("#{prefix}part"){ |part| >> my_parts << get_hash(part.attributes) >> - } >> + } >> end >> + if message.elements["#{prefix}documentation"] >> + my_message["description"] = message.elements["#{prefix}documentation"].text >> + end >> my_message["the_parts"]= my_parts >> my_message_attributes << my_message >> } >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> BioCatalogue-developers mailing list >> BioCatalogue-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/biocatalogue-developers >> > > ------------------------------------------------------------------------ > > _______________________________________________ > BioCatalogue-developers mailing list > BioCatalogue-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/biocatalogue-developers > -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 248 bytes Desc: not available URL: From noreply at rubyforge.org Thu Oct 30 10:35:50 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 30 Oct 2008 10:35:50 -0400 (EDT) Subject: [BioCatalogue-developers] [108] trunk: - Added acts_as_solr plugin from myExperiment codebase. Message-ID: <20081030143551.0F96818581AE@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Thu Oct 30 12:19:52 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 30 Oct 2008 12:19:52 -0400 (EDT) Subject: [BioCatalogue-developers] [109] trunk/config/initializers: Renamed the main config file so that it can be initialised after biocat_local .rb Message-ID: <20081030161953.1769318585A0@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Fri Oct 31 05:35:35 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 31 Oct 2008 05:35:35 -0400 (EDT) Subject: [BioCatalogue-developers] [110] trunk/public/javascripts/boxover.js: Added a tooltip JS library which automatically converts structured 'title' attributes on elements to tooltips. Message-ID: <20081031093538.3801C185859F@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Fri Oct 31 05:50:43 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 31 Oct 2008 05:50:43 -0400 (EDT) Subject: [BioCatalogue-developers] [111] trunk: - Removed unnecessary files in layouts. Message-ID: <20081031095044.0B48F185859C@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Fri Oct 31 06:05:05 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 31 Oct 2008 06:05:05 -0400 (EDT) Subject: [BioCatalogue-developers] [112] trunk: Added flag images and Country Codes handling code ( all from myExperiment) to allow us to easily display flags for locations. Message-ID: <20081031100505.A642018585A7@rubyforge.org> An HTML attachment was scrubbed... URL: From jits at cs.man.ac.uk Fri Oct 31 06:16:37 2008 From: jits at cs.man.ac.uk (Jiten Bhagat) Date: Fri, 31 Oct 2008 10:16:37 +0000 Subject: [BioCatalogue-developers] Rails Widgets plugin Message-ID: <490ADB05.7070307@cs.man.ac.uk> Hi guys, So a while back I added a plugin called "widgets" which provides a few useful UI tools (http://www.seesaw.it/en/toolbox/widgets/ and http://github.com/paolodona/rails-widgets/wikis). The only real documentation for this is a presentation which is about 2MB. If you would like to have a copy of this you can either get it from http://www.slideshare.net/paolo.dona/rails-widgets-by-paolo-dona-at-railstoitaly or ask me for a copy :-) Though it might be a bit old. Jits From noreply at rubyforge.org Fri Oct 31 06:41:01 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 31 Oct 2008 06:41:01 -0400 (EDT) Subject: [BioCatalogue-developers] [113] trunk: Removed widgets plugin in preparation for upgrading it to latest version. Message-ID: <20081031104101.F191418582B4@rubyforge.org> An HTML attachment was scrubbed... URL: From ericnzuo at ebi.ac.uk Fri Oct 31 07:09:34 2008 From: ericnzuo at ebi.ac.uk (Eric Nzuobontane) Date: Fri, 31 Oct 2008 11:09:34 +0000 Subject: [BioCatalogue-developers] biocatalogue/wiki Message-ID: <490AE76E.2070903@ebi.ac.uk> there is a redirect in place for biocatalogue.org/wiki to the public wiki. So the availability of th content is now imperative. Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: ericnzuo.vcf Type: text/x-vcard Size: 238 bytes Desc: not available URL: From noreply at rubyforge.org Fri Oct 31 08:05:07 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 31 Oct 2008 08:05:07 -0400 (EDT) Subject: [BioCatalogue-developers] [114] trunk/app/views/layouts: Bug fix for head partial. Message-ID: <20081031120507.ED2CE18585A9@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Fri Oct 31 09:11:30 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 31 Oct 2008 09:11:30 -0400 (EDT) Subject: [BioCatalogue-developers] [115] trunk: Added latest version of widgets plugin (now known as " rails-widgets") from GitHub. Message-ID: <20081031131130.5604218585AA@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Fri Oct 31 09:55:33 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 31 Oct 2008 09:55:33 -0400 (EDT) Subject: [BioCatalogue-developers] [116] trunk: Updated resolr scripts to use find(:all) instead of find_all ( latter is not supported in Rails 2.x) Message-ID: <20081031135533.F16DC18585A7@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Fri Oct 31 12:29:14 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 31 Oct 2008 12:29:14 -0400 (EDT) Subject: [BioCatalogue-developers] [117] trunk: Implemented full soap service submission ( including creation of associated service, service_version, service_deployment and service_provider objects). Message-ID: <20081031162915.9A1CB16780DC@rubyforge.org> An HTML attachment was scrubbed... URL: From noreply at rubyforge.org Fri Oct 31 13:29:24 2008 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 31 Oct 2008 13:29:24 -0400 (EDT) Subject: [BioCatalogue-developers] [118] trunk/app: Some work to the show page for services. Message-ID: <20081031172925.0C6B8185818F@rubyforge.org> An HTML attachment was scrubbed... URL: