I am not sure what this problem is, please let me know what version of
geronimo you are using and I will try it and let you know.
Thanks
Rakesh
On 1/8/07, Christopher M. Cardona <[EMAIL PROTECTED]> wrote:
Rakesh,
I tried combining your patches last time and I was able to build the
server but the it fails on startup with the following error:
[*************************> ] 93% 20s Loading
org.apache.geronimo...19:29:49,3
12 ERROR [DeploymentFactoryImpl]
java.lang.AbstractMethodError
at
org.apache.geronimo.deployment.plugin.jmx.JMXDeploymentManager.initia
lize(JMXDeploymentManager.java:83)
at
org.apache.geronimo.deployment.plugin.jmx.LocalDeploymentManager.<ini
t>(LocalDeploymentManager.java:28)
at
org.apache.geronimo.deployment.plugin.factories.DeploymentFactoryImpl
.getDeploymentManager(DeploymentFactoryImpl.java:141)
at
org.apache.geronimo.deployment.hot.DirectoryHotDeployer.getDeployment
Manager(DirectoryHotDeployer.java:317)
at
org.apache.geronimo.deployment.hot.DirectoryHotDeployer.doStart(Direc
toryHotDeployer.java:157)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI
nstance.java:984)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart
(GBeanInstanceState.java:267)
...
Not sure if I missed something. I'll give your combined patch a shot and
let you know.
Best wishes,
chris
Rakesh Midha wrote:
>
> Posted combined patch
> https://issues.apache.org/jira/secure/attachment/12348488/allviews.patch
> in JIRA 2689
>
> Please review and commit.
>
> Thanks
> Rakesh
>
> On 1/8/07, *Rakesh Midha* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
> Hello All,
>
> Thanks for quick review,
>
> Joe, You are right about the difference in two prespectivies, the
> debug view - dependencies is to show the hirarchical dependencies
> of all components, modules and it also list repository elements,
> whereas Config Manager is to list the potential ramifications if a
> configuration is removed.
>
> Another major difference being the Config Manager only shows
> serviceparents only, where as this view directly list the direct
> dependencies as well as serviceparents.
>
> Sachin, Prasad, David :
> About
>
http://geronimo.apache.org/maven/server/modules/geronimo-webservices-builder/dependencies.html
> it shows the static dependencies of the default server, and
> doens't list any customized services, repository elements,
> components and configurations deployed on server. The idea is to
> show the dependency information for a particular server in its
> console.
>
> I hope it clear all the points discussed here.
>
> Chris, As you suggested I will create a single patch for all three
> and post it in one of the JIRA. (Will inform once it is done).
>
> Thanks
> Rakesh
>
>
>
> On 1/5/07, *Christopher M. Cardona* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
> Hi Rakesh,
>
> Thanks for the patches. I haven't looked at the source too but
> the pix
> looks good. It would be nice if you can create a combined
> patch for the
> 3 jiras so people who wanted to check out the new debug views
> can use
> this as another option.
>
> Best wishes,
> chris
>
> Rakesh Midha wrote:
> > Hello
> >
> > First of all I am sorry for being missing from the list for
> last few
> > days, actually I have been trying to get this work item done.
> I kinda
> > liked the idea of having ClassLoader, JNDI and Dependency
> views in
> > console.
> >
> > We have discussed this before in dev list, please read the
> discussion
> > below.
> >
> > I got this thing working, so I created three JIRA's, Please
> have a
> > look at https://issues.apache.org/jira/browse/GERONIMO-2689
> > https://issues.apache.org/jira/browse/GERONIMO-2690
> <https://issues.apache.org/jira/browse/GERONIMO-2690>
> > https://issues.apache.org/jira/browse/GERONIMO-2691
> >
> > These three JIRA's adds 3 view in console which shows
> > 1. JNDIView
> > This view shows all the JNDI names binded in various componet
> contexts
> > as well as Global context. Have a look at
> >
https://issues.apache.org/jira/secure/attachment/12348327/12348327_jndi.gif
> > to get idea of what it will show. As we can see it shows JNDI
> names
> > for which are available at each component context level. For
> details
> > of how this is implemented please have a look at comments of
> this JIRA.
> >
> > 2. ClassloaderView
> > This view shows all the classloaders and
> classes/interfaces loaded by
> > that classloader in heirarchical fashion. Have a look at
> >
https://issues.apache.org/jira/secure/attachment/12348333/12348333_classloader.gif
> <
https://issues.apache.org/jira/secure/attachment/12348333/12348333_classloader.gif
>
> > to get idea of what it will show. As we can see it shows
> classes and
> > interfaces for all the classloaders and its child
> classloaders. For
> > details of how this is implemented please have a look at
> comments of
> > this JIRA.
> >
> > 3. DependencyView
> > This view shows all the components and repository items and
its
> > dependencies in hierarchical fashion in which they are loaded.
To
> > facilitate locating of items of interest the tree view can be
> > searched.. Have a look at
> >
https://issues.apache.org/jira/secure/attachment/12348336/12348336_dependency.gif
> > to get idea of what it will show. As we can see it shows
> dependencies
> > for each component. For details of how this is implemented
> please have
> > a look at comments of this JIRA.
> >
> > This is a request that please try these patches and let me
> know your
> > comments on it. I think I liked it and these views will
> definatly be
> > useful for debugging purpose, and from my expierance I can
> tell that
> > all these views are trying to facilitate solving of problems
> which are
> > difficult to tackle otherwise.
> >
> > Also notice that we may like to add another section in
> navigation for
> > debug views as shown in
> >
https://issues.apache.org/jira/secure/attachment/12348329/12348329_navigation.gif
> <
https://issues.apache.org/jira/secure/attachment/12348329/12348329_navigation.gif
>
> > <
>
https://issues.apache.org/jira/secure/attachment/12348329/12348329_navigation.gif
>
> > this is not implemented for now but we may do it once we
> agree to put
> > the above views in console.
> >
> > Thanks in advance, please do have a look and comment.
> > Rakesh
> >
> > On 7/20/06, *Erin Mulder* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> > <mailto: [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>>> wrote:
> >
> > Aaron Mulder wrote:
> > > http://people.apache.org/~ammulder/classloaders.png
> <http://people.apache.org/%7Eammulder/classloaders.png>
> > < http://people.apache.org/%7Eammulder/classloaders.png>
> > >
> > > However, I'm not sure how useful it will be -- it'll
> show you
> > > dependencies at the class loader level, but it won't
> tell you which
> > > class loaders hold a particular class or which class
> loader you're
> > > actually getting at some point when an error is
uncovered.
> >
> > Also, it still needs arrows. :)
> >
> > Right now, the code for that graph produces SVG. It
> would be great to
> > make it interactive so that you could drag the nodes
> around, click
> > on a
> > node to load a div that shows which classes are loaded in
> it, and
> > maybe
> > even collapse certain branches. At JavaOne, I got a few
> simple
> > JavaScript behaviors working with the graph prototype,
> but I'm not
> > sure
> > how complex it would be to add full-out drag and drop.
> >
> > Perhaps you can throw the code into the sandbox so other
> people can
> > check it out and build on it? If I recall correctly, I
> was careful to
> > make sure that all of its dependencies have
> Apache-compatible
> > licenses,
> > (which was actually quite difficult).
> >
> > Alternatively, someone could create and share a
> non-ASF-hosted plugin
> > that makes use of one of the many LGPL graph libraries
> out there.
> >
> > Cheers,
> > Erin
> >
> >
>
>
>
