Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of
 lists+1214986160035-208411@n2.nabble.com designates 216.139.236.158 as
 permitted sender)
Message-ID: <1236359073474-2436888.post@n2.nabble.com>
Date: Fri, 6 Mar 2009 09:04:33 -0800 (PST)
From: Pinaki Poddar <ppoddar@apache.org>
To: users@openjpa.apache.org
Subject: Re: ClassNotFoundException on persisting serialized class
In-Reply-To: <1236354427197-2436442.post@n2.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <6e479eb30903051632v3c98eb9ek694c2f0b2bb76bea@mail.gmail.com>
 <1236354427197-2436442.post@n2.nabble.com>


You are annotating getter/setter, but their names do not match bean-style.
public com.MyData getMyData() {...}
public void setMetadataList(com.MyData myData) {...}


Jon Solanu wrote:
> 
> The errors went away when I added an explicit em.flush to the method
> inserting the serialized object.  However a null is still being inserted
> into the databse for that field.  I attempted to change the attribute
> value to specify that it was a blob field but that had no affect.
> 
> 
> 
> 	@Lob()
> 	@Basic(fetch=FetchType.EAGER)
> 	@Column(name="MYDATA_LIST")
> 	public com.MyData getMyData() {
> 		return this.myData;
> 	}
> 	public void setMetadataList(com.MyData myData) {
> 		this.myData= myData;
> 	}
> 
> 

-- 
View this message in context: http://n2.nabble.com/ClassNotFoundException-on-persisting-serialized-class-tp2433282p2436888.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.