Hi, I think there is a good reason for not pushing the http stuff in the standard distro, you still have the feature for customization. Another thing about the configuration, everything is already in the feature xml which is used by the configuration admin. But you're still able to override it like you have done :)
Regarding the whiteboard pattern to me it has the same impact as the web-extender since it basically does the same. For standard http service the http feature is sufficient. If you need more just install the war feature. On the other hand it could be discussed what is the benefit of a http service without the extender since most users usually want to start with a full featured web-container (which leads to the war-feature). Regards, Achim > > > Am 15.02.2011 10:43, schrieb [email protected]: >> Hi Christian, >> >> Two points: >> 1/ the http feature should push the configuration file. The features >> descriptor supports the<file/> element. For example, we use it in >> ActiveMQ to push the broker blueprint xml. Anyway the configuration >> file could be in the standard distribution but not on the minimal one > +1 for putting it in the standard distro >> . >> 2/ we have two ways for the Pax Web Extender: we add it in the http >> feature or we add a http-extender feature including the http one + >> the pax web extender. Honestly, I think it could be added to the http >> one. > +1 For moving the whiteboard pattern from the war feature to the http > feature. > > Christian > >
