geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-1935) WAR with local EJB reference fails with complaints about remote interfaces
Date Fri, 28 Apr 2006 05:25:38 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-1935?page=comments#action_12376877 ] 

Aaron Mulder commented on GERONIMO-1935:
----------------------------------------

OK, so this seems to be the problem.

The ConfigurationBuilder has 3 methods called in this order:

1) getDeploymentPlan
2) getConfigurationID
3) buildConfiguration

Looking at EARConfigurationBuilder, this translates into the following ModuleBuilder calls:

1) getDeploymentPlan
   - createModule(Object, JarFile, ...)
   - createModule(File, JarFile,...)
2) getConfigurationID
3) buildConfiguration
   - installModule
   - initContext
   - addGBeans

So the problem is that EARConfigBuilder attempts to set the correct ConfigID (with version
number) in step 2, but the module builders (e.g. JettyModuleBuilder) do things with the ConfigID
in the createModule calls in step one.  In particular, they stuff it into the WebModule, which
presumably is how it filters into the GBeans.

We need to think about how to what the best time is to mangle the ConfigID...

> WAR with local EJB reference fails with complaints about remote interfaces
> --------------------------------------------------------------------------
>
>          Key: GERONIMO-1935
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1935
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: deployment, OpenEJB
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.1

>
> web.xml contains:
>     <ejb-local-ref>
>         <ejb-ref-name>ejb/StoreManager</ejb-ref-name>
>         <ejb-ref-type>Session</ejb-ref-type>
>         <local-home>dk.jaoo.geronimo.laptop.ejb.StoreManagerHome</local-home>
>         <local>dk.jaoo.geronimo.laptop.ejb.StoreManager</local>
>         <ejb-link>StoreManager</ejb-link>
>     </ejb-local-ref>
> ejb-jar.xml contains:
>       <session>
>           <display-name>Store Manager Session Bean</display-name>
>           <ejb-name>StoreManager</ejb-name>
>           <local-home>dk.jaoo.geronimo.laptop.ejb.StoreManagerHome</local-home>
>           <local>dk.jaoo.geronimo.laptop.ejb.StoreManager</local>
>           <ejb-class>dk.jaoo.geronimo.laptop.ejb.StoreManagerBean</ejb-class>
>           <session-type>Stateless</session-type>
>           <transaction-type>Container</transaction-type>
>           <resource-ref>
>               <res-ref-name>jdbc/LaptopDatabase</res-ref-name>
>               <res-type>javax.sql.DataSource</res-type>
>               <res-auth>Container</res-auth>
>               <res-sharing-scope>Shareable</res-sharing-scope>
>           </resource-ref>
>       </session>
> Deployment error is:
>     Error: Unable to distribute laptopstore-ear-1.0-SNAPSHOT.ear: Could
>     not find an EJB for reference ejb/StoreManager to a remote session
>     bean that has the home interface
>     dk.jaoo.geronimo.laptop.ejb.StoreManagerHome and the remote
>     interface dk.jaoo.geronimo.laptop.ejb.StoreManager

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message