There are a few problems I think. What isn't helping is the layers here. 1. If you want a webservice, you have to package your classes etc in a certain way. 2. If you want persistence, you have to package your classes in a different way. 3. If you want a webservice with persistence, no one knows how to package it, as far as I can tell.
My problems have nothing to do with Jetspeed so long as Jetspeed doesn't do *something* to make persistence different. But that would be totally nuts but I thought I should check, to see if anyone had a memory of "Oh yeah, in that case you have to jump up and down 4 times when you deploy..." My specific problem is an exception when I'm calling EntityManager: javax.persistence.PersistenceException: No Persistence provider for EntityManager named xyzzy. Of course, there is. However, it looks like my code can't find the file, or I have something wrong in the file and I'm getting a really really sorry error message. But again, that isn't Jetspeed. I'm checking assumptions is all. ----- Original Message ----- From: Christine <[email protected]> Date: Tuesday, September 29, 2009 10:44 Subject: Re: Trouble with an axis2 web service and persistence To: Jetspeed Users List <[email protected]> > Ate Douma wrote: > > ANTHONY ENNIS wrote: > >> Is there anything in Jetspeed that would cause a web service > to not > >> be able to persist objects? > As Ate says, your question is kind of broad. What is it exactly > that > you're trying to do? > I use Hibernate in my portlets, I don't see why Hibernate or any > persistance api would cause problems, other than some > dependencies that > you have to resolve. > > dagdag > Christine > > > > > Short answer: > > No. > > > > Long answer: > > Your question really is too simplistic with no indication > > how/where/what you try to persist that a sensible answer > cannot be given. > > If you encounter a problem which *might* be related to the way > you > > packaged and deployed your web service into Jetspeed and you > want to > > find out if it possibly might be caused by conflicting > interactions > > with Jetspeed and/or the packages/jars on the classpath, > you'll need > > to provide us more details. > > > > Possible library (version) conflicts of course *might* cause > problems, > > so if you have an idea it is something in that area you should > > carefully compare the Jetspeed provided dependencies and those > needed > > by your web service. And then, *if* you found a conflict, > there are > > probably plenty solutions possible to resolve them (different > or > > separate packaging/deployment, upgrading dependencies, etc.) > > > >> > >> I asked more specific "why does this not work" questions on > the Axis2 > >> list, of course. > > Good thing. I'd suggest first investigating there and if that > comes > > back pointing at your deployment environment, we might be able > to help > > you out further. > > > > Regards, > > > > Ate > > > >> > >> > >> > > > > > > --------------------------------------------------------------- > ------ > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: jetspeed-user- > [email protected]> > > > -- > dagdag is just a two-character rotation of byebye. > > > ----------------------------------------------------------------- > ---- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
