DO NOT REPLY [Bug 9870] New: - Bug importing classes from tomcat libs

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9870>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9870

Bug importing classes from tomcat libs

           Summary: Bug importing classes from tomcat libs
           Product: Cocoon 2
           Version: 2.0.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: core
        AssignedTo: cocoon-dev@xml.apache.org
        ReportedBy: z.bennett@its.utexas.edu


I've confirmed this behavior in Cocoon 2.0.2-dev on Windows XP and HP-UX 11 
under Tomcat 4.0.3.  Classes that live in "tomcat_home/lib" are importable via 
package imports in xsp:include statements, but fail when attempting to import 
specific classes within those packages.

This is reproducable by attempting to import a class already in that directory, 
such as org.apache.jasper.compiler.PluginGenerator:

<xsp:structure>
    <xsp:include>org.apache.jasper.compiler.PluginGenerator</xsp:include>
</xsp:structure>

which results in:
org.apache.cocoon.ProcessingException: Language Exception: 
org.apache.cocoon.components.language.LanguageException: Error compiling 
hello_xsp:
Line 41, column 40: cannot access class PluginGenerator; file 
org\apache\jasper\compiler\PluginGenerator.class not found

whereas the package import below successfully compiles and executes.
<xsp:structure>
    <xsp:include>org.apache.jasper.compiler.*</xsp:include>
</xsp:structure>

thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org