Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #8012
| From | Arved Sandstrom <asandstrom3minus1@eastlink.ca> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: JSF/JPA problem |
| References | (4 earlier) <EWRbq.10526$EP3.6864@newsfe05.iad> <j4or6k$ctb$1@dont-email.me> <MqTbq.18258$YA4.3466@newsfe14.iad> <UtTbq.20792$oz6.12673@newsfe11.iad> <j4p3e8$nqp$1@dont-email.me> |
| Message-ID | <w1_bq.20838$oz6.7934@newsfe11.iad> (permalink) |
| Organization | Public Usenet Newsgroup Access |
| Date | 2011-09-14 05:59 -0300 |
On 11-09-13 11:27 PM, markspace wrote: > On 9/13/2011 6:31 PM, Arved Sandstrom wrote: > >> Err...I should have added, my setup works just fine. I see new data >> being persisted. This being the application-managed JTA entity manager >> scenario. > > > Thanks for that, it at least gives me a few things to try out. > > If you want to test further, I'm basically using the NetBeans IDE for > this project. It has GlassFish and Derby built-in, so it uses those for > JEE projects. It even has a wizard for making the persistence.xml file, > which is what I used. I'd be curious if it's NetBeans that's setting > things up screwy, or if I missed a needed step. > > Will try some of those ideas as soon as I can. > I may try NetBeans here, but I can't see that in this case that the IDE of choice is the problem. Normally I would have used NB for this experiment, since I have some development biases (mostly unfounded quirks) that lead me to use NB + Glassfish, Eclipse + all other app servers. It just so happened that I had set up Eclipse Indigo on an Ubuntu box with Glassfish Tools just to try it out, and had a single Facelets page + single JSF managed bean WAR project already sitting there ready to adapt. :-) The JPA facet in Eclipse does pretty much the same thing as JPA support in NB: back & forth wizard-driven JPA artifacts <=> DB stuff. Both are fine, provided that you sanity-check source every so often. Unless you don't have a data source declared in persistence.xml and not defined in the app server I doubt you missed anything - this particular test case is pretty simple. I think it's the added annotation of your session EJB as a JSF managed bean (not just @Stateless), plus pulling it in to the calling JSF managed bean with @ManagedProperty. As I mentioned previously my session EJB is just that, @Stateless (no @ManagedBean on that class), and where you've got @ManagedProperty I've got @EJB. The fact that your container-managed @PersistenceContext DI is also not working supports this conclusion. AHS -- job creator: US Republican term for a wealthy party contributor
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar
JSF/JPA problem markspace <-@.> - 2011-09-13 09:19 -0700
Re: JSF/JPA problem Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2011-09-13 17:24 -0300
Re: JSF/JPA problem Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2011-09-13 17:40 -0300
Re: JSF/JPA problem markspace <-@.> - 2011-09-13 15:38 -0700
Re: JSF/JPA problem markspace <-@.> - 2011-09-13 17:06 -0700
Re: JSF/JPA problem Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2011-09-13 22:28 -0300
Re: JSF/JPA problem Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2011-09-13 22:31 -0300
Re: JSF/JPA problem markspace <-@.> - 2011-09-13 19:27 -0700
Re: JSF/JPA problem Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2011-09-14 05:59 -0300
Re: JSF/JPA problem markspace <-@.> - 2011-09-14 10:36 -0700
Re: JSF/JPA problem Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2011-09-14 17:51 -0300
Re: JSF/JPA problem markspace <-@.> - 2011-09-13 16:12 -0700
csiph-web