[Lift] Re: Need for lightweight JPA archetype
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 instead of using modules. Derek On Sun, Apr 5, 2009 at 10:23 AM, Derek Chen-Becker dchenbec...@gmail.comwrote: 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 this fixed in the archetype and in the demo site. Derek On Sat, Apr 4, 2009 at 5:04 PM, bradford fingerm...@gmail.com wrote: I pasted it here: http://pastebin.com/m1da32b3 Thanks, Bradford On Apr 4, 5:25 pm, Derek Chen-Becker dchenbec...@gmail.com 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 fingerm...@gmail.com wrote: 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. Thanks a lot for the demo and your help. Thanks, Bradford On Apr 4, 3:26 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 fingerm...@gmail.com 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-basic. NetBeans is complaining on 'import javax.persistence._' not being found in jpatest-spa's Author.scala. It also complains on 'import org.scala_libs.jpa._' in jpatest-web's Model.scala. Thanks, Bradford On Apr 3, 4:45 am, Charles F. Munat c...@munat.com wrote: 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 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 is what I say - make a branch, knock yourself out and then post to the list before merging to master Cheers, Tim On Apr 2, 7:17 pm, Charles F. Munat c...@munat.com wrote: 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/4a5d4530b407782a2f0e0e99b277432dbb. .. Cheers, Tim On Apr 2, 6:02 pm, Charles F. Munat c...@munat.com wrote: Where is the code for these archetypes and how tricky is it to create them? Chas. --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
Awesome work Derek! On 13/04/2009 23:24, Derek Chen-Becker dchenbec...@gmail.com 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-archetype-jpa-blank-single - same as blank, but set up to all be in a single project instead of using modules. Derek On Sun, Apr 5, 2009 at 10:23 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 this fixed in the archetype and in the demo site. Derek On Sat, Apr 4, 2009 at 5:04 PM, bradford fingerm...@gmail.com wrote: I pasted it here: http://pastebin.com/m1da32b3 Thanks, Bradford On Apr 4, 5:25 pm, Derek Chen-Becker dchenbec...@gmail.com 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 fingerm...@gmail.com wrote: 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. Thanks a lot for the demo and your help. Thanks, Bradford On Apr 4, 3:26 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 fingerm...@gmail.com 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-basic. NetBeans is complaining on 'import javax.persistence._' not being found in jpatest-spa's Author.scala. It also complains on 'import org.scala_libs.jpa._' in jpatest-web's Model.scala. Thanks, Bradford On Apr 3, 4:45 am, Charles F. Munat c...@munat.com wrote: 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 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 is what I say - make a branch, knock yourself out and then post to the list before merging to master Cheers, Tim On Apr 2, 7:17 pm, Charles F. Munat c...@munat.com wrote: 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/4a5d4530b407782a2f0e0e99b277432dbb. .. Cheers, Tim On Apr 2, 6:02 pm, Charles F. Munat c...@munat.com wrote: Where is the code for these archetypes and how tricky is it to create them? Chas. --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
Great! I can't wait to check these out. Thanks, Bryan On Apr 13, 6:32 pm, Timothy Perrett timo...@getintheloop.eu wrote: Awesome work Derek! On 13/04/2009 23:24, Derek Chen-Becker dchenbec...@gmail.com 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-archetype-jpa-blank-single - same as blank, but set up to all be in a single project instead of using modules. Derek On Sun, Apr 5, 2009 at 10:23 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 this fixed in the archetype and in the demo site. Derek On Sat, Apr 4, 2009 at 5:04 PM, bradford fingerm...@gmail.com wrote: I pasted it here: http://pastebin.com/m1da32b3 Thanks, Bradford On Apr 4, 5:25 pm, Derek Chen-Becker dchenbec...@gmail.com 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 fingerm...@gmail.com wrote: 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. Thanks a lot for the demo and your help. Thanks, Bradford On Apr 4, 3:26 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 fingerm...@gmail.com 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-basic. NetBeans is complaining on 'import javax.persistence._' not being found in jpatest-spa's Author.scala. It also complains on 'import org.scala_libs.jpa._' in jpatest-web's Model.scala. Thanks, Bradford On Apr 3, 4:45 am, Charles F. Munat c...@munat.com wrote: 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 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 is what I say - make a branch, knock yourself out and then post to the list before merging to master Cheers, Tim On Apr 2, 7:17 pm, Charles F. Munat c...@munat.com wrote: 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/4a5d4530b407782a2f0e0e99b277432dbb. .. Cheers, Tim On Apr 2, 6:02 pm, Charles F. Munat c...@munat.com wrote: Where is the code for these archetypes and how tricky is it to create them? Chas. --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 this fixed in the archetype and in the demo site. Derek On Sat, Apr 4, 2009 at 5:04 PM, bradford fingerm...@gmail.com wrote: I pasted it here: http://pastebin.com/m1da32b3 Thanks, Bradford On Apr 4, 5:25 pm, Derek Chen-Becker dchenbec...@gmail.com 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 fingerm...@gmail.com wrote: 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. Thanks a lot for the demo and your help. Thanks, Bradford On Apr 4, 3:26 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 fingerm...@gmail.com 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-basic. NetBeans is complaining on 'import javax.persistence._' not being found in jpatest-spa's Author.scala. It also complains on 'import org.scala_libs.jpa._' in jpatest-web's Model.scala. Thanks, Bradford On Apr 3, 4:45 am, Charles F. Munat c...@munat.com wrote: 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 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 is what I say - make a branch, knock yourself out and then post to the list before merging to master Cheers, Tim On Apr 2, 7:17 pm, Charles F. Munat c...@munat.com wrote: 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/4a5d4530b407782a2f0e0e99b277432dbb. .. Cheers, Tim On Apr 2, 6:02 pm, Charles F. Munat c...@munat.com wrote: Where is the code for these archetypes and how tricky is it to create them? Chas. --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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.scala_libs.jpa._' in jpatest-web's Model.scala. Thanks, Bradford On Apr 3, 4:45 am, Charles F. Munat c...@munat.com wrote: 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 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 is what I say - make a branch, knock yourself out and then post to the list before merging to master Cheers, Tim On Apr 2, 7:17 pm, Charles F. Munat c...@munat.com wrote: 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/4a5d4530b407782a2f0e0e99b277432dbb... Cheers, Tim On Apr 2, 6:02 pm, Charles F. Munat c...@munat.com wrote: Where is the code for these archetypes and how tricky is it to create them? Chas. --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 fingerm...@gmail.com 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-basic. NetBeans is complaining on 'import javax.persistence._' not being found in jpatest-spa's Author.scala. It also complains on 'import org.scala_libs.jpa._' in jpatest-web's Model.scala. Thanks, Bradford On Apr 3, 4:45 am, Charles F. Munat c...@munat.com wrote: 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 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 is what I say - make a branch, knock yourself out and then post to the list before merging to master Cheers, Tim On Apr 2, 7:17 pm, Charles F. Munat c...@munat.com wrote: 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/4a5d4530b407782a2f0e0e99b277432dbb... Cheers, Tim On Apr 2, 6:02 pm, Charles F. Munat c...@munat.com wrote: Where is the code for these archetypes and how tricky is it to create them? Chas. --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 fingerm...@gmail.com wrote: 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. Thanks a lot for the demo and your help. Thanks, Bradford On Apr 4, 3:26 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 fingerm...@gmail.com 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-basic. NetBeans is complaining on 'import javax.persistence._' not being found in jpatest-spa's Author.scala. It also complains on 'import org.scala_libs.jpa._' in jpatest-web's Model.scala. Thanks, Bradford On Apr 3, 4:45 am, Charles F. Munat c...@munat.com wrote: 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 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 is what I say - make a branch, knock yourself out and then post to the list before merging to master Cheers, Tim On Apr 2, 7:17 pm, Charles F. Munat c...@munat.com wrote: 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/4a5d4530b407782a2f0e0e99b277432dbb. .. Cheers, Tim On Apr 2, 6:02 pm, Charles F. Munat c...@munat.com wrote: Where is the code for these archetypes and how tricky is it to create them? Chas. --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
I pasted it here: http://pastebin.com/m1da32b3 Thanks, Bradford On Apr 4, 5:25 pm, Derek Chen-Becker dchenbec...@gmail.com 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 fingerm...@gmail.com wrote: 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. Thanks a lot for the demo and your help. Thanks, Bradford On Apr 4, 3:26 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 fingerm...@gmail.com 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-basic. NetBeans is complaining on 'import javax.persistence._' not being found in jpatest-spa's Author.scala. It also complains on 'import org.scala_libs.jpa._' in jpatest-web's Model.scala. Thanks, Bradford On Apr 3, 4:45 am, Charles F. Munat c...@munat.com wrote: 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 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 is what I say - make a branch, knock yourself out and then post to the list before merging to master Cheers, Tim On Apr 2, 7:17 pm, Charles F. Munat c...@munat.com wrote: 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/4a5d4530b407782a2f0e0e99b277432dbb. .. Cheers, Tim On Apr 2, 6:02 pm, Charles F. Munat c...@munat.com wrote: Where is the code for these archetypes and how tricky is it to create them? Chas. --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 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 is what I say - make a branch, knock yourself out and then post to the list before merging to master Cheers, Tim On Apr 2, 7:17 pm, Charles F. Munat c...@munat.com wrote: 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/4a5d4530b407782a2f0e0e99b277432dbb... Cheers, Tim On Apr 2, 6:02 pm, Charles F. Munat c...@munat.com wrote: Where is the code for these archetypes and how tricky is it to create them? Chas. --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 the persistance sub-project, the public sub-project, and the admin-subproject. Is this a good idea? And is it just as easy as copying the current webapp subproject, renaming it, and then deleting the parts that don't belong in each of the public and admin sub-projects? But then how would I package it? How would I deploy it? Has anyone done anything like this? Chas. 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. Perhaps lift-jpa-archetype-blank-split lift-jpa-archetype-blank-consolidated Thoughts? Tim On Apr 2, 7:33 am, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 place but otherwise be empty. The Lift side could have the basic Boot and perhaps a Model class set up with a placeholder persistence setup. Thoughts? Derek On Wed, Apr 1, 2009 at 3:16 PM, Timothy Perrett timo...@getintheloop.euwrote: Glad im not the only one ;-) On Apr 1, 11:15 pm, Viktor Klang viktor.kl...@gmail.com wrote: Timmy, yeah, I can see that coming in handy. Cheers, Viktor On Wed, Apr 1, 2009 at 11:13 PM, Tim Perrett timo...@getintheloop.eu 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 and examples, having something thats a workable starting point without having to remove code etc would be helpful. I appreciate this is a bit lazy - but i don't think it would take much work and would provide a neat solution Thoughts? Tim -- Viktor Klang Senior Systems Analyst --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 module (change packaging to ejb), but otherwise it's a simple change. Otherwise, you can just deploy the JPA module jar and webapp modules separately. To answer your question, I think that you should be able to just duplicate the existing project, although I think that you should be able to handle enforcing login and SSL via SiteMap for just the portions you want to protect. Derek On Thu, Apr 2, 2009 at 12:41 AM, Charles F. Munat c...@munat.com wrote: 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 the persistance sub-project, the public sub-project, and the admin-subproject. Is this a good idea? And is it just as easy as copying the current webapp subproject, renaming it, and then deleting the parts that don't belong in each of the public and admin sub-projects? But then how would I package it? How would I deploy it? Has anyone done anything like this? Chas. 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. Perhaps lift-jpa-archetype-blank-split lift-jpa-archetype-blank-consolidated Thoughts? Tim On Apr 2, 7:33 am, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 place but otherwise be empty. The Lift side could have the basic Boot and perhaps a Model class set up with a placeholder persistence setup. Thoughts? Derek On Wed, Apr 1, 2009 at 3:16 PM, Timothy Perrett timo...@getintheloop.eu wrote: Glad im not the only one ;-) On Apr 1, 11:15 pm, Viktor Klang viktor.kl...@gmail.com wrote: Timmy, yeah, I can see that coming in handy. Cheers, Viktor On Wed, Apr 1, 2009 at 11:13 PM, Tim Perrett timo...@getintheloop.eu 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 and examples, having something thats a workable starting point without having to remove code etc would be helpful. I appreciate this is a bit lazy - but i don't think it would take much work and would provide a neat solution Thoughts? Tim -- Viktor Klang Senior Systems Analyst --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
Works for me :) On Wed, Apr 1, 2009 at 11:51 PM, Timothy Perrett timo...@getintheloop.euwrote: 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 Thoughts? Tim On Apr 2, 7:33 am, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 place but otherwise be empty. The Lift side could have the basic Boot and perhaps a Model class set up with a placeholder persistence setup. Thoughts? Derek On Wed, Apr 1, 2009 at 3:16 PM, Timothy Perrett timo...@getintheloop.eu wrote: Glad im not the only one ;-) On Apr 1, 11:15 pm, Viktor Klang viktor.kl...@gmail.com wrote: Timmy, yeah, I can see that coming in handy. Cheers, Viktor On Wed, Apr 1, 2009 at 11:13 PM, Tim Perrett timo...@getintheloop.eu 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 and examples, having something thats a workable starting point without having to remove code etc would be helpful. I appreciate this is a bit lazy - but i don't think it would take much work and would provide a neat solution Thoughts? Tim -- Viktor Klang Senior Systems Analyst --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 that having the possibility of creating either a merged project or a split project is important as JPA brings things to the table some great features that people should be able to use however they want. IMO, the archetypes are enablers - I know we could create this stuff manually, but we want to enable people to be productive quickly. Thoughts? Tim On Apr 2, 3:06 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: Works for me :) On Wed, Apr 1, 2009 at 11:51 PM, Timothy Perrett timo...@getintheloop.euwrote: 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 Thoughts? Tim On Apr 2, 7:33 am, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 place but otherwise be empty. The Lift side could have the basic Boot and perhaps a Model class set up with a placeholder persistence setup. Thoughts? Derek On Wed, Apr 1, 2009 at 3:16 PM, Timothy Perrett timo...@getintheloop.eu wrote: Glad im not the only one ;-) On Apr 1, 11:15 pm, Viktor Klang viktor.kl...@gmail.com wrote: Timmy, yeah, I can see that coming in handy. Cheers, Viktor On Wed, Apr 1, 2009 at 11:13 PM, Tim Perrett timo...@getintheloop.eu 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 and examples, having something thats a workable starting point without having to remove code etc would be helpful. I appreciate this is a bit lazy - but i don't think it would take much work and would provide a neat solution Thoughts? Tim -- Viktor Klang Senior Systems Analyst --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 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 module (change packaging to ejb), but otherwise it's a simple change. Otherwise, you can just deploy the JPA module jar and webapp modules separately. To answer your question, I think that you should be able to just duplicate the existing project, although I think that you should be able to handle enforcing login and SSL via SiteMap for just the portions you want to protect. Derek On Thu, Apr 2, 2009 at 12:41 AM, Charles F. Munat c...@munat.com mailto:c...@munat.com wrote: 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 the persistance sub-project, the public sub-project, and the admin-subproject. Is this a good idea? And is it just as easy as copying the current webapp subproject, renaming it, and then deleting the parts that don't belong in each of the public and admin sub-projects? But then how would I package it? How would I deploy it? Has anyone done anything like this? Chas. 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. Perhaps lift-jpa-archetype-blank-split lift-jpa-archetype-blank-consolidated Thoughts? Tim On Apr 2, 7:33 am, Derek Chen-Becker dchenbec...@gmail.com mailto:dchenbec...@gmail.com wrote: 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 place but otherwise be empty. The Lift side could have the basic Boot and perhaps a Model class set up with a placeholder persistence setup. Thoughts? Derek On Wed, Apr 1, 2009 at 3:16 PM, Timothy Perrett timo...@getintheloop.euwrote: Glad im not the only one ;-) On Apr 1, 11:15 pm, Viktor Klang viktor.kl...@gmail.com mailto:viktor.kl...@gmail.com wrote: Timmy, yeah, I can see that coming in handy. Cheers, Viktor On Wed, Apr 1, 2009 at 11:13 PM, Tim Perrett timo...@getintheloop.eu 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 and examples, having something thats a workable starting point without having to remove code etc would be helpful. I appreciate this is a bit lazy - but i don't think it would take much work and would provide a neat solution Thoughts? Tim -- Viktor Klang Senior Systems Analyst --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 c...@munat.com wrote: Where is the code for these archetypes and how tricky is it to create them? Chas. --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 Apr 2, 6:02 pm, Charles F. Munat c...@munat.com wrote: Where is the code for these archetypes and how tricky is it to create them? Chas. --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 is what I say - make a branch, knock yourself out and then post to the list before merging to master Cheers, Tim On Apr 2, 7:17 pm, Charles F. Munat c...@munat.com wrote: 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/4a5d4530b407782a2f0e0e99b277432dbb... Cheers, Tim On Apr 2, 6:02 pm, Charles F. Munat c...@munat.com wrote: Where is the code for these archetypes and how tricky is it to create them? Chas. --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 timo...@getintheloop.euwrote: 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 things to the table some great features that people should be able to use however they want. IMO, the archetypes are enablers - I know we could create this stuff manually, but we want to enable people to be productive quickly. Thoughts? Tim On Apr 2, 3:06 pm, Derek Chen-Becker dchenbec...@gmail.com wrote: Works for me :) On Wed, Apr 1, 2009 at 11:51 PM, Timothy Perrett timo...@getintheloop.eu 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. Perhaps lift-jpa-archetype-blank-split lift-jpa-archetype-blank-consolidated Thoughts? Tim On Apr 2, 7:33 am, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 place but otherwise be empty. The Lift side could have the basic Boot and perhaps a Model class set up with a placeholder persistence setup. Thoughts? Derek On Wed, Apr 1, 2009 at 3:16 PM, Timothy Perrett timo...@getintheloop.eu wrote: Glad im not the only one ;-) On Apr 1, 11:15 pm, Viktor Klang viktor.kl...@gmail.com wrote: Timmy, yeah, I can see that coming in handy. Cheers, Viktor On Wed, Apr 1, 2009 at 11:13 PM, Tim Perrett timo...@getintheloop.eu 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 and examples, having something thats a workable starting point without having to remove code etc would be helpful. I appreciate this is a bit lazy - but i don't think it would take much work and would provide a neat solution Thoughts? Tim -- Viktor Klang Senior Systems Analyst --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
Timmy, yeah, I can see that coming in handy. Cheers, Viktor On Wed, Apr 1, 2009 at 11:13 PM, Tim Perrett timo...@getintheloop.euwrote: 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 and examples, having something thats a workable starting point without having to remove code etc would be helpful. I appreciate this is a bit lazy - but i don't think it would take much work and would provide a neat solution Thoughts? Tim -- Viktor Klang Senior Systems Analyst --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
Glad im not the only one ;-) On Apr 1, 11:15 pm, Viktor Klang viktor.kl...@gmail.com wrote: Timmy, yeah, I can see that coming in handy. Cheers, Viktor On Wed, Apr 1, 2009 at 11:13 PM, Tim Perrett timo...@getintheloop.euwrote: 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 and examples, having something thats a workable starting point without having to remove code etc would be helpful. I appreciate this is a bit lazy - but i don't think it would take much work and would provide a neat solution Thoughts? Tim -- Viktor Klang Senior Systems Analyst --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Need for lightweight JPA archetype
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 Thoughts? Tim On Apr 2, 7:33 am, Derek Chen-Becker dchenbec...@gmail.com wrote: 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 place but otherwise be empty. The Lift side could have the basic Boot and perhaps a Model class set up with a placeholder persistence setup. Thoughts? Derek On Wed, Apr 1, 2009 at 3:16 PM, Timothy Perrett timo...@getintheloop.euwrote: Glad im not the only one ;-) On Apr 1, 11:15 pm, Viktor Klang viktor.kl...@gmail.com wrote: Timmy, yeah, I can see that coming in handy. Cheers, Viktor On Wed, Apr 1, 2009 at 11:13 PM, Tim Perrett timo...@getintheloop.eu 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 and examples, having something thats a workable starting point without having to remove code etc would be helpful. I appreciate this is a bit lazy - but i don't think it would take much work and would provide a neat solution Thoughts? Tim -- Viktor Klang Senior Systems Analyst --~--~-~--~~~---~--~~ 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 liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
