Heh
heh...ditch the proprietary software. Go with Tomcat +
JBoss.
MARK
Mark
Galbreath
Principal
Consultant
Workflow Process
Engineering and Systems Integration
410-703-367 /
800-799-8545
"Never
attribute to malice that which can be adequately explained by
stupidity." ~Hanlon's Razor
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 14, 2003 5:12 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [wsif] EJB questions
I just got the EJB addressbook sample to work. :-) To make it work I had to do a couple of things:
1. The EJB is running on WebSphere, and on the client side I *had* to use IBM's JDK. When I used Sun's JDK I got a naming exception "javax.naming.ServiceUnavailableException: NULL returned when resolving initial reference=NameService". Apparently the RMI/IIOP implementation between these two vendors is not compatible. Anyone else seen this problem before? Is this compatibility issue a known problem?
2. I had to make the AddressBook EJB stub classes available to the WSIF client. I was hoping WSIF would give the same independence SOAP does between client and server for EJB services. In other words, to not have to distribute a jar to clients to use my service. Do I have to distribute my EJB stubs to my WSIF clients, or is there a way around this? Also, If I change the interface, or API of my EJB, won't the stubs change, forcing me to distribute the new ones?
Thanks,
David
