Hello I got the Classloader tree size reduced by 90% using the manual links in dojo tree, for all the classloaders which occurs multiple times. These links are loaded only when parent node is expanded.
From user perspective this will not make any difference, but internally all
the dojo functionality are changed. This should take care of OutOfMemory and StackOverflow excception we were getting. Earlier the size of StringTree for dojo tree children was 6542173 chars, and not it is reduced to 665019 chars for my Geronimo server. This is imporvement is visible is tree loading, now it is much quicker. I attached classloaderViewLinks.patch in http://issues.apache.org/jira/browse/GERONIMO-2690, Please review and commit. Thanks Rakesh On 1/12/07, Paul McMahan <[EMAIL PROTECTED]> wrote:
It seems there is some confusion about the difference between a Geronimo plugin and a view that "plugs in" to the admin console. This is probably due to the fact that we haven't really established the terminology and best practices behind these new concepts yet. To further complicate the issue we've also alluded to future capabilities that we want to add to the admin console to make it more "pluggable". This has made it very difficult to keep the conversation on track. In hindsight I think it was unwise for me to bring all this up in the context of a patch submission, a bit premature. Plugins and their relationship to the admin console is a pretty heavyweight concept and probably deserves to be discussed and documented via a wiki page. I'll go start writing something up asap to help get that discussion underway. So as I indicated earlier I'm +1 on committing the patch as-is and then factoring out the views from the admin console that should be implemented as plugins, if we decide that's the right way to go. Best wishes, Paul On 1/12/07, Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote: > I don't know if I understand your comments about ca-helper app correctly. > The purpose of the ca-helper app is to enable users submit certificate > requests from web browsers (currently, from browsers that support KEYGEN > tag), download and install issued certificates into web browsers. Access to > the ca-helper application should not be controlled by "geronimo-admin" realm > and also the application exports certificates with appropriate mime type for > user certs and ca cert. ca-helper is not exactly the one that plugs in to > Geronimo Console and becomes the CA portlet. ca-helper app and CA portlet > have no common functionality. > > Vamsi > > > On 1/11/07, Paul McMahan <[EMAIL PROTECTED]> wrote: > > On 1/10/07, Kevan Miller <[EMAIL PROTECTED]> wrote: > > > > > > Paul, > > > Are you suggesting that we should start architecting the console to > > > be more pluggable? Or suggesting that Rakesh rewrite these viewers? > > > > We've talked about architecting the console to be more pluggable and > > I'm definitely in favor of that. But until that effort gets underway > > we still have the capability to make UIs pluggable into Geronimo by > > implementing them as standalone webapps. ca-helper is a good example > > of this approach. So really my question was whether or not Rakesh > > would consider wrappering the viewers as webapps that can then be > > installed as Geronimo plugins instead of integrating them directly > > into the console as portlets. If that's not going to work out then > > I'm fine with Donald's suggestion of integrating in their current form > > and making them into plugins later. The viewers are definitely a > > value contribution to Geronimo and I look forward to seeing them in > > our next release. > > > > Best wishes, > > Paul > > > >
