What is the experience out there regarding the reuse of Business Components,
particularly distributed components? My experience has been that systems
level stuff can be componentized and reused (an example is EJB). However,
when it comes to domain objects, reuse has largely eluded me. I have yet to
completely or even largely reuse a Customer, Partner, Address, Phone, or
other business object. When I refer to reuse, I really mean reuse outside of
a business domain. No points will be awarded to solutions demonstrating
reuse within a tight domain.
I hope this isn't yet another fault in my crack-ridden capabilities. One has
only to look at the work of groups such as Rosetta.net, XML/DTD in general,
EDI, CrossWorlds, and ERP vendors to see that reuse is important but
elusive. As another poster (ok Imre) said, it turns out that there is some
"public" data and some "private" data in systems he's been involved with (he
used it in another context but the idea holds here too). I've found the same
to be true and apparently that's because there is no one definition (view)
of anything. It also turns out that the truly "public" or sharable data is a
small fraction of the "private" data. I usually refer to the difference as
fixed and variable attributes but the problem remains.
So, what are the prospects of reusable business domain components (note that
an application is a component). The current rush to outsource entire
applications makes this reuse even more critical, but I've seen no good
solution to it. Every integration effort I've seen has either duplicated
data in disparate systems or modified the underlying systems so they were no
longer truly decoupled.
===========================================================================
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".
