Spring Implementation of EJB 3.0

[kishore skipper]

Hi All

i am trying to use spring implementation of ejb3.0 and stuck at configuring it in ApplicationContext.xml

Business Interface
HelloService.java

  public interface HelloService {
                   public String method();
            }

HelloServiceImpl.java

   public class HelloServiceImpl implements HelloService {
                  public String method() {
                     return "Hello Service";
                   }
             }
 

HelloServiceLocal.java

   
       @Local
       public interface HelloServiceLocal extends HelloService {
              }
 

HelloServiceEJB.java

   
     @Stateless
     @Interceptors(SpringBeanAutowiringInterceptor.class)
     public class HelloServiceEJB implements HelloService {
          @Autowired
           private HelloService helloService;

           public String method() {
                return helloService.method();
            }
}

 

and i have the bean configuration like this

   
<bean id="helloService" class="HelloServiceImpl">


 

How shoud i give the jndi name to access this bean locally and remotely in applicationContext.xml...is it the same as EJB2.x implementation?


can somebody help me out in this as i could not find any articles on spring implementaion of ejb 3.0?

Thanks

[Mark Spritzler]

<jee:lookup> ???

Of course you need to add the xsd for the jee context.

Mark

[kishore skipper]

Hi Mark,

Thanks for the reply..as i am new to spring i did not follow the spring implementation of ejb concept...

i am using myeclipse and weblogic 10.3 and spring 2.5

can i write spring ejbs in a web application and deploy it to weblogic server or still i need to use seperate ejb project in a EAR?
if yes where should i keep the weblogic deployment descripter?

could you please provide the information?

[Mark Spritzler]

Well, you don't really use Spring to create EJBs. I mean there are classes and apis that your EJBs can implement/extend and they make EJBs that have access to an ApplicationContext. But I feel the cleanest route is creating EJBs and doing lookups and injecting them into your classes as needed.

Now the upcoming Java EE specs might change things.

Mark