Cannot find endpoint meta data with super-simple WS

[jimpo991]

I am trying to deploy a very very simple helloworld WS using

JBossAS 4.2.1-GA
JBossWS jbossws-3.0.1-native-2.0.4.GA

both out-of-the-box installations. I have installed JbossWS and run the tests, it should be ok.

I basically have class com.foo.Banana:

package com.foo;

import javax.jws.WebMethod;
import javax.jws.WebService;

@WebService
public class Banana {

 @WebMethod
 public int foo(int bar) {
 return 7;
 }
}

and web.xml:

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
 http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
 version="2.4">

 <display-name>Archetype Created Web Application</display-name>

 <servlet>
 <servlet-name>Banana</servlet-name>
 <servlet-class>com.foo.Banana</servlet-class>
 </servlet>

 <servlet-mapping>
 <servlet-name>Banana</servlet-name>
 <url-pattern>/banaaninpoimija</url-pattern>
 </servlet-mapping>
</web-app>

Nothing else. AFAIK I should be able to just package this in standard WAR and deploy to JBoss. No need for any wscompile / etc tools, right? When I deploy I get the error:

16:45:38,734 ERROR [[HtmlAdaptor]] Servlet.service() for servlet HtmlAdaptor threw exception
java.lang.IllegalStateException: Cannot find endpoint meta data for: Banana
 at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.getEndpointMetaData(UnifiedMetaDataDeploymentAspect.java:117)
 at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:86)
 at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118)
 at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
 at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
 at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
 at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
 at $Proxy45.start(Unknown Source)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
 at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)

I see other people have reported this as well:

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132729

There was no solution there though, he just gave up on the approach and implemented an EJB endpoint instead.

[ritesh001]

jimpo, have you found a solution to this problem? I'm having the same problem, though my service deploys just fine on GlassFish and WebLogic, just that JBoss is screwed up with "cannot find endpoint meta data" error.

[jimpo]

"ritesh001" wrote:
jimpo, have you found a solution to this problem? I'm having the same problem, though my service deploys just fine on GlassFish and WebLogic, just that JBoss is screwed up with "cannot find endpoint meta data" error.

Sorry I can't help you. I can't remember if I figured out a solution this, and I am not using this approach anymore (I am creating the interface artifacts from WSDL using wsconsume tool). Also I'm using jbossws 2.0 now for other reasons.

[rishabh2u]

Yeah this is still a problem in in jboss 4.2.3 GA. and 2.0.4 GA. and Java 5.
On some forums there are workarounds to this problem by isolating some jars etc. I am working on a solution and willl update this post soon.

[rishabh2u]

ok... this problem seems to be not a problem :-0
Can you make sure that your war does not contain the javax.jws contating jar in it. If you use the Banana example from jimpo then you should not have any jars in your war as all. It shoud have only 3 files, web.xml,Banana.class and the manifest file.
This totally worked for me on jboss 4.2.3 GA., JBoss 2.0.4 GA. and Java 5.