Great! I can't wait to check these out.
Thanks,
Bryan
On Apr 13, 6:32 pm, Timothy Perrett wrote:
> Awesome work Derek!
>
> On 13/04/2009 23:24, "Derek Chen-Becker" wrote:
>
>
>
> > OK, I just checked in two more archetypes for JPA:
>
> > lift-archetype-jpa-blank - same as the basic one, but w
Awesome work Derek!
On 13/04/2009 23:24, "Derek Chen-Becker" wrote:
> OK, I just checked in two more archetypes for JPA:
>
> lift-archetype-jpa-blank - same as the basic one, but with only the bare
> minimum set of files for a JPA project with separate Persistence and Web
> modules
> lift-arch
OK, I just checked in two more archetypes for JPA:
lift-archetype-jpa-blank - same as the basic one, but with only the bare
minimum set of files for a JPA project with separate Persistence and Web
modules
lift-archetype-jpa-blank-single - same as blank, but set up to all be in a
single project ins
Ah, I forgot to check in the BookOps.add.doAdd method whether or not the
author was set. There should be a check there with an error that would
prevent a book from not having an author. Even better, I should update the
Book entity object to put a not-null constraint on the author property. I'll
get
I pasted it here: http://pastebin.com/m1da32b3
Thanks,
Bradford
On Apr 4, 5:25 pm, Derek Chen-Becker wrote:
> If you have a second, could you send the stack trace for the NPE? That's
> definitely not something that should be happening.
>
> Derek
>
> On Sat, Apr 4, 2009 at 2:34 PM, bradford wr
If you have a second, could you send the stack trace for the NPE? That's
definitely not something that should be happening.
Derek
On Sat, Apr 4, 2009 at 2:34 PM, bradford wrote:
>
> Yeah, just NetBeans. It probably makes sense, but everything in
> NetBeans was fine after I did mvn compile; mvn
Yeah, just NetBeans. It probably makes sense, but everything in
NetBeans was fine after I did mvn compile; mvn install. Running the
app works too. I did happen to get a NullPointerException when I
would add a book with no author. And then again when I would click on
Book list. Just an FYI.
T
Hmmm. Does maven complain if you try to compile, or is it just NetBeans?
Derek
On Sat, Apr 4, 2009 at 9:31 AM, bradford wrote:
>
> Hi,
>
> I think I would like to use JPA for my project. This archetype would
> be nice. Just a second ago I ran mvn archtype:generate on lift-
> archetype-jpa-bas
Hi,
I think I would like to use JPA for my project. This archetype would
be nice. Just a second ago I ran mvn archtype:generate on lift-
archetype-jpa-basic. NetBeans is complaining on 'import
javax.persistence._' not being found in jpatest-spa's Author.scala.
It also complains on 'import org.
No, I meant there were a few candidates for a first commit, not that
someone else should do it. I have my fingers in a bunch of things at the
moment...
At the moment, however, I have to pay the bills. But I'll keep tinkering.
Chas.
Timothy Perrett wrote:
> Probally between yourself and Derek
I agree. The cost of creating the archetypes is relatively low, so having
variations on a theme would be nice.
Derek.
On Thu, Apr 2, 2009 at 9:27 AM, Timothy Perrett wrote:
>
> I guess if your deploying into an "enterprise container", then EAR is
> fine, however if your deploying into Jetty then
Probally between yourself and Derek in all honesty - I simply dont
have the time right now and my "lift time" and what I do with it has
other investments right now...
Derek might well be swamped with the book at the moment... so perhaps
there are not so many candidates as you think :-)
Crack on
Yup. But there seem to be a few candidates...
Timothy Perrett wrote:
> Are you eyeing up for your first commit Chas? ;-)
>
> The src of the JPA archetype is here:
>
> http://github.com/dpp/liftweb/tree/4a5d4530b407782a2f0e0e99b277432dbb41b640/lift-archetype-jpa-basic
>
> Cheers, Tim
>
> On Ap
Are you eyeing up for your first commit Chas? ;-)
The src of the JPA archetype is here:
http://github.com/dpp/liftweb/tree/4a5d4530b407782a2f0e0e99b277432dbb41b640/lift-archetype-jpa-basic
Cheers, Tim
On Apr 2, 6:02 pm, "Charles F. Munat" wrote:
> Where is the code for these archetypes and ho
Hmm. I forgot about EARs. Thanks for this information. I'll play around
with it over the weekend.
Chas.
Derek Chen-Becker wrote:
> I don't know if this is typical, but I typically deploy my apps in an
> EAR, in which case you just add another "EAR Build" module that packages
> up the Persiste
Where is the code for these archetypes and how tricky is it to create them?
Chas.
Timothy Perrett wrote:
> I guess if your deploying into an "enterprise container", then EAR is
> fine, however if your deploying into Jetty then you don't have the
> possibility of deploying to EAR. I just think th
I guess if your deploying into an "enterprise container", then EAR is
fine, however if your deploying into Jetty then you don't have the
possibility of deploying to EAR. I just think that having the
possibility of creating either a merged project or a split project is
important as JPA brings thing
Works for me :)
On Wed, Apr 1, 2009 at 11:51 PM, Timothy Perrett wrote:
>
> I 100% see why you want a seperate module for persistance, but
> workflow wise I've found JPA a lot more productive if it's in the lift
> app as it means you don't have to keep deploying the JAR into your
> local repo.
>
I don't know if this is typical, but I typically deploy my apps in an EAR,
in which case you just add another "EAR Build" module that packages up the
Persistence module as an EJB module (v3) and then adds the WAR(s). It
requires that you make some slight changes to the POM for the Persistence
modul
Hmmm. This brings up something I've been meaning to ask about.
I have a public JPA app which has a log-in only maintenance area. I'm
thinking about moving the maintenance part to a subdomain and serving it
via SSL.
I think it would be easier to pull out a separate sub-project, so I
might have
I 100% see why you want a seperate module for persistance, but
workflow wise I've found JPA a lot more productive if it's in the lift
app as it means you don't have to keep deploying the JAR into your
local repo.
Perhaps
lift-jpa-archetype-blank-split
lift-jpa-archetype-blank-consolidated
Th
I thought I had sent out an email on the list earlier asking what people
would want to see in such an archetype. As a base, probably a master POM
with a module for the persistence unit and a module for the Lift side of
things. The persistence unit could have a skeleton persistence.xml in the
right
Glad im not the only one ;-)
On Apr 1, 11:15 pm, Viktor Klang wrote:
> Timmy,
>
> yeah, I can see that coming in handy.
>
> Cheers,
> Viktor
>
> On Wed, Apr 1, 2009 at 11:13 PM, Tim Perrett wrote:
>
>
>
>
>
> > Guys,
>
> > Do people see room for a blank JPA archetype just like we have blank
> >
Timmy,
yeah, I can see that coming in handy.
Cheers,
Viktor
On Wed, Apr 1, 2009 at 11:13 PM, Tim Perrett wrote:
>
> Guys,
>
> Do people see room for a blank JPA archetype just like we have blank
> and basic of normal lift archetypes?
>
> IMO, whilst its great having the basic one for learning a
24 matches
Mail list logo
