Jacopo, Thank You for answering/helping me . I searched the old ML and found your posts. Here a short combined snipped:
"the best way to go is to probably implement the part of the configurable stuff that was originally planned but then never completed: add support for storing the configurations The original idea, if I'm not wrong was this: a) add a "store" method to the ProductConfigWrapper (or Worker) to store the configuration in the ProductConfigConfig entity (by assigning a new configId) b) add a new constructor to the ProductConfigWrapper to load a wrapper from a stored configId Then the config id could be added to the quote (but we should discuss a bit more about this, I guess, because is a pretty major change), request, order items etc... Or (probably better) we could use the configId to create a new special type of variant product (something like "variant configuration", associated to the configurable product template and to the given configId) and then use the new productId in quotes, requests, order items etc..." I created an jira issue(OFBIZ-1453) and attached the first draft for a) and b) It works as expected, but reviews, tests and comments are greatly appreciated. Now i like to know where to add the configId field. I think that we should add it to OrderItem, CustRequestItem, QuoteItem, ShoppingListItem. Then we can easily get it (together with productId) and configure product, before adding to cart. May be the other solution you propose is better, but it looks to me a bit tricky/more_complicated way, thats why i donot like it. (i will give one more try to understand it). Any opinions where to save this configId for configurable products? Would interested commiters comment on this also. What could be the accepted way for ofbiz ? Bilgin -- View this message in context: http://www.nabble.com/Enhance-configurable-%28AGGREGATED%29-products-tf4888953.html#a14028019 Sent from the OFBiz - Dev mailing list archive at Nabble.com.
