Agreed.
For me, it makes sense to facade your loosely-typed implementation
with a strongly-typed interface for your public consumers. That way
you get the best of both worlds: flexibility and agility in your
implementation, and stability and simplicity at the edges.
/Ade
On 20 Nov 2008, at 08:17, Drone42 wrote:
Hi Ade,
Exactly; the expectation for a strongly typed interface. I have worked
heavily with IDL before and WSDL for web services and that leaves
little
freedom. I need to warp my brain.
I like the flexible interface, even though I will most like in my
design
introduce 'gates' at key points providing strongly typed interfaces to
ensure consistency in the flow (and satisfy my need for control...).
Thanks,
Gert.
Adrian Trenaman-2 wrote:
Hi there Drone42,
Good point! JBI does borrow some things from WSDL - like the message
exchange paradigms (MEPs), and the concept that a service is a
collection of endpoints. But that's about as far as it goes: when you
create services on the bus you identify them using a WSDL-like
service
name, but you don't have to define any WSDL. All your service does is
receive a MessageExchange, which contain your message payload as XML,
and potentially a number of MIME attachments. So, you don't need to
define a WSDL "interface" for your service.
This took a while for me to get used to - I'm used to strongly typed
services with well-defined interfaces. In ServiceMix, however,
service
definition is loosely typed: a service on the NMR just listens to
MessageExchanges.
That said, if you do want to write a strongly-typed service with
WSDL,
then use the cxf-se component do deploy a JAX-WS service
implementation onto the NMR. This works for both WSDL-first and Code-
first approaches, and allows you to write pure Java code and not
worry
about MessageExchanges. You can then hook up the cxf-bc component to
add a binding to connect that service to the outside world.
Best,
Ade
On 19 Nov 2008, at 22:57, Drone42 wrote:
Reading the JBI and the service mix documentation there is a lot of
talk
about MEPs and service definitions in WSDL. Maybe this has put me on
a wrong
track, because when I first wanted to create a SU, I expected to
start with
the WSDL definition of the service and messages to be exchanged.
And since I have been confused in regards to where the format of the
messages exchanged are defined.
Looking at all the tutorials and example code, I have namely yet to
run into
a WSDL file. Where are they? (I feel a bit like X-files; I know they
must be
out there, but where...).
--
View this message in context:
http://www.nabble.com/Conceptual-problem--Where-is-all-the-WSDL--tp20591446p20591446.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
---
Adrian Trenaman, Consultant Fellow, PS - Opensource Center of
Competence
Progress Software Corp
Shelbourne Road, Dublin 4, Ireland
---
+353-1-637-2659 (Office)
+353-1-637-2882 (Fax)
+353-86-6051026 (Mobile)
adrian.trenaman (Skype)
----
Blog: http://trenaman.blogspot.com
--
View this message in context:
http://www.nabble.com/Conceptual-problem--Where-is-all-the-WSDL--tp20591446p20596808.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
---
Adrian Trenaman, Consultant Fellow, PS - Opensource Center of Competence
Progress Software Corp
Shelbourne Road, Dublin 4, Ireland
---
+353-1-637-2659 (Office)
+353-1-637-2882 (Fax)
+353-86-6051026 (Mobile)
adrian.trenaman (Skype)
----
Blog: http://trenaman.blogspot.com
