Re: [Springframework-developer] Method Visibility

[Rod J. <rod...@in...>]

Ralph

This really is irrelevant for performance. The issue is: is it annoying
enough to justify changing the visibility?

Juergen, what are your thoughts? This has come up in the forums before. I'd
have no objection to changing it to public.

Rgds
Rod

----- Original Message -----
From: "Ralph Schaer" <ral...@ya...>
To: <spr...@li...>
Sent: Sunday, May 23, 2004 10:03 PM
Subject: [Springframework-developer] Method Visibility


> Hello
>
> I often have this sort of code in my dao's:
>
>     HibernateCallback callback = new HibernateCallback() {
>
>       public Object doInHibernate(Session session) throws
HibernateException {
>         Criteria criteria = getHibernateTemplate().createCriteria(session,
User.class);
>         criteria.add(Expression.eq("userName", userName));
>         if (id != null) {
>           criteria.add(Expression.not(Expression.eq("id", id)));
>         }
>         return criteria.list();
>       }
>     };
>
> Now Eclipse complains with this warning message:
> Access to enclosing method getHibernateTemplate() from the type
> HibernateDaoSupport is emulated by a synthetic accessor method.
> Increasing its visibility will improve your performance
>
> That's because getHibernateTemplate() is protected.
>
> Regards
> Ralph
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g.
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>