How does "hot-depoly" works?

[Oliver Michalke]

Hello community

I've got some questions about the OFBiz hot-deploy functionality. I had
a look at the Apache OFBiz Cookbook and also searched the Web for
information about it. Now I got something from 2008 and 2013 with
completly different content. So I guess here is the best place to ask
for the current implementation of this feature.

So we guess we can use the hot-deploy folder to throw in an
OFBiz-Component when OFBiz already started. We compile it with "ant
build", OFBiz detects and loads it correctly (if the component is
properly build) and we can instantly call it and see it in the
backoffice with all it's services and functionality. The question would
be, if we can change and maybe even delete the component without
restarting OFBiz?
Another issue would be the on the fly reloading of the compiled
.class-files. Is it possible to refactore our component (Or even
replacing a .jar-File in it) without restarting OFBiz?

Thank you in advance,

Oliver Michalke

[Adrian Crum-3]

The hot-deploy folder is not an accurate description of what it
contains, so your confusion is understandable.

It is true you can drop your custom components in the hot-deploy folder
and OFBiz will recognize them and include them the next time it starts.

If you change or delete a hot-deploy component, the change will not be
recognized until OFBiz is restarted.

OFBiz does not support run-time reloading of components. There are too
many inter-dependencies to make a feature like that reliable.

Adrian Crum
Sandglass Software
www.sandglass-software.com

On 9/5/2014 11:57 AM, Oliver Michalke wrote:

>
> Hello community
>
> I've got some questions about the OFBiz hot-deploy functionality. I had
> a look at the Apache OFBiz Cookbook and also searched the Web for
> information about it. Now I got something from 2008 and 2013 with
> completly different content. So I guess here is the best place to ask
> for the current implementation of this feature.
>
> So we guess we can use the hot-deploy folder to throw in an
> OFBiz-Component when OFBiz already started. We compile it with "ant
> build", OFBiz detects and loads it correctly (if the component is
> properly build) and we can instantly call it and see it in the
> backoffice with all it's services and functionality. The question would
> be, if we can change and maybe even delete the component without
> restarting OFBiz?
> Another issue would be the on the fly reloading of the compiled
> .class-files. Is it possible to refactore our component (Or even
> replacing a .jar-File in it) without restarting OFBiz?
>
> Thank you in advance,
>
> Oliver Michalke
>
>
>
>

[Gavin Mabie-2]

Hot-deploy  in Ofbiz is not the conventional "hot-deploy" that you might be
familiar with, i.e. deployment that does not require server restart.  You
are still required to restart Ofbiz before any apps are mounted.Have a look
at the ComponentContainer class - you can call reload containers - but you
will have to write some additional code!

Gavin



On Fri, Sep 5, 2014 at 12:57 PM, Oliver Michalke <[hidden email]> wrote:

>
> Hello community
>
> I've got some questions about the OFBiz hot-deploy functionality. I had
> a look at the Apache OFBiz Cookbook and also searched the Web for
> information about it. Now I got something from 2008 and 2013 with
> completly different content. So I guess here is the best place to ask
> for the current implementation of this feature.
>
> So we guess we can use the hot-deploy folder to throw in an
> OFBiz-Component when OFBiz already started. We compile it with "ant
> build", OFBiz detects and loads it correctly (if the component is
> properly build) and we can instantly call it and see it in the
> backoffice with all it's services and functionality. The question would
> be, if we can change and maybe even delete the component without
> restarting OFBiz?
> Another issue would be the on the fly reloading of the compiled
> .class-files. Is it possible to refactore our component (Or even
> replacing a .jar-File in it) without restarting OFBiz?
>
> Thank you in advance,
>
> Oliver Michalke
>
>
>
>
>