Re: Hard Coded Cookie Path

Hi Deepak That largely depends on the use case whether to set cookie path as the root of the web server or not. Yes, generally, it is preferred to keep the cookies separate for the various web apps deployed on the server. In OFBiz case, various web applications are deployed on separate mount

Re: Component and Component Set Dependencies

Thanks Pierre, I'll have a closer look. If it's only labels that can be "easily" fixed. Jacques Le 04/10/2018 à 14:05, Pierre Smits a écrit : Hi Jacques, all, Doing a search in your favourite IDE on 'manufacturing' reveals all references. A cursory review in mine showed a lot of inclusions

Re: Component and Component Set Dependencies

Hi Jacques, all, Doing a search in your favourite IDE on 'manufacturing' reveals all references. A cursory review in mine showed a lot of inclusions of the ManufacturingUiLabels. Best regards, Pierre Smits *Apache Trafodion , Vice President* *Apache Directory

Hard Coded Cookie Path

Hello Folks, During the code walkthrough, I observed that everywhere the cookie path attribute is hardcoded as root '/' using the setPath() method. This is not the correct implementation because if the cookie path is set to the root '/', then the cookie will be sent to all the application under

Re: Component and Component Set Dependencies

Hi Pierre, Without explanation about the exact dependency from Accounting to Manufacturing I'll remove the comments. It would really help to have even just an idea of the kind of this/se dependeny/ies if it's/they are still existing. Then, if they still exist, a OFBIZ-3500 subtask could be