Hi all,
I have the following architecture of an axis web service with attachments.
The attachments are parameters
of the type DataHandler.
---------------------- -----------------------------------
----------------------------------
| .NET Client | (1) | iPlanet Web Server 6.1| (2)
| BEAWeblogic8.1.5 |
| | ----------> | java Web Service |
------------> | EJB Methods |
| (machineA) | | (machineB) |
|
(machineC) |
---------------------- -----------------------------------
----------------------------------
The call to a method fails in step (2), which is the java RMI call with a
java.ioNotSerializableException of the DataHandler type.
However if I change my architecture to:
---------------------- -----------------------------------
----------------------------------
| .NET Client | (1) | BEAWeblogic8.1.5 | (2)
| BEAWeblogic8.1.5 |
| | ----------> | java Web Service |
------------> | EJB Methods |
| (machineA) | | (machineB) |
|
(machineB) |
---------------------- -----------------------------------
----------------------------------
everything work fine.
Notice that step (2), although in the same machine, is still a remote call
through RMI, as the EJB Methods are available only for remote call.
The key question is: How does Weblogic serialize the DataHandler (which is
not serializable) and how can I do iPlanet make it serialize the same way?
Can somebody explain?
PD: I cannot use the latter aechitecture since the weblogic server is not
available through the Internet whereas the iPlanet is.
Thanks so much,
Sergio.l
--
View this message in context:
http://www.nabble.com/Axis-web-service-architecture-problem-tf3429966.html#a9561702
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
