geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Quintin Beukes (JIRA)" <>
Subject [jira] Updated: (GERONIMO-4918) Incomplete, not working support for singleton EJBs even though OpenEJB 3.1.2 is used
Date Wed, 28 Oct 2009 19:24:59 GMT


Quintin Beukes updated GERONIMO-4918:

    Attachment: singleton-deploy-type.patch

The commit didn't include the SINGLETON type in plugins/openejb/geronimo-openejb-builder/src/main/java/org/apache/geronimo/openejb/deployment/

Without it you receive the following when deploying a Singleton EJB:
org.apache.geronimo.common.DeploymentException: Unable to deploy KunyeEAR-ear.ear: Unknown
enterprise bean type org.apache.openejb.jee.SingletonBean

There are 2 places to update for a bean type, this one and plugins/openejb/geronimo-openejb-builder/src/main/java/org/apache/geronimo/openejb/deployment/

It looks like the file has been created though, so the patch
should do it.

> Incomplete, not working support for singleton EJBs even though OpenEJB 3.1.2 is used
> ------------------------------------------------------------------------------------
>                 Key: GERONIMO-4918
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: OpenEJB
>    Affects Versions: 2.2
>            Reporter: Quintin Beukes
>             Fix For: 2.2, 3.0
>         Attachments: GERONIMO-4918.patch, geronimo-singleton-support-geronimo.patch,, singleton-deploy-type.patch,
> The singleton support hasn't been completely implemented, so it's impossible to deploy
an singleton session bean (EJB).
> I added the support, recompiled + tested and it's working.
> The patch requires creating a new file, so both need to be applied.
> The patch was made from the root of the svn checkout of branches/2.2. 
> The new files path from the same root is: plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/

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

View raw message