I interviewed a guy last month who, as a consultant, had implemented an XA
2pc for PeopleSoft a few years back. In his words, the transactions
sometimes took 6 hours to commit or rollback, but it was nevertheless
working through standard interfaces.
I wouldn't give up on the feasibility of "correct" integration for small
projects. I've got an employee writing a custom JDBC driver to do some
integration through the "front door". It's not nearly as hard as we
expected (working prototype in 2 weeks, months early).
David
Tom Valesky <[EMAIL PROTECTED]> on 04/23/99 11:18:20 AM
Please respond to A mailing list for Enterprise JavaBeans development
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: David Rauschenbach/ZLAND)
Subject Re: EJB and native methods; also, restrictions
: in spec
I suppose so. I'm not recommending the idea (and certainly not for beans
that
are intended to be redistributed). On the other hand, I'm mainly a systems
integrator, so I'm naturally curious about how to integrate systems. :-) In
my
experience, every MIS shop has at least one legacy system (and by "legacy",
I don't mean "relational database"; I mean "an aging, obsolescent system
that may not even be supported anymore by the original vendor, yet must
be made to work within your system for business reasons"). Some examples:
a Sharebase 8000 relational database system, or a Metaphor visual
query builder, or the gateway program that runs on a MicroVax way
in the back of the machine room that nobody touches except to reboot
the box once a week (all 100% real systems that I've had to deal with
in the past). Sometimes your continued success with a client comes
down to, "Can you make your system work with my weird old box?"
===========================================================================
Tom Valesky -- [EMAIL PROTECTED]
http://www.patriot.net/users/tvalesky
-----Original Message-----
From: David Rauschenbach <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, April 23, 1999 1:06 PM
Subject: Re: EJB and native methods; also, restrictions in spec
>>> Can an EJBean have native methods?
>
>Interesting "evil thought". Would you then want to bundle DLL's in a JAR?
>And if so, would the EJB server then need to track shared usage of
>registered DLL's for a given EJB, like Windows uninstall?
>
>David
>
>==========================================================================
=
>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".
===========================================================================
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".
===========================================================================
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".
