Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <19001807.post@talk.nabble.com>
Date: Fri, 15 Aug 2008 09:38:39 -0700 (PDT)
From: hbuch4 <hbuch@straussauto.com>
To: user-java@ibatis.apache.org
Subject: Re: don't call Managed Bean init method
In-Reply-To: <18989735.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <18989735.post@talk.nabble.com>


Actually, I found that it is far easier and clearer to simply retrieve the
list of objects from the db directly in the "get" method corresponding to
that list, rather than in the bean's init method.

Thanks,

Heather Buch


hbuch4 wrote:
> 
> Is there any way to prevent Ibatis from calling the init method of my
> ManagedBean, when it creates a new bean for a ResultMap?
> 
> I only want to call the ManagedBean's init method when it is being
> instantiated through MyFaces, NOT through Ibatis. The only solution I
> thought of was, before the init method, to iterate through the stack trace
> and skip over if it finds: 
> 
> at com.ibatis.common.beans.ClassInfo.instantiateClass
> 
> but execute if:
> 
> at org.apache.myfaces.shared_impl.util.ClassUtils.newInstance
> 
> but this seems a little clunky.....
> 
> any ideas?
> 
> thanks, Heather Buch
> 

-- 
View this message in context: http://www.nabble.com/don%27t-call-Managed-Bean-init-method-tp18989735p19001807.html
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.