The @component's (@repository, @service, @controller) should be configurable by defining an explicit bean by that id in your custom Spring configuration (applicationContext, dispatcher-servlet). You can remove the component scan on the entire package in your custom setup.
In your web.xml you define which Spring configuration files are loaded. On 20 February 2012 16:24, Raminderjeet Singh <[email protected]>wrote: > +1 for extending vanilla extension for shindig. We need to address > extending of rave API in this or similar extension. I am facing problem if > i want to extend rave-core to customize the user model as it does not > repackage rave-core jar. I added NewCustomUser model already to svn but > that does not work. Marlon faced similar problem to extend rave-web. He > tried to replace the PageController to MyPageController but that was not > successful. > > Any ideas on how to make these extensions work. > > Thanks > Raminder > > On Feb 20, 2012, at 7:43 AM, Jasha Joachimsthal wrote: > > > The current vanilla extension only creates a custom portal. There's no > > module to overlay the rave-shindig war if you want to change the database > > jar or Spring configuration. In order to make that more clear I've > > refactored the vanilla extension structure. > > See the attachment in https://issues.apache.org/jira/browse/RAVE-474 > > If nobody objects I'll commit the patch tomorrow morning. > > > > Jasha Joachimsthal > > > > Europe - Amsterdam - Oosteinde 11, 1017 WT Amsterdam - +31(0)20 522 4466 > > US - Boston - 1 Broadway, Cambridge, MA 02142 - +1 877 414 4776 (toll > free) > > > > www.onehippo.com > >
