Mailing-List: contact cayenne-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cayenne-user@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of blacknext@gmail.com designates
 64.233.162.201 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=uW5guImKN11LHfvR3TYmqhPmO/FyuWvaiEaIixu1FE2LBs7O6Ox1Ra6eTkRQmPXomfnopp3fG6AasILO+PdtcmAtcJXtl9GO9hHBpv4IM3p6HkaAJRIn4D6bBp3MKDBzOWOINfmw4M9778XCEg+tLrs7tLjj7F70ORdbRYJObGo=
Message-ID: <f65b8ae30610271232t61ed0900l9f39afa63bd1bb63@mail.gmail.com>
Date: Fri, 27 Oct 2006 15:32:59 -0400
From: "Michael Gentry" <blacknext@gmail.com>
To: cayenne-user@incubator.apache.org
Subject: Re: Re: a few qestions if you don't mind
In-Reply-To: <469958e20610270707j39a617f6pc3e87e8c15318ab1@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <469958e20610231837u83464a2i25a53c8ffb96b83d@mail.gmail.com>
	 <f65b8ae30610241020x29f3b97vb42bf8ad4fdaecf5@mail.gmail.com>
	 <469958e20610270707j39a617f6pc3e87e8c15318ab1@mail.gmail.com>

The DataSqueezer will definitely work, but keep in mind it is a
potentially insecure solution if that is a concern for you.  (All
depends on the nature of your application.)

/dev/mrg


On 10/27/06, edward pedersson <cpsmadness@googlemail.com> wrote:
> Thank ou very much Mike and Michael. Managed to fix my problem using the
> DataSqueezer.
>
> On 24/10/06, Michael Gentry <blacknext@gmail.com> wrote:
> >
> > Hi Edward,
> >
> > See if this posting might help:
> >
> > http://www.objectstyle.org/cayenne/lists/cayenne-user/2006/04/0073.html
> >
> > In a nutshell, when using Tapestry 4 + Cayenne, I don't serialize any
> > Cayenne objects through Tapestry.  The posting has more details.
> >
> > /dev/mrg
> >
> > PS. I used to pass my objects around with an ActionLink (now
> > deprecated) in Tapestry 3, but changed my techniques when I moved to
> > Tapestry 4.  Also, I only use DirectLink now -- PageLink has some
> > session quirks.
> >
> >
> > On 10/23/06, edward pedersson <cpsmadness@googlemail.com> wrote:
> > > Hi
> > >
> > > I noticed you post in the archives [RE: "Can't build a query for
> > temporary
> > > id" after upgrade from 1.2B2 to 1.2RC2] here
> > >
> > http://mail-archives.apache.org/mod_mbox/incubator-cayenne-dev/200607.mbox/%3C110DED9F5106CC47A186602C0DD3938201168C92@EXVF.fanniemae.com%3Eand
> > > I seem to be having problems which might be similar to yours. I could
> > > not see how you resolved your problems but maybe if you tell me how you
> > were
> > > doing a few things I may be able to solve my own problems.
> > >
> > > I am using Tapestry 4 and Cayenne 1.2
> > >
> > > When you said "...hen my objects are unserialized and reattached to
> > their
> > > datacontexts on the following request.." were you just doing
> > >
> > >             anObject.setDataContext(this.getDataContext());
> > >             anObject.getDataContext
> > > ().getObjectStore().resolveHollow(anObject);
> > >
> > > where anObject is an object that is a listener parameter to the method
> > so I
> > > am assuming it has been serialised and is unserialised when I get it at
> > this
> > > point. The object is hollow as well. Is this the best way to reattach
> > the
> > > object back to the dataContext?
> > >
> > > My problems don't stop there as the code itself runs ok but not
> > correctly.
> > > The object remains hollow and looking into the ObjectStore's public void
> > > resolveHollow(DataObject object) method I noticed there is this call
> > >
> > > List results = context.getChannel().onQuery(context, query).firstList();
> > >
> > > but nothing is done with that results List. I have inspected the results
> > > List and it is in fact the object I need but the method does not return
> > the
> > > list or the object. Is there something I am missing here i.e. the object
> > > passed in is updated elsewhere? I have followed the object graph and
> > could
> > > not find it.
> > >
> > > Any help would be much appreciated.
> > >
> > > Regards
> > >
> > > --
> > >
> > >
> > > -- e
> > >
> > >
> >
>
>
>
> --
>
>
> -- e
>
>