Derek,

Thanks for posting up the code.

In general, I like to keep conversations on-list.  People learn a lot by
seeing back and forth communications rather than simply the magic result.
Additionally, there are a number of folks who have different skills and
different perspectives and allowing them to be part of the conversation is
very important as well... as they will contribute to the over-all result.

To put this in perspective, I have very, very few off-list communications
(and they are mainly in the form of IMs related to small, timely decisions)
with the other committers about what we commit to Lift.  We intensionally
keep our communications visible.

Thanks,

David

On Fri, Sep 5, 2008 at 6:01 AM, Derek Chen-Becker <[EMAIL PROTECTED]>wrote:

> I think Chas didn't post up the code because I had said I wanted to wait to
> release this until the kinks were worked out, not because he's
> obstructionist :). I've attached the current form of the tutorial project.
> The code in question is
> JPADemo/perscala/src/main/scala/com/jpaweb/foo/model/Author.scala. Chas is
> helping me work out the kinks and I'm waiting for 0.10 to go GA before we
> update the actual tutorial page on the wiki to match. Right now it's mostly
> down to some maven issues, which I'd appreciate any help on:
>
>
>    1. The webapp module is dependent on the perscala module. As the
>    project is currently layed out, you need to run "mvn install" in the
>    perscala project before you can go into the webapp project and run "mvn
>    jetty:run". I was hoping there would be a way for the webapp module to
>    trigger the "mvn install" when you try to run things (test, jetty:run, 
> etc),
>    but I'm no maven guru
>    2. I had some problems with my dependencies that meant you had to
>    manually install some jars. I'm hoping to get it down to completely
>    automatic on the dependency updates.
>
> Cheers
>
> Derek
>
>
> On Fri, Sep 5, 2008 at 5:26 AM, Tim Perrett <[EMAIL PROTECTED]> wrote:
>
>>
>> Chas,
>>
>> It would be usefull if you just posted the entity code - if it's from
>> the tutorial, or a varient of that, I don't see why your not giving
>> others their chance to contribute? Just post up the code... There are
>> a lot of talented people on this list who I'm sure can a) help improve
>> the implementation, and b) would be very interested to see scala JPA.
>>
>> Cheers
>>
>> Tim
>>
>> Sent from my iPhone
>>
>> On 5 Sep 2008, at 10:20, "Charles F. Munat" <[EMAIL PROTECTED]> wrote:
>>
>> >
>> > I think Derek has a new version of the tutorial. I've been
>> > communicating
>> > with him about it, and am trying to get his Scala-only version
>> > working.
>> > I'll check with him to make sure my suspicions are correct. Then one
>> > of
>> > us will update the tutorial.
>> >
>> > I was planning to revise the tutorial myself, but since he has a
>> > revised
>> > one pretty much ready to go (I think), I'm just trying to help him to
>> > debug it.
>> >
>> > Either way, it will be fixed shortly.
>> >
>> > Chas.
>> >
>> > Viktor Klang wrote:
>> >> Sorry Chas,
>> >>
>> >> I think I expressed myself somewhat unfortunate,
>> >> what I meant was: "Can you paste in the code for the Author-class"?
>> >>
>> >>
>> >> Cheers,
>> >> Viktor
>> >>
>> >> On Thu, Sep 4, 2008 at 10:18 PM, Charles F. Munat <[EMAIL PROTECTED]
>> >> <mailto:[EMAIL PROTECTED]>> wrote:
>> >>
>> >>
>> >>    Oh, sorry, Victor. I think I posted a response to my own
>> >> question almost
>> >>    immediately after I posted it. I was aiming this question at
>> >> anyone who
>> >>    had used the JPA tutorial because I figured that the problem was
>> >> in the
>> >>    difference between using POJOs and POSOs (hence, I assumed they
>> >> would
>> >>    have not just the Author model, but the entire sample app,
>> >> available). I
>> >>    should have tried a few things before posting. As it turned out,
>> >> using
>> >>    author.name <http://author.name> worked fine.
>> >>
>> >>    Thanks for the help.
>> >>
>> >>    Chas.
>> >>
>> >>    Viktor Klang wrote:
>> >>> Chas,
>> >>>
>> >>> You'll have to give us more than that, i.e. the definition of
>> >>> Author.
>> >>>
>> >>> Cheers,
>> >>> Viktor
>> >>>
>> >>> On Wed, Sep 3, 2008 at 4:29 AM, Charles F. Munat <[EMAIL PROTECTED]
>> >>    <mailto:[EMAIL PROTECTED]>
>> >>> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote:
>> >>>
>> >>>
>> >>>    Has anyone followed the JPA tutorial using pure Scala instead
>> >>    of Java?
>> >>>    I've got it very close to running, but I am getting the
>> >>    following error:
>> >>>
>> >>>    [WARNING]
>> >>>
>> >>    /private/var/www/wsbg/webapp/src/main/scala/com/foo/jpaweb/
>> >> snippet/AuthorOps.scala:22:
>> >>>    error: value getName is not a member of
>> >>    com.foo.jpaweb.model.Author
>> >>>    [WARNING]      "name" --> Text(author.getName()),
>> >>>    [WARNING]                             ^
>> >>>    [WARNING] one error found
>> >>>
>> >>>    I'm neither a Scala nor a Java programmer, but I'm guessing
>> >>    that the
>> >>>    getter for the name attribute in Scala is not "getName". Is this
>> >>>    correct?
>> >>>
>> >>>    Chas.
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Viktor Klang
>> >>> Rogue Software Architect
>> >>>
>> >>>>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Viktor Klang
>> >> Rogue Software Architect
>> >>
>> >>>
>> >
>> > >
>> >
>>
>>
>>
>
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to