You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Manu T George (JIRA)" <ji...@apache.org> on 2006/11/21 12:18:01 UTC
[jira] Created: (OPENEJB-339) NPE in class AnnotationDeployer
during deployment of annotated beans
NPE in class AnnotationDeployer during deployment of annotated beans
--------------------------------------------------------------------
Key: OPENEJB-339
URL: http://issues.apache.org/jira/browse/OPENEJB-339
Project: OpenEJB
Issue Type: Bug
Components: ejb3 simplified
Affects Versions: 3.0
Environment: All
Reporter: Manu T George
Fix For: 3.0
When you try to deploy an annotated stateless session bean shown below, a NPE is thrown.
The ejb3 core spec says in section 13.3.6
By default, a session bean or message-driven bean has container managed transaction demarcation if the
transaction management type is not specified.
This means that even if we do not specify the annotation or deployment descriptor element for TransactionManagement then it should default to container managed transaction management
--
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
[jira] Closed: (OPENEJB-339) NPE in class AnnotationDeployer during
deployment of annotated beans
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OPENEJB-339?page=all ]
David Blevins closed OPENEJB-339.
---------------------------------
Resolution: Fixed
Assignee: Manu T George
Nice catch!
$ svn ci
Sending openejb-core/src/main/java/org/apache/openejb/alt/config/AnnotationDeployer.java
Transmitting file data .
Committed revision 477756.
> NPE in class AnnotationDeployer during deployment of annotated beans
> --------------------------------------------------------------------
>
> Key: OPENEJB-339
> URL: http://issues.apache.org/jira/browse/OPENEJB-339
> Project: OpenEJB
> Issue Type: Bug
> Components: ejb3 simplified
> Affects Versions: 3.0
> Environment: All
> Reporter: Manu T George
> Assigned To: Manu T George
> Fix For: 3.0
>
> Attachments: AnnotationDeployer.patch
>
>
> When you try to deploy an annotated stateless session bean shown below, a NPE is thrown.
> The ejb3 core spec says in section 13.3.6
> By default, a session bean or message-driven bean has container managed transaction demarcation if the
> transaction management type is not specified.
> This means that even if we do not specify the annotation or deployment descriptor element for TransactionManagement then it should default to container managed transaction management
--
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
[jira] Updated: (OPENEJB-339) NPE in class AnnotationDeployer
during deployment of annotated beans
Posted by "Manu T George (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OPENEJB-339?page=all ]
Manu T George updated OPENEJB-339:
----------------------------------
Attachment: AnnotationDeployer.patch
Patch for setting the TransactionManagement to Container if both annotation and dd element are not given
> NPE in class AnnotationDeployer during deployment of annotated beans
> --------------------------------------------------------------------
>
> Key: OPENEJB-339
> URL: http://issues.apache.org/jira/browse/OPENEJB-339
> Project: OpenEJB
> Issue Type: Bug
> Components: ejb3 simplified
> Affects Versions: 3.0
> Environment: All
> Reporter: Manu T George
> Fix For: 3.0
>
> Attachments: AnnotationDeployer.patch
>
>
> When you try to deploy an annotated stateless session bean shown below, a NPE is thrown.
> The ejb3 core spec says in section 13.3.6
> By default, a session bean or message-driven bean has container managed transaction demarcation if the
> transaction management type is not specified.
> This means that even if we do not specify the annotation or deployment descriptor element for TransactionManagement then it should default to container managed transaction management
--
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
[jira] Commented: (OPENEJB-339) NPE in class AnnotationDeployer
during deployment of annotated beans
Posted by "Manu T George (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OPENEJB-339?page=comments#action_12451604 ]
Manu T George commented on OPENEJB-339:
---------------------------------------
package org.apache.openejb.test.stateless;
import javax.ejb.Local;
import javax.ejb.Remote;
import javax.ejb.Stateless;
@Stateless
@Local ({BasicStatelessBusinessLocal.class})
@Remote ({BasicStatelessBusinessRemote.class})
public class BasicStatelessAnnotatedBean extends BasicStatelessBean {
}
> NPE in class AnnotationDeployer during deployment of annotated beans
> --------------------------------------------------------------------
>
> Key: OPENEJB-339
> URL: http://issues.apache.org/jira/browse/OPENEJB-339
> Project: OpenEJB
> Issue Type: Bug
> Components: ejb3 simplified
> Affects Versions: 3.0
> Environment: All
> Reporter: Manu T George
> Fix For: 3.0
>
>
> When you try to deploy an annotated stateless session bean shown below, a NPE is thrown.
> The ejb3 core spec says in section 13.3.6
> By default, a session bean or message-driven bean has container managed transaction demarcation if the
> transaction management type is not specified.
> This means that even if we do not specify the annotation or deployment descriptor element for TransactionManagement then it should default to container managed transaction management
--
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