mockobjects-java-dev — For people who are working on the implementation of the java version

[MO-java-dev] CVS: mockobjects-java/src/j2ee12/com/mockobjects - New directory

[Steve F. <sm...@us...>]

Update of /cvsroot/mockobjects/mockobjects-java/src/j2ee12/com/mockobjects
In directory usw-pr-cvs1:/tmp/cvs-serv7328/mockobjects

Log Message:
Directory /cvsroot/mockobjects/mockobjects-java/src/j2ee12/com/mockobjects added to the repository
--> Using per-directory sticky tag `restructured_for_versions_and_libraries'

[MO-java-dev] CVS: mockobjects-java/src/j2ee12/com - New directory

[Steve F. <sm...@us...>]

Update of /cvsroot/mockobjects/mockobjects-java/src/j2ee12/com
In directory usw-pr-cvs1:/tmp/cvs-serv7265/com

Log Message:
Directory /cvsroot/mockobjects/mockobjects-java/src/j2ee12/com added to the repository
--> Using per-directory sticky tag `restructured_for_versions_and_libraries'

[MO-java-dev] CVS: mockobjects-java/src/j2ee12 - New directory

[Steve F. <sm...@us...>]

Update of /cvsroot/mockobjects/mockobjects-java/src/j2ee12
In directory usw-pr-cvs1:/tmp/cvs-serv6122/j2ee12

Log Message:
Directory /cvsroot/mockobjects/mockobjects-java/src/j2ee12 added to the repository
--> Using per-directory sticky tag `restructured_for_versions_and_libraries'

RE: [MO-java-dev] Multi Prepared Statement MockConnections

[Oskar H. <osk...@de...>]

OK ... great ... here are the changes we made to the MockObjects. (See
attached zip file)

List of changes
* Support for validating multiple PreparedStatements executions pr.
Connection.
* The number of PreparedParameters are validated against the Prepared SQL
statement.
* PreparedStatements now supports the setNull(...) method
* MockResultSetMetaData added.
* MockResultSet.getString(int columnIndex) now converts all values to
String.

Changed files:
com/mockobjects/sql/MockConnection.java
com/mockobjects/sql/MockPreparedStatement.java
com/mockobjects/sql/MockResultSet.java

New files:
com/mockobjects/ExpectationQueue.java (Used by the MockConnection class for
PreparedStatement.)
com/mockobjects/sql/MockResultSetMetaData.java
com/mockobjects/test/TestExpectationQueue.java
com/mockobjects/test/TestMockResultSetMetaData.java (This is not complete,I
just implemented the methods I had use for.)
com/mockobjects/test/TestConnection.java

Hope you guys can use this.

Regards
Oskar H.

-----Original Message-----
From: moc...@li...
[mailto:moc...@li...]On Behalf Of
Steve Freeman
Sent: 9. jan=FAar 2002 22:37
To: MockObjects
Subject: Re: [MO-java-dev] Multi Prepared Statement MockConnections


From: "Vincent Massol" <vm...@oc...>
> Just a clarification to Steve's email so that there is no
> misunderstanding (hoping that it is not me who is misunderstanding it
> :-0 ).
>
> "In theory, people should send changes to one of the committers and
have
> them check it in"
>
> Of course, this means sending the patches to the list (not to an
> individual committer) so that any committer who is available can help.
> It also lets other review the submitted code and comment on it (this
is
> the principle of open source peer-review, as opposed to XP's
> pair-programming ;-) )

sure, in practice I've been the only one committing for a while, so I
just collapsed the format.

S.





=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Mockobjects-java-dev mailing list
Moc...@li...
https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev

Re: [MO-java-dev] Multi Prepared Statement MockConnections

[Steve F. <st...@m3...>]

From: "Vincent Massol" <vm...@oc...>
> Just a clarification to Steve's email so that there is no
> misunderstanding (hoping that it is not me who is misunderstanding it
> :-0 ).
>
> "In theory, people should send changes to one of the committers and
have
> them check it in"
>
> Of course, this means sending the patches to the list (not to an
> individual committer) so that any committer who is available can help.
> It also lets other review the submitted code and comment on it (this
is
> the principle of open source peer-review, as opposed to XP's
> pair-programming ;-) )

sure, in practice I've been the only one committing for a while, so I
just collapsed the format.

S.

RE: [MO-java-dev] Multi Prepared Statement MockConnections

[Vincent M. <vm...@oc...>]

Just a clarification to Steve's email so that there is no
misunderstanding (hoping that it is not me who is misunderstanding it
:-0 ).

"In theory, people should send changes to one of the committers and have
them check it in"

Of course, this means sending the patches to the list (not to an
individual committer) so that any committer who is available can help.
It also lets other review the submitted code and comment on it (this is
the principle of open source peer-review, as opposed to XP's
pair-programming ;-) )

Now, some new committers would really be cool ! Becoming a new committer
is simple :
- send some patches to the list,
- have them integrated in the code base,
- send some more until the existing committers are fed up and give you
direct write access to CVS !

Thanks
-Vincent

> -----Original Message-----
> From: moc...@li...
> [mailto:moc...@li...] On Behalf Of
> Steve Freeman
> Sent: 09 January 2002 21:58
> To: moc...@li...
> Subject: Re: [MO-java-dev] Multi Prepared Statement MockConnections
> 
> as you may have seen from the list, we've been a bit stuck recently
and
> have just started on an overdue refactoring of the build. In theory,
> people should send changes to one of the committers and have them
check
> it in, but we've been getting grossly behind. I have more time now and
> am intending to clear the backlog -- and to make the process easier.
> 
> I suppose the obvious question is whether anyone out there would like
to
> become an apprentice committer to spread the load?
> 
> Steve
> 
> ----- Original Message -----
> From: "Oskar Hannesson" <osk...@de...>
> To: "'Robert Manning'" <man...@te...>
> Cc: <moc...@li...>
> Sent: Wednesday, January 09, 2002 8:39 AM
> Subject: RE: [MO-java-dev] Multi Prepared Statement MockConnections
> 
> 
> > We here at DeCode inc. have already implemented multiple
> PreparedStatements
> > for MockConnection and it is working fine.
> > I have not been able to commit this code because I can't find any
> guidelines
> > on how to do so.
> > I posted a question to
> 'moc...@li...'
> > but have not got any answer yet.
> > Can anyone give me a hint on how to post this code.
> > Regards
> > Oskar H.
> >
> >
> > -----Original Message-----
> > From: moc...@li...
> > [mailto:moc...@li...]On Behalf
Of
> > Robert Manning
> > Sent: 9. januar 2002 02:28
> > To: moc...@li...
> > Subject: [MO-java-dev] Multi Prepared Statement MockConnections
> >
> >
> > I see that someone (smgf) checked in work on MockConnection in the
> "core"
> > module 9/19/2001.  Yet it appears unfinished and is obviously not in
> the
> > latest build posted 8/21/2001.  Any idea when this will get
released?
> What
> > I need to have is the ability to track close calls on multiple
> > PreparedStatements that are being prepared within a single method
from
> the
> > same Connection.    One thing that's missing in the current
> implementation
> > is the ability to associate close calls with a particular
> PreparedStatement
> > (I guess using the SQL as an index into the HashMap).  Or maybe I'm
> totally
> > off the Mark and you can set me straight ??
> >
> > Rob Manning
> >
> > _______________________________________________
> > Mockobjects-java-dev mailing list
> > Moc...@li...
> > https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev
> >
> >
> > _______________________________________________
> > Mockobjects-java-dev mailing list
> > Moc...@li...
> > https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev
> >
> 
> 
> 
> _______________________________________________
> Mockobjects-java-dev mailing list
> Moc...@li...
> https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev

Re: [MO-java-dev] Multi Prepared Statement MockConnections

[Steve F. <st...@m3...>]

as you may have seen from the list, we've been a bit stuck recently and
have just started on an overdue refactoring of the build. In theory,
people should send changes to one of the committers and have them check
it in, but we've been getting grossly behind. I have more time now and
am intending to clear the backlog -- and to make the process easier.

I suppose the obvious question is whether anyone out there would like to
become an apprentice committer to spread the load?

Steve

----- Original Message -----
From: "Oskar Hannesson" <osk...@de...>
To: "'Robert Manning'" <man...@te...>
Cc: <moc...@li...>
Sent: Wednesday, January 09, 2002 8:39 AM
Subject: RE: [MO-java-dev] Multi Prepared Statement MockConnections


> We here at DeCode inc. have already implemented multiple
PreparedStatements
> for MockConnection and it is working fine.
> I have not been able to commit this code because I can't find any
guidelines
> on how to do so.
> I posted a question to
'moc...@li...'
> but have not got any answer yet.
> Can anyone give me a hint on how to post this code.
> Regards
> Oskar H.
>
>
> -----Original Message-----
> From: moc...@li...
> [mailto:moc...@li...]On Behalf Of
> Robert Manning
> Sent: 9. januar 2002 02:28
> To: moc...@li...
> Subject: [MO-java-dev] Multi Prepared Statement MockConnections
>
>
> I see that someone (smgf) checked in work on MockConnection in the
"core"
> module 9/19/2001.  Yet it appears unfinished and is obviously not in
the
> latest build posted 8/21/2001.  Any idea when this will get released?
What
> I need to have is the ability to track close calls on multiple
> PreparedStatements that are being prepared within a single method from
the
> same Connection.    One thing that's missing in the current
implementation
> is the ability to associate close calls with a particular
PreparedStatement
> (I guess using the SQL as an index into the HashMap).  Or maybe I'm
totally
> off the Mark and you can set me straight ??
>
> Rob Manning
>
> _______________________________________________
> Mockobjects-java-dev mailing list
> Moc...@li...
> https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev
>
>
> _______________________________________________
> Mockobjects-java-dev mailing list
> Moc...@li...
> https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev
>

Re: [MO-java-dev] CVS: mockobjects-java build.xml,1.15,1.16

[Steve F. <st...@m3...>]

OK

In case you're wondering, I've been doing the resturcturing in a branch.
I'm busy tomorrow, but should get back to it on Friday.

Steve

From: "Vincent Massol" <vm...@oc...>
> Steve,
>
> Actually the year should rather be :
>
> value="2001-2002"
>
> See the thread named "License change for new year" that I started on
the
> Jakarta general mailing-list if you want details.

RE: [MO-java-dev] CVS: mockobjects-java build.xml,1.15,1.16

[Vincent M. <vm...@oc...>]

Steve,

Actually the year should rather be :

value="2001-2002"

See the thread named "License change for new year" that I started on the
Jakarta general mailing-list if you want details.

-Vincent

> -----Original Message-----
> From: moc...@li...
> [mailto:moc...@li...] On Behalf Of
> Steve Freeman
> Sent: 09 January 2002 15:08
> To: moc...@li...
> Subject: [MO-java-dev] CVS: mockobjects-java build.xml,1.15,1.16
> 
> Update of /cvsroot/mockobjects/mockobjects-java
> In directory usw-pr-cvs1:/tmp/cvs-serv22471
> 
> Modified Files:
> 	build.xml
> Log Message:
> changed the year and some comments
> 
> Index: build.xml
> ===================================================================
> RCS file: /cvsroot/mockobjects/mockobjects-java/build.xml,v
> retrieving revision 1.15
> retrieving revision 1.16
> diff -u -r1.15 -r1.16
> --- build.xml	2001/11/05 00:11:51	1.15
> +++ build.xml	2002/01/09 15:08:00	1.16
> @@ -4,6 +4,15 @@
> 
>
========================================================================
==
> ===
>      Build file for the mockobjects project.
> 
> +    The following Ant tasks must be available in your ant
installation
> +    (i.e. the Ant task themselves and their dependent jars need to be
put
> +    in ANT_HOME/lib) :
> +
> +        stylebook             [REQUIRED] For builing the
documentation
> and
> +                               web site.
> +
> +        junit                 [REQUIRED] For running the unit tests.
> +
>      The following properties need to be set in a ./build.properties
or
>      or ${user.home}/build.properties file :
> 
> @@ -15,13 +24,9 @@
>      Depending on what mock implementation you wish to build you'll
need
> to
>      put associated jars in <root>/lib. For example, if you wish to
build
>      the servlet mock implementation you'll need to put the Servlet
API
> jar
> -    in <root>/lib. If it not there, then the servelt mock
implementation
> will
> +    in <root>/lib. If it not there, then the servlet mock
implementation
> will
>      simply not be built.
> 
> -    Note: You'll also need to have the 'junit' and 'stylebook' tasks
> defined
> -    in your Ant installation for running the unit tests and the
> documentation
> -    and web site generation.
> -
>      This script should be started with the following command line :
> 
>          ant <target>
> @@ -42,7 +47,7 @@
>      <property name="project.name" value="mockobjects"/>
> 
>      <!-- Miscellaneous settings -->
> -    <property name="year" value="2001"/>
> +    <property name="year" value="2002"/>
>      <property name="debug" value="on"/>
>      <property name="optimize" value="off"/>
>      <property name="deprecation" value="off"/>
> @@ -400,6 +405,7 @@
>          <copy todir="${out.doc.dir}">
>              <fileset dir="${xdoc.dir}">
>                  <include name="misc/*.pdf"/>
> +                <include name="papers/**"/>
>              </fileset>
>          </copy>
> 
> 
> 
> _______________________________________________
> Mockobjects-java-dev mailing list
> Moc...@li...
> https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev

[MO-java-dev] CVS: mockobjects-java/lib .keepit,NONE,1.1.2.1

[Steve F. <sm...@us...>]

Update of /cvsroot/mockobjects/mockobjects-java/lib
In directory usw-pr-cvs1:/tmp/cvs-serv15766/lib

Added Files:
      Tag: restructured_for_versions_and_libraries
	.keepit 
Log Message:
Started restructuring for multiple library versions

--- NEW FILE: .keepit ---
This file is only there so that CVS clients will not prune this directory.
Why ? Because Ant will look for user jars in this diretory and if the directory
does not exist Ant will exit with an error (something "directory lib does
not exist" !).

[MO-java-dev] CVS: mockobjects-java/src/extensions/com/mockobjects/atg MockDynamoServlet.java,NONE,1.1.2.1

[Steve F. <sm...@us...>]

Update of /cvsroot/mockobjects/mockobjects-java/src/extensions/com/mockobjects/atg
In directory usw-pr-cvs1:/tmp/cvs-serv15766/src/extensions/com/mockobjects/atg

Added Files:
      Tag: restructured_for_versions_and_libraries
	MockDynamoServlet.java 
Log Message:
Started restructuring for multiple library versions

--- NEW FILE: MockDynamoServlet.java ---
package com.mockobjects.atg;

import java.util.HashSet;
import java.util.Iterator;
import java.util.Set;
import com.mockobjects.ExpectationCounter;
import com.mockobjects.ExpectationSet;
import com.mockobjects.MapEntry;
import com.mockobjects.Verifiable;
import com.mockobjects.util.Verifier;

public class MockDynamoServlet extends DynamoServlet implements Verifiable {
    private ExpectationCounter myServiceCalls = new ExpectationCounter("MockDynamoServlet.service");
    private ExpectationSet myOutputParameters = new ExpectationSet("Output Parameters");
    private Set myParameterNames = new HashSet();

    public void setExpectedServiceCalls(int callCount) {
        myServiceCalls.setExpected(callCount);
    }

    public void setExpectedParameter(String name, Object value) {
        myOutputParameters.addExpected(new MapEntry(name, value));
        myParameterNames.add(name);
    }

    public void service(DynamoHttpServletRequest request, DynamoHttpServletResponse response)
            throws javax.servlet.ServletException, java.io.IOException {
        myServiceCalls.inc();

        if (request instanceof MockDynamoHttpServletRequest) {
            MockDynamoHttpServletRequest mockRequest = (MockDynamoHttpServletRequest) request;
            for (Iterator i = myParameterNames.iterator(); i.hasNext();) {
                String key = (String) i.next();
                Object value = mockRequest.getOutputParameter(key);
                myOutputParameters.addActual(new MapEntry(key, value));
            }
        }
    }

    public void verify() {
        Verifier.verifyObject(this);
    }
}

[MO-java-dev] CVS: mockobjects-java/dist mockobjects-0.02.zip,NONE,1.1.2.1 mockobjects-0.01.zip,NONE,1.1.2.1

[Steve F. <sm...@us...>]

Update of /cvsroot/mockobjects/mockobjects-java/dist
In directory usw-pr-cvs1:/tmp/cvs-serv15766/dist

Added Files:
      Tag: restructured_for_versions_and_libraries
	mockobjects-0.02.zip mockobjects-0.01.zip 
Log Message:
Started restructuring for multiple library versions

--- NEW FILE: mockobjects-0.02.zip ---
PK

LJÄ0À`þ¼þ«Æ“Q–WUc”—ð›ªCê#Fº~Oð6ˆŒµýu DÀ¾o€Þ(ü¹åî\ÖZ|ÿ£ãò£
Ö>w¢¾ IAÇ/ÔQÎ,ÍÛ+­iZB˜OQçÉòûõñ¸W°cöH{¯vÿOµ-ü¸ÐÆÐðññ…‚™aµÌÄï7ODåaKz‹¥›Ë}:7X¯û£Ã`}àJ²Ð06¢!Æ÷	Léûü_¬€øs™:Ø1ý÷(ÿ’°s0µq0±šººü4ú¿‘¶røÌ£à
tqý¿Tqsµ²ýŒ£ââôwXÿFÃhlÿwÆÿ»o±¶û;
À¿ÐÙÝèúŸ¦ÞÕ¢þ÷?²üŸG%g+{WMg+W 3£©­±‹K¨ª¿â¼ÊWƒæÙ&:„4¸Ht”!NÀÇH±aÈ–^£§iZ¬–%W‚±aÖx†Ù
ä0Ö­&àD`Åc·Çå¦Ë´KËÇËû;iÚ <¬&̆*s4$¤½T+ÑðgHþ$šVjcšX ¤óŽÐ^!¦;QƒW_gÅYõMúf	Úy¥¬'%ñrlóÄ{†•x"f¦Mìõìª
¿-…ÐHã|‰ÂHòËÞþbˆ¾±
Ôº
ýnQÐÌEαÊÔ¾ùä
p[jzƒœèàûØjÂðål÷Ä=E˜©N?ßïÚC¢}ܱ~8ªE©
b°yN™Öæ„Ð2óÈqȤÎúìçžÚ8†è/.Ù.ÛâõUãÊ0B«Y$‹wIô·óhy¦¢U„H&C°Bö8(â˜|ÎU£d5ž€Ì!^PT¤$ãõSÝüEøøš¯nõpÙ=`hR$ýÚ"Œ»q¯<ì(Gù_í)SHdŒê²ÕàçXöFøhŠBXTÏ0Ô<‡f$=bL¬~HòöÀú\Ù¡q•Eíx…mjø~×n™I}…j‚=ÇÐ&“'žTVÉ"ž´H‡—#Ã3I~ÃùĺÍ–"âö*Y8àäÀayV»ùcö4×ì6"—‚#úï€ÌÁ,dM[:†P™D„å
abÎE÷È%^ùGÛ°3Ý3ßÌMó…}DFXûìMcx°9¸x©¸lWCê¶ÙÐãù/8ã5
ø4
ktÜ5ð@”ΝùFéõtÚ)32Y¹÷º5«=…ôèã0“v´Èʌ>!–ÓÍÇ­n¾çïšþï1øÕ»Tˆª­UƸ-˜•)Ž’wúÉ	6pɵÕ"{¯ù–¢ƒ”Ý(»©¸ÙÍb÷Ÿ?]'pˆ_‹Æû+¬ãîÛ@nS[²D»yÇù­#â{l:g1öû6œ»MÄ.½8Ú?ϵ±óëÀ\É鸵ïyÏD°.YÞ#¸€r°Š¨(æϯ»#qúnßêNW!õ·²†×rhÄŬh«\½å+ðFȅrÏ	Y“
¬‡‘'©%‹u›m +Ú^	@oí=8C™ÍãD¡Ù~BuŒ]Í?Ï´ºö¸Ó‘sÖD-(őiðÕܺsF6‘‚®î™‚¸ŽB®ÀAð–›è]å˜P[ÅèîßYk@
¯YwWŸJ’
ŽSF¼Ç@veš´ÔÚöˆ¸˜šf/&¯bßM(>^:ñ<?ˆ¯]S¡gÝn‚{Sj">¾ðÁ­bõ˕s‘'”¾†|<7ôFЇçÜn„”3×3À@sS«ëq<9GŽß5Á"~(£U‡-¤ `ãþýÛ1b¬NÊ­	ÂU¯§ŒƒöšñWú8R÷üµ€5/–ñ/OäËÓL5-Ôñ„ "×7˜Kÿm,'’íO~,eð§nŸÊð­~å_iã›ÿýAüLj×"ïE»¼&bɃPP¶NrTßÞ×ã>Aà$Ûì¨ÇHï-T:K4ÊÀ/’튋º5’Ï×&Ü
%
Z´ì›uc[‹‚:
~§<ü¦NÖ[
<-ŸÁÀ°aþhþ{0Ptsutû?Ñ ÉAOcè;‰?§v
¸•°ŽµexhîàK	©z&BЋ‰6ÔJûèžy;Ñ CÞŒçšË]ÑØ>[‡1zÂڋ‰‡»ùÅûd×tŸÿïÛ7Eræ("7½^?Ä(ßüdäz@è'-ïÜì›*"¯ë†fbدûôµW½ªªò¦¤ÓTÞ¥+)?¥Úœ^MÞÏ\Û"b&¸hÓaŠÅ«ó¸­šÜpüŸ$j“¢K·¬wJåñÑø&áõsUr¾eÓ{ÑÜK³§”ƒ.výÛX	ó=í÷H¼¿“Y:UFè××9ôÖº‡
_ë»–΍»Ÿ	Gé“÷=BpoˆÛ‰æ1CÏCyxÜ>™a9>7	’‘ÄîsgíçLpä‘lêfƒ›‰àÁ6îú‚HÖsëìÕKzã®åÅ^6,'Dk^íTfC7áóÕÌ Ɍ­„ŸÐÅ.„¾c*mðÇNzDR?öXçÛ§µ»¹ÑÇi÷Á¬Vîï
ñ ;2«ƒ’€Ñ½ò1r›ì–YõÀٕ¬ã<“Wà÷DÌYœ^åÒõ_ÞaΩoŒ4óŠE—\éÓu7‡ñVýˆü²‚Éd›AeYI»n~}´OD†Çœâ/K=ÜÕu—Û_ÀMz”êö¢O=Uw^è:Æz1äŒæ„1U¡š™-vø&*–ƒ@vŸùž¶zµPZ}cۉ÷îŠmŸBc‹ú+e§Íà;&ƒ¨ü‘,vÈ&à7ވ†4x„Ž÷níÊËS8®¥êZ:ÔDÉÏÚOxp¸%û•sìÍwÖà+8òcµ=:"°úUëC$ü!šð÷“-ãÔû¿€ãkG9nìJ
ò˜[
Oíúd4à
@;Ÿ ä߁û­·
à$PI9%lMYYŒdGtû>Ð
E°P_á®ý’5	˜Å¢cïn¥>³
zð-\†Ã¯¨1ß%ý'Æ5Îq®857Ów€«qñH±¨.[$%L»rç@™d>‘²›Ñ,–%“#€–§Òƒ[_sŒEö}ŒàC®­_Ï)È{ßu?d5JÌÕÙ÷K
îPîîPHPÍõù2P戓ÌPÕ;osùj-YjPÌßôÌMTÊ
4L´Iɂ՜¿VµÿêìþUEÃÚYºNð$Y0˜TÌWƒön!­Œ˜øÀøÀˆO
ЌÑD¯,Mò—iUå QѨûòŽdTª4…7t%7ˆ»„CI;¬°YùA—ë”#ç–üQo„„ˆ™é9Åüþ‹e•ÊNVqþ=ÖTI%kOäòîº\ï99ãkÏiÆ´=_XÊWÃ^³CíµA0š³pB›„¬;&9,ÀààEè’/múÃ~Žù°¦Š ž+¡¤“}sã´Û”[CÐõéÌ~†Š´öÅálð³Ü,º4øqžøçD
‰¯¯=¶VD”’æ`2V»|Z'h†@û”‡OÞßî »¤ˆ‘0É€Á¶CÂ:!c–³ê°,©4a2îRxŠñ‰!©	ZÖß0M”ýu*·@•sE_ˆ5f]ŽçסƉe^‰QgjClÑåZ`Š¸È¹½²áM¼"´ZŽ•ûÈf÷¹Â§BÓTfñòŽC0ôMR/¡²Égð	r~)}·,ûn/r’Äð¡ý†ï¥ñꞖ2Ç`%úö¤&ÙÛóc‘1©M˜eB¥àHJ4pIE²×¤b'š?ù÷?ø@+'BÃäŸâÀûo‹ƒÇDL\\M]ÿS¨üGu ï²®†"P9®¬FÅR·F)¯Wm»ìۘäËN
ËAŽÄ>¨´eöÊ«l*-’ðù™fùªÁ	ÀÛO–½+ÉrfPk“‰#Áæs©ž³)Ðñøñ>MäOKÚ½ßìÔ§E_¯5W[iŠ@ÇK@Xß[’亖®¤¨›Z!ÜuSÆÞãŽá
Î_µì Ù¦FS€-kÝ+׸ùøI’ì¶tpI˜äY‰‘?gHºÞ7x›eÆ7™ÎC»Ï/˜èÒÜu{‘%ó	uòÎÛ>yU®TTÓ¶fá¹·©ªçÚ+C&®7ÓÑڕP¾•hTQˆzºU¨7ùfNÇ« "Û~éêÒÌJØ_DîZs‰ÄJZ²9Ö½¯eⶳêöÁï†en7UayâÄË´MŒdöRˆˆX7­éyi÷B·ð”iãΔ¬&KÇÌ8FßÕfìœ2?Û°Bśö‹°J+ʧ!ˆÈ¯¹UôµdRAHg6ô.Ûsp"‰½×.aiSŒµÐ8Ÿ¾¨ñï-ÍÝԜ/¦LšMGß3R9ìðFBU
õp`9ìÑ6ýί®Ç‹ôÛm،
l1Â-5JuÆ5³ëÚ´­ßÄ~JðÌ¡"½›+òÒ2^DWÆ~pÒl
+ÁífU¬„³ÓÎ5ÖÖtt›Q¾±ò :_ۙ^žYÈÊJ
	—øÕtòuѶ›yi6Þ®`È_j±ÈÔ«ç
sË?“J´¦BùÛ(â:Û­]{XQ±"öžÏ´}Õ(H2»UÒ¤7kø.kýÝDé†N€†5}Ëk/ƯcúQ^?Ñ@Î-~dY‰ùÐ4
×­…’¼
—”ù‰1¸
Hã±*¸1ßó3ÝtFò˜ìAc1‹gXE
[...1716 lines suppressed...]















”ÐÍ
êÊX

)


--- NEW FILE: mockobjects-0.01.zip ---
PK

Æ¿QqqúÏ™ÿE÷ßh¸[¹¸Û[
æðLÅz»MTÁôé†FŠª¯ô…Ír}WK5f#î„ҝh6Q?Àãìýlò¥ÃÒ

Piгµqº
Ø\¼T\¶«!uÛlèq„¬$
Ãkði
ìÿÝ3T]Ævÿá1jþ.ó(~Ø¿¿…“¯À’7r"ŒPX£ã®¢$p. èÌ7J¯§ÓNqÀ˜ÑÉʽ׭Yí)¤Ÿ@‡™´{ EVfô	y´œn>nuó=×ôÁ¯Þ¥BTm­2ÆmÁ¬Lq”,¸ÓON°»H®­‰Ø{Í·¤ìFÙMÅÍn»ÿüé:y„CüZ4އ\a—pßr›Ú’%ÚÍ;ÎoßcÓ9‹±ß·áÜm"vùëŹÐþy®ý›·XæJNÇE¨}Ï{&‚uÉò^Á”ƒUDE)0~݉ÓwûV7pº
©¿íí4¸–C#.fE[åê-_7B.”ÛxNȚT`=ìŒ<I-Y4¨Ûl]Ðö²H
Íö»ª{ `Ìèjþy¦ÕͰǝŽœ³&jA)ŽLƒ¯æ֝3²‰\puÏÄuz0°p‚w°ÜDï*DŽÚ*FwÿÎZ+
=ëvܛšPãññ…n«_®œû‹<¡ô5ä㹡7‚Î8ü;çvã ¤œ¹ž
š›Z]ãÉ9rü®	ñC­:l!
÷ïߎcuRnMx®z=•`,ü³×Œ¿ÒÐǑºç¯¬y±Œy"_ž®`ªùh¡Ž'¹¾Á¸À\úoc	<‘lòc)ƒ?uû¬P†ÿhõ+ÿJßü—èâgR»y‡(Úå5K„‚²u’£úö¾÷	'ÙfG8Fzo¡ÒY¢Qö
dÎâô*—®ÿòsN}c¤™W,²¸äJŸ®»9Œï˜°êGä—lLÖ Ûš(ËBØHÞuóë£}|"2<æYêá®®»4Øþn*УT·xꩺóB×1փˆ g4'Œ©
ÕÌl±Ã7Q±²ûÌ÷´Õƒ¬…ÒêÛN¼wWlû[ÔX);m&
èp헬IÀ,k|w+õ™
Ѓoáà2~EíŒùÆ8(é?1®qŽCpÅ©¹™¾\‹GŠEuÙ")a:Øؕ;Êü ó‰”ÝŒf±Ä(™i´<•Üúšã8`,ú°ïcÿjtmýzNAÞûv¨û!Û¨Qb®Î¾_ø…T"܁Š‹ÓLüëts麥î
M/²u×~Ãiþw ÏwHÍV>ûºPÙÔ!&5Ìø|‡ÌäXm+ß?Àò¥»l™Ú	òA»rõ¹m˜Z™íGbUßyç¤óÂ1¯Èq|诽=ð-.d€wÙÅ
ÌV]¦rž§³Ùn_§§
ÍP™0ÈY*ŒÀ\œÖCuQì•[)vasj±^ë
s£_ß=swHkñûMA‹žÏ'Ÿ—ý*®È¢ÖEÍ/ÅøæNJ͉’éºmV$m>k˜Ê>žfàˆ
^–ׯ¸p@ðš·Qгv%C8	> ÉÇSäŽËÆòQÈî›ÃÀCÜ>ä`åß+W€ŸvÓdI!·r*±q:è;ömdzo$ukâahí£\;ƒ(4áõNq¯“Rr6õòJ4I{ª6å˜ÛáîCúûµ½¹jYí·¢Wxmc¦Ò#,á$˜¦
›•?t¹N9rnÉõF8@ˆ˜™žSÌ￱X&\©ìÔaçßcÍ@•T²öD.ï®Ëõž“3¾öœfLÛó…¥|5ì5û01Ô^£9'´IÈú¸c’Ã^„!ùÒ¦?ìç˜kÚ¨â¹J:yÐ77N»A¹5íQŸÎìg¨Hk_ŽñÈ?ËÍ¢Kƒç‰NԐøúÚ3`kEDé i&cµË§u‚&`´OyøäýíºKŠ	“ì
Ž¤D—T${M*v¢ù“ÿƒ´r"4LþI¼ÿ69øw|@ÄÄÅÕÙØÔõ?¹Ê¿²}—u5zÌqe5*–j¼5Jy¸jÛeßÆ$_v
XXr$öA¥-³W^eSi‘„ÏÏ4»ÈW}ðN
[...1237 lines suppressed...]














?‡
	
Q
º

[MO-java-dev] CVS: mockobjects-java/src/core/com/mockobjects/servlet MockServletOutputStream.java,1.2,NONE MockRequestDispatcher.java,1.1,NONE MockHttpSession.java,1.1,NONE MockHttpServletResponse.java,1.1,NONE MockHttpServletRequest.java,1.1,NONE

[Steve F. <sm...@us...>]

Update of /cvsroot/mockobjects/mockobjects-java/src/core/com/mockobjects/servlet
In directory usw-pr-cvs1:/tmp/cvs-serv15766/src/core/com/mockobjects/servlet

Removed Files:
      Tag: restructured_for_versions_and_libraries
	MockServletOutputStream.java MockRequestDispatcher.java 
	MockHttpSession.java MockHttpServletResponse.java 
	MockHttpServletRequest.java 
Log Message:
Started restructuring for multiple library versions

--- MockServletOutputStream.java DELETED ---

--- MockRequestDispatcher.java DELETED ---

--- MockHttpSession.java DELETED ---

--- MockHttpServletResponse.java DELETED ---

--- MockHttpServletRequest.java DELETED ---

[MO-java-dev] CVS: mockobjects-java/src/core/com/mockobjects/jms MockTextMessage.java,1.1,NONE MockTemporaryQueue.java,1.1,NONE MockSession.java,1.1,NONE MockQueueSession.java,1.1,NONE MockQueueSender.java,1.1,NONE MockQueueReceiver.java,1.1,NONE MockQueueConnectionFactory.java,1.1,NONE MockQueueConnection.java,1.1,NONE MockQueue.java,1.2,NONE MockMessageProducer.java,1.1,NONE MockMessageConsumer.java,1.1,NONE MockMessage.java,1.1,NONE MockConnection.java,1.1,NONE

[Steve F. <sm...@us...>]

Update of /cvsroot/mockobjects/mockobjects-java/src/core/com/mockobjects/jms
In directory usw-pr-cvs1:/tmp/cvs-serv15766/src/core/com/mockobjects/jms

Removed Files:
      Tag: restructured_for_versions_and_libraries
	MockTextMessage.java MockTemporaryQueue.java MockSession.java 
	MockQueueSession.java MockQueueSender.java 
	MockQueueReceiver.java MockQueueConnectionFactory.java 
	MockQueueConnection.java MockQueue.java 
	MockMessageProducer.java MockMessageConsumer.java 
	MockMessage.java MockConnection.java 
Log Message:
Started restructuring for multiple library versions

--- MockTextMessage.java DELETED ---

--- MockTemporaryQueue.java DELETED ---

--- MockSession.java DELETED ---

--- MockQueueSession.java DELETED ---

--- MockQueueSender.java DELETED ---

--- MockQueueReceiver.java DELETED ---

--- MockQueueConnectionFactory.java DELETED ---

--- MockQueueConnection.java DELETED ---

--- MockQueue.java DELETED ---

--- MockMessageProducer.java DELETED ---

--- MockMessageConsumer.java DELETED ---

--- MockMessage.java DELETED ---

--- MockConnection.java DELETED ---

[MO-java-dev] CVS: mockobjects-java build.xml,1.16,1.16.2.1 build.properties.sample,1.4,1.4.2.1

[Steve F. <sm...@us...>]

Update of /cvsroot/mockobjects/mockobjects-java
In directory usw-pr-cvs1:/tmp/cvs-serv15585

Modified Files:
      Tag: restructured_for_versions_and_libraries
	build.xml build.properties.sample 
Log Message:
Started restructuring for multiple library versions

Index: build.xml
===================================================================
RCS file: /cvsroot/mockobjects/mockobjects-java/build.xml,v
retrieving revision 1.16
retrieving revision 1.16.2.1
diff -u -r1.16 -r1.16.2.1
--- build.xml	2002/01/09 15:08:00	1.16
+++ build.xml	2002/01/09 17:58:55	1.16.2.1
@@ -36,12 +36,11 @@
 -->
 <project name="mockobjects" default="jar" basedir=".">
 
-    <!-- Give user a chance to override without editing this file
-         (and without typing -D each time it compiles it) -->
+    <!-- Local customizations -->
     <property file="${user.home}/build.properties" />
     <property file="build.properties" />
 
-    <!-- Generic project properties -->
+    <!-- Project description -->
     <property name="project.fullname" value="Mock Objects"/>
     <property name="project.version" value="0.02"/>
     <property name="project.name" value="mockobjects"/>
@@ -53,29 +52,20 @@
     <property name="deprecation" value="off"/>
     <property name="package.prefix" value="com/mockobjects/"/>
 
-    <!--
-       ========================================================================
-         Set the properties related to the source tree
-       ========================================================================
-    -->
-    <!-- Source locations for the build -->
+    <!-- Source properties -->
     <property name="src.dir" value="src"/>
     <property name="src.core.dir" value="${src.dir}/core"/>
     <property name="src.examples.dir" value="${src.dir}/examples"/>
     <property name="src.extensions.dir" value="${src.dir}/extensions"/>
+    <property name="src.j2ee.dir" value="${src.dir}/j2ee"/>
     <property name="conf.dir" value="conf"/>
     <property name="doc.dir" value="doc"/>
     <property name="xdoc.dir" value="${doc.dir}/xdocs"/>
     <property name="skin.dir" value="${doc.dir}/skins"/>
     <property name="lib.dir" value="lib"/>
 
-    <!--
-       ========================================================================
-         Set the properties related to the build area
-       ========================================================================
-    -->
-    <!-- Destination locations for the build (relative to the basedir as
-         specified in the basedir attribute of the project tag) -->
+    <!-- Build output properties -->
+    <!-- (relative to the basedir attribute of the project) -->
     <property name="out.dir" value="out"/>
     <property name="out.doc.dir" value="${out.dir}/doc"/>
     <property name="out.javadoc.dir" value="${out.doc.dir}/javadoc"/>
@@ -85,22 +75,17 @@
     <property name="out.src.core.dir" value="${out.src.dir}/core"/>
     <property name="out.src.examples.dir" value="${out.src.dir}/examples"/>
     <property name="out.src.extensions.dir" value="${out.src.dir}/extensions"/>
+    <property name="out.src.j2ee.dir" value="${out.src.dir}/j2ee"/>
     <property name="out.conf.dir" value="${out.dir}/conf"/>
     <property name="out.xdoc.doc.dir" value="${out.dir}/xdoc/doc"/>
     <property name="out.xdoc.site.dir" value="${out.dir}/xdoc/site"/>
 
-    <!--
-       ========================================================================
-         Default values for properties not defined in build.properties
-       ========================================================================
-    -->
+    <!-- Defaults for properties not defined in build.properties -->
     <property name="dist.dir" value="dist"/>
 
-    <!--
-       ========================================================================
-        Short names of deliverables
-       ========================================================================
-    -->
+    <!-- ============================================================
+         Short names of deliverables
+     -->
 
     <!-- The project jar -->
     <property name="jar.name" value="${project.name}"/>
@@ -118,12 +103,11 @@
     <!-- The project zip which contains the jar + doc + samples -->
     <property name="dist.name" value="${project.name}-${project.version}"/>
 
-    <!--
-       ========================================================================
+    <!-- ============================================================
          Useful file patterns for targets
-       ========================================================================
-    -->
-    <!-- All source files of the projet. These source files will be copied
+      -->
+
+    <!-- All source files of the project. These source files will be copied
          to the destination source directory in the prepare task -->
     <patternset id="all.src.files">
 
@@ -151,12 +135,11 @@
 
     </patternset>
 
-    <!--
-       ========================================================================
-         Check to see what libraries are available in order to decide what
-         mock implementation will be built
-       ========================================================================
-    -->
+    <!-- ============================================================
+         Decide which mock implementations to build depending on which
+         libraries are available.
+      -->
+
     <path id="lib.classpath">
         <fileset dir="${lib.dir}">
             <include name="*.jar"/>
@@ -164,27 +147,19 @@
     </path>
 
     <target name="check.availabilities">
-
-        <available property="servlet.present"
-            classname="javax.servlet.Servlet"
-            classpathref="lib.classpath"/>
-
-        <available property="jms.present"
-            classname="javax.jms.Message"
-            classpathref="lib.classpath"/>
-
+        <available file="${j2ee12.jar.file}" property="j2ee12.jar.present"/>
+        <available file="${j2ee13.jar.file}" property="j2ee13.jar.present"/>
     </target>
 
-    <!--
-       ========================================================================
+    <!-- ============================================================
          Initialize the build. Must be called by all targets
-       ========================================================================
-    -->
+      -->
+
     <target name="init" depends="check.availabilities">
 
         <tstamp/>
 
-        <echo message="--------- ${project.fullname} ${project.version} ---------"/>
+        <echo message="-- ${project.fullname} ${project.version} --"/>
         <echo message=""/>
 
         <echo message="java.class.path = ${java.class.path}"/>
@@ -198,48 +173,52 @@
         <filter token="version" value="${project.version}"/>
         <filter token="year" value="${year}"/>
         <filter token="today" value="${TODAY}"/>
-
     </target>
-
-    <!--
-       ========================================================================
-         Prepare the output directory by copying the source files into it
-       ========================================================================
-    -->
-    <target name="prepare" depends="init">
 
+    <!-- ============================================================
+         Prepare the output directory by copying the source files into it.
+	 Apply filters to replace the tokens for the version
+      -->
+
+    <target name="prepare-java-core" depends="init">
+        <delete dir="${out.src.dir}"
+	        quiet="yes" />
         <mkdir dir="${out.src.dir}"/>
 
-        <!-- Copy all source files to destination dir. Apply the filters in
-             order to replace the tokens for the version -->
         <copy todir="${out.src.dir}" filtering="on">
             <fileset dir="${src.core.dir}">
                 <patternset refid="all.src.files"/>
             </fileset>
-            <!--fileset dir="${src.extensions.dir}">
+        </copy>
+    </target>
+
+    <target name="prepare-java-j2ee12" 
+            depends="prepare-java-core"
+            if="j2ee12.jar.present" >
+        <copy todir="${out.src.dir}" filtering="on">
+            <fileset dir="${src.j2ee.dir}">
                 <patternset refid="all.src.files"/>
             </fileset>
-            <fileset dir="${src.examples.dir}">
-                <patternset refid="all.src.files"/>
-            </fileset-->
         </copy>
-
+	<property name="j2ee.jar.location" value="${j2ee12.jar.file}" />
     </target>
 
-    <!--
-       ========================================================================
-         Compiles the source directory
-       ========================================================================
-    -->
-    <!-- Preparation target for the compile target -->
-    <target name="prepare-compile" depends="prepare">
+    <target name="prepare-java" 
+            depends="prepare-java-core, prepare-java-j2ee12" />
 
+    <!-- ============================================================
+         Compile the source directory
+      -->
+    <!-- Preparation target for the compile target -->
+    <target name="prepare-compile" depends="prepare-java">
+        <delete dir="${out.classes.dir}"
+	        quiet="yes" />
         <mkdir dir="${out.classes.dir}"/>
-
     </target>
 
-    <!-- Run the java compilation -->
-    <target name="compile" depends="prepare-compile">
+    <target name="compile" 
+            depends="prepare-compile"
+	    description="Prepare and compile the java classes">
 
         <javac srcdir="${out.src.dir}"
             destdir="${out.classes.dir}"
@@ -247,23 +226,9 @@
             deprecation="${deprecation}"
             optimize="${optimize}">
 
-            <!-- Exclude all files that are not .java source files -->
-
-            <!-- All doc files -->
-            <exclude name="**/package.html"/>
-            <exclude name="**/overview.html"/>
-
-            <!-- All conf files (including test files) -->
-            <exclude name="**/*.txt"/>
-            <exclude name="**/*.xml"/>
-            <exclude name="**/*.properties"/>
-
-            <!-- Exclude all java files for which no library is present -->
-            <exclude name="${package.prefix}/servlet/**" unless="servlet.present"/>
-            <exclude name="${package.prefix}/jms/**" unless="jms.present"/>
-
             <classpath>
                 <path refid="lib.classpath"/>
+                <pathelement path="${j2ee.jar.location}" />
                 <pathelement path="${java.class.path}"/>
             </classpath>
 
@@ -274,21 +239,22 @@
             <fileset dir="${src.core.dir}">
                 <patternset refid="all.nonjava.files"/>
             </fileset>
+<!--
             <fileset dir="${src.examples.dir}">
                 <patternset refid="all.nonjava.files"/>
             </fileset>
             <fileset dir="${src.extensions.dir}">
                 <patternset refid="all.nonjava.files"/>
             </fileset>
+ -->
         </copy>
 
     </target>
 
-    <!--
-       ========================================================================
+    <!-- ============================================================
          Create the runtime jar file
-       ========================================================================
-    -->
+      -->
+
     <!-- Preparation target for the jar target -->
     <target name="prepare-jar" depends="compile">
 
@@ -309,20 +275,17 @@
 
         <jar jarfile="${out.dir}/${jar.name}.jar"
             manifest="${out.conf.dir}/manifest">
-
             <fileset dir="${out.classes.dir}"/>
-
         </jar>
 
     </target>
 
-    <!--
-       ========================================================================
+    <!-- ============================================================
          Generate the javadoc
-       ========================================================================
     -->
+
     <!-- Preparation target for the javadoc target -->
-    <target name="prepare-javadoc" depends="prepare">
+    <target name="prepare-javadoc" depends="prepare-java">
 
         <mkdir dir="${out.javadoc.dir}"/>
 
@@ -334,9 +297,10 @@
 
     </target>
 
-    <!-- Generate the javadoc for the current Servlet API -->
-    <target name="javadoc" depends="prepare-javadoc"
-        unless="javadoc.notrequired">
+    <target name="javadoc" 
+            depends="prepare-javadoc"
+            unless="javadoc.notrequired"
+	    description="Generate the javadoc for the mockobjects" >
 
         <javadoc
             sourcepath="${out.src.dir}"
@@ -372,10 +336,8 @@
 
     </target>
 
-    <!--
-       ========================================================================
+    <!-- ============================================================
          Generate the full documentation, i.e. web site + javadoc
-       ========================================================================
     -->
     <target name="prepare-doc" depends="javadoc">
 
@@ -418,10 +380,9 @@
 
     </target>
 
-    <!-- Generate the documentation -->
     <target name="doc" depends="prepare-doc"
         unless="stylebook.doc.notrequired"
-        description="generate the documentation">
+        description="Generate the documentation">
 
         <!-- Generate the documentation web site -->
         <stylebook book="${out.xdoc.doc.dir}/book.xml"
@@ -436,11 +397,10 @@
 
     </target>
 
-    <!--
-       ========================================================================
+    <!-- ============================================================
          Generate the web site
-       ========================================================================
     -->
+
     <target name="prepare-site" depends="init">
 
         <mkdir dir="${out.xdoc.site.dir}"/>
@@ -514,11 +474,10 @@
 
     </target>
 
-    <!--
-       ========================================================================
+    <!-- ============================================================
          Run the unit tests
-       ========================================================================
     -->
+
     <target name="test" depends="compile"
         description="run the unit tests">
 
@@ -543,40 +502,39 @@
 
     </target>
 
-    <!--
-       ========================================================================
+    <!-- ============================================================
          Remove all build generated files
-       ========================================================================
     -->
-    <target name="clean" depends="init"
-        description="clean up all generated files">
+
+    <target name="clean" 
+            depends="init"
+            description="Clean up all generated files">
 
-        <delete>
+        <delete quiet="yes">
             <fileset dir=".">
                 <include name="**/*.bak"/>
             </fileset>
         </delete>
 
         <!-- Deletes all files ending with '~' -->
-        <delete>
+        <delete quiet="yes">
             <fileset dir="." includes="**/*~" defaultexcludes="no"/>
         </delete>
 
         <!-- Remove the out directory -->
-        <delete dir="${out.dir}"/>
-
+        <delete dir="${out.dir}"
+	        quiet="yes"/>
     </target>
 
-    <!--
-       ========================================================================
+    <!-- ============================================================
          Create the distributables
-       ========================================================================
     -->
+
     <target name="prepare-dist" depends="jar,doc">
         <mkdir dir="${dist.dir}"/>
     </target>
 
-    <target name="ZipJavaSources" depends="prepare">
+    <target name="ZipJavaSources" depends="prepare-java">
       <zip zipfile="${out.dir}/${src.name}.zip"
            basedir="${out.src.dir}" />
     </target>
@@ -596,24 +554,20 @@
 
     </target>
 
-    <!--
-       ========================================================================
+    <!-- ============================================================
          Do it all
-       ========================================================================
     -->
     <target name="all" depends="clean,jar,doc,test,site,dist"
         description="do it all (clean, jar, doc, test, site)">
     </target>
 
-    <!--
-       ========================================================================
+    <!-- ============================================================
          Deploy the web site to SourceForge, using the 'scp'
          and 'ssh' commands. The variable "username" need to be passed to Ant
          when calling this target and represent your username on SourceForge.
 
          Ex: ant -Dusername=vmassol deploy-site
 
-       ========================================================================
     -->
     <target name="deploy-site" depends="clean,site" if="username"
         description="deploy the web site to SourceForge (see target for details)">
@@ -632,11 +586,9 @@
 
     </target>
 
-    <!--
-       ========================================================================
+    <!-- ============================================================
          Formats the source code using JRefactory Pretty Printer. The
          JRefactory jar need to be place in ${ANT_HOME}/lib.
-       ========================================================================
     -->
     <target name="format" depends="init"
         description="reformats all java code">
@@ -653,3 +605,4 @@
     </target>
 
 </project>
+

Index: build.properties.sample
===================================================================
RCS file: /cvsroot/mockobjects/mockobjects-java/build.properties.sample,v
retrieving revision 1.4
retrieving revision 1.4.2.1
diff -u -r1.4 -r1.4.2.1
--- build.properties.sample	2001/11/05 00:12:13	1.4
+++ build.properties.sample	2002/01/09 17:58:55	1.4.2.1
@@ -9,3 +9,9 @@
 # You can also change your libraries directory. If none is specified here, it
 # will default to 'lib'
 #lib.dir = lib
+
+# J2EE libraries. 
+# Set up an entry here for each version of the J2EE libraries 
+# you would like to build.
+# j2ee12.jar.file=D:/Java/j2sdkee1.2.1/lib/j2ee.jar
+# j2ee13.jar.file=D:\Java\j2sdkee1.3\lib\j2ee.jar

[MO-java-dev] CVS: mockobjects-java/dist - New directory

[Steve F. <sm...@us...>]

Update of /cvsroot/mockobjects/mockobjects-java/dist
In directory usw-pr-cvs1:/tmp/cvs-serv11949/dist

Log Message:
Directory /cvsroot/mockobjects/mockobjects-java/dist added to the repository
--> Using per-directory sticky tag `restructured_for_versions_and_libraries'

[MO-java-dev] CVS: mockobjects-java build.xml,1.15,1.16

[Steve F. <sm...@us...>]

Update of /cvsroot/mockobjects/mockobjects-java
In directory usw-pr-cvs1:/tmp/cvs-serv22471

Modified Files:
	build.xml 
Log Message:
changed the year and some comments

Index: build.xml
===================================================================
RCS file: /cvsroot/mockobjects/mockobjects-java/build.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- build.xml	2001/11/05 00:11:51	1.15
+++ build.xml	2002/01/09 15:08:00	1.16
@@ -4,6 +4,15 @@
   =============================================================================
     Build file for the mockobjects project.
 
+    The following Ant tasks must be available in your ant installation
+    (i.e. the Ant task themselves and their dependent jars need to be put
+    in ANT_HOME/lib) :
+
+        stylebook             [REQUIRED] For builing the documentation and
+                               web site.
+
+        junit                 [REQUIRED] For running the unit tests.
+
     The following properties need to be set in a ./build.properties or
     or ${user.home}/build.properties file :
 
@@ -15,13 +24,9 @@
     Depending on what mock implementation you wish to build you'll need to
     put associated jars in <root>/lib. For example, if you wish to build
     the servlet mock implementation you'll need to put the Servlet API jar
-    in <root>/lib. If it not there, then the servelt mock implementation will
+    in <root>/lib. If it not there, then the servlet mock implementation will
     simply not be built.
 
-    Note: You'll also need to have the 'junit' and 'stylebook' tasks defined
-    in your Ant installation for running the unit tests and the documentation
-    and web site generation.
-
     This script should be started with the following command line :
 
         ant <target>
@@ -42,7 +47,7 @@
     <property name="project.name" value="mockobjects"/>
 
     <!-- Miscellaneous settings -->
-    <property name="year" value="2001"/>
+    <property name="year" value="2002"/>
     <property name="debug" value="on"/>
     <property name="optimize" value="off"/>
     <property name="deprecation" value="off"/>
@@ -400,6 +405,7 @@
         <copy todir="${out.doc.dir}">
             <fileset dir="${xdoc.dir}">
                 <include name="misc/*.pdf"/>
+                <include name="papers/**"/>
             </fileset>
         </copy>
 

RE: [MO-java-dev] Multi Prepared Statement MockConnections

[Oskar H. <osk...@de...>]

We here at DeCode inc. have already implemented multiple PreparedStatements
for MockConnection and it is working fine.
I have not been able to commit this code because I can't find any guidelines
on how to do so.
I posted a question to 'moc...@li...'
but have not got any answer yet.
Can anyone give me a hint on how to post this code.
Regards
Oskar H.


-----Original Message-----
From: moc...@li...
[mailto:moc...@li...]On Behalf Of
Robert Manning
Sent: 9. januar 2002 02:28
To: moc...@li...
Subject: [MO-java-dev] Multi Prepared Statement MockConnections


I see that someone (smgf) checked in work on MockConnection in the "core"
module 9/19/2001.  Yet it appears unfinished and is obviously not in the
latest build posted 8/21/2001.  Any idea when this will get released?  What
I need to have is the ability to track close calls on multiple
PreparedStatements that are being prepared within a single method from the
same Connection.    One thing that's missing in the current implementation
is the ability to associate close calls with a particular PreparedStatement
(I guess using the SQL as an index into the HashMap).  Or maybe I'm totally
off the Mark and you can set me straight ??

Rob Manning

_______________________________________________
Mockobjects-java-dev mailing list
Moc...@li...
https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev

[MO-java-dev] Multi Prepared Statement MockConnections

[Robert M. <man...@te...>]

I see that someone (smgf) checked in work on MockConnection in the "core" m=
odule 9/19/2001.  Yet it appears unfinished and is obviously not in the lat=
est build posted 8/21/2001.  Any idea when this will get released?  What I =
need to have is the ability to track close calls on multiple PreparedStatem=
ents that are being prepared within a single method from the same Connectio=
n.    One thing that's missing in the current implementation is the ability=
 to associate close calls with a particular PreparedStatement (I guess usin=
g the SQL as an index into the HashMap).  Or maybe I'm totally off the Mark=
 and you can set me straight ??

Rob Manning

Re: [MO-java-dev] MO for SAX API

[Steve F. <st...@ok...>]

Alexander Thomas <ale...@gm...> said: 
> Hi gents, 
> I would like to use mock objects for testing some SAX2 related 
code. However
> I could not find the corresponding classes on the 
www.mockobjects.com page.
> Are there already some SAX MO available (esp. 
ContentHandlerMockObject)? If
> not I would voluntear to contrubute...

There are none at present. A contribution would be most welcome. 
I'm away from home at the moment, but will be back online next week.

Steve

[MO-java-dev] MO for SAX API

[Alexander T. <ale...@gm...>]

Hi gents,

I would like to use mock objects for testing some SAX2 related code. However
I could not find the corresponding classes on the www.mockobjects.com page.
Are there already some SAX MO available (esp. ContentHandlerMockObject)? If
not I would voluntear to contrubute...

Regards, 

Alexander Thomas
 

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

RE: [MO-java-dev] Need help on MockObjects !!!

[Tim M. <tim...@po...>]

Just to clarify a small point - of course you can use MockObjects to
populate the state of many objects - we do this for some of our "system
tests" were we want to run a little more end to end (note these are not
acceptance tests - something inbetween where we are testing linkages between
objects).

By passing values in - there is no reason why some master object high up in
your chain can't be given a load of populated mock objects so that you can
have a more end to test running. If you want that to be something that you
look at in a browser that should be fine. Just remember that you mock
objects are very basic objects that don't do much. If you find yourself
adding extra behavior to them so that you can view different things in the
browser then you are going beyond the bounds of mock objects and are
probably writing a simple database. Of course you can take the basic mock
implementations and turn them into something else - just please dont confuse
everyone by calling it a mock database.

Just use some common sense with this stuff and you should be ok.

Tim
> -----Original Message-----
> From: moc...@li...
> [mailto:moc...@li...]On Behalf Of
> Steve Freeman
> Sent: 14 December 2001 10:54 am
> To: moc...@li...
> Cc: ra...@re...
> Subject: Re: [MO-java-dev] Need help on MockObjects !!!
>
>
>
> Radirs <ra...@re...> said:
> >   Iam using MockObjects in our project. We have made a mock system
> > (database) and are populating this MO by inputting data in to the
> > MockResultSet and stuff like that.And all these MO codes resides
> in the test
> > method of the test class(written for the class under test) and
> the test is
> > working fine.
>
> That's nice to hear.
>
> > Requirement :
> >     To get the data from the Mock system (remember the MO
> > coding[instantiation and initialization] is done in the test
> class) and
> > display on to the browser using jsp's.(similar to getting the
> values from
> > the database and displaying on to the screen).
>
> What do you want to test by viewing JSP's in a browser? This sounds
> more like an integration test. The MO approach is intended for unit
> testing individual classes, or small clusters of classes. If you
> want a substitute database, there's one included in the mock
> objects extensions source tree as well as other options such as
> cloudscape.
>
> > My Questions are :
> > 1) Is there any way this(refer Requirement) can be done?if yes,
> How this can
> > be accomplished?
> > 2) Are there any steps to be followed ,specific to MO,if we need
> to
> > integrate MO into any propreitary framework?
>
> I don't understand what this means. Could you give me an example?
>
> Steve
>
>
>
> _______________________________________________
> Mockobjects-java-dev mailing list
> Moc...@li...
> https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev
>

Re: [MO-java-dev] Need help on MockObjects !!!

[<kr...@da...>]

Steve:
  Thanks for ur reply. 
Your Question:
"What do you want to test by viewing JSP's in a browser?"
Answer: I wanted to know whether i can reuse the data 
which i have intialized in the mockobjects as a 
substitute for database.( for which u have replied that 
it cant be done).

You have also said abt a substitute database in "mock 
objects extensions source tree". 
Where can i find this ?


Thanks,
Kris.

Re: [MO-java-dev] Need help on MockObjects !!!

[<kr...@da...>]

Steve:
  Thanks for ur reply. 
Your Question:
"What do you want to test by viewing JSP's in a browser?"
Answer: I wanted to know whether i can reuse the data 
which i have intialized in the mockobjects as a 
substitute for database.( for which u have replied that 
it cant be done).

You have also said abt a substitute database in "mock 
objects extensions source tree". 
Where can i find this ?


Thanks,
Kris.

Re: [MO-java-dev] Need help on MockObjects !!!

[Steve F. <st...@ok...>]

Radirs <ra...@re...> said: 
>   Iam using MockObjects in our project. We have made a mock system
> (database) and are populating this MO by inputting data in to the
> MockResultSet and stuff like that.And all these MO codes resides 
in the test
> method of the test class(written for the class under test) and 
the test is
> working fine.

That's nice to hear.
 
> Requirement : 
>     To get the data from the Mock system (remember the MO
> coding[instantiation and initialization] is done in the test 
class) and
> display on to the browser using jsp's.(similar to getting the 
values from
> the database and displaying on to the screen).

What do you want to test by viewing JSP's in a browser? This sounds 
more like an integration test. The MO approach is intended for unit 
testing individual classes, or small clusters of classes. If you 
want a substitute database, there's one included in the mock 
objects extensions source tree as well as other options such as 
cloudscape.
 
> My Questions are : 
> 1) Is there any way this(refer Requirement) can be done?if yes, 
How this can
> be accomplished?
> 2) Are there any steps to be followed ,specific to MO,if we need 
to
> integrate MO into any propreitary framework?

I don't understand what this means. Could you give me an example?

Steve