• Post Reply Bookmark Topic Watch Topic
  • New Topic


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

I would like some advice on a solution architecture I will be using. This is a brief description of the physical architecture:

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. I have the option to use JAX-RPC, SOAP directly or with a web services layer on top. I haven't completely decided this.

The client will a UI navigation flow as the user moves through the use case, but it will handle simple input validation and write and read data from xml objects on each service call.

The server will be made up of the following layers:

service - session facade class exposing stateless service interface.

business controller - handles any reusable business processing on the DTOs coming from the client or datasource.

domain managers - normally handles data access from database (CRUD stuff). In my case I will be calling services on an external system via sockets. Unfortunately, data is returned in a native text format, so I decided to handle this using XML technology. So domain manager will call data access layer to transform DTOs to xml objects. I will use custom xslt scripts to extract data from xml objects to generate native requests to the external system and vice versa on return.

The transactions takes place inside the external system. I check the response messages for success, otherwise throw any exceptions reported in the response.

Please give me your thoughts and suggestions on this solution architecture and fill in the blanks as requested.

Many Thanks
Cleuton Sampaio
Ranch Hand
Posts: 181
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I have developed a similar architecture last year. The only difference is the client was a full .NET application, not a compact application.

I recommend you use JAX-RPC and start creating the XML schema and the WSDL of your services.

Follow the WSDL-to-Java approach. This will guarantee the stability of your interface and avoid problems between .NET and Java interpretations.

But be aware of the response time. I don�t know what are your Non-functional requirements, but JAX-RPC implies in heavy XML processing. You said you will use XSL to transform messages, but you should consider not use the Web Services types (generated from the WSDL) inside your core endpoint, so you should map the external types into an internal model, and using XSL for this is very complicated.
my overalls have superpowers - they repel people who think fashion is important. Tiny ad:
the new thread boost feature brings a LOT of attention to your favorite threads
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!