https://issues.apache.org/bugzilla/show_bug.cgi?id=54239
--- Comment #11 from Sheldon Shao <xs...@ebay.com> ---
Thank you very much for your information!
I'll try to follow up with this approach.
(In reply to comment #10)
> (In reply to comment #9)
> > (In reply to comment #3)
>
> > > 4. I dislike the use of system properties when they are not necessary. If
> > > the class name was handled as a servlet context initialization parameters
> > > then Tomcat already has the necessary plumbing for global, per host and
> > > per
> > > web application configuration.
> > ~~~~~~~~~~~~~~~~~~ Supported passing the class name from context
> > initialization parameters. Still keep the feature from System Property.
> > In our case, System Property can be easily passed in from such kind of
> > Daemon-Watcher, For example: JSW.
>
> I haven't looked at the details here but it might be useful for you that
> system properties are automaticaly supported in most Tomcat config files,
> e.g. in server.xml and context.xml. What should work if you already support
> a className attribute is className="${my.el.interpreter}" (using a system
> property reference) and setting the system property via
> "-Dmy.el.interpreter=some.class.i.Use". No need for special code or a fixed
> system property name for this type of use case.
>
> Regards,
>
> Rainer
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
