tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "NormW" <no...@bocnet.com.au>
Subject Re: Discussion - /jkstatus and stylesheets
Date Thu, 01 Apr 2004 22:19:47 GMT
Good morning All.
I've not looked at XML or XSL for that matter, but in either case, hopefully
this still means the colour palette/style selection is still external to the
JK2 program, which then still requires a 'path' of some kind to find it. As
noted in my initial introduction to the thread, this could either be a fixed
or (preferably) a programatic one, and if the latter, adding a variable to
the [status:] object still remains, IMO, the most logical option.

Norm

----- Original Message ----- 
From: "Henri Gomez" <hgomez@apache.org>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Sent: Thursday, April 01, 2004 7:57 PM
Subject: Re: Discussion - /jkstatus and stylesheets


> Craig McClanahan wrote:
>
> > jean-frederic clere wrote:
> >
> >> Thorsten Kamann wrote:
> >>
> >>> Hello,
> >>>
> >>> Henri Gomez schrieb:
> >>>
> >>>> Well I didn't like very well the hardcoded way, so I'd like to have
it
> >>>> externally.
> >>>>
> >>>> We could :
> >>>>
> >>>> Define a stylesheet property var in workers2.properties, which will
> >>>> contains a full URL and if this var is null, fallback to previous
> >>>> method.
> >>>
> >>>
> >>>
> >>>
> >>> Is there a chance the jk provides the status as xml? So the status can
> >>> checked programmatically. With an nice XSL-Stylesheet I can integrate
> >>> the status in every monitor page .
> >>>
> >>> Your comments?
> >>
> >>
> >>
> >> Sounds a good idea to me.
> >>
> > Hmm .. separating the view from the model ... now where have I heard
> > that before?  :-)
> >
>
> No problem for me to provide the result in XML, since I've got friend
> aroud which could provide me some nice XSL still sheet.
>
> Second advantage, the jkstatus could be used by others apps for example
> for monitoring purposes.
>
> +0 for XML (lack of time to works on this ;().
>
> So we should now define a DTD.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message