My friend, I must admit that I have never applied inheritance on static
nested classes in my life.
(Not at least that I can remember :) )
I'm not to sure what the minimal access control level for static nested
classes is from point of nested inheritance and Struts system.
Maybe it has to do
Alen Ribic wrote:
My friend, I must admit that I have never applied inheritance on static
nested classes in my life.
(Not at least that I can remember :) )
I'm not to sure what the minimal access control level for static nested
classes is from point of nested inheritance and Struts system.
Maybe
Aaaa, my suspicion seemed to lean to right direction. :)
--Alen
- Original Message -
From: Gareth Andrew [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, June 19, 2003 5:25 PM
Subject: Re: Problems with an inherited getter in a
The answer to your puzzle is found in the JLS, 8.2.1.4 Accessing Members of
Inaccessible Classes. For brevity I won't copy and paste everything but
leave it as an exercise for the reader. ;^)
http://java.sun.com/docs/books/jls/second_edition/html/classes.doc.html#4086
2
David Hibbs
Staff
Hi,
Just for fun I set up a little test app. It demonstrates that the bug
is definitely in Common Beanutils. Normal Java relfection can call a
method derived from a protected nested class without problems. The
problem seems to be in o/a/c/b/MethodUtils.java : line 442ish where
Beanutils
In my struts application, I have a base bean with a set of basic
properties (e.g. name) and then I create various derived beans with
their own extra properties. I have a problem with the html:options tag
in that if I try to read a property that is inherited from the base
bean from a
I'm doing the same thing in my current project successfully.
No problems in my specializes class.
e.g.
public abstract class BaseBusinessBean
implements java.io.Serializable {
protected int id;
protected String description;
// getters/setters here
}
e.g.
public class Category
thanks for confirming that this should work - one fact that I omitted in
my original mailing was that the classes were inner classes
i.e. it was the PostCode.Area class that is in the collection
public class PostCode
{
protected static class Pbase
{
protected String name;
8 matches
Mail list logo