geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Created: (GERONIMO-5322) Start ejb gbeans before servlet gbeans so injection can have a target
Date Tue, 18 May 2010 17:00:42 GMT
Start ejb gbeans before servlet gbeans so injection can have a target
---------------------------------------------------------------------

                 Key: GERONIMO-5322
                 URL: https://issues.apache.org/jira/browse/GERONIMO-5322
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: OpenEJB, web
    Affects Versions: 3.0
            Reporter: David Jencks
            Assignee: David Jencks
             Fix For: 3.0


In 2.2 all the ejbs got started before any web apps because each web app was in a separate
configuration.  Right now in 3.0 we're only creating one bundle for an ear, so all the gbeans
are in the same configuration.  Ejb references used in injection are evaluated immediately
and if the approprate ejb gbeans aren't started before the web gbeans you get naming exceptions.

One easy and hopefully temporary way to deal with this is to increase the priority of the
ejb gbeans (i.e. a smaller priority value).  Since osgi leans towards asynchronous-friendly
solutions a more lazy evaluation approach might be better.  This is tricky ATM due to openejb's
architecture, although they may have a solution ready-to-use that I don't know about.  The
java: ejb references are References that point to the openejb/Deployments jndi tree which
is filled in only as the apps are started.  To make this more asynchronous I think the info
to create the proxy would have to be bound at the java: jndi location directly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message