Hi Tom, That's an interesting idea. Let me check if I understood what you said. The subordinate WAR-charm will essentially be a place-holder for the .war file. The interface connecting the WAR-charm and the java container would enable the WAR-charm to say "I got this war file stored on this path". The java container (Tomcat, Wildfly, Karaf etc) would have to copy the file to the appropriate (container specific) directory and do whatever is needed to load it. What we gain is that the same WAR-charm would work with any java container.
It has been some time since I looked into JEE, but I think this approach would work for loading jars (EJBs) on any JEE container, right? Cheers, Konstantinos On Sat, Mar 5, 2016 at 1:39 PM, Tom Barber <[email protected]> wrote: > Okay so here's one I wanted to know if it made sense to people or not now > there are layers, interfaces etc. > > Take Saiku or any other WAR based webapp. Currently our app is a Tomcat > subordinate, which installs the WAR and a few other directories and just > sed-s a few files to set some variables. > > In this land of layers and interfaces, does it make sense to have a webapp > interface? I realise most of the current interfaces are for services and > not file archives, but, if I deploy Tomcat, Wildfly, Karaf I know that > (with a bit of tweaking) I can deploy a war to each of those and they > should behave pretty much the same. So does it make sense to have an > interface that lets me charm up my WAR file and then add a relation from > WAR <-> J2EE Container so I can just link them together and have Juju place > my WAR in the correct location? > > That way you can deploy on multiple services without having to do much, if > anything, to your code. > > Cheers > > Tom > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > > -- Konstantinos Tsakalozos
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
