This sounds a bit like JMX, would publishing your services to JMX and editing via the JMX console solve your problems?
If you'd still like to have the full power of a scripting language (eg bsh) at your fingertips, you could @Inject the ObjectLocator and make it available in the bsh context. From there you will be able to lookup any service and invoke methods on them. http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/ioc/ObjectLocator.html As you mentioned, this is a pretty large security hole ;) -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-app-live-console-tp5714144p5714146.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
