Return-Path: Delivered-To: apmail-jakarta-cactus-user-archive@apache.org Received: (qmail 80292 invoked from network); 27 Nov 2002 20:51:58 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 27 Nov 2002 20:51:58 -0000 Received: (qmail 29369 invoked by uid 97); 27 Nov 2002 20:53:04 -0000 Delivered-To: qmlist-jakarta-archive-cactus-user@jakarta.apache.org Received: (qmail 29353 invoked by uid 97); 27 Nov 2002 20:53:04 -0000 Mailing-List: contact cactus-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Cactus Users List" Reply-To: "Cactus Users List" Delivered-To: mailing list cactus-user@jakarta.apache.org Received: (qmail 29332 invoked by uid 98); 27 Nov 2002 20:53:03 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3DE5304B.3000307@bestweb.net> Date: Wed, 27 Nov 2002 15:51:23 -0500 From: Michael Burke User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Cactus Users List Subject: Re: Tutorial help References: <001a01c293fa$9fe7c970$0200a8c0@octovma> <3DE5007F.1040401@bestweb.net> <3DE50419.4090603@gmx.de> <3DE51B7A.7040108@bestweb.net> <3DE51E08.8090605@gmx.de> <3DE52CEE.3030401@bestweb.net> <3DE52FCC.80403@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Christopher Lenz wrote: > Michael Burke wrote: > >> Christopher Lenz wrote: >> >>> Michael Burke wrote: >>> >>>> Christopher Lenz wrote: >>>> >>>>> Can you confirm that: >>>>> (a) the XML source contains a line >>>>> (somewhere at >>>>> the beginning) >>>>> (b) the file pointed to by the above declaration is retrievable by the >>>>> browser? >>>>> >>>> here's the source: >>>> >>>> >>> name="TestSampleServlet" tests="1" failures="0" errors="0" >>>> time="0.136">>>> time="0.126"> >>>> >>>> I don't understand your second question. >>> >>> >>> No, need if (a) fails - as it has - (b) doesn't matter (yet). >>> Your problem has nothing to do with Mozilla... how can Mozilla know >>> which stylesheet to use to transform the XML source? It can't. >>> >>> Okay, so just to get the obvious out of the way... >>> You're 100% sure you have got the "xsl" request parameter right in >>> the URL, as in: >>> >>> http://server:port/mywebapp/ServletTestRunner?suite=mytestcase&xsl=junit-noframes.xsl >>> >>> ^^^^^ >>> >> Looks like we're talking about two different things. I was trying to >> run the tutorial with xml output (the first example on the tutorial >> page) not with html which is what you're talking about I guess. I >> haven't tried that yet. > > > No wonder you're getting a blank page then ;-) > > In contrast to Internet Explorer, Mozilla doesn't do the > "XML-Explorer" thing. That's a completely IE-specific feature, and I > don't know any other web browser that displays XML in such a way > automatically. Mozilla or for instance Opera require an > XSLT-stylesheet to transform an XML source into something displayable. > > Maybe that should be noted in the tutorial :-P > Thanks for the info I'll try the second approach (html). -- To unsubscribe, e-mail: For additional commands, e-mail: