Announcement Announcement Module
No announcement yet.
Spring Remoting EJB issue Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Spring Remoting EJB issue

    Hello everyone,

    we are currently developping an application making use of the spring technology. In this application we use a lot of remote calls.
    Up untill now these calls were done by an HTTPInvoker; the problem this causes, is that we loose our transactions from the moment we do a remote call. This is why we would like to change this, and in stead of HTTP invocation we would like to use EJB invocation, were we can keep our transactions. For this reason we already migrated from a Tomcat server to a glassfish server.
    However we encounter some problems doing this migration of the HTTPInvoker to the EJB way of remote invocation.
    Our application is not an EJB application, and we do not wan't to make too much modifications in our already existing application (such as create explicit EJB session beans, add EJB annotations, introduce a lot of ejb libraries...).
    In our ideal scenario we would simply like to migrate the existing remoting HTTPInvoker applicationContext.xml from :

    <bean id="loggerServiceRemote" class="org.springframework.remoting.httpinvoker.Ht tpInvokerProxyFactoryBean">
    <property name="serviceUrl">
    <property name="serviceInterface">
    <value>be.scarlet.oss.bss.tx2.service.LoggerServic e</value>


    <bean id="loggerServiceRemote"
    class="org.springframework.ejb.access.LocalStatele ssSessionProxyFactoryBean">
    <property name="jndiName" value="ejb/loggerService"/>
    <property name="businessInterface" value="be be.scarlet.oss.bss.tx2.service.LoggerService "/>

    Can anyone please provide some extra info in how we can handle this change please?
    We assume that we have to define this jndi resource in the EJB container (into our running glassfish server), and that we need to be able to link the businessInterface with our custom service implementation (which in the Http case was done by a service-servlet.xml file by the SimpleUrlHandlerMapping and the HttpInvokerServiceExporter). But this is the part were we encounter our problems. We simply do not seem to get this configuration up and running.
    Any help about how to handle this problem would be deeply appriciated.

    Thanks in advance