HttpConfigurationMBean defines some method which are implemented by HttpConfiguration. As I understand, these methods are used by Jetty. There is also one attribute "component.properties" in the code but I do not see it in the package structure. What is its use?. Why HttpConfigurationMBean has suffix MBean. It does not extends any special interface? is is possible for you to give a brief description about this class?
Regards, Amit gnodet wrote: > > This is up to you. > For example, the WSNotification component activates > two endpoints when the component is started. > The service name and endpoint names can not be changed in > this case. If you need to be able to configure them, you > should use a configuration mbean (take a look at servicemix-jms > and servicemix-http code). > > On 3/22/07, aharsola <[EMAIL PROTECTED]> wrote: >> >> >> Thanks. >> >> What do you mean exactly ? When using a standard JBI component, >> you don't have to configure anything in the servicemix.xml configuration >> file. >> ==> What I mean is where do I specify service name and endpoint >> information? >> In the same jbi.xml where we specify Bootstrap and component class? >> >> Regards, >> Amit >> >> >> >> gnodet wrote: >> > >> > On 3/22/07, aharsola <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> Hi, >> >> >> >> I want to write a SE or BC that would not have SUs. Component would >> >> provide >> >> fixed set of services i.e. it would have a service and endpoint >> activated >> >> when it is installed. How do I write such component? >> > >> > >> > You can use servicemix-common do to that easily. >> > You just have to override one method to remove the ServiceUnitManager >> > creation. See the tutorials and archetypes on the web site. >> > >> > Is there a way to >> >> provide servicemix.xml during component installation? >> > >> > >> > What do you mean exactly ? When using a standard JBI component, >> > you don't have to configure anything in the servicemix.xml >> configuration >> > file. >> > >> > Regards, >> >> Amit >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Writing-a-SE-or-BC-component-that-would-not-be-a-container-component-tf3446225s12049.html#a9610491 >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> > -- >> > Cheers, >> > Guillaume Nodet >> > ------------------------ >> > Architect, LogicBlaze (http://www.logicblaze.com/) >> > Blog: http://gnodet.blogspot.com/ >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Writing-a-SE-or-BC-component-that-would-not-be-a-container-component-tf3446225s12049.html#a9610695 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Architect, LogicBlaze (http://www.logicblaze.com/) > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/Writing-a-SE-or-BC-component-that-would-not-be-a-container-component-tf3446225s12049.html#a9611662 Sent from the ServiceMix - User mailing list archive at Nabble.com.
