Here they are. Thanks -Vincent
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On > Behalf Of Mike Aizatsky > Sent: 28 March 2002 19:52 > To: [EMAIL PROTECTED] > Subject: RE: [Eap-list] idea #614 - Internal error occurred > > Vincent, > > Can you sent me your file and DTD for checking here? > > Best regards, > Mike Aizatsky. > ------------------------------ > JetBrains, Inc / IntelliJ Software > http://www.intellij.com > "Develop with pleasure!" > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > On > > Behalf Of Vincent Massol > > Sent: Thursday, March 28, 2002 7:11 PM > > To: [EMAIL PROTECTED] > > Subject: [Eap-list] idea #614 - Internal error occurred > > > > Hi, > > > > Can someone tell me how I can turn off the XML "validation". For > almost > > all the XML files I open with IDEA, I get an "internal error occurred" > > dialog box. For example, on the current file I have, whenever I type > any > > single letter I get 3 times the dialog box ! It is a nightmare and I > > have to revert using a standard text editor to edit my XML ... :-( > > > > Here is the stack trace, if it helps : > > > > [27503879] ERROR - intellij.plugins.PluginManager - > > [27503929] ERROR - intellij.plugins.PluginManager - IntelliJ IDEA > > (Ariadna) > > [27503939] ERROR - intellij.plugins.PluginManager - JDK: 1.3.1_01 > > [27503939] ERROR - intellij.plugins.PluginManager - VM: Java > > HotSpot(TM) Clien > > [27503939] ERROR - intellij.plugins.PluginManager - Vendor: Sun > > Microsystems I > > [27503939] ERROR - intellij.plugins.PluginManager - OS: Windows 2000 > > [27503939] ERROR - intellij.plugins.PluginManager - > > java.lang.NullPointerException > > at com.intellij.xml.a.a.c.i(c.java:14) > > at com.intellij.xml.a.a.c.a(c.java:26) > > at com.intellij.codeInsight.daemon.impl.ck.d(ck.java:0) > > at com.intellij.codeInsight.daemon.impl.ck.b(ck.java:36) > > at com.intellij.codeInsight.daemon.impl.ck.a(ck.java:40) > > at com.intellij.psi.impl.source.g.q.a(q.java:4) > > at com.intellij.codeInsight.daemon.impl.ch.a(ch.java:405) > > at com.intellij.psi.s.a(s.java:10) > > at com.intellij.psi.impl.source.g.q.a(q.java:4) > > at com.intellij.codeInsight.daemon.impl.i.a(i.java:95) > > at com.intellij.codeInsight.daemon.impl.i.run(i.java:59) > > at com.intellij.psi.impl.q.run(q.java:0) > > at > > com.intellij.vfs.VirtualFileManager.a(VirtualFileManager.java:136) > > at com.intellij.psi.impl.z.b(z.java:198) > > at com.intellij.codeInsight.daemon.impl.cn.b(cn.java:6) > > at com.intellij.codeInsight.daemon.impl.cn.a(cn.java:26) > > at com.intellij.codeInsight.daemon.impl.cn.a(cn.java:51) > > at com.intellij.codeInsight.daemon.impl.bw.run(bw.java:2) > > at > > com.intellij.progress.ProgressManager.a(ProgressManager.java:18) > > at com.intellij.codeInsight.daemon.impl.cn.run(cn.java:25) > > > > > > P.S.: These XML files have a dtd defined. If you need the file and the > > DTD, tell me and I'll send them. > > > > Thanks > > -Vincent > > > > > > > > _______________________________________________ > > Eap-list mailing list > > [EMAIL PROTECTED] > > http://www.intellij.com/mailman/listinfo/eap-list > > > _______________________________________________ > Eap-list mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-list
document-v10.dtd
Description: Binary data
<?xml version="1.0"?>
<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
<document>
<header>
<title>Jakarta Cactus</title>
<subtitle>Server-Side Unit Testing Framework</subtitle>
<authors>
<person name="Vincent Massol" email="[EMAIL PROTECTED]"/>
</authors>
</header>
<body>
<s1 title="Project description">
<p>
Cactus is a simple test framework for unit testing server-side java
code (Servlets, EJBs, Tag Libs, Filters, ...).
</p>
<p>
The intent of Cactus is to lower the cost of writing tests for
server-side code. It
uses <link href="http://junit.org";>JUnit</link> and extends it.
</p>
<p>
Cactus has been developed with the idea of automatic testing in mind
and it provides a packaged and simple
mechanism based on <link href="http://jakarta.apache.org/ant";>Ant</link>
to automate server-side testing.
</p>
<p>
Cactus implements an in-container strategy (click on the diagram below
to understand how it works). An alternative but complementary approach
not covered by Cactus is to use Mock Objects (see the
<link href="mockobjects.html">Mock vs Container</link> page to
understand the differences and why Cactus believes in the
usefulness of an in-container approach).
</p>
<p>
<link href="how_it_works.html">
<figure src="images/archiani.gif" alt="How it works ..."/></link>
</p>
</s1>
<s1 title="Different kind of unit tests">
<p>
There are several kinds of unit testing frameworks. We categorize them
in 3 types :
</p>
<ol>
<li>
<strong>Type 1 : code logic unit testing</strong>. Probably the
best strategy for these tests is to use a
<link href="http://www.mockobjects.com";>Mock Objects</link> type
framework.
</li>
<li>
<strong>Type 2 : integration unit testing</strong>. Cactus is
typically in this category (I'll let you judge if it is the best or
not :)). These tests will exercise the interactions with the
container.
</li>
<li>
<strong>Type 3 : functional unit testing</strong>. These unit tests
will let you test the returned values from your server code. This is
for example
<link href="http://sourceforge.net/projects/httpunit";>HttpUnit
</link> (Note that HttpUnit also performs standard functional testing
- as opposed to functional unit testing -, which let you test full
use cases - a login use case for example, which is comprised of
several requests/responses).
</li>
</ol>
<p>
Ideally you would use 3 different frameworks just to unit test your
code ! Then you have to think about acceptance testing, system
integration testing, ...
</p>
<p>
Cactus was developed to fit Type 2 but also to be a very good
compromise for Type 1 and 3, with the idea that it is much easier to
have to write tests for a single framework than for several ! Moreover,
you can never fully test your code. We believe Cactus provides a middle
ground that provides a high confidence that your code will run when
deployed. However, it is your choice and you can use Cactus only for
Type 2 if you wish.
</p>
</s1>
<s1 title="Getting Started">
<p>
To get started, read the
<link href="getting_started.html">Getting Started</link> guide.
</p>
</s1>
</body>
</document>
