On Mar 28, 2008, at 9:53 AM, Amy Roh wrote:
> From the logging message, I see that a jar gets added in glassfish
> \lib appropriately.
>
> Mar 28, 2008 9:40:58 AM com.sun.enterprise.glassfish.bootstrap.ASMain
> $ExtensibleClassLoader jarAdded
> INFO: Added file:/v3/distributions/web/target/web/glassfish/lib/
> tomcat-ajp.jar to shared classpath, no need to restart appserver
>
> The tomcat-ajp.jar depends on coyote related classes which are in
> webtier.jar but cannot find it resulting in
> java.lang.NoClassDefFoundError: org/apache/coyote/...
>
> Jars in lib added to shared classpath cannot access webtier.jar - I
> believe this is intended behavior.
>
> Is there a way to get around this?
no, there is not
no only way to do this is to make tomcat-ajp.jar a module that imports
webtier or add tomcat-ajp.jar to the webtier module.
I believe that once we will have the support for --libraries when
deploying applications, this will be resolved but you will need to put
the jar in applibs and then deploy the application with --library flag.
jerome
>
>
> Thanks,
> Amy
>
> Amy Roh wrote:
>> Is there a pointer which clarifies which custom jars will be picked
>> up from modules vs. lib? It seems that tomcat-ajp.jar placed in
>> modules is not recognized but is in lib directory.
>>
>> Thanks,
>> Amy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>