[ https://issues.jboss.org/browse/JBIDE-10850?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10850: ------------------------------------------ There's no way for the UI to find out whether the cartridges were loaded or not. The lazy loading is completely handled in the openshift-java-library. The UI therefore always launches a background job to get the available cartridges. Still, when verifying this, the page was available instantly to me, the delay was abs. minimal (< 1 sec). -- 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-10850?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-10850. -------------------------------------- Resolution: Done -- 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-10850?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10850 at 2/17/12 9:05 AM: ------------------------------------------------------------------- There's no way for the UI to find out whether the cartridges were loaded or not. The lazy loading is completely handled in the openshift-java-library. The UI therefore always launches a background job to get the available cartridges. If the UI (re-)uses the same user instance, the (application and embeddable) cartridges that were once loaded are returned instantly. No further loading would happen. Still, when verifying this, the page was available instantly to me, the delay was abs. minimal (< 1 sec) - see the attached screencast. was (Author: adietish): There's no way for the UI to find out whether the cartridges were loaded or not. The lazy loading is completely handled in the openshift-java-library. The UI therefore always launches a background job to get the available cartridges. If the UI (re-)uses the same user instance, the (application and embeddable) cartridges that were once loaded are returned instantly. No further loading would happen. Still, when verifying this, the page was available instantly to me, the delay was abs. minimal (< 1 sec). -- 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-10850?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10850: ------------------------------------- Release Notes Text: (was: ) Fix Version/s: 3.3.0.CR1 (was: 3.3.0.Beta1) Affects Version/s: 3.3.0.Beta1 Environment: (was: ) -- 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-10850?page=com.atlassian.jira.plugi... ] Stefan Bunciak edited comment on JBIDE-10850 at 5/14/12 4:49 AM: ----------------------------------------------------------------- @Xavier: i cannot find out how to verify this. When I provide credentials, go to next (app. configuration) page, back to credentials page and forth again (without changing anything) to app.configuration the cartridges are loaded once again. was (Author: sbunciak): @Xavier: i cannot find out how to verify this. When I provide credentials, go to next (app. configuration) page, back to credentials page and forth again to app.configuration the cartridges are loaded once again. -- 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-10850?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-10850: ----------------------------------- 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-10850?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-10850: ----------------------------------- Attachment: out-1.ogv -- 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-10850?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10850: --------------------------------------------- Stefan - "loading embeddable cartridges" is in your video shown to take less than a second in both cases. The loading of that is already cached when it goes that fast. -- 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-10850?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-10850. ---------------------------------- Verified in JBoss Developer Studio Version: 5.0.0.CR1 Build id: v20120605-0238-H182-CR1 Build date: 20120605-0238 -- 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