Hi Aaron,
Thanks for the response.
As to the question; IMO the 'right' thing to do is separate out the
interfaces. But practically speaking is that reasonable? Seems like
that is a huge task for not much gain (unless I'm missing something
from a future expected use discussion that I missed).
Now making sure I understood what you said the cause of the error
message is. Since the jetty-deployer is 'provided' scope it is not
added explicitly to the class loader for the console. The jetty-
deloyer has the interface and impl for JettyWebAppContext. Since the
jar that this interface is in is not explicitly added to the
console's class path (because of 'provided' if I understand
correctly) it barfs.
However, if we were to separate the interfaces of 'jetty-deployer'
from the implementation classes we could put an explicit reference
into the console to the interfaces and leave the implementation as
'provided'.
Please fix my lack of understanding :-)
Thanks again,
-bd-
On Sep 4, 2006, at 8:54 AM, Aaron Mulder wrote:
It's actually the proxy manager that produces those messages. It
means that the console asked for a proxy to some GBean, and some of
the interfaces implemented by that GBean weren't available in the
caller's (the console's) class loader.
It would be nice to have a larger discussion about how to handle this.
For example, do we package all management interfaces in separate JARs
from the core libraries (Jetty, Tomcat, ActiveMQ, etc.) so that the
console can add only the interfaces to its class loader? Or are we OK
with the console just adding the full implementation JARs for
everything to its class path?
Thanks,
Aaron
On 9/4/06, Bill Dudney <[EMAIL PROTECTED]> wrote:
Hi All,
The consoles (tomcat & jetty) are spewing warning messages like this;
08:00:18,511 WARN [BasicProxyManager] Could not load interface
org.apache.geronimo.jetty.JettyWebAppContext in provided ClassLoader
for org.apache.geronimo.configs/welcome-jetty/1.2-SNAPSHOT/car?
J2EEApplication=null,j2eeType=WebModule,name=org.apache.geronimo.conf
igs
/welcome-jetty/1.2-SNAPSHOT/car
To fix it we can simply remove the <scope>provided</scope> from the
<artifactId>{jetty,tomcat}-deployer</artifactId> dependencies in the
webconsole-{jetty,tomcat}/pom.xml.
Could someone who knows more about the console than me please review
the patch (GERONIMO-2344.bdudney-2.patch) here;
http://issues.apache.org/jira/browse/GERONIMO-2344
And apply it if it makes sense?
Thanks!
-bd-
