Hi all,
I am using WSIF in a J2EE environment (WAS) for
service invocation.
Our team has defined a number of service modules
and each module
resides in its own EAR. The idea is that any
service module can
make service calls (binding independent) to any
other service module.
One service may call upon several other service
modules to get its job done.
Our class loader policy is set to multiple,
implying that each EAR (service
module) will have its own class loader. All
transfer objects and stubs for service
invocation are kept in the application
EAR.
Since WAS comes with WSIF it is by default in the
path to the
WAS class loader which is a single loader and
parent to the application
class loader.
I am running into ClassCastException issues due
to proxy confusion.
It appears to me that WSIF was not designed to
be used in this manner. When
a call is made from one module to another
module, and the called module
attempts to call yet two other modules
sequencially a ClassCastException occurs
on the second call.
I have much more information on the problem, but
I didn't want post too much.
I would be happy to provide anyone with more
information on my problem.
This has become a real sticking point in our
development effort. Any thoughts
would be very much appreciated.
Thanks,
--Keith
"Attention: This message is intended only for the individual to whom it is
addressed and may contain information that is confidential or privileged. If
you are not the intended recipient, or the employee or person responsible for
delivering it to the intended recipient, you are hereby notified that any
dissemination, distribution, copying or use is strictly prohibited. If you
have received this communication in error, please notify the sender and
destroy or delete this communication immediately."
==============================================================================
