hmm, so it seems the readme is not yet complete ;)
btw tomee has a ssh connector with some commands ( https://rmannibucau.wordpress.com/2012/05/09/tomee-and-its-ssh-connector/). That said joining our efforts would still be good and even if in 3 lines of clojure you avoid maybe 10 lines of java you stay "alone" in term of community and you can't assume you have clojure on prod machines IMO and that "prod" guys can write clojure - but you can assume you have java and that prod guys are shell expert, no? BTW looking forward to see what's your remote solution! Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-04-14 7:05 GMT+02:00 htmfilho <[email protected]>: > Hi Romain, > > Concerning Clojure, we try to think about the goal, not the medium. If a > language allow us to provide more for TomEE with less effort and time then > that's the one we are going to use. > > Good that there are some commands available. We can easily embed all of > them > into TomEE-CLI by simply reusing them. > > Clojure's REPLs can connect to each other. So, if we have a cluster > environment, we can start TomEE-CLI in each one of the servers and control > all of them from the instance you started at your machine. We don't need to > code this complex mechanism in Java to achieve the same result. More news > about this feature in the next milestone that comes out every 30 days. > > Thanks > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/A-client-to-manage-your-Apache-TomEE-instances-tp4674390p4674398.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
