Hi Jason, This reply is very late, so I don’t know if it is still relevant or not...
I have started looking into Angular a bit. My impression is that this will be difficult to do. Angular 2/4 seems to be more than just a js file: it is a complete environment that comes with a compilation tool. I get the impression that you can’t just treat it as a resource. If that is the case, then I personally don’t see how this approach could be used for Angular 2/4. Instead, you would have to figure out a way to ship your entire (complied) Angular app. You could use an Extender pattern to do this. Indeed, that is what I am doing, but for AngularJS. I am only now looking into updating to 4. Then again, I am no Angular expert. Maybe it is possible, but it seems to me at this point that I would not want to develop in Angular without all the tooling that comes with it, and I don’t see how to continue to use the enRoute approach AND benefit from the tooling. But maybe I’m missing something. Cheers, =David > On Aug 3, 2017, at 11:20 PM, Jason Fauble <jason.fau...@myfuelmaster.com> > wrote: > > Are there any plans to update the enRoute Angular bundle > (https://github.com/osgi/osgi.enroute.bundles/tree/master/osgi.enroute.google.angular.webresource) > > <https://github.com/osgi/osgi.enroute.bundles/tree/master/osgi.enroute.google.angular.webresource)> > to support Angular 2/4? I would like to migrate my existing enRoute web > application. My searches haven’t come up with much to direct me on how to > approach this effort. > > Any help would be appreciated. > > Thanks, > Jason > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> > https://mail.osgi.org/mailman/listinfo/osgi-dev > <https://mail.osgi.org/mailman/listinfo/osgi-dev>
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
