On 29 December 2012 16:33, Nolan Darilek <[email protected]> wrote:
> On 12/29/2012 08:23 AM, Jasha Joachimsthal wrote: > >> Shindig expects to run under the root context, Wookie under /wookie, >> Rave portal under /portal and the Rave demo gadgets /under demogadgets. >> > > By "expects," do you mean regardless of whether I run it under Cargo? So > if I deploy these wars to production, is it essential that I mimic this > context structure (less demogadgets, of course.) > You can change the context of the Rave portal and Wookie, but Shindig needs to run under the root context (/). When you deploy Rave on a server, don't forget to change the properties files [1] for correct references between the three webapps. [1] http://rave.apache.org/documentation/host-configuration.html > > Thanks. > > > > On 29 December 2012 15:05, Nolan Darilek <[email protected]> wrote: >> >> Cool, thanks for the fast response. >>> >>> I guess what I'm asking is, the vanilla project seems to create two wars >>> then merge them with Maven's overlay functionality. Am I right? Why is >>> there a rake-vanilla-extension-shindig project that only provides a >>> web.xml >>> file? What do I lose if, for my own portal project, I eliminate that >>> project and flatten the structure, simply depending on the Shindig >>> snapshot >>> war? In my test project, I'd like to have Rave and Shindig in the same >>> container under the root context if possible, then deploy functionality >>> as >>> separate OpenSocial apps running in different containers, or maybe even >>> written in different languages. >>> >>> Thanks. >>> >>> >>> >>> On 12/29/2012 07:09 AM, Jasha Joachimsthal wrote: >>> >>> Hi Nolan, >>>> >>>> the vanilla extension hasn't been updated for a while. I just updated >>>> the >>>> project to work with the latest 0.19 code. Sorry for this inconvenience. >>>> The idea behind the vanilla extension is to show how you can overlay the >>>> regular portal and override the default services, in this case the >>>> UserService. >>>> Shindig has its own war to separate the portal from the actual >>>> OpenSocial >>>> container. Besides Shindig we also bundle Wookie for rendering W3C >>>> widgets. >>>> In your local setup Shindig, Wookie and the Rave portal will run in the >>>> same Tomcat instance, but in production it is possible to separate these >>>> wars over multiple machines. In [1] you can find the architectural >>>> diagram >>>> of the several components. >>>> >>>> [1] >>>> http://rave.apache.org/****documentation/components.html<http://rave.apache.org/**documentation/components.html> >>>> <**http://rave.apache.org/**documentation/components.html<http://rave.apache.org/documentation/components.html> >>>> > >>>> >>>> >>>> Jasha >>>> >>>> >>>> On 29 December 2012 11:27, Nolan Darilek <[email protected]> >>>> wrote: >>>> >>>> Hi, >>>> >>>>> I'm attempting to determine if Rave is a good fit for a project. To >>>>> that >>>>> end, after playing with the demo, I tried bootstrapping the vanilla >>>>> portal >>>>> as per these instructions: >>>>> >>>>> http://rave.apache.org/******documentation/rave-extensions.******html<http://rave.apache.org/****documentation/rave-extensions.****html> >>>>> <http://rave.apache.**org/**documentation/rave-**extensions.**html<http://rave.apache.org/**documentation/rave-extensions.**html> >>>>> > >>>>> >>>>> <http://rave.apache.org/****documentation/rave-extensions.****html<http://rave.apache.org/**documentation/rave-extensions.**html> >>>>> <http://rave.apache.org/**documentation/rave-extensions.**html<http://rave.apache.org/documentation/rave-extensions.html> >>>>> > >>>>> >>>>> with the plan of slowly adding on functionality. I ran into several >>>>> issues, though. >>>>> >>>>> First, apologies for not providing detailed logs and such. I can if >>>>> desired, but I think these directions are clear enough to duplicate the >>>>> issues, and I didn't deviate from the docs much at all. >>>>> >>>>> I checked out and built the 0.19-SNAPSHOT. I then checked out the >>>>> vanilla >>>>> repository. Vanilla depends on 0.15-SNAPSHOT, which was my first >>>>> hurdle. >>>>> I >>>>> upgraded the dependency to 0.19-SNAPSHOT and that worked. >>>>> >>>>> Next I ran into issues where the standard user service didn't compile >>>>> under 0.19. I removed this plus the tests, so I can't say if this >>>>> caused >>>>> the final problem I experienced. Figured I didn't need the service >>>>> since >>>>> the demo worked, and I could add extras if I needed them. >>>>> >>>>> Finally I ran cargo, and received a huge exception with at least one >>>>> other >>>>> as its cause. I'd include it here, but it's pages upon pages upon pages >>>>> of >>>>> output. >>>>> >>>>> It looks like the Vanilla portal hasn't been updated to 0.19-SNAPSHOT, >>>>> or >>>>> even 0.18, and I'm guessing that any developer who tries will run into >>>>> the >>>>> same series of problems I did. Is there a better course of action than >>>>> what >>>>> I did, or is there a new recommended procedure? >>>>> >>>>> Also, I'm a bit confused about the vanilla portal's creation of two >>>>> rather >>>>> than one project. I understand that the portal creates user accounts, a >>>>> default gadget store, etc. and uses Shindig as a gadget container. Is >>>>> there >>>>> any reason Shindig comes as a separate project in the vanilla portal? >>>>> Is >>>>> it >>>>> so you can override Shindig pages in your own portal? I'm very new to >>>>> Maven, vastly preferring Gradle, so I'm not familiar with how the war >>>>> overlay stuff works. It'd be nice if someone has a Gradle version of >>>>> the >>>>> vanilla project, but my tentative research suggests it doesn't do >>>>> overlays, >>>>> so I suspect it's out. >>>>> >>>>> Thanks, and please let me know if I need to provide detailed logs after >>>>> all. >>>>> >>>>> >>>>> >
