I've looked into it a little bit more. The only thing even remotely difficult is that the client app spec says that the client app should be packaged as a runnable jar and the developor should write their own main method. It doesn't specify any particular API that they should call, so the container developer is left to work out for themselves how to get bootstrap code called.
My thought was maybe to supply our own main, then rewrite the manifest to call that, which would bootstrap the JBoss spine and any configured services, set the context classloader appropriately and call into the old main. But that's about as far as I got thinking about it, too. danch David Jencks wrote: > I haven't looked into it much, but I suspect it would be pretty simple to > do. Mostly you'd leave everything out of normal jboss, right? Maybe you'd > mostly need an "client app runner" mbean. Might also be a good opportunity > to make our tm distributed and logging so it will really handle xa tx. On > the other hand I haven't heard anyone say they are about to implement it. > > david jencks > > On 2002.02.27 14:39:13 -0500 David Ward wrote: > >>Are J2EE application clients going to be supported in JBoss3? It would >>be nice to be able to use the java:comp/env namespace from a remote gui, >>and also maybe even initiate a Transaction from one (yes, I'm familiar >>with the dangers of that). >> >>Geeze I ask too much... >> >> _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
