I like the idea of
site
\- default
\- conf
\- deploy
\- logs
\- whatever
\- cluster
\- conf
\- deploy
\- logs
\- whatever
Having the named deploy dirs like system/user/etc still doesn't give the
user an instant clue as to what runs first.
I would guess, making it more simple:
1) for all files in deploy, deploy each one in sorted order
2) for all directories (in sorted order), deploy each file in it (and
walk the dir tree for as much depth as you want)
so, order of execution
deploy/aaa-service.xml
deploy/a/aaa-service.xml
deploy/b/aaa-service.xml
Still maintaining the <depends> or <ejb-ref> system for dependancies.
But make site/default/deploy
be exactly as it is today.
So, to the un-initiated, the only real change from 2.4 is the fact that
we made the conf/deploy/whatever as a single unit, easily backed up, or
CVS controlled.
But, when someone needs some kind of "I need to deploy after EVERYTHING
else is deployed", they just name the file
deploy/ZZ-whatver-service.xml
And if they want to get more fancy with runlevel type stuff, they can
move it all around as much as they want.
Then, jboss-init could really just be as simple as a shutdown/restart
with new config.
ie: run.sh does
#make sure to clean up old state in case we crashed when restarting
if [ -f newconf.cfg ] ; then rm newconf.cfg; fi
if [ -z $1 ]; then
CONF=default
else
CONF=$1
fi
while (true); do
java -Dconfig=$CONF
if [ -f newconf.cfg ]; then
CONF=`cat newconf.cfg`
rm newconf.cfg
continue
fi
echo JBoss Shutdown
exit
done
This would allow admins to get pseudo uptime of jboss by checking the
start time of run.sh, and you'd be ensured no funky leaks when switching
configs. And you don't have to worry about KXXX scripts, since the
server bounces each runlevel change.
Ok, maybe this is overkill. But it allows more control of deployment,
while still allowing the current directory layout, and doesn't add a
bunch of complexity to the code.
Just add to the payfor-docs the description, or maybe even examples of
ways you can use this.
-David
On Sun, 11 Nov 2001, Allen Fogleson wrote:
> Actually what if the deploy directory was a subdir of the conf directory?
>
> That doesnt seem like it would be too confusing to even a new user.
>
> Al
>
>
> [EMAIL PROTECTED] wrote:
>
> >>Hiram, I don't understand your problem with deploy dirs and different
> >>configurations. Can't you have directories
> >>
> >>deploy/conf1/lib
> >>deploy/conf1
> >>deploy/conf2/lib
> >>deploy/conf2
> >>?
> >>
> >>
> >Yes, that would be nice. Since the default layout is setup to support
> >multiple conf dirs, it makes sense to my to have multiple deploy dirs
> >too. Would that be too confusing for a beginer.
> >
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
