Hello everyone, I'm using Axis to generate my web services. I'm trying to figure out what Java Data Types I can actually pass in and out of methods. I know I can use Axis's simple data types e.g., arrays, String, Calendar, boolean, etc... But I've also heard I can use any type that adheres to the JavaBean spec. I.e., it has only 1 contructor that accepts no parameters and has only get and set methods. How will a .Net client demarshall this arbitrary JavaBean type on their end? Also, I've also heard I can pass any type I want in Java e.g., a DriverManager, or a JFrame, as long as I create the serialization code. Again, how will a .Net client handle this? Should I just stay in the safety of using Axis's simple built in types? Thanks, Prem Saggar. :roll: [ May 15, 2005: Message edited by: prem saggar ]
Kishore Dandu
Ranch Hand
Joined: Jul 10, 2001
Posts: 1934
posted
0
a search in google with 'SOAP java data type' did yield some interesting urls that might be helpful for you.
Originally posted by prem saggar: How will a .Net client demarshall this arbitrary JavaBean type on their end? Also, I've also heard I can pass any type I want in Java e.g., a DriverManager, or a JFrame, as long as I create the serialization code. Again, how will a .Net client handle this?
You can send and receive javabeans(encoded as complex types) between java and .NET using soap. For example a javabean class like public class Order {
can be sent and received between the java and .net provided you made proper de/serialization configuration in the deployment descriptor. A javabean containing bean array is also possible. Check this example that comes with Axis =>http://cvs.apache.org/viewcvs.cgi/ws-axis/java/samples/userguide/example5/