aspose file tools*
The moose likes Websphere and the fly likes is EJB jar server specific ? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "is EJB jar server specific ?" Watch "is EJB jar server specific ?" New topic
Author

is EJB jar server specific ?

vaibhav waghmare
Greenhorn

Joined: May 16, 2001
Posts: 15
are stubs and skels generated for one server compatible to other servers?. Or universaly same for all of them.
------------------
love n regards,
-VaibhaV.


love n regards,<P>-VaibhaV.
Kumarasun Nadar
Greenhorn

Joined: Apr 25, 2001
Posts: 2
No they are not compatible because each vendor such as IBM, WebLogic implement their EJB server in their own way, hence the stub and skeleton generated on one server will be different from other.

[This message has been edited by Kumarasun Nadar (edited May 21, 2001).]


Sun Certified Java Programmer( 94 %)
vaibhav waghmare
Greenhorn

Joined: May 16, 2001
Posts: 15
hi nadar,
first off all thx for your reply. but I would like to know more about the same. What i want to know know is that what makes the jar files different for different servers ? is it because they follow different EJB specifications like 1.0 or 1.1 OR is there some other reason behind this ?
thx in advance , but plz reply me.
Originally posted by Kumarasun Nadar:
No they are not compatible because each vendor such as IBM, WebLogic implement their EJB server in their own way, hence the stub and skeleton generated on one server will be different from other.

[This message has been edited by Kumarasun Nadar (edited May 21, 2001).]


------------------
love n regards,
-VaibhaV.
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1859
vaibhav,
The stub and skelitions generated in the jar files contain the means to connect to & invoke remote calls on the EJB. The whole of EJB API is only consisting of interfaces. There are no implementations. The vendors implement these interfaces in their application server classes in a vendor specific way. Thus you cannot connect from a Client with a Websphere Client jar file to a Weblogic server. I hope you get this.
However note that though the vendor client jar file may change you need not change the Client code. You just have to put another vendors jar file in the classpath and the client works fine.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: is EJB jar server specific ?