Multiple Composite Activity classes ??????
Posted: Mon Feb 13, 2012 8:13 am
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
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