[ https://issues.jboss.org/browse/AS7-4896?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-4896: ----------------------------------- This looks more like the case where the EJB isn't being marked with an implicit no-interface view. I think I know why that would be the case. Can you in the meantime just mark RuleService bean with a @LocalBean: {code} @Stateless @WebService @LocalBean // exposes an explicit no-interface view public class RuleService { {code} That should get you past this. -- 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

[ https://issues.jboss.org/browse/AS7-4896?page=com.atlassian.jira.plugin.s... ] 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. -- 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

[ https://issues.jboss.org/browse/AS7-4896?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-4896: ----------------------------------- It shouldn't be any different. Can you post that relevant SFSB including any annotations, implements clause and any deployment descriptor configurations? -- 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

[ https://issues.jboss.org/browse/AS7-4896?page=com.atlassian.jira.plugin.s... ] Davide Consonni commented on AS7-4896: -------------------------------------- I was wrong with stateful and jndi, you are right. Have a stateful && webservice may be a nonsense combination :) anyway here my tests: @Stateless @WebService //@LocalBean public class RuleService { // * NO EJB, OK WEBSERVICE * 12:51:42,968 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) 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: 12:51:42,991 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) JBAS016005: Starting Services for CDI deployment: profilesync-application-ear-2.0.ear 12:51:43,026 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-3) Add Service id=RuleService address=http://localhost:8080/profilesync-application-ejb-2.0/RuleService implementor=com.amadeus.profilesync.ruleseditor.service.RuleService invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker serviceName={http://service.ruleseditor.profilesync.amadeus.com/}RuleServ... portName={http://service.ruleseditor.profilesync.amadeus.com/}RuleService... wsdlLocation=null mtomEnabled=false properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.subunit."profilesync-application-ear-2.0.ear"."profilesync-application-ejb-2.0.jar".component.RuleService.VIEW."com.amadeus.profilesync.ruleseditor.service.RuleService".SERVICE_ENDPOINT] ---------8<-------------8<------------- @Stateful @WebService //@LocalBean public class RuleService { // * OK EJB, NO WEBSERVICE * 12:53:30,511 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) 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: java:global/profilesync-application-ear-2.0/profilesync-application-ejb-2.0/RuleService!com.amadeus.profilesync.ruleseditor.service.RuleService java:app/profilesync-application-ejb-2.0/RuleService!com.amadeus.profilesync.ruleseditor.service.RuleService java:module/RuleService!com.amadeus.profilesync.ruleseditor.service.RuleService java:global/profilesync-application-ear-2.0/profilesync-application-ejb-2.0/RuleService java:app/profilesync-application-ejb-2.0/RuleService java:module/RuleService ---------8<-------------8<------------- @Stateless @WebService @LocalBean public class RuleService { // * OK EJB, OK WEBSERVICE * 12:55:00,976 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) 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: java:global/profilesync-application-ear-2.0/profilesync-application-ejb-2.0/RuleService!com.amadeus.profilesync.ruleseditor.service.RuleService java:app/profilesync-application-ejb-2.0/RuleService!com.amadeus.profilesync.ruleseditor.service.RuleService java:module/RuleService!com.amadeus.profilesync.ruleseditor.service.RuleService 12:55:00,975 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment profilesync-application-web-seneca-2.0.war 12:55:01,015 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) JBAS016005: Starting Services for CDI deployment: profilesync-application-ear-2.0.ear 12:55:01,046 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-3) Add Service id=RuleService address=http://localhost:8080/profilesync-application-ejb-2.0/RuleService implementor=com.amadeus.profilesync.ruleseditor.service.RuleService invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker serviceName={http://service.ruleseditor.profilesync.amadeus.com/}RuleServ... portName={http://service.ruleseditor.profilesync.amadeus.com/}RuleService... wsdlLocation=null mtomEnabled=false properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.subunit."profilesync-application-ear-2.0.ear"."profilesync-application-ejb-2.0.jar".component.RuleService.VIEW."com.amadeus.profilesync.ruleseditor.service.RuleService".SERVICE_ENDPOINT] ---------8<-------------8<------------- Thank you again -- 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