Page 1 of 1

Multiple Composite Activity classes ??????

Posted: Mon Feb 13, 2012 8:13 am
by avinash
Hi All,

While I was exploring the workflow concepts in Broadleaf commerce framework, I have come across multiple implementations of CompositActivity class with identical code in different packages (checkout, pricing, and payment), Instead of having a common one in the org.broadleafcommerce.core.workflow package. This seems to me a bit confusing, Is this intentional ?

Thanks,
Avinash

Re: Multiple Composite Activity classes ??????

Posted: Mon Feb 13, 2012 11:28 am
by bpolster
I've added a JIRA defect (BLC-331) to address this. All of these will be deprecated with a common Activity class introduced in 1.6.