[ 
https://issues.apache.org/jira/browse/FREEMARKER-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15718146#comment-15718146
 ] 

Daniel Dekany commented on FREEMARKER-40:
-----------------------------------------

It turns out that the original authors were right about this. Java reflection 
doesn't allow you to access the public members of non-public classes, unless 
that member overrides a public method of a public class or interface. If it's a 
such override, then it's accessible from FreeMarker too. So FreeMarker is 
consistent with the Java reflection rules, as far as I can tell.

My {{exposePublicMembersOfNonPublicClasses}} patch doesn't work... it finds the 
members and all, but you still end up with {{java.lang.IllegalAccessException}} 
when you actually try to call them. (I have no idea why it worked for me back 
then... must have been an oversight.)

> ClassIntrospector should detect public methods in non-public classes
> --------------------------------------------------------------------
>
>                 Key: FREEMARKER-40
>                 URL: https://issues.apache.org/jira/browse/FREEMARKER-40
>             Project: Apache Freemarker
>          Issue Type: Bug
>          Components: engine
>    Affects Versions: 2.3.25-incubating
>            Reporter: Jochen Wiedmann
>            Assignee: Daniel Dekany
>            Priority: Minor
>
> In ClassIntrospector.discoverAccessibleMethods, the assumption is made, that 
> only public classes can have accessible methods. This is plainly wrong: For 
> example, a private object might be implementing an interface.
> Freemarker should detect public gettters, and treat them as accessible. At 
> the very least, it should inform the user about the problem. A message like
>   "Key <propertyName> was not found on an instance of ..."
> should be replaced by
>   "Key <propertyName> was not found on an instance of ..."
>   "A possible reason is,that the class must be public."
> Thanks,
> Jochen



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to