• Post Reply Bookmark Topic Watch Topic
  • New Topic

complex types

 
Aftab Hussain
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Please help!!

I have a .net client device using compact framework on Win CE 4.2 which will talk to a websphere servlet to call a stateless service. The service call will be made over an RF network with good bandwidth. I'm planning on passing complex types i.e. DTOs - these are just lightweight objects(POJOs) which represent my domain model. I want to avoid using simple types as this would
mean further rework to add additional parameters to the service calls if the business needs change.

My understanding is web services map parameters to the lowest common denominator to easily map types from one language to another (in my case a C# client talking to a Java server). With all this in my mind what solution would be best for me??? I think I have the following options:

1. Web services running over SOAP or JAX-RPC. Maybe Apache Axis here.
2. Just use SOAP or JAX-RPC directly. What open source solutions are availabe here?

Thanks
Aftab
 
Bear Bibeault
Author and ninkuma
Marshal
Posts: 65524
105
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"Aftab786",

There aren't many rules that you need to worry about here on the Ranch, but one that we take very seriously regards the use of proper names. Please take a look at the JavaRanch Naming Policy and adjust your display name to match it.

In particular, your display name must be a first and a last name separated by a space character, and must not be obviously fictitious.

Thanks!
bear
JavaRanch Sheriff
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13078
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm planning on passing complex types i.e. DTOs - these are just lightweight objects(POJOs) which represent my domain model. I want to avoid using simple types as this would


Unless your data is exceptionally complex, why not use Maps? That way you avoid Java language dependency.

I did this survey article on XML-RPC and JAX-RCP recently.
Since you client may be resource limited, XML-RPC looks like the way to go as being simpler than full blown SOAP.
Here is the home of the XML-RPC spec. Note the support for Maps and nested Maps.

I see people backing off from the complex monster that SOAP has become and thinking in terms of XML-RPC or REST.
Bill
 
Rick Alsopp
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Be careful with the Apache Axis solution you mentioned here... The WebSphere doc's explicitly tell you that using the Apache Axis runtime should be for testing purposes only - it also tells you to use the IBM runtime for production...

R A
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!