[jira] [Commented] (OFBIZ-4296) JmsTopicListener started twice when distributed-cache-clear is active

[ https://issues.apache.org/jira/browse/OFBIZ-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13117078#comment-13117078 ] Sascha Rodekamp commented on OFBIZ-4296: Hm guys in my opinion the code in the

[jira] [Commented] (OFBIZ-4296) JmsTopicListener started twice when distributed-cache-clear is active

[ https://issues.apache.org/jira/browse/OFBIZ-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13117082#comment-13117082 ] Dimitri Unruh commented on OFBIZ-4296: -- Sascha, I know what you mean and I agree

[jira] [Commented] (OFBIZ-4296) JmsTopicListener started twice when distributed-cache-clear is active

[ https://issues.apache.org/jira/browse/OFBIZ-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13117083#comment-13117083 ] Adrian Crum commented on OFBIZ-4296: Another thing to look at is the bug where the JMS

[jira] [Closed] (OFBIZ-765) Create New Customer fails if done after initial/aborted anonymous checkout

[ https://issues.apache.org/jira/browse/OFBIZ-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp closed OFBIZ-765. - Resolution: Fixed Fix Version/s: SVN trunk Assignee: Sascha Rodekamp Fixed in

[jira] [Closed] (OFBIZ-4000) JMSListener starts in two threads - receive JMS message twice

[ https://issues.apache.org/jira/browse/OFBIZ-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp closed OFBIZ-4000. -- Resolution: Duplicate Fix Version/s: (was: SVN trunk) Assignee: Sascha

Re: REST Servlet

Thanks for your work Adrian, I haven't had a chance to take a look yet unfortunately but have been trying to read a bit more about REST in my spare time. Hopefully soon I feel like I know enough about the topic to be able to contribute to this discussion. Regards Scott On 19/09/2011, at

Re: REST Servlet

Cool - thanks! -Adrian On 9/29/2011 8:43 AM, Scott Gray wrote: Thanks for your work Adrian, I haven't had a chance to take a look yet unfortunately but have been trying to read a bit more about REST in my spare time. Hopefully soon I feel like I know enough about the topic to be able to

[jira] [Created] (OFBIZ-4453) Refactoring JMS Handling

Refactoring JMS Handling Key: OFBIZ-4453 URL: https://issues.apache.org/jira/browse/OFBIZ-4453 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Dimitri Unruh This is the

[jira] [Commented] (OFBIZ-4296) JmsTopicListener started twice when distributed-cache-clear is active

[ https://issues.apache.org/jira/browse/OFBIZ-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13117102#comment-13117102 ] Dimitri Unruh commented on OFBIZ-4296: -- Let's start do diskuss this things here

[jira] [Created] (OFBIZ-4454) Enable/Disable JMS

Enable/Disable JMS -- Key: OFBIZ-4454 URL: https://issues.apache.org/jira/browse/OFBIZ-4454 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Dimitri Unruh See OFBIZ-4296: Adrian

[jira] [Created] (OFBIZ-4455) Prevent a Singelton creation with double lock

Prevent a Singelton creation with double lock -- Key: OFBIZ-4455 URL: https://issues.apache.org/jira/browse/OFBIZ-4455 Project: OFBiz Issue Type: Sub-task Components: framework

[jira] [Commented] (OFBIZ-4446) OnePageCheckout creates new billing/shipping phone number even if user selects the default values

[ https://issues.apache.org/jira/browse/OFBIZ-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13117117#comment-13117117 ] Sascha Rodekamp commented on OFBIZ-4446: Hi Kiran i could reproduce the error, but

[jira] [Closed] (OFBIZ-4449) phone number field length on OnePageCheckout.ftl don't match that of editcontactmech.ftl

[ https://issues.apache.org/jira/browse/OFBIZ-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp closed OFBIZ-4449. -- Resolution: Fixed Fix Version/s: SVN trunk Hi Kiran, thanks for reporting. i fixed that

[jira] [Commented] (OFBIZ-4453) Refactoring JMS Handling

[ https://issues.apache.org/jira/browse/OFBIZ-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13117143#comment-13117143 ] Martin Kreidenweis commented on OFBIZ-4453: --- I'd like to make two remarks: I

[jira] [Updated] (OFBIZ-4453) Refactoring JMS Handling

[ https://issues.apache.org/jira/browse/OFBIZ-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Kreidenweis updated OFBIZ-4453: -- Attachment: JMS-keep-connection.patch We already made some code changes to reuse the

Re: discussion: party preference and user(loginId) preference

Thanks BJ for the comment. In order to keep the framework (login preference) and party preference separated i would like to suggest to either: 1. extend the UserPreference entity and adding the field partyId to the key, override the related services and make the PartyId mandatory. 2. copy the

Re: discussion: party preference and user(loginId) preference

I would prefer #2. The distinction between users and parties is already blurred enough, and relating User Preferences to a party will just make that worse. -Adrian On 9/29/2011 11:11 AM, Hans Bakker wrote: Thanks BJ for the comment. In order to keep the framework (login preference) and

Re: discussion: party preference and user(loginId) preference

I agree with Adrian. But then we will not have the possibility to have preferences by logins, only parties. Not sure it's a big deal, maybe should be considered? (Why it was done that way...?) Jacques From: Adrian Crum adrian.c...@sandglass-software.com I would prefer #2. The distinction

End of month : Main New features

Please devs, don't forget to add your changes in Main New features with shorts explanations https://cwiki.apache.org/confluence/display/OFBIZ/Main+New+Features Thanks Jacques

Re: discussion: party preference and user(loginId) preference

I also agree with Adrian, on beautyfull world PartyPreference just contains only functionnal preference while UserPreference embeds navigation information (or useful information) to work with OFBiz IHM Nicolas Jacques Le Roux a écrit : I agree with Adrian. But then we will not have the

Re: discussion: party preference and user(loginId) preference

#3. rename to Preferences with a TypeID added. However use the logniID to find the Preference with the type Party. since we now have the login tied to the partryID already. Hans Bakker sent the following on 9/29/2011 3:11 AM: Thanks BJ for the comment. In order to keep the framework (login

Re: discussion: party preference and user(loginId) preference

I like to see the item model used in orders and agreements. this lets preferences to expand in the futures without redesign Nicolas Malin sent the following on 9/29/2011 4:21 AM: I also agree with Adrian, on beautyfull world PartyPreference just contains only functionnal preference while

Re: discussion: party preference and user(loginId) preference

guess I should address you orginal requirement. you would link to preference from party or login with either Pary or user type. So add the preference ID to party. then have a preference Item with one to many to preference BJ Freeman sent the following on 9/29/2011 4:54 AM: #3. rename to

Re: discussion: party preference and user(loginId) preference

Hi BJ, Is an interesting solution, however only one problem...how about a party without a userlogin? Regards,Hans On Thu, 2011-09-29 at 05:53 -0700, BJ Freeman wrote: guess I should address you orginal requirement. you would link to preference from party or login with either Pary or user

Re: discussion: party preference and user(loginId) preference

sorry if I was not clear add preferenceID to Party, partyGroup, and change the userlogin to preferenceID. this is a one to one. So each one can have preference independent and specific to that level. So the Party Group would be first, then add the Party that is Associated then lookup the userlogin

[jira] [Commented] (OFBIZ-4449) phone number field length on OnePageCheckout.ftl don't match that of editcontactmech.ftl

[ https://issues.apache.org/jira/browse/OFBIZ-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13117447#comment-13117447 ] Kiran Gawde commented on OFBIZ-4449: Hello Sascha, No problem. I reported it as bug

[jira] [Created] (OFBIZ-4456) Creating purchase order from New Order

Creating purchase order from New Order -- Key: OFBIZ-4456 URL: https://issues.apache.org/jira/browse/OFBIZ-4456 Project: OFBiz Issue Type: Task Affects Versions: Release 10.04 Reporter: