Yes, I'm storing it as text.
----- Original Message -----
From: "Dmitri Colebatch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 25, 2001 8:05 PM
Subject: Re: [JBoss-user] CMP of a byte[] array vanishes on
re-deployment(fwd)
> sorry - itchy trigger finger... as I was saying...
>
> if you're encoding it as Base64 I'm assuming its text... just checking - I
> have this situation working fine with text.
>
> cheesr
> dim
>
> ---------- Forwarded message ----------
> Date: Thu, 26 Jul 2001 10:03:59 +1000 (EST)
> From: Dmitri Colebatch <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] CMP of a byte[] array vanishes on re-deployment
>
> Are you saving the field as text of byte[]. If you're encoding
>
> On Wed, 25 Jul 2001, Scott Stevelinck wrote:
>
> > I have what I would consider an extremely odd issue. I'm encoding a
> > byte[] using Base64 into a container managed field. I'm using
> > Postgres as my back end database. Everything works fine when the bean
> > read/writes that byte[] array to the database (of course it's actually
> > writing the encoded string to an OID field in the back end table).
> > Now the problem, if I re-deploy the bean ALL the byte[] get changed to
> > something odd that's only 6k, when they were 12k-14k before the
> > re-deployment. All the other fields in the table remain untouched.
> >
> > I've inserted debug code into the bean and it doesn't appear that
> > ejbStore() is getting called, which should be the ONLY place a db
> > write is occurring. I don't see anything funny in the server.log that
> > would indicate the database is being modified?
> >
> > Any ideas??
> >
> > --Scott
> >
>
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
