Hi David,
i interpreted your answer as there should not be a problem with Spring.
Hence thanks for the hint ;-).
So i took my test web application and tried to get Spring 2.5.1 running with
JndiObjectFactoryBean and it worked.
Hence i looked in our production application and i am sorry we had a
p
On Jan 31, 2009, at 2:49 AM, JensToerber wrote:
Hi,
i am facing the same problem in Tomcat 6.0.18. EntityManager does
not get
injected: "no such property".
Openejb 3.1 works in a test application with EJB-, EntityManager-,
DataSource-, javax.Mail.Session-, Queue-injection.
Now i have the
Hi,
i am facing the same problem in Tomcat 6.0.18. EntityManager does not get
injected: "no such property".
Openejb 3.1 works in a test application with EJB-, EntityManager-,
DataSource-, javax.Mail.Session-, Queue-injection.
Now i have the situation to port an existing application which uses Sp
Hi,
I'm having the same problem with tomcat and tapestry 5 + openejb 3.1! I
created a slsb and tried to obtain an EntityManager like this:
@Stateless
public class CoreEJB implements CoreEJBLocal {
@PersistenceContext(unitName = "myContext", type =
PersistenceContextType.TRANSACTION)
private
On Apr 2, 2008, at 3:30 PM, klewelling wrote:
You may want to try setting the properties as system properties,
i.e. java
...
-
Djava
.naming
.factory.initial=org.apache.openejb.client.LocalInitialContextFactory
-Djava.naming.factory.url.pkgs=org.apache.naming.factory.XXX
or something l
You may want to try setting the properties as system properties, i.e. java
...
-Djava.naming.factory.initial=org.apache.openejb.client.LocalInitialContextFactory
-Djava.naming.factory.url.pkgs=org.apache.naming.factory.XXX
or something like that. I think it may be important that openEJB's
initia
On Apr 1, 2008, at 12:14 PM, klewelling wrote:
FYI I got the injection to work. When I was putting together a
demonstration
the injection started working. The problem has to do with
dependencies in
the pom.xml. I am not sure if there was something extra causing the
problem
or perhaps the
On Mar 29, 2008, at 1:14 PM, ebaxt wrote:
I'm trying to run my application with Tomcat+openEJB, but I can't
figure out
why the EntityManager isn't injected correctly into the EAO
sessionbean.
My war file is packed with the ejb.jar in \WEB-INF\lib.
The client is able to lookup the facade,
Thank you Kenneth!
I have tried to set the properties you talked about, but I don't really know
how to configure it to lookup Tomcat's JNDI context.
I have tried this with no luck:
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,
"org.apache.openejb.client
FYI I got the injection to work. When I was putting together a demonstration
the injection started working. The problem has to do with dependencies in
the pom.xml. I am not sure if there was something extra causing the problem
or perhaps the order of the jars in the classpath. I am uploading an ex
I am having the same problem with Jetty. I am using the maven jetty:run
plugin and when I put my SSBs in a separate EJB jar openEJB starts up fine.
The EJBs are loaded correctly and I can get the local interface from JNDI,
however when I call any method I get a NPE because nothing is injected. Whe
I'm trying to run my application with Tomcat+openEJB, but I can't figure out
why the EntityManager isn't injected correctly into the EAO sessionbean.
My war file is packed with the ejb.jar in \WEB-INF\lib.
The client is able to lookup the facade, but when the facade delegates the
EntityManager a
12 matches
Mail list logo
