That's what I thought. Thanks On Saturday, September 27, 2014 1:42:54 PM UTC+2, stefaan luckermans wrote: > > Let me sketch the situation I am in. > > > I am using Play framework - java in combination with AngularJs. > > I use my play framework controllers (server side) to do the routing > through my application. This means that my server app renders a a view that > consists of a main part (main.html) and a content dependent part > (sub.html)... > > In the main.html I also provide my ng-app and appController. In the > sub.html I provide the content dependent controller. > > > In the main.html I included the scripts for a steeringService, that should > contain data that flows through all my other screens. > > My problem is that by leaving the routing to my server application, the > main.html is rendered on each transition and my steering Service is > initialised on every screen transition ... > > Is there any way that I can prohibit a service of initialising twice? > > I could pass the data as parameters when calling the screens, but that > would kill the beauty of AngularJs, no? > > Thank you for any advice you can give ... > > > Stefaan >
-- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
