Oh Sorry Scott, I realize that I didn't understand your previous message :/
My purpose is to cover your dream ;)
I check your analyze and modify my previous patch.
What's your prefer ? I close OFBIZ-4333 or change it to OFBIZ-3894 sub-task
Nicolas
Le 07/07/2011 12:51, Scott Gray a écrit :
Fou
Found it: https://issues.apache.org/jira/browse/OFBIZ-3894
Regards
Scott
On 7/07/2011, at 8:33 PM, Nicolas Malin wrote:
> Ok I create a jira issue.
>
> This refactoring isn't easier. I propose to advanced step by step.
> 1. refactoring entities
> 2. refactoring service
> 3. impact modification
Ok I create a jira issue.
This refactoring isn't easier. I propose to advanced step by step.
1. refactoring entities
2. refactoring service
3. impact modification on exist code
4. create service data migration
5. update screen
Nicolas
Le 06/07/2011 00:58, Scott Gray a écrit :
I'm sure there is
I'm sure there is an open jira issue around somewhere that is relevant to this
discussion.
Regards
Scott
HotWax Media
http://www.hotwaxmedia.com
On 6/07/2011, at 3:13 AM, BJ Freeman wrote:
> I would like to hear why the EmailTemplateSetting was emplemented.
> I am also concerned that the curre
I would like to hear why the EmailTemplateSetting was emplemented.
I am also concerned that the current production systems, with
customization would be effected.
so if this effort can be done so that it is transparent to production
servers, then I don't see a problem.
Nicolas Malin sent the follow
Hi all,
I analyse email notification in OFBiz to set a generic system for a crm
et project managment components.
We have two entity to manage email notification : EmailTemplateSetting
and ProductStoreEmailSetting. In OFBiz history, the first entity used
was ProductStoreEmailSetting, for auto
