I am currently using the pattern syntax in all my references to EJBs that exist in the seperate module deployed within Geronimo. As an example, here is a snippet of the geronimo-web.xml for my webapp:
<?xml version="1.0" encoding="UTF-8"?> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"; xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.1"; xmlns:tomcat="http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.1";> <environment> <dependencies> ... </dependencies> </environment> <context-root>/services</context-root> <ejb-local-ref> <ref-name>ejb/PortalAccess</ref-name> <pattern> <groupId>testcompany</groupId> <artifactId>testdaomodule</artifactId> <version>3.0</version> <module>backend-dao-module.jar</module> <name>PortalAccessEJB</name> </pattern> </ejb-local-ref> ... </web-app> I attempted to remove the dependency in my geronimo-application.xml for the webapp on the other deployed module, but this resulted in an error in locating the ejb: Error: Unable to distribute backend-registration-module.ear: Could not locate ejb matching testcompany/testdaomodule/3.0/car?EJBModule=backend-dao-module.jar,name=PortalAccessEJB# in configuration testcompany/testregistrationmodule/3.0/car This error occured both when I deployed the testdaomodule first or when I attempted to deploy the testregistrationmodule first. I'll be watching this thread and the JIRA issue posted for further updates. Thanks again, Rick Sears On 6/14/06, David Jencks <[EMAIL PROTECTED]> wrote:
On Jun 14, 2006, at 8:44 AM, Rick Sears wrote: > I'm having a similar problem with an application that I am porting > from Geronimo 1.0 to the 1.1-rc1 snapshot. There are references > (tried both ejb-ref remote references and ejb-local-ref local > references) in my webapp that refer to EJBs deployed in another ear > within Geronimo. This worked perfectly fine in Geronimo 1.0, but is > now not working at all in Geronimo 1.1-rc1 with the same > ClassCastException referred in the previous message. Please let me > know if there is some other way to allow classes in my webapp to refer > to a locally deployed EJB that exists in another ear within Geronimo. > If there is no workaround, then I am anxiously awaiting a resolution > to this issue in Geronimo 1.1. The only workaround I currently think might work is to _not_ have the webapp have a dependency on the ear (or ejb app for Ted's case) and to deploy the web app first. This will avoid the logic that has the CCE. You also have to specify the components of the ejb target name rather than using an ejb-link in the geronimo plan. Please let us know if this works. thanks david jencks > > Thanks for your guys hard work, > Rick Sears
