Well, it is not running in the client JVM, but our developers are able to
run Orion, with Hypersonic DB, in one JVM and the client in another all on
one Win98 box. Orion supports hot deployment, although like others it is
maturing. I find it very impressive and very productive.
With this arrangement, I find I do not need tight integration with my IDE
(which is good, since I do not like them). All I need is a good editor and
a good compiler, and they need not be the same product. Toss in Cygwin for
shell and gnu make, and you've got what I consider to be a very productive
environment.
tim.
> What would be ideal is a light weight, non-distributed EJB server/container
> that runs In The Client JVM!
>
> Since we don't have this today, and since the integrated environments are
> immature ( I have heard this from our customers too...), you might consider
> some design patterns that eliminate EJB'ness during development. In the
> GemStone/J Developer's Guide, the domain objects are not-EJB's. EJB's wrap
> them for deployment. So one could develop, test and debug prior to wrapping
> as beans and deploying to EJB.
>
> There is also a design pattern for this approach on java.success.com. It is
> admittedly incomplete, but it's not a bad start.
>
> -Chris.
>
> > -----Original Message-----
> > From: Humphrey Sheil [SMTP:[EMAIL PROTECTED]]
> > Sent: Tuesday, July 11, 2000 12:57 PM
> > To: [EMAIL PROTECTED]
> > Subject: MI2: Strategies to reduce EJB development time?
===========================================================================
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".
