> I'd prefer for my clients to generate their code from the wsdl and get
strongly typed stubs, with correct data structures and correct number of
> parameters for each call.  I don't have control over the clients to this
system, only the server side.  Client side will probably mostly be .NET but
> could be anything.

Tim, i think you're missing the whole point here. If what you need is a
strongly typed solution, where your clients use the wsdl to compile stubs
and with non-Java clients, why attemp to use a messaging-oriented technology
?

> That would work, but it would lead to a weakly typed solution.
>

The weak-typing is actually the benefit of messaging ... you can add
services on the server-side without breaking your interface to the outside
world. If I were you, I'd design (devise) avery specific message protocol &
give my clients a few DTDs that describe the message scheme.

>
> That, plus I have hundreds of classes full of transactions to expose and
don't fancy maintaining a big if statement for which one to call. :-)
>

As for the big if statement ... Again, if I were you, I'd have my central
message handler dynamically instantiate the class that is needed to
process each message.

My current project is actually using such an architecture ( if that can be
considered an architecture and not a 'dirty solution' .... ) and I've added
services to the system constantly without even restarting the server ... If
you start developing with this .. message-orientation frame of mind, I bet
you'll never want to go back to RPC-like web services.

Well ,,, that didn't help, but I certainly hope it was an interesting read
;]

Angel
O:]








-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
jibx-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jibx-users

Reply via email to