> Regarding "legacy code", I find that the starting point for CICS customers
> is that they have a body of code which is doing a good job and they have an
> effective development organisation which can keep that code in step with
> the needs of the business. There is usually no "legacy" connotation of
> something having died leaving this code behind.
>
> But this code also needs to be reused to enable new products or new
> channels to market, so these customers want good ways to integrate it into
> other developments. My concept of re-usable components therefore fully
> embraces this sort of wrappering. Wrappering is not a poor cousin of real
> component software.
>
I didn't mean to use the term "legacy" in a condescending way. I used
it as a way of referring to existing code. I am the last person
to advocate rewriting a working system, especially using very
new technology.
That said, the reason I didn't consider wrapping and screen-scraping
was that these technologies reuse entire systems, and not part of
those systems. It is sort of like using netscape as a whole to
show help pages instead of using the HTML painting component of
netscape to embed into your software. While there are no strict
definitions of what makes a component, I feel that when people
talk about building systems using components and then about
reuse in the same breath, they are talking about making parts
of a system being usable in other systems. I don't believe
we have that kind of environment for business components. The
stage is set for visual components and other computer-science
related objects, but not for business components.
I don't expect to be buying entities like invoice beans etc. anytime
in the near future (next 5 years). There may be a market for
process beans, such as tax calculators.
-Sriram
BEA/Weblogic
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
