Thanks for the response Bill, I had missed that part. Unfortunately, there seem to be different problems from this approach. I start getting things like
anonymous wrote : Faild to aspectize class com.ibm.etools.websphere.tools.internal.util.FileUtil. Could not find class it references com.ibm.etools.rft.api.IConnectionData Then the process just dies after a few of these. When I do jboss.aop.verbose=true, it looks like the ClassLoader is considering every single class that it brings up and every method on it and it indicates that it successfully loads up the jboss-aop.xml. I guess the question in my mind is whether or not IBM's JVM (or its root classloader) does some voodoo between its classloaders so that where there are normally scoping issues they don't have it? From what I understand a parent classloader won't be able to see a child's classes. I made sure that I was using the /p switch on the -Xbootclasspath so I'm pretty positive whatever classes it normally puts in the bootclasspath are still there. I'm going to keep kicking it around and see if I can see anything, but if anyone has any insight into IBM's JVM core classes (probably the java.lang.ClassLoader) vs. Sun's, and/or the startup of WebSphere that might help I'd appreciate it. Thanks, Tom View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858114#3858114 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3858114 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
