in revision 4036 for jbpm 3.2.6 you changed the names of services in org.jbpm.svc.Services
from an List to a collection. What's the reason for it?
I think the list is a better choice, since closing the services then occur in the order
like in XML, and for some services this can be relevant (e.g. closing the
PersistenceService may cause problems if "later" services need something from
the database during closing)...
And efficiency isn't a big argument in this 5 services list I think... Not allowing
duplicates could be introduced by a simple check in the addService...
Or what do you think?
View the original post :
Reply to the post :