Re: transaction rolls back when returning from a remove method of a SFSB

Sorry was thinking of Passivate/Activate Here's the more up to date docs: http://java.sun.com/javaee/5/docs/tutorial/doc/bnbmt.html#bnbmu I'm curious to know what it is you're doing in postProcess, I'm still inclined to say that it

Re: transaction rolls back when returning from a remove method of a SFSB

What you're describing is exactly what's supposed to be happening. You're not supposed to invoke the @Remove method from your own code. When the bean container passivates the instance, it calls @Remove for you. On Mon, Dec 14, 2009 at 5:13 AM, is_maximum wrote: > > Hello > I have a Stateful se

Re: NamingExpection: Name openejb is not bound in this Context

Hmmm ok good to know you're using spring then. Are you attempting to look things up via spring objects or via EJBs? Based on the spring integration page, it looks like there are a number of existing classes that are designed to help in this scenario: http://openejb.apache.org/3.0/spring.html And

Re: NamingExpection: Name openejb is not bound in this Context

Sounds like an error in your jndi.properties. Based on your other comment, could be something to do with classloading as well. Can you post a bit more sample code? Something like this: new InitialContext().lookup("java:openejb/Resource/mySqlDatabase"); Will be unlikely to work unless you speci

Re: NamingExpection: Name openejb is not bound in this Context

Hi What if you just lookup this.context.lookup("mySqlDatabase"); ? On Sun, Nov 29, 2009 at 6:56 AM, Cae Fernandes wrote: > > Can't lookup openejb context so I can hardly lookup anything actually. > Help? > > properties: > > > java.naming.factory.initial=org.apache.openejb.client.LocalInitialC

Re: REQUIRES_NEW within a NEVER transaction throwing an exception, bug or misuse?

the OpenEJB examples, or supported. > > Thanks! > > On Tue, Nov 17, 2009 at 6:50 PM, John Ament wrote: > > > Based on how JTA's supposed to work, if a NEVER is calling a REQUIRES_NEW > > EJB, then the REQUIRES_NEW runs in its own transaction context. No > > ex

Re: REQUIRES_NEW within a NEVER transaction throwing an exception, bug or misuse?

Based on how JTA's supposed to work, if a NEVER is calling a REQUIRES_NEW EJB, then the REQUIRES_NEW runs in its own transaction context. No exception should be thrown. In my opinion, from a design stand point, assuming that you mean method A calls methods B and C, then A should be anything (pref

Timer API not launching correctly?

All I found a weird issue, or maybe it's the expected behavior I'm not sure. I created a long running process that uses openejb for datasource mgmt and ejb timer apis. I created a job that is meant to run at 0430 daily. When we start the process before noon, it works fine. when we start it aft

Re: suggestion for defining local ref name for session beans

I'm not sure, could be that I'm missing the the subtlety of your request, but isn't this what the mappedName attribute is for on the Stateless/Stateful annotation? - John On Sun, Sep 13, 2009 at 4:20 AM, Mohammad Nour El-Din < nour.moham...@gmail.com> wrote: > Hi Mohammad Nourouzi... > > Seems

WebService client in an embedded scneario

Does anyone have any comments as to support for web service clients in openejb? I don't see anything commented as far as this goes. Do I need an external library? Thanks, John