Anymore more thoughts on this issue? If not, I guess I'll just add options for specifying the username, password and port number as a temporary solution to get this fixed for the 2.1.1 release.
Jarek On Mon, Mar 17, 2008 at 11:01 AM, Jarek Gawor <[EMAIL PROTECTED]> wrote: > On Sat, Mar 15, 2008 at 12:28 AM, Jason Dillon <[EMAIL PROTECTED]> wrote: > > On Mar 15, 2008, at 12:34 AM, Donald Woods wrote: > > > Jarek Gawor wrote: > > >> Jason, > > >> I thought TCK was using the maven plugin to start the server. I'm not > > >> proposing to change that. But even if start-server command is used by > > >> TCK, I don't think that alone should dictate how the command should > > >> behave. I'm thinking what happens if you start any command in the > > >> background in a regular shell or even use geronimo.sh run or > > > > The --background option is not intended to behave like a shells & > > operator... and some daemons do fork right away and return while the > > child continues, but other more robust daemons fork, then wait for the > > child to become booted, then return, so that any error status can be > > returned to the invoking shell for handling. > > > > IMO this is how Geronimo should behave... > > > > Adding a --wait or --nowait option might be useful, though I'd really > > like to solve the username/passwd problem... I think we need any > > anonymous way to query the status... > > Whether to poll and how to poll are two separate issues to me. I agree > that we do need a way to anonymously query the status but I don't > think we need to query the status in the normal/default case in the > first place. When executing a script we'll need to know the status of > the server and polling will be necessary but when starting the server > in foreground polling is unnecessary. > > Jarek >
