>-----Original Message----- >From: Jasha Joachimsthal [mailto:[email protected]] >Sent: Monday, February 20, 2012 8:37 AM >To: [email protected] >Subject: Re: Extending the vanilla extension (RAVE-474) > >On 20 February 2012 14:27, Franklin, Matthew B. <[email protected]> >wrote: > >> >-----Original Message----- >> >From: Jasha Joachimsthal [mailto:[email protected]] >> >Sent: Monday, February 20, 2012 7:43 AM >> >To: [email protected] >> >Subject: Extending the vanilla extension (RAVE-474) >> > >> >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. >> >> +1. >> >> We should also start talking about the best way to handle splitting out >> the Rave custom components of the rave-shindig module. Right now, we >have >> our code in the overlay, which isn't very scalable. I think we need to >> look at either splitting out the rave-shindig into two projects or >> splitting rave-opensocial-provider into server & client sub-projects. >> > >That can be done when Shindig is split up into more modules than their >current war.
The problem that we have right now is that we don't expose any of the things we have done for rave-shindig as something that an implementer can depend on for compile time. If I want to extend the OAuth stuff for example, I can't just build on the rave impls; I have to provide my own Shindig impl and wire it in.
