Hi Jonathan,
All the basic stuff are part of the Webaccess module. Currently it has a
list of active sessions and contexts, a scripting console (js and groovy)
and a log listing.
>From the console you can access the jndi info if you want....
***************************************
import java.util.Properties
import javax.naming.Context
import javax.naming.InitialContext
def printNames(Context context, String root, String ident) {
context.list(root).each({
def bean = context.lookup("${root}/${it.name}")
if (Context.isInstance(bean)) {
println "${ident}[context] ${root}/${it.name}"
printNames(context, "${root}/${it.name}", ident + ' ')
} else {
println "${ident}[bean] ${root}/${it.name}
${bean.class.interfaces*.name}"
bean.class.methods.each { m ->
if (m.declaringClass != Object) {
println "${ident} ${m.returnType.simpleName}
${m.name}(${(m.parameterTypes*.simpleName).join(',
')})"
}
}
}
})
}
printNames(new InitialContext([
(Context.INITIAL_CONTEXT_FACTORY):
'org.apache.openejb.client.RemoteInitialContextFactory',
(Context.PROVIDER_URL): 'http://localhost:8080/tomee/ejb'
] as Properties), '', '')
***************************************
Output...
...
[context] /global
[context] /global/openejb
[context] /global/openejb/openejb
[bean] /MEJB [javax.management.j2ee.ManagementHome,
org.apache.openejb.client.EJBHomeProxy]
EJBHomeHandler getEJBHomeHandler()
EJBMetaData getEJBMetaData()
HomeHandle getHomeHandle()
void remove(Handle)
void remove(Object)
boolean equals(Object)
String toString()
int hashCode()
...
The idea of moving these stuff out of the webapp was to make the
distribution as small as possible.
[]s,
Thiago.
On Wed, Nov 12, 2014 at 4:36 PM, Jonathan Gallimore <
[email protected]> wrote:
> We used to have a couple of basic features in the old webapp (showing the
> JNDI tree for example). I'm sure these were in the new webapp at some
> point. Should we get those features implemented in the new webapp?
>
> Jon
>
> On Wed, Nov 12, 2014 at 6:57 AM, Romain Manni-Bucau <[email protected]
> >
> wrote:
>
> > any other thoughts?
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau
> > http://www.tomitribe.com
> > http://rmannibucau.wordpress.com
> > https://github.com/rmannibucau
> >
> >
> > 2014-11-11 8:48 GMT+01:00 Romain Manni-Bucau <[email protected]>:
> > > Maybe I was unclear, sorry. I dont want to remove the webapp. I want to
> > > remove it from tomee distribution. Ie if you dowload a tomee you dont
> > have
> > > it but if you download tomcat and use drop in war then you keep current
> > > webapp setup.
> > >
> > > Le 11 nov. 2014 01:44, "Thiago Veronezi" <[email protected]> a
> écrit :
> > >
> > >
> > >>
> > >> >>Fully optional, remove it and it still works
> > >> Cool, I just saw the programmatic setup elsewhere. It looks good.
> > >>
> > >> >>Fully useless for tomee,makes sense for the drop in war solution
> > >> How to address the drop-in approach without the webapp?
> > >>
> > >> >>Never saw it working myself with openejb version features (jndi
> > etc...)
> > >> Please note that this app, afaik, has no special feature. It was
> > supposed
> > >> to map the "/ejb/*" and to install the drop-in war. Once the app is
> > >> installed, it does not have any other purpose.
> > >>
> > >> If we no longer need to map "/ejb/*" (It looks settled) and we have a
> > new
> > >> way to call "org.apache.tomee.installer.Installer.execute()" without
> > user
> > >> intervention and without a servlet, I agree that this app should go.
> > >>
> > >> Anyway, I'm still not sure why we would need to call the installer
> > method.
> > >>
> > >> []s,
> > >> Thiago.
> > >>
> > >>
> > >> On Mon, Nov 10, 2014 at 5:33 PM, Romain Manni-Bucau
> > >> <[email protected]>
> > >> wrote:
> > >>
> > >> > Le 10 nov. 2014 22:39, "Thiago Veronezi" <[email protected]> a
> > écrit :
> > >> > >
> > >> > > Hi,
> > >> > >
> > >> > > Off the top of my head:
> > >> > > * The webapp maps the
> > "org.apache.openejb.server.httpd.ServerServlet"
> > >> > > to
> > >> > > "/ejb/*"
> > >> >
> > >> > Fully optional, remove it and it still works
> > >> >
> > >> > > * Due to the drop-in war approach, the webapp gives a way to set
> the
> > >> > > parameters (catalinaBaseDir, catalinaHome and serverXmlFile) and
> > >> > > trigger
> > >> > > the "org.apache.tomee.installer.Installer.execute()" method. Is it
> > for
> > >> > > historical reasons? Do we really need to call that method?
> > >> > >
> > >> >
> > >> > Fully useless for tomee,makes sense for the drop in war solution
> > >> >
> > >> > > Is it broken now?
> > >> > >
> > >> >
> > >> > Never saw it working myself with openejb version features (jndi
> > etc...)
> > >> >
> > >> > > []s,
> > >> > > Thiago.
> > >> > >
> > >> > >
> > >> > > On Mon, Nov 10, 2014 at 3:57 PM, Romain Manni-Bucau <
> > >> > [email protected]
> > >> > >
> > >> > > wrote:
> > >> > >
> > >> > > > Hi guys
> > >> > > >
> > >> > > > do we remove tomee webapp completely from tomee itself (=
> > packaged)?
> > >> > > >
> > >> > > > Current version doesn't bring much things and is often broken so
> > it
> > >> > > > is
> > >> > > > from my point of view more an issue than an added value.
> > >> > > >
> > >> > > > wdyt? Anyone using it?
> > >> > > >
> > >> > > >
> > >> > > > Romain Manni-Bucau
> > >> > > > @rmannibucau
> > >> > > > http://www.tomitribe.com
> > >> > > > http://rmannibucau.wordpress.com
> > >> > > > https://github.com/rmannibucau
> > >> > > >
> > >> >
> >
>
