for the scripting stuff did you look org.apache.openejb.server.cli.OpenEJBScripter? it makes the bean manager available in a limited version.
The security is a more general subject for tomee, for instance you can deploy an app without any particular permissions... I think it is a great feature we should keep - Romain 2012/4/10 Thiago Veronezi <[email protected]> > I just created a window that gives access to the JavaScript (Rhino) engine > at the server side. > Basically, the user can send a JS code to the server. The code will have > the response and the request instances, so the user can lookup a bean and > execute one of its methods from a web page. > > Here is the code: http://people.apache.org/~tveronezi/ConsoleServlet.java > Here is how to create a JS for it: > > http://docs.oracle.com/javase/6/docs/technotes/guides/scripting/programmer_guide/index.html > > It seems really dangerous! Do you think that limiting the access to > localhost and adding servlet security is enough? Do you think I should add > this feature at all? > > []s, > Thiago. > > > On Tue, Apr 10, 2012 at 9:03 AM, Romain Manni-Bucau > <[email protected]>wrote: > > > 1) yes exactly > > 2) was mainly thinking of simple things like pages to show friendly wsdl > > and wadl, but it can be done manually too > > > > - Romain > > > > > > 2012/4/10 Thiago Veronezi <[email protected]> > > > > > Hi Romain, > > > > > > 1) What do you mean by console? Do you mean something like the grails > > > console? http://grails.org/plugin/console > > > It seems interesting. > > > > > > 2) I am not a big fan of code generation. I like more the JSON approach > > > (from this thread > > > > > > > > > http://openejb.979440.n4.nabble.com/Various-TomEE-improvements-td4343090.html > > > ). > > > I was focusing on that with a js webapp that can easily support mobile > > > browsers. > > > > > > > > > []s, > > > Thiago. > > > > > > > > > > > > On Tue, Apr 10, 2012 at 2:34 AM, Romain Manni-Bucau > > > <[email protected]>wrote: > > > > > > > Hi, > > > > > > > > that's not the moment (because of the coming release) but i had some > > idea > > > > regarding our gui and want to share it before forgetting ;) > > > > > > > > 1) why not replacing our invocation flow by a console (a bit like the > > > > common-cli module we have -> you type what you want to do)? > > > > 2) why not using a kind of gui plugin (potentially linked to our > > > > services?), a plugin describe the corresponding gui and then we use a > > > > GUIBuilder (one implementation could be TomEEGuiBuilder) to generate > > the > > > > corresponding gui according to the used GUI (we obvioulsy thought to > > > webapp > > > > but it can be a cli one too replacing screens by prompt etc...) > > > > > > > > well, just 2 thouthgts trying to make our gui more effective and more > > > easy > > > > to maintain. > > > > > > > > IMHO it can be nice to get it for the version 4.0.0+1 > > > > > > > > wdyt? > > > > > > > > - Romain > > > > > > > > > >
