> I found out that the problem was with Voyager's class loader.
> When I passed
> the current class loader to its startup method, everything worked
> fine. Now
> I can start and stop our voyager container with jBoss!!
Interesting, please do describe the "integration" you have done as we might
want to document it for folks needing that integration. We might want to
start it as a JMX mbean also so you would just say "I want the Voyager
stuff" and we would get it going for you (just like we do with Tomcat).
Note that we have EXACTLY the same problem with Tomcat, namely that the
visibility of the class loaders is not unified. Of course we need to pass
the class loaders around. Also be careful that many of our interfaces are
build and passed at runtime so that the visibility on the class definition
is passed around at runtime in a "lean and mean" fashion... in clear the
class loader you pass will not contain the visibility on the deployed beans.
marc
>
> Thanks
>
> -rick
>
>
>
