You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2010/12/02 17:31:11 UTC

[jira] Resolved: (MYFACES-2990) JDTCompiler wants access to more classes in osgi

     [ https://issues.apache.org/jira/browse/MYFACES-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonardo Uribe resolved MYFACES-2990.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.3-SNAPSHOT
         Assignee: Leonardo Uribe

Thanks to David Jencks for provide this patch

> JDTCompiler wants access to more classes in osgi
> ------------------------------------------------
>
>                 Key: MYFACES-2990
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2990
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.0.3-SNAPSHOT
>            Reporter: David Jencks
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.3-SNAPSHOT
>
>         Attachments: MYFACES-2990.patch
>
>
> Running the tck we get into a bunch of problems with superclasses of exposed classes not being visible to the eclipse JDTCompiler used to compile jsps.   A typical error looks like...
> 11-30-2010 17:23:11:  TRACE: [WIRE] - << "Caused by: org.apache.jasper.JasperException: Unable to compile class for JSP: [\n]"
> 11-30-2010 17:23:11:  TRACE: [WIRE] - << "[\n]"
> 11-30-2010 17:23:11:  TRACE: [WIRE] - << "An error occurred at line: 1 in the generated java file[\n]"
> 11-30-2010 17:23:11:  TRACE: [WIRE] - << "The type org.apache.myfaces.shared_impl.taglib.UIComponentELTagBase cannot be resolved. It is indirectly referenced from required .class files[\n]"
> I don't know how the eclipse compiler is tying itself in these knots, I guess it assumes that the classloader you give it can load by name all superclasses of accessible classes.  It would be better to figure out either how to give the compiler such a classloader or figure out how to remove this assumption from the compiler, but it seems more practical at the moment to just export the needed superclasses.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.