|
David
I will look into the issue #1
As regards #2, you are right - we haven't yet been
able to create a stubless EJB invoker the same as we have for SOAP. We would
like to create a pure RMI-IIOP provider, but since the EJB provider
works, its never crept up the todo list high
enough for anyone to do it.
Paul
----- Original Message -----
Sent: Friday, February 14, 2003 10:11
PM
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
|
