[jboss-jira] [JBoss JIRA] Commented: (JBMETA-251) JBossSessionBeanMetaData incorrectly reporting singleton beans as stateless

[jaikiran pai (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMETA-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12509411#action_12509411 ] 

jaikiran pai commented on JBMETA-251:
-------------------------------------

Pete,

There aren't any new jboss-metadata-ejb releases planned for JBoss AS 6.0.0.M2. Do you need this fix for M2? If not, i'll schedule it for the next metadata-ejb release and make it available in AS 6.0.0.M3. 


> JBossSessionBeanMetaData incorrectly reporting singleton beans as stateless
> ---------------------------------------------------------------------------
>
>                 Key: JBMETA-251
>                 URL: https://jira.jboss.org/jira/browse/JBMETA-251
>             Project: JBoss Metadata
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: ejb
>         Environment: r100032
>            Reporter: Pete Muir
>            Assignee: jaikiran pai
>             Fix For: jboss-metadata-ejb-2.0.0-alpha-6
>
>
> For http://anonsvn.jboss.org/repos/weld/cdi-tck/tags/1.0.1-CR1/impl/src/main/java/org/jboss/jsr299/tck/tests/implementation/enterprise/definition/Laika.java sbmd.isStateless() is returning true, when in fact it should return false as the bean is a singleton. This in turn causes Weld to fail the deployment as the @ApplicationScoped is not allowed for stateless beans (but is for singletons).
> I am disabling the CDI TCK tests for this package.

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