Cannot expose EJB3.0 Stateless Session Bean as JAXWS webservice onWAS 6.1 - Websphere

This is a discussion on Cannot expose EJB3.0 Stateless Session Bean as JAXWS webservice onWAS 6.1 - Websphere ; I am trying to expose EJB3.0 Stateless Session Bean as a JAX-WS webservice on WAS 6.1. Server is WAS 6.1.0.13 Getting following error while deploying EJB 7/17/08 15:18:41:220 IST 000000dd WASWSDLGenera E WSWS7054E: The Web Services Description Language (WSDL) file ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Cannot expose EJB3.0 Stateless Session Bean as JAXWS webservice onWAS 6.1

  1. Cannot expose EJB3.0 Stateless Session Bean as JAXWS webservice onWAS 6.1

    I am trying to expose EJB3.0 Stateless Session Bean as a JAX-WS webservice on WAS 6.1.

    Server is WAS 6.1.0.13

    Getting following error while deploying EJB



    7/17/08 15:18:41:220 IST 000000dd WASWSDLGenera E WSWS7054E: The Web Services Description Language (WSDL) file could not be generated for the bs.dk.ejb.HelloBean Web service implementation class because of the following error: java.lang.Exception: A WSDL Definition could not be generated for the implementation class: bs.dk.ejb.HelloBean

    7/17/08 15:18:41:252 IST 000000dd ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv0 1\logs\ffdc\server1_000000dd_ 08.07.17_15.18.41_0.txt

    7/17/08 15:18:41:298 IST 000000dd ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv0 1\logs\ffdc\server1_000000dd_ 08.07.17_15.18.41_0.txt

    7/17/08 15:18:41:345 IST 000000dd WSModuleDescr E WSWS7027E: JAX-WS Service Descriptions could not be correctly built because of the following error: javax.xml.ws.WebServiceException: WSWS7054E: The Web Services Description Language (WSDL) file could not be generated for the bs.dk.ejb.HelloBean Web service implementation class because of the following error: java.lang.Exception: A WSDL Definition could not be generated for the implementation class: bs.dk.ejb.HelloBean

    at com.ibm.ws.websvcs.wsdl.WASWSDLGenerator.generateW sdl(WASWSDLGenerator.java:210 )

    at org.apache.axis2.jaxws.description.impl.EndpointDe scriptionImpl.generateWSDL(En dpointDescriptionImpl.java:1752)

    at org.apache.axis2.jaxws.description.impl.EndpointDe scriptionImpl. (Endpoint DescriptionImpl.java:330)

    at org.apache.axis2.jaxws.description.impl.ServiceDes criptionImpl.setupServiceDesc riptionImpl(ServiceDescriptionImpl.java:225)

    at org.apache.axis2.jaxws.description.impl.ServiceDes criptionImpl.(ServiceDe scriptionImpl.java:183)

    at org.apache.axis2.jaxws.description.impl.Descriptio nFactoryImpl.createServiceDes criptionFromDBCMap(DescriptionFactoryImpl.java:179 )

    at org.apache.axis2.jaxws.description.DescriptionFact ory.createServiceDescriptionF romDBCMap(DescriptionFactory.java:135)

    at com.ibm.ws.websvcs.desc.WSModuleDescriptorImpl.bui ldServices(WSModuleDescriptor Impl.java:320)

    at com.ibm.ws.websvcs.desc.WSModuleDescriptorImpl.get Services(WSModuleDescriptorIm pl.java:260)

    at com.ibm.ws.webservices.admin.deploy.ServiceIndexDa taBuilder.getWSData(ServiceIn dexDataBuilder.java:50)

    at com.ibm.ws.webservices.admin.deploy.ServiceIndexSe rverTaskImpl.listWebServices( ServiceIndexServerTaskImpl.java:142)

    at com.ibm.ws.webservices.admin.deploy.ServiceIndexSe rverTaskImpl.listWebServices( ServiceIndexServerTaskImpl.java:107)

    at com.ibm.ws.webservices.admin.deploy.ServiceIndexSe rverTask.performTask(ServiceI ndexServerTask.java:163)

    at com.ibm.ws.management.application.SchedulerImpl.ru n(SchedulerImpl.java:262)

    at java.lang.Thread.run(Thread.java:810)

    Caused by: java.lang.Exception: A WSDL Definition could not be generated for the implementation class: bs.dk.ejb.HelloBean

    at com.ibm.ws.websvcs.wsdl.WASWSDLGenerator.generateW sdl(WASWSDLGenerator.java:183 )

    ... 14 more

  2. Re: Cannot expose EJB3.0 Stateless Session Bean as JAXWS webserviceon WAS

    Following is the code:



    @Stateless
    @WebService(serviceName= "HelloWS" )
    public class HelloBean implements HelloIntr
    {
     
    @WebMethod
    public String callHello(String name)
    {
    System.out.println( "in callHello()" );
    System.out.println( "Input - String name : " + name);
    return "Hello " + name + " !!!!!!" ;
    }
    }




    Is it possible to expose EJB3.0 as JAX-WS webservice ??

  3. Re: Cannot expose EJB3.0 Stateless Session Bean as JAXWS webserviceon WAS

    Hopefully somebody will correct me if they have better information but I
    believe that is is not possible to directly expose an EJB3 session bean
    as a JAX-WS Web Services in WebSphere 6.1. Instead you need to expose a
    plain Java object as a JAX-WS Web Service, and have that Java object
    invoke the EJB3 bean.

    Sonal.Mundhe@lntinfotech.com wrote:
    > Following is the code:
    >
    >
    >
    > @Stateless
    > @WebService(serviceName= "HelloWS" )
    > public class HelloBean implements HelloIntr
    > {
    >  
    > @WebMethod
    > public String callHello(String name)
    > {
    > System.out.println( "in callHello()" );
    > System.out.println( "Input - String name : " + name);
    > return "Hello " + name + " !!!!!!" ;
    > }
    > }
    >
    >
    >
    >
    > Is it possible to expose EJB3.0 as JAX-WS webservice ??


+ Reply to Thread