ANTHONY ENNIS wrote:
My specific problem is an exception when I'm calling EntityManager:
javax.persistence.PersistenceException: No Persistence provider for
EntityManager named xyzzy.
I had the same issue. One of the things I found is that Hibernate needs
the proper versions of slf4j and log4j but it doesn't specifically
complain about not having them. You get an error message about ejb3
instead. You can test your assumption about not finding the config file
by hard coding the config file, i.e. by creating a Configuration in your
code and hand it the config file. That shouldn't be necessary though.
dagdag
Christine
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 <christ...@christine.nl>
Date: Tuesday, September 29, 2009 10:44
Subject: Re: Trouble with an axis2 web service and persistence
To: Jetspeed Users List <jetspeed-user@portals.apache.org>
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: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-
h...@portals.apache.org>
--
dagdag is just a two-character rotation of byebye.
-----------------------------------------------------------------
----
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
--
dagdag is just a two-character rotation of byebye.
