File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Websphere and the fly likes VAJ4.0 EJB Test Client to verify a WAS4.0 EJB Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "VAJ4.0 EJB Test Client to verify a WAS4.0 EJB" Watch "VAJ4.0 EJB Test Client to verify a WAS4.0 EJB" New topic
Author

VAJ4.0 EJB Test Client to verify a WAS4.0 EJB

Jeff Kinsey
Greenhorn

Joined: Jan 08, 2002
Posts: 19
Kyle,
Regarding daman sidhu�s message: Topic: Kyle?? Tony?? URGENT: not being able to lookup EJB's
I can see why someone could be confused about attempting to run a client in VAJ4.0 attempting to access an EJB in Websphere 4.0. The following redbook describes doing just that (using VAJ to test a deployed EJB). sg24-6144-00 -- EJB Development with VAJ for WebShpere Application Server. In chapter 14 there is a section titled "Testing with the VisualAge EJB test client" that describes using the VAJ EJB test client to test a deployed EJB. Granted this redbook applies to VisualAge for Java Version 3.5.3 and WebSphere Application Server Version 3.5.3.
What one might derive is that you could do the same thing using VAJ4.0 with WAS4.0.
My first question, is there a link that you are aware of that summarizes the version of VAJ, WTE, and the J2EE version / EJB version that is supported?
My second question, what specifically prevents a VAJ4.0 client from testing a WAS4.0 deployed EJB? Would one have the same problem if they were to attempt to run a "client" from WAS3.5 attempting to access an EJB deployed on WAS4.0? Are incompatibilities always a risk when talking EJB's between different versions of appservers?
FYI...
We had similar problems when using a VAJ3.5.2 EJB test client to test the deployment of an EJB after we had patched the server to WAS3.5.4. There was a problem in the EJBMetadata object.
Thanks,
Jeff
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Originally posted by Jeff Kinsey:
Kyle,
Regarding daman sidhu’s message: Topic: Kyle?? Tony?? URGENT: not being able to lookup EJB's
I can see why someone could be confused about attempting to run a client in VAJ4.0 attempting to access an EJB in Websphere 4.0. The following redbook describes doing just that (using VAJ to test a deployed EJB). sg24-6144-00 -- EJB Development with VAJ for WebShpere Application Server. In chapter 14 there is a section titled "Testing with the VisualAge EJB test client" that describes using the VAJ EJB test client to test a deployed EJB. Granted this redbook applies to VisualAge for Java Version 3.5.3 and WebSphere Application Server Version 3.5.3.
What one might derive is that you could do the same thing using VAJ4.0 with WAS4.0.
My first question, is there a link that you are aware of that summarizes the version of VAJ, WTE, and the J2EE version / EJB version that is supported?
My second question, what specifically prevents a VAJ4.0 client from testing a WAS4.0 deployed EJB? Would one have the same problem if they were to attempt to run a "client" from WAS3.5 attempting to access an EJB deployed on WAS4.0? Are incompatibilities always a risk when talking EJB's between different versions of appservers?
FYI...
We had similar problems when using a VAJ3.5.2 EJB test client to test the deployment of an EJB after we had patched the server to WAS3.5.4. There was a problem in the EJBMetadata object.
Thanks,
Jeff

As far as I know there's no one link that crosses all of the products and gives the compatibility across them. As to what keeps you from testing VAJ 4.0 with WAS 4.0 -- WAS 4.0 is an EJB 1.1 server. VAJ 4.0 only supports EJB 1.0 clients. (It will generate EJB 1.1 Server JAR files externally but won't run them). The two spec levels generally aren't interoperable. We changed a TON of things between the two versions(different ORB, etc.). And yes, when the spec changes, incompatibility is going to be par for the course.
Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: VAJ4.0 EJB Test Client to verify a WAS4.0 EJB