tags:

views:

499

answers:

0

Weblogic 9.2.2 throws a compile error when my custom function uses Java 1.5 generics.

Let me explain.

My JSP contains the following taglib:

<%@ taglib prefix="validPre" uri="aValidURI"%>

My tld contains a single custom function:

<function>
    <name>contains</name>
    <function-class>SessionServiceImpl</function-class>
    <function-signature>boolean contains(x.y.z.ServiceTask, java.util.List)</function-signature>
</function>

My custom function uses generics in the method signature.

public static boolean contains(ServiceTask serviceTask, List<SessionServiceTask> sessionServiceTasks) {       
     return true;
}

With the above configuration, Weblogic 9.2.2 will throw a compile error. If I remove <SessionServiceTask> from the method signature, the JSP compiles without any errors. I've confirmed that this syntax is valid in another Servlet container (Resin). I've also confirmed that Weblogic will compile a scriptlet that uses generics.

The compile error I receive with the generic version of the signature is:

"The qualifier of this name is a package, which cannot contain fields."

Any thoughts on why this doesn't work with Weblogic 9.2?

Thank you.