WAS 6.1 - EJB 3 and Web Service Annotations

rja...@aol.com

unread,

Feb 19, 2008, 6:29:30 PM2/19/08

to

Folks, 
 
Does anyone know if WebSphere 6.1 with the EJB 3 and the Webservice packs will support EJB 3 beans annotated with JAX-WS? 
 
@HandlerChain( file="handler-chain.xml") 
@WebService(name = "Simple3EJB") 
@Stateless 
public class Simple3EJB implements Simple3EJBLocal, Simple3EJBRemote { 
 
@WebMethod 
@WebResult(name = "sum") 
public DataSum addInts(int x, int y) { 
int retVal = 0; 
retVal = x + y; 
DataSum dataSum = new DataSum(retVal); 
return dataSum; 
} 
 
} 
 
It not working right now in AST. It doesn't seem to understand the web service annotations. I have applied the service packs for EJB 3 and Web Services for WAS 6.1. 
 
Regards, 
 
Robert Jackson

Ben_

unread,

Feb 20, 2008, 5:14:20 AM2/20/08

to

Don't know for sure, but when I played with WSFeP with RAD, it required RAD
7.0.0.3 to have support for code completion and all stuff. Applying the
Feature Pack like you'd apply to WAS is not an option: you also need to
update the IDE for it to support the new way of coding.

HTH.

Paul Ilechko

unread,

Feb 20, 2008, 8:56:16 AM2/20/08

to

rja...@aol.com wrote:

> It not working right now in AST. It doesn't seem to understand the web service annotations. I have applied the service packs for EJB 3 and Web Services for WAS 6.1.

I'm not sure that the two packs are currently compatible. You might want
to open a PMR and get a definitive answer on that from support.

Ben_

unread,

Feb 20, 2008, 9:28:51 AM2/20/08

to

Install guide covers the case where you want to apply EJB3 on top of WSFeP
and vice-versa.

Paul Ilechko

unread,

Feb 20, 2008, 10:08:39 AM2/20/08

to

OK, good. I know that the betas did not work together - I hoped that the
GA code would ...

Jacek Laskowski

unread,

Feb 20, 2008, 7:42:53 PM2/20/08

to

Hi, 
 
I asked the same quesiton on RADv7.5 forum and got a response that EJB3 exposed as web services are not supported. So, although you can install EJB3 and WS feature packs atop WAS 6.1 in a single profile and they will work fine (tested and verified by myself) no EJB3 with @WebService annotations will work. They will as pure EJBs, but not as web services. You can certainly develop your EJBs with these annotations, but the runtime environment (WAS 6.1 + feature packs) are not ready for it yet. 
 
Jacek 
 
--- 
Jacek Laskowski 
<a href="http://www.JacekLaskowski.pl">http://www.JacekLaskowski.pl</a>

Randy Schnier

unread,

Feb 22, 2008, 2:28:20 PM2/22/08

to

The two feature packs each support their respective specifications (EJB 3.0 and JAX-WS), but are not tightly coupled to each other in a manner that would support EJB3 beans simultaneously acting as JAX-WS endpoints. On the feature packs you will need to write a simple "redirector" object to act as the JAX-WS endpoint, which has the same methods and signatures as your target EJB 3.0 bean. Each method in the redirector object invokes the corresponding method on the target EJB3 bean.

The web service feature pack provides an update for AST 6.1, which among other things provides support for the webservice annotations. To get this update, you can use the Eclipse updater function inside AST 6.1. You can use tools and wizards in the updated AST 6.1 to help create the redirector object I mentioned above. Basically you run the wsgen utility against your EJB3 impl class, annotated with @WebService as you've shown in your example...to generate a WSDL file and schema xsd file:

wsgen -cp . -wsdl com.xyz.Simple3EJB

Then you run the 'Generate Java Bean Skeleton' wizard against the wsdl file you just generated. The resulting Java skeleton object will have the same methods and signatures as your original EJB impl class, with empty implementations. To make this object a "redirector" to your EJB3 bean, you basically fill in the method implementations to invoke the same method on the target EJB3 bean. You can do the EJB imvocation either through the EJB remote interface (cross-server) or the EJB local interface (if your target EJB3 bean is located in the same server as where you have the redirector object).

rja...@aol.com

unread,

Feb 22, 2008, 5:48:24 PM2/22/08

to

Folks,

Thanks to all of you for the information. I was able to verify all this information. I was also able to verify this information.

Jacek Laskowski

unread,

Feb 27, 2008, 6:31:38 PM2/27/08

to

Hi Randy, 
 
I followed the steps until I hit the deployment problem. 
 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d WASWSDLGenera E WSWS7054E: The Web Services Description Language (WSDL) file could not be generated for the itso.bank.EchoServiceBeanPortImpl Web service implementation class because of the following error: java.lang.Exception: A WSDL Definition could not be generated for the implementation class: itso.bank.EchoServiceBeanPortImpl 
<strike>2/27/08 15:19:31:578 PST</strike> 0000006d 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 itso.bank.EchoServiceBeanPortImpl Web service implementation class because of the following error: java.lang.Exception: A WSDL Definition could not be generated for the implementation class: itso.bank.EchoServiceBeanPortImpl 
at com.ibm.ws.websvcs.wsdl.WASWSDLGenerator.generateWsdl(WASWSDLGenerator.java:210) 
at org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.generateWSDL(EndpointDescriptionImpl.java:1754) 
at org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.<init>(EndpointDescriptionImpl.java:352) 
at org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.setupServiceDescriptionImpl(ServiceDescriptionImpl.java:228) 
at org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.<init>(ServiceDescriptionImpl.java:186) 
at org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescriptionFromDBCMap(DescriptionFactoryImpl.java:192) 
at org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescriptionFromDBCMap(DescriptionFactory.java:135) 
at com.ibm.ws.websvcs.desc.WSModuleDescriptorImpl.buildServices(WSModuleDescriptorImpl.java:328) 
at com.ibm.ws.websvcs.desc.WSModuleDescriptorImpl.getServices(WSModuleDescriptorImpl.java:268) 
at com.ibm.ws.webservices.admin.deploy.ServiceIndexDataBuilder.getWSData(ServiceIndexDataBuilder.java:50) 
at com.ibm.ws.webservices.admin.deploy.ServiceIndexServerTaskImpl.listWebServices(ServiceIndexServerTaskImpl.java:142) 
at com.ibm.ws.webservices.admin.deploy.ServiceIndexServerTaskImpl.listWebServices(ServiceIndexServerTaskImpl.java:107) 
at com.ibm.ws.webservices.admin.deploy.ServiceIndexServerTask.performTask(ServiceIndexServerTask.java:163) 
at com.ibm.ws.management.application.SchedulerImpl.run(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: itso.bank.EchoServiceBeanPortImpl 
at com.ibm.ws.websvcs.wsdl.WASWSDLGenerator.generateWsdl(WASWSDLGenerator.java:183) 
... 14 more 
 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R Problem encountered during annotation processing; 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R see stacktrace below for more information. 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R java.lang.ClassCastException: com.sun.tools.apt.mirror.declaration.ClassDeclarationImpl incompatible with com.sun.mirror.declaration.InterfaceDeclaration 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.getEndpointInterfaceDecl(WebServiceVisitor.java:429) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.isLegalImplementation(WebServiceVisitor.java:545) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.shouldProcessWebService(WebServiceVisitor.java:352) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.ws.processor.modeler.annotation.WebServiceVisitor.visitClassDeclaration(WebServiceVisitor.java:145) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.apt.mirror.declaration.ClassDeclarationImpl.accept(ClassDeclarationImpl.java:109) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.buildModel(WebServiceAP.java:347) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.ws.processor.modeler.annotation.WebServiceAP.process(WebServiceAP.java:232) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.mirror.apt.AnnotationProcessors$CompositeAnnotationProcessor.process(AnnotationProcessors.java:78) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.apt.comp.Apt.main(Apt.java:472) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.apt.main.JavaCompiler.compile(JavaCompiler.java:486) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.apt.main.Main.compile(Main.java:1103) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.apt.main.Main.compile(Main.java:966) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.apt.Main.processing(Main.java:113) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.apt.Main.process(Main.java:103) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.apt.Main.process(Main.java:85) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.ws.wscompile.CompileTool.buildModel(CompileTool.java:605) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.ws.wscompile.CompileTool.run(CompileTool.java:538) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.ws.util.ToolBase.run(ToolBase.java:56) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.sun.tools.ws.util.WSToolsObjectFactoryImpl.wsgen(WSToolsObjectFactoryImpl.java:44) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.ibm.ws.websvcs.wsdl.WASWSDLGenerator.generateWsdl(WASWSDLGenerator.java:179) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.generateWSDL(EndpointDescriptionImpl.java:1754) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.<init>(EndpointDescriptionImpl.java:352) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.setupServiceDescriptionImpl(ServiceDescriptionImpl.java:228) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.<init>(ServiceDescriptionImpl.java:186) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescriptionFromDBCMap(DescriptionFactoryImpl.java:192) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescriptionFromDBCMap(DescriptionFactory.java:135) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.ibm.ws.websvcs.desc.WSModuleDescriptorImpl.buildServices(WSModuleDescriptorImpl.java:328) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.ibm.ws.websvcs.desc.WSModuleDescriptorImpl.getServices(WSModuleDescriptorImpl.java:268) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.ibm.ws.webservices.admin.deploy.ServiceIndexDataBuilder.getWSData(ServiceIndexDataBuilder.java:50) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.ibm.ws.webservices.admin.deploy.ServiceIndexServerTaskImpl.listWebServices(ServiceIndexServerTaskImpl.java:142) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.ibm.ws.webservices.admin.deploy.ServiceIndexServerTaskImpl.listWebServices(ServiceIndexServerTaskImpl.java:107) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.ibm.ws.webservices.admin.deploy.ServiceIndexServerTask.performTask(ServiceIndexServerTask.java:163) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:262) 
<strike>2/27/08 15:19:31:562 PST</strike> 0000006d SystemErr R at java.lang.Thread.run(Thread.java:810) 
 
I've created a web service client-only dynamic web project and am stuck with ejb-ref definition in web.xml file to the ejb the web service impl delegates calls to. I defined it as follows: 
 
<ejb-ref> 
<description></description> 
<ejb-ref-name>ejb/echo</ejb-ref-name> 
<ejb-ref-type>Session</ejb-ref-type> 
<home></home> 
<remote>itso.bank.EchoService</remote> 
</ejb-ref> 
 
The EchoService is in another ear. The web (web services client) project deploys and works fine until I execute the web service which in turn calls the ejb via ejb/echo reference. I'm getting an error message saying that ejb is not part of the ear so I should not expect it working. 
 
Caused by: com.ibm.ejs.container.EJBNotFoundException: EJB with interface itso.bank.EchoService not present in application WebServiceProjectEAR 
at com.ibm.ejs.container.HomeOfHomes.getHomeByInterface(HomeOfHomes.java:567) 
at com.ibm.ws.ejbcontainer.injection.factory.EJBLinkObjectFactory.getObjectInstance(EJBLinkObjectFactory.java:252) 
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:316) 
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:917) 
... 42 more 
 
So, I added the web (web service client) project as a part of the EAR with the ejb it delegates calls to. The above exception's thrown upon deployment. What am I doing wrong?

Jacek Laskowski

unread,

Feb 27, 2008, 9:22:30 PM2/27/08

to

Hi,

Just to let you know I got it working. Thanks Randy for the tip. Don't know if I'm now able to describe it clearly as the entire technique seems like a candidate for the gratest hack in 2008 ;-)

Jacek Laskowski

unread,

Feb 29, 2008, 7:05:05 PM2/29/08

to

Hi,

Please correct me if I'm wrong, but the wire/pass-through approach with POJO-based JAX-WS service implementation can't allow to bundle the web app with the web service in the EAR of the @WebService EJB 3.0 bean. Can anyone work it around and make such a configuration working?

Randy Schnier

unread,

Mar 3, 2008, 11:55:37 PM3/3/08

to

I know of no reason this would not work -- the web service POJO is bundled in a WAR module; the EJB 3.0 bean is bundled in an ejb-jar module. I'm pretty sure at least one of the customers I'm working with is doing exactly that. What symptom are you experiencing?

rja...@aol.com

unread,

Mar 10, 2008, 12:22:30 PM3/10/08

to

Folks, 
 
I want to thank everyone again for contributing to this thread. 
 
I've tried the redirector strategy and I getting a weird error. I cannot find the error anywhere, and I wonder if it could be related to security or my install. 
 
1) Created a WAR with a JAX-WS 2.0 Annotated POJO. The POJO is a redirector for EJB methods. 
2) Put the War and my EJB into an EAR file. (Wonder web annotations might cause problems, but I think that are ignored). 
3) Packed it in a EAR file. EAR uses JavaEE5 application.xml file... 
 
It deploys fine but when I try to access the webservice, here is what I get: 
 
<ul class="jive-dash">
<li><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"></li>
<li><soapenv:Body></li>
<li><soapenv:Fault></li>
</ul>
<faultcode>soapenv:Client</faultcode> 
<faultstring>java.lang.NoClassDefFoundError: com.ibm.ws.wssecurity.trust.server.sts.Util.STSPolicySetUtil (initialization failure)</faultstring> 
<detail /> 
</soapenv:Fault> 
</soapenv:Body> 
</soapenv:Envelope> 
 
Any Ideas...

rja...@aol.com

unread,

Mar 11, 2008, 9:41:34 AM3/11/08

to

Folks,

I wonder if I need to configure some type of Policies? 
 
Robert Jackson

sourabh...@tcs.com

unread,

Mar 12, 2008, 4:03:23 AM3/12/08

to

Dear Robert Jackson, 
 
We are also getting same error. Please do let me know, if you have got resolution to this problem.

rja...@aol.com

unread,

Mar 12, 2008, 12:02:59 PM3/12/08

to

Folks,

It's good to know that it's not just me. I've pretty much tried everything I can think of to get this to work. 
 
1) Just tried a simple POJO in a WAR. 
2) Compiling with Several jdk 1.5.1 java versions (IBM and Sun) 
3) Etc.. 
 
An IBMer helping me out noticed that the FFDC file seems to list this as the primary problem. 
 
Caused by: java.lang.NullPointerException 
at javax.xml.bind.ContextFinder.handleClassCastException(ContextFinder.java:95) 
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:147) 
at javax.xml.bind.ContextFinder.find(ContextFinder.java:299) 
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372) 
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337) 
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:244) 
at com.ibm.ws.wssecurity.platform.websphere.trust.server.sts.STSConfigurationMapLoaderImpl.loadSTSConfigurationMap(STSConfigurationMapLoaderImpl.java:75) 
at com.ibm.ws.wssecurity.trust.server.sts.Util.STSConfigUtil.loadSTSConfigurationMap(STSConfigUtil.java:610) 
at com.ibm.ws.wssecurity.trust.server.sts.Util.STSConfigUtil.getSTSConfigurationMap(STSConfigUtil.java:679) 
at com.ibm.ws.wssecurity.trust.server.sts.Util.STSPolicySetUtil.configure(STSPolicySetUtil.java:147) 
at com.ibm.ws.wssecurity.trust.server.sts.Util.STSPolicySetUtil.initialize(STSPolicySetUtil.java:386) 
at com.ibm.ws.wssecurity.trust.server.sts.Util.STSPolicySetUtil.<clinit>(STSPolicySetUtil.java:60) 
at java.lang.J9VMInternals.initializeImpl(Native Method) 
at java.lang.J9VMInternals.initialize(J9VMInternals.java:194) 

I noticed some else had this problem with JAX-WS when there were multiple jars with JAX-WS apis in the classpath. 
 
Maybe there is a problem with the service packs. My next thing to try is to just install the Webservices service pack in a another WebSphere install. 
 
Regards, 
 
Robert Jackson

rja...@aol.com

unread,

Mar 12, 2008, 5:01:00 PM3/12/08

to

Folks,

1) I've found out is that you need to have this jar in your classpath for the client: 
 
Appserver\runtimes\com.ibm.jaxws.thinclient_6.1.0.jar 
 
2) You also need to run the client using the IBM JDK. 
 
I'm still getting strange errrors though. 
 
Here's my current Application Server Setup. 
 
WebSphere Base 6.1.0.13 
EJB 3.0.6.0.13 
WS FEP 6.1.0.9 
 
From myceclipse I'm getting this error: 
 
Exception in thread "main" HTTP Status-Code 400: Bad Request 
at com.sun.xml.ws.transport.http.client.HttpClientTransport.checkResponseCode(Http ClientTransport.java:226) 
at com.sun.xml.ws.transport.http.client.HttpClientTransport.getHeaders(HttpClientT ransport.java:145) 
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPip e.java:116) 
at com.sun.xml.ws.protocol.soap.ClientMUPipe.process(ClientMUPipe.java:58) 
at com.sun.xml.ws.handler.HandlerPipe.process(HandlerPipe.java:107) 
at com.sun.xml.ws.handler.HandlerPipe.process(HandlerPipe.java:107) 
at com.sun.xml.ws.client.Stub.process(Stub.java:121) 
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:122) 
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:238) 
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:212) 
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:105) 
at $Proxy13.sayGreeting(Unknown Source) 
at com.ca.sample.HelloWorldClient.main(HelloWorldClient.java:12) 

From the command line I'm gettting this error: 
 
Exception in thread "main" java.lang.NoSuchMethodError: javax.xml.soap.MessageFactory.newInstance(Ljava/lang/String;)Ljavax/xml/soap/Me ssageFactory; 
at com.sun.xml.ws.api.SOAPVersion.<init>(SOAPVersion.java:141) 
at com.sun.xml.ws.api.SOAPVersion.<clinit>(SOAPVersion.java:68) 
at com.sun.xml.ws.api.BindingID.<clinit>(BindingID.java:300) 
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parseBinding(RuntimeWSDLParser.jav a:269) 
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parseWSDL(RuntimeWSDLParser.java:1 92) 
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parseWSDL(RuntimeWSDLParser.java:1 54) 
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:99)
at com.sun.xml.ws.wsdl.WSDLContext.<init>(WSDLContext.java:65) 
at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:207)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:165) 
at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:49) 
at javax.xml.ws.Service.<init>(Service.java:57) 
at samples.example1.HelloWorldService.<init>(HelloWorldService.java:40) 
at com.ca.sample.HelloWorldClient.main(HelloWorldClient.java:10)

da...@illsley.org

unread,

Mar 12, 2008, 5:57:45 PM3/12/08

to

Robert, 
Which JDK are you using? 
David

Sourabh Sodani

unread,

Mar 13, 2008, 5:15:33 AM3/13/08

to

When I tried through client, I have got following error:

Caused by: java.lang.NullPointerException 
at javax.xml.bind.ContextFinder.handleClassCastException(ContextFinder.java:95)

at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:213) 
at javax.xml.bind.ContextFinder.find(ContextFinder.java:368) 
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574) 
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522) 
at org.apache.axis2.jaxws.message.databinding.JAXBUtils$4.run(JAXBUtils.java:819) 
at org.apache.axis2.java.security.AccessController.doPrivileged(AccessController.java:130) 
at org.apache.axis2.jaxws.message.databinding.JAXBUtils.JAXBContext_newInstance(JAXBUtils.java:816) 
at org.apache.axis2.jaxws.message.databinding.JAXBUtils.createJAXBContextValue(JAXBUtils.java:313) 
at org.apache.axis2.jaxws.message.databinding.JAXBUtils.getJAXBContext(JAXBUtils.java:146) 
at org.apache.axis2.jaxws.message.databinding.JAXBBlockContext.getJAXBContext(JAXBBlockContext.java:111) 
at org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl._outputFromBO(JAXBBlockImpl.java:199) 
at org.apache.axis2.jaxws.message.impl.BlockImpl.outputTo(BlockImpl.java:331) 
at org.apache.axis2.jaxws.message.impl.BlockImpl.serialize(BlockImpl.java:255) 
at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume(OMSourcedElementImpl.java:573) 
at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:802) 
at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:831) 
at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:274) 
at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:262) 
at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:831) 
at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:456) 
at org.apache.axis2.transport.http.SOAPMessageFormatter.getBytes(SOAPMessageFormatter.java:94) 
at com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.prepareHttpRequestHeaders(SOAPOverHTTPSender.java:1908) 
at com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.sendSOAPRequest(SOAPOverHTTPSender.java:465) 
at com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:366) 
at com.ibm.ws.websvcs.transport.http.HTTPTransportSender.invoke(HTTPTransportSender.java:274) 
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:550) 
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:335) 
at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:299) 
at org.apache.axis2.jaxws.core.controller.AxisInvocationController.execute(AxisInvocationController.java:582)

christop...@mobi.ch

unread,

Mar 13, 2008, 8:58:10 AM3/13/08

to

@rjack: Exception in thread "main" java.lang.NoSuchMethodError: javax.xml.soap.MessageFactory.newInstance(Ljava/lang/String;)Ljavax/xml/soap/Me ssageFactory;: You probably use SAAJ 1.2 instead of 1.3. Please make sure that you have the WS FeaturePack activated in the profile of the used server.

rja...@aol.com

unread,

Mar 13, 2008, 10:41:31 AM3/13/08

to

Folks,

I'm using the JDK supplied with WebSphere... 
java version "1.5.0" 
Java(TM) 2 Runtime Environment, Standard Edition (build pwi32devifx-20071025 (SR6b)) 
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20071007 (JIT enabled) 
J9VM - 20071004_14218_lHdSMR 
JIT - 20070820_1846ifx1_r8 
GC - 200708_10) 
JCL - 20071025 
C:\IBM\WebSphere\AppServer\java\bin 
 
This JDK seems to have JAX-WS 2.0 built in. I'm also using it in my ant script for building the server side application. 
 
I'm using the client jar that comes with WebSphere for the client. This like the problem is happening on the client side. 
 
Robert Jackson

rja...@aol.com

unread,

Mar 13, 2008, 12:53:30 PM3/13/08

to

Folks,

I got my simple example to work as a pojo in the Servlet containter. I installed just the Web Services pack on top of the base. 
 
I had also tried just creating a profile with Web Services only using an install with both packs. That didn’t work either. 
 
So it seems the Webservices and EJB 3.0 service packs are in conflict or I am installing them incorrectly. 
 
If anyone has sucessfully installed both packs and gotten web services to work, please share your procedure. Here's the procedure I followed. 
 
1) Use Factory Install Tool to creat install of: 
WAS 6.1.013 Base 
EJB 3.0 Service Pack 
Webservices Service Pack 
 
2) Installled everything 
3) Created New Web Services Profile-Appsrv02 
4) Augmented Appsrv02 with EJB 3.0 Pack 
 
Regards, 
 
Robert Jackson 
 
Regards, 
 
Robert Jackson

Sourabh Sodani

unread,

Mar 14, 2008, 5:39:43 AM3/14/08

to

Dear Robert, 
 
I tried to install everything from scratch, FYI.. it worked. Am not getting HandleCastException now. 
 
Please note that IF you are using web service and ejb fix packs, please make sure that they are of same version of the application server ie. 6.1.0.13. 
To check versions of different feature packs and the server, a command "versioninfo" could be used. Please run in "<websphere folder>/bin" folder 
 
Following are the recommended helps: 
1. http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/topic/com.ibm.iea.wasfpws_v6/wasfpws/6.1/Overview/WASv61_WSFP_Overview.pdf?dmuid=20070621102004645575 
2. WAS 6.1 Feature Pack for Web Services\win\WEBSV\docs\GettingStarted_en.html (in your Feature Pack installation image) 
 
Thanks, 
Sourabh Sodani.

Randy Schnier

unread,

Mar 14, 2008, 9:37:20 AM3/14/08

to

To the best of my knowledge, the web services feature pack (with updates to bring it up to the 6.1.0.13 level) and EJB 3.0 feature pack (at the 6.1.0.13 level) are not in conflict. However, it is important to install them, and their updates, in a certain order. For example, the GA of the web services feature pack is at 6.1.0.9, while the GA of the EJB 3.0 feature pack is at 6.1.0.13. You need to apply updates to the web service feature pack to get it up to 6.1.0.13 before installing the EJB 3.0 feature pack.

Here's a procedure that's been verified to work:

- Install WAS 6.1 GA
- Install webservices feature pack GA
- Use update installer to install interim fix PK53084
- Use update installer to install WAS 6.1 fixpack 13 and webservices feature pack fixpack 13 *at the same time*
- Install EJB 3.0 feature pack GA

For reference, here are the various URLs to download from:

6.1.0.13 fixpack URL: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24017334
(contains WAS 6.1.0.13, *fixpak for webservice feature pack to bring it up to 6.1.0.13 level*, and webservice fp iFixes)

Feature pack for web services GA URL: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21264563

Feature pack for EJB 3.0 GA URL: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21287579

Ben_

unread,

Mar 14, 2008, 10:03:02 AM3/14/08

to

> To the best of my knowledge, the web services feature pack (with updates
> to bring it up to the 6.1.0.13 level) and EJB 3.0 feature pack (at the
> 6.1.0.13 level) are not in conflict.

I hope they're not because it's clearly documented in their install guide
how to install them concurrently and it would be non-sense to not be able to
develop an application using the two...

rja...@aol.com

unread,

Mar 14, 2008, 1:07:02 PM3/14/08

to

Folks,

Thank you for the install information. I will try it. 
 
What about the Profiles? The create/augment order should not matter right. 
 
Robert

Ben_

unread,

Mar 17, 2008, 5:01:01 AM3/17/08

to

> The create/augment order should not matter right.

Doesn't matter. It's documented.

rja...@aol.com

unread,

Mar 17, 2008, 1:08:35 PM3/17/08

to

Folks,

Following the instructions, I've gotten it to work. Thanks for everybody's help. 
 
I've noticed two things in the process: 
 
1) As a WeSphere Developer on the cutting edge, I've got to get used to reading release notes, install Guides, and Info Center install information. 
 
2) Seems like this a pretty complex install compared to the other App Servers that support JavaEE5. 
 
Again, I do appreciate the help of the IBM folks and others on the forum. 
 
Regards, 
 
Robert Jackson

Ben_

unread,

Mar 17, 2008, 1:29:24 PM3/17/08

to

> 1) As a WeSphere Developer on the cutting edge, I've got to get used to
> reading release notes, install Guides, and Info Center install
> information.

Yes, I know it's boring... But cutting edge or not, RTFM is often a time
saver.

> 2) Seems like this a pretty complex install compared to the other App
> Servers that support JavaEE5.

Feature packs are *additions*. Even with that WAS 6.1 is not Java EE 5
certified.

rja...@aol.com

unread,

Mar 18, 2008, 7:00:02 PM3/18/08

to

Folks,

I got the POJO WEb -> EJB strategy to work on the simeple example. When I tried a more complex data class I got this error: 
 
com.ibm.ws.exception.RuntimeWarning: javax.xml.ws.WebServiceException: WSWS7054E: The Web Services Description Language (WSDL) file could not be generated for the egolf.ListScoringImpl Web service implementation class because of the following error: java.lang.Exception: A WSDL Definition could not be generated for the implementation class: egolf.ListScoringImpl 
 
I can take this same EAR and run it in Weblogic with no problem. "ListScoringImpl" is the POJO in the front end talkng to the EJB. The EAR installs fine, but I get the Error when I try to run it. 
 
1) Has anyone else encountered this problem? The FFDC incident files don't contain any more information. 
 
2) I should be able to create the using all standard Java tools right?

<li>JDK 1.6 (1.5 target)</li>
<li>JAX-WS 2.0</li>
</ul>
 
3) Any ideas how to debug this? I wonder if it's related to Axis? Or if I can use Axis to debug it? 

Robert Jackson

rja...@aol.com

unread,

Mar 19, 2008, 6:05:55 PM3/19/08

to

Folks,

I suspect my application might be having this problem because POJO in the web container that has the web service annotations used classes in the EJB container for parameters and return values. 
 
I'm going to try to open a trouble ticket with IBM.

Randy Schnier

unread,

Mar 20, 2008, 4:57:10 PM3/20/08

to

What classes within the EJB container are you referring to? Classes within the EJB module of the EJB 3.0 bean that the webservice POJO is invoking?

If so, then you'll need to include those classes in the web module where the POJO resides.

rja...@aol.com

unread,

Mar 27, 2008, 4:27:09 PM3/27/08

to

<div class="jive-quote">Guest wrote: 
What classes within the EJB container are you referring to? Classes within the EJB module of the EJB 3.0 bean that the webservice POJO is invoking? 
 
If so, then you'll need to include those classes in the web module where the POJO resides. 
 
rja...@aol.com wrote: 
<div class="jive-quote">Folks,

I suspect my application might be having this problem because POJO in the web container that has the web service annotations used classes in the EJB container for parameters and return values. 
 
I'm going to try to open a trouble ticket with IBM. 
 
Regards,

Robert Jackson</div></div>

Folks,

Thanks to your help and other folks at IBM, I've come very close toa a solution. It turns out the Data classes were not the problem. I did not have my targets set correct for the EJB project and Web Services. Im building with 1.6jdk targeting 1.5 for WebSphere. 
 
1) For EJB I updated it as follows: 
 
<javac srcdir="${src_directory}" 
destdir="${class_file_directory}" 
debug="on" 
deprecation="on" 
optimize="off" 
includes="**" 
source="${source}" 
target="${target}"> 
<classpath refid="project_classpath"/> 
</javac> 
 
source and target are set to 1.5 in the properties file. 
 
2) For Web Service Ant tasks, I'm using sun JAX-WS 2.0 stuff. The wsgen task doesn't allow you to specify a target, but apt task does. 
 
<taskdef name="ws_apt" classname="com.sun.tools.ws.ant.Apt"> 
<classpath refid="jaxws.classpath"/> 
</taskdef> 
 
<ws_apt destdir="${class_file_directory}" 
sourcedestdir="${web_service_gen_source}" 
sourcepath="${src_directory}" debug="true" target="${target}"> 
 
<classpath> 
<path path="${class_file_directory}"/> 
<path refid="project_classpath"/> 
</classpath> 
<source dir="${src_directory}"> 
<include name="${web_service_files}.java"/> 
</source> 
 
</ws_apt> 
 
Now, I'm able to run web services in the servlet container that access 3.0 EJBs in the EJB container. I have one remaining issue. 
 
3) My issue is with this infocenter article: Link:<a class="jive-link-external" href="http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ejbfep.multiplatform.doc/info/ae/ae/rejb_webservice.html"><cl ick here></a> 
 
This article talk about using a servlet to frontend a 3.0 EJB. I would rather use a plain POJO in the servlet container, but this does not work. 
 
Does anyone know how to implement the strategy discussed in this article? Any examples? 
 
Seems like it's problematic getting a servlet to be a web service. I'm not sure I understand what this meeans: You can do this by simply declaring a link between the desired Endpoint name in the Web service deployment descriptor of the EJB module. During deployment and installation of the bean into the Application Server environment, the bean is linked to the specified Web service endpoint

Randy Schnier

unread,

Mar 28, 2008, 1:19:59 PM3/28/08

to

The InfoCenter article should have said "a servlet *or a Java object* as the webservice impl."

The sentence "you can do this by simply declaring a link..." refers to the first paragraph of the article, prior to when the two feature-pack-specific paragraphs were inserted. The "this" being referred to is "...by enabling you to expose an EJB stateless session bean as a Web service."

I'm going to open a problem report on the infocenter to get that fixed. Sorry for any confusion.

Sourabh Sodani

unread,

Apr 7, 2008, 3:40:06 AM4/7/08

to

Folks,

As I was not able to expose a session EJB3 bean as a web service, I used a simple java object defined as web service impl and which looks-up this Session EJB3 bean locally. It worked for me. 
 
Now my requirement is to propogate the transacion object from my simple java object web service imple to EJB3 bean. As this is a simple java object, I am not sure how to obtain a transaction object and begin a transaction. Had it been a servlet or ejb, i could have got the transaction object from either servlet context or ejb context. All help will be appreciated. 
 
Thanks in advance, 
Sourabh Sodani.

da...@illsley.org

unread,

Apr 7, 2008, 7:03:51 AM4/7/08

to

A POJO web services runs in the web container so you should be able get the ServletContext from the WebServiceContext. Though it's about a different JAX-WS impl, you can find details of the relevant (standard) property at [1] 
 
I hope that helps, 
David 
 
[1]https://jax-ws.dev.java.net/articles/MessageContext.html