We accomplished the same "optimization" by adding a few simple dependencies to our
make files. It
then works with any IDE, assuming you can control the IDE from the command line.
Robert Krueger wrote:
"...with lots of EJBs this gets very inefficient with orion because a code change in
one EJB
implementation (not even the interface) requires you to redeploy the entire
application which
(even with jikes) takes a while."
I cannot think of any reason why a good component architecture would require
rebuilding every
component if part of one changes. Is there no way in Orion to redeploy only one bean?
What if I
wanted to add a new bean?
--Victor Langelo
Bernhard Merkle wrote:
> >Here are some of the things I've been looking into to mitigate the problem.
> >...
>
> Hi Humprhey,
>
> we had the same observations. Hotdeyploy etc, does help, however most of the
>development
> time is often spent in unecessary build steps because the build envrionment of
>ejb-containers
> is not optimal (often only *.bat files or scripts !!!)
>
> <vendor>
> therefore we have integrated an "opti-build" step in our ArcStyler EJB development
>suite.
> have a look at http://www.arcstyler.com
> In this tool suite you can generate EJBeans for different servers. We have
> optimized the build step so you only need to rebuild the necessary parts of a bean.
> This speeds up things enormously. ;-)
> </vendor>
>
> hope this helps,
> best regards,
> Berni.
>
> ===========================================================================
> 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".