Re: [discussion] With plugins, is hot-deploy necessary?

My preference is to remove the hot-deploy folder. As a side note, the name "hot-deploy" has always been misleading because most of the components actually require a system restart. Jacopo On Sat, Mar 4, 2017 at 4:48 AM, Wai wrote: > This discussion is in reference to... >

Re: [discussion] With plugins, is hot-deploy necessary?

I imagine it would be fairly simple to add another top level folder with the same functionality as plugins if desired. Easy enough that we don't have to include it out of the box. On 5/03/2017 03:42, "Wai" wrote: > Either way is fine for me. I'll name my components

Re: Use OkHttp?

What is wrong with Apache Commons HttpClient? Wouldn't it be easier to contact a fellow ASF contributor when we experience issues with the 3rd party solution? Best regards, Pierre Smits ORRTIZ.COM OFBiz based solutions & services OFBiz Extensions Marketplace

Re: [discussion] With plugins, is hot-deploy necessary?

Either way is fine for me. I'll name my components directories in 'plugins' with a specific prefix. Thanks -- View this message in context: http://ofbiz.135035.n4.nabble.com/discussion-With-plugins-is-hot-deploy-necessary-tp4702976p4702995.html Sent from the OFBiz - Dev mailing list archive at

Re: Should be keep the multitenant feature even if broken?

I dig into the issue and proposed one solution in the same Jira ticket OFBIZ-9230. Please see if it looks fine or may be we can proceed in that direction. Quick Reference from ticket: "In the template/FTL context or in the screen context whenever we get the delegator as null we can use this

Use OkHttp?

Hi, This is minor and more for sharing. While reading http://blog.jevsejev.io/2017/02/19/java-libraries-you-cannot-miss-in-2017/ I spotted OkHttp and thought about OFBIZ-4430 And I found this https://github.com/google/agera/issues/22#issuecomment-212353096 So I wonder if we should not use

Re: [discussion] With plugins, is hot-deploy necessary?

I tend to agree with Jacques in this case. The behavior of /plugins is identical to the behavior of /hot-deploy. You can put your component here or there without a problem. So given that /plugins achieves more, which is automatic control of plugins through the plugins API, I think we should prefer