--- In [email protected], Michael Poulin <[EMAIL PROTECTED]> wrote: > > Well, we want not only "the behavior of the existing applications" > but the behavior in SO manner. > > For example, let us take an old Lotus Domino 5 applications server > and a Java application deployed on it. The application performs > very important to us functionality. Now, we TAKE it as a > FUNCTIONALITY, i.e. behavior, wrap it with a Web Service and ... > fail. Why? It is the right behavior, we need it! The reason is a > very small thing not visible at the level of Functionality - Java > on Lotus Domino 5 is single-threaded. > > That is, the legacy application simply cannot work in SOA. Period. > > The example may mislead you toward threading issues.
I might suggest using a different example then, because this implementation issue 1) isn't an SO concern; 2) doesn't necessarily negate the usability of that capability within an SO solution; 3) doesn't categorically indict *all* legacy applications as being ill- suited for SO use, which you seem to be implying (please correct this perception if it is wrong). > However, my > point is that useful behavior of legacy applications is not enough > to reuse it as-in in SOA. What additional characteristics must exist or be added that would make such use acceptable for you? -Rob
