FWIW regarding naming, since the change I've started to mentally
rename "RequestVar" to "PageVar". I don't think it's reasonable to
rename the actual class, since everybody uses it, but I found it was a
helpful mnemonic to remember what scope it has.
-Ross
On Nov 13, 2009, at 6:00 PM, Kris
On Fri, Nov 13, 2009 at 3:42 PM, David Pollak
wrote:
>
>
> On Fri, Nov 13, 2009 at 12:12 PM, Kris Nuttycombe
> wrote:
>>
>> On Fri, Nov 13, 2009 at 11:46 AM, Derek Chen-Becker
>> wrote:
>> > Looks like it. Probably private[liftweb] would work, too. In any case,
>> > the
>> > scaladocs need to b
On Fri, Nov 13, 2009 at 12:12 PM, Kris Nuttycombe wrote:
>
> On Fri, Nov 13, 2009 at 11:46 AM, Derek Chen-Becker
> wrote:
> > Looks like it. Probably private[liftweb] would work, too. In any case,
> the
> > scaladocs need to be updated to reflect what it's for.
> >
> > On Fri, Nov 13, 2009 at 12
On Fri, Nov 13, 2009 at 11:46 AM, Derek Chen-Becker
wrote:
> Looks like it. Probably private[liftweb] would work, too. In any case, the
> scaladocs need to be updated to reflect what it's for.
>
> On Fri, Nov 13, 2009 at 12:26 PM, Kris Nuttycombe
> wrote:
>>
>> Hmmm is this now TransientRequ
Looks like it. Probably private[liftweb] would work, too. In any case, the
scaladocs need to be updated to reflect what it's for.
On Fri, Nov 13, 2009 at 12:26 PM, Kris Nuttycombe wrote:
>
> Hmmm is this now TransientRequestVar? It's private[http], but
> could it be protected instead?
>
> Kr
Let me just try it out since I've got a test case, and if need be I'll
file the ticket & commit.
Kris
On Fri, Nov 13, 2009 at 10:45 AM, Derek Chen-Becker
wrote:
> Looking at 81f1715f671e8b5ee4f6d3ce242cc9da272611d1, maybe the RequestVar
> needs to be changed to an UnboundRequestVar. It's not cl
Hmmm is this now TransientRequestVar? It's private[http], but
could it be protected instead?
Kris
On Fri, Nov 13, 2009 at 11:22 AM, Kris Nuttycombe
wrote:
> Let me just try it out since I've got a test case, and if need be I'll
> file the ticket & commit.
>
> Kris
>
> On Fri, Nov 13, 2009 a
Looking at 81f1715f671e8b5ee4f6d3ce242cc9da272611d1, maybe the RequestVar
needs to be changed to an UnboundRequestVar. It's not clear from the
scaladocs on UnboundRequestVar, though, that this is the intent. It looks
like those scaladocs were just copied and pasted from RequestVar. If this
sounds l
On Thu, Nov 12, 2009 at 5:57 PM, David Pollak
wrote:
> Kris,
>
> There was a bunch of changes in the net.liftweb.mapper.DB code for
> transaction management, but I don't think that would impact JPA.
>
> Also, in M7, there were changes in how RequestVars are handled during Ajax
> requests... basic
That's really odd. As far as I know the only thing JPA related that might
have changed is for the JPA Demo site (pom Hibernate version change). The
transaction handling code is all in ScalaJPA, which also hasn't changed.
JndiEMF explicitly opens a transaction before it even retrieves the EM from
JN
Kris,
There was a bunch of changes in the net.liftweb.mapper.DB code for
transaction management, but I don't think that would impact JPA.
Also, in M7, there were changes in how RequestVars are handled during Ajax
requests... basically, state is snapshotted when the Ajax request is created
and the
11 matches
Mail list logo