Steve, echoing Serge..
> > 2. enhanced configuration error handling > > No repeated stack trace dumps, and tying an error to the line number > (and column!) in the configuration file. This has been a thron in our side for a while, it would be nice to have meaningful and concise errors from the container integrated intelligently with the errors from the app. > > > 3. remotely accessible services (e.g. via JNDI) > > This is more of a wish list (to me at least). Me too, for now, but I strongly believe that remote services accessable via JNDI could be a massive advantage to James (caveat.. they have to be _reasonably_ simple to deploy and lookup, and to a lesser extent build and debug). It would also provide an alternative to EJB's for other existing and potential Avalon clients... d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
