Details

  • User impact:
    Medium
  • Similar Issues:
    None

Description

Users can no longer set a default pooling-profile in a seda-model

Issue Links

Activity

Hide
Daniel Feist added a comment -

We discussed with when MULE-3171 was logged, but didn't manage to get it into 2.0.0.

In 1.4 the default pooling profile was configured as a global default rather than on the seda model according to MULE-3171.

I'm not sure that seda model is the right place to put this default given that this is not a seda-service default and services in the seda model can use components of any type java/script/bpm. I not sure where else we can put component defaults though, we may have script/bpm etc. component defaults that we want to configure somewhere also.

Having said that entry-point-resolvers are component specific but we currently set those on the seda model..

Show
Daniel Feist added a comment - We discussed with when MULE-3171 was logged, but didn't manage to get it into 2.0.0. In 1.4 the default pooling profile was configured as a global default rather than on the seda model according to MULE-3171. I'm not sure that seda model is the right place to put this default given that this is not a seda-service default and services in the seda model can use components of any type java/script/bpm. I not sure where else we can put component defaults though, we may have script/bpm etc. component defaults that we want to configure somewhere also. Having said that entry-point-resolvers are component specific but we currently set those on the seda model..

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated: