[ https://issues.jboss.org/browse/JBIDE-11680?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-11680: --------------------------------------- in the previous version of the client library, all applications with their cartridges could be retrieved in a single request. With the current new client, you need to send a request per application, there's no aggregation mecanism yet (but it seems to be in discussion in the openshift team). So, in B2, not having lazy loading for cartridges was not noticeable, whereas it is now. Xavier -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11680?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-11680 at 4/27/12 6:06 AM: ------------------------------------------------------------------- yes, that's also what I would identify as culprit. The former service allowed one to retrieve all infos for a user in a single (bulk) request (request user info that contained everything, the domain, the apps, the catridges etc.). The new RESTful service does not offer this any longer. You'd have to request on a per resource base (domain, application, key, cartridge etc.). Exceptions to this are provided where one can request a listing of all domains/apps/keys (request all domains OR all applications OR all keys etc.). A noticeable limitation is where one would list the applications. The embedded cartridges are reported in a way that only contains basic informations (ex. mysql connection url). The response does not contain links (delete, alter, etc.) that allow resource manipulations. In order to get a complete response for an embedded cartridge, one would have to GET the individual cartridge. The only optimisation I currently see is to correct the explorer to load cartridges lazyly (which it obviously does not for the moment). We could eventually also swallow the stub-response (with the connection url only) and load the rest lazyly. Not sure if that would make a big difference though. IMHO the only approach that would noticeably improve things is to add the ability for bulk request in the service (which seems in discussion). We should also examine our current lib and see if it really caches as much as possible and doesn't do unnecessary requests. was (Author: adietish): yes, that's also what I would to as culprit. The former service allowed one to retrieved all infos for a user in a single (bulk) request (request user info that contained everything, the domain, the apps, the catridges etc.). The new RESTful service does not offer this any longer. You'd have to request on a per resource base. Exceptions to this are where you can request all domains/apps to be listed. A noticeable limitation is where one would list the applications. The embedded cartridges are reported in a way that only contains basic informations (ex. mysql url). The response does not contain links (delete, alter, etc.). In order to get the all infos for a embedded cartridge, we'd have to request info for every single embedded cartridge. The only optimisation I currently see, that we could do on our side, is to correct the explorer to load cartridges lazy (which it obviously does not for the moment). We could eventually also swallow the stub-response (with the connection url only) for the cartridge and load the rest lazyly. Not sure if that would make a big difference though. IMHO the only approach that would noticeably improve things is to add the ability for bulk request in the service (which seems in discussion). We should also examine our current lib and see if it really caches as much as possible and doesn't do unnecessary requests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11680?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11680: ---------------------------------------- Fix Version/s: 3.3.0.CR1 (was: 3.3.0.Beta3) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11680?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-11680. ----------------------------------- Labels: new_and_noteworthy (was: ) Resolution: Done when expanding the User node, the list of applications is retrieved from OpenShift, but the cartridges are not loaded -> lazy-loading approach is implemented. App cartridges are loaded only when the application node is expanded -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11680?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-11680. ----------------------------------- Verified 5.0.0.v201205272317M-H143-CR1. Cartridges are loaded lazily. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira