We removed auto-scanning recently and we need to update related documentation as well on guidelines to program components and add/enable a plugin into CloudStack. I'll update the wiki accordingly soon
Kelven On 4/4/13 2:50 PM, "Ryan Dietrich" <r...@betterservers.com> wrote: >Ok, it works now. I just had to add: > > <bean id="timeOfDayManagerImpl" >class="com.cloud.test.TimeOfDayManagerImpl"> </bean> > >to client/tomcatconf/componentContext.xml.in > >I'll wait for Kelven to update the xml in 4.1, and then I'll pretty up my >example plugin and update the wiki. > >Thank you all for your assistance. > >-Ryan Dietrich > >On Apr 4, 2013, at 3:00 PM, Alex Huang <alex.hu...@citrix.com> wrote: > >> Ryan, >> >> I believe it's something Kelven added recently. Auto-Scanning via >>@Component has been disabled. There are numerous reasons why >>auto-scanning is bad. Take for example the case of someone extending a >>component with the @Component annotation, they don't want to modify the >>parent class at all but they only want their component to be loaded but >>because of auto-scanning both gets loaded. There are other cases of >>this. A declarative description is much better. >> >> We apologize for the inconvenience this change has caused for you. >>Kelven should be able to give you better instructions on how to add it >>properly in the latest 4.1 branch. >> >> --Alex
