[jboss-jira] [JBoss JIRA] (AS7-4896) AS7 does not deploy @Stateless + @Webservice

[jaikiran pai (JIRA)]

    [ https://issues.jboss.org/browse/AS7-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696402#comment-12696402 ] 

jaikiran pai commented on AS7-4896:
-----------------------------------

Actually, I misread a part of your bug description and the title of this JIRA kind of mislead me. This isn't really a bug. The EJB3 spec states:
{quote}
4.9.8Session Bean’s No-Interface View

The following are the requirements for a session bean that exposes a no-interface view :

 - The bean class must designate that it exposes a no-interface view via its bean class definition or in the deployment descriptor. The following rules apply :
       * If the bean does not expose any other client views (Local, Remote, No-Interface, 2.x Remote Home, 2.x Local Home, Web Service) and its implements clause is empty, the bean defines a no-interface view.
...
{quote}

So the SLSB is being deployed with just the webservice view. The no-interface view isn't implicitly added because of the presence of the webservice view and webservice views aren't bound to JNDI. If you really want the no-interface view too, then you'll have to explicitly mark it with a @LocalBean as I showed in my previous comment.

I'm closing this JIRA as not a bug.

                
> AS7 does not deploy @Stateless + @Webservice
> --------------------------------------------
>
>                 Key: AS7-4896
>                 URL: https://issues.jboss.org/browse/AS7-4896
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 7.1.1.Final
>         Environment: any
>            Reporter: Davide Consonni
>            Assignee: jaikiran pai
>              Labels: stateless, webservice
>
> Classes marked with @stateless and @webservice are not deployed. (@Stateful+ at Webservice works)
> -----8<-----------8<-------
> @Stateless
> @WebService
> public class RuleService {
> -----8<-----------8<-------
> @Stateless
> //@WebService /*COMMENTED OUT*/
> public class CredentialService {
> -----8<-----------8<-------
> Here the logs, where you can see that CredentialService is corectly deploye as ejb, but RuleService not:
> 10:08:17,738 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment profilesync-application-ejb-2.0.jar
> 10:08:17,741 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named RuleService in deployment unit subdeployment "profilesync-application-ejb-2.0.jar" of deployment "profilesync-application-ear-2.0.ear" are as follows:
> 10:08:17,743 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named CredentialService in deployment unit subdeployment "profilesync-application-ejb-2.0.jar" of deployment "profilesync-application-ear-2.0.ear" are as follows:
>         java:global/profilesync-application-ear-2.0/profilesync-application-ejb-2.0/CredentialService!com.amadeus.profilesync.ruleseditor.service.CredentialService
>         java:app/profilesync-application-ejb-2.0/CredentialService!com.amadeus.profilesync.ruleseditor.service.CredentialService
>         java:module/CredentialService!com.amadeus.profilesync.ruleseditor.service.CredentialService
>         java:global/profilesync-application-ear-2.0/profilesync-application-ejb-2.0/CredentialService
>         java:app/profilesync-application-ejb-2.0/CredentialService
>         java:module/CredentialService

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira