Costin Manolache wrote:
It was about time !
I suppose we'll end up with Bootstrap + Catalina.
What I would like is to have a similar bean/ant-like interface
on both ( i.e. setter methods for all options configurable on
command line + execute() pattern ). With the main distinction
beeing that Bootstrap will be a class with no deps that'll create the
loaders and use reflection on Catalina.
Yes, I figured the bean like methods would be useful, and I plan to have
some.
Please take a look at my latest commit on catalina.xml ( the run/run-wait
targets).
And I hope the 'random method additions' are not mine :-)
You're a suspect, I'm afraid. Some had your coding style ;-)
Remy
Costin
Remy Maucherat wrote:
>... as well as the Catalina and CatalinaService classes. The idea is to
>remove the *Service, and have only one set of classes (which would still
>handle all use cases). There has been a number of random method
>additions which make the whole thing a mess (IMO). For example, the
>"Service" version can be made to behave like the non-"Service" one.
>Kinda confusing ...
>
>This will likely break a few things.
>Please complain if you like the current mess better ;-)
>
>Remy
--
To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
