Flex & ESB ( SOA )

Question

Hi,
I'm new in Flex technologies & java Technologies, but i
liked too much the way it's resolved the communication with de Java
Services & my Pojos.
The question is:
My Flex Client , define a .As…. comunicate via LCDS
with the server to an Java-Assembler-Service, who recibed the
petition …..¿¿¿¿ the Java-Assembler
comunicate with de ESB ( Mule ) for the especific services???...
the ESB route to the services-server the petition ( jBoss )…
a java service attend the petition
How i should communicate the Assembler with de Services??? i
want to keep the non-XML-parsing-model..
Thanks! and Happy new Year!!
Office-Mail

Answer 1

Chanyoung,
I think it depends how you look "SOA". In my point of view, both j2ee ,
corba, .NET and Tuxedo are SOA bricks. The SOA infrastructure can bring a
uniform "service" vision by combining all these backbone technologies
together. The combination here definitely means part of the integration
capability. So from my point of view, constructing a SOA IT infrastructure
doesn't means we ignore the traditional technology purposely.
Wayne
<chanyoung lee> wrote in message news:[email protected]..
I Now the tuxedo's update feature to SOA like XML and metadata repository
and WTC etc.
We can apporoach SOA in two way,
One is integration with SOA Based Web/WAS Service and adaptor in ESB, in
that point tuxedo is good.
the other is point of reusabilty of service
as i know TP Monitor is written C,C++, CORBA
So C language feature and C++, Corba have limitation of reusabilty(not
code reusability, i mean service reusability) although some are object
based designed.
They are hard coded in application and it lacks of reusable architecure
and granularity of component and in data sturcture point of view not fit
SOA.
My opion is TP Monitor itself is not fit for SOA but it can integrated
with SOA based Web/WAS or ESB.
What is your opinion?