xmlwiki-developers — xmlWiki developers list

[xmlWiki-developers] No more CVS passwords

[Jim K. <ka...@ie...>]

If you guys are as weary as I was from entering your Sourceforge password
for every little CVS action, you'll be glad to know that the public key file
solution does work.  The Sourceforge docs tell you roughly how to do it, but
it still takes a little work.  You'll probably have to use my linux box to
create the ID files with ssh-keygen since the Windows versions are broken.
But once you get through that, you will never need to enter your password
again and man is it sweet...  Give it a try.

Regards,
Jim

[xmlWiki-developers] A better build.xml

[Jim K. <ka...@ie...>]

I've made changes to the 'deploy' target so the entire directory hierarchy
under Tomcat and its config files will be set up properly.  What this means
is that if you have all of the necessary JARS and your classpath is in
order, 'ant deploy' should completely setup our application for you. You
should be able to start Tomcat and point your browser to:
http://127.0.0.1:8080/xmlWiki to begin using the app.  One caveat:  Tomcat's
server.xml and web.xml are merely copied over, so any changes you've made to
those files will be lost.  If there is a need to make backups, we can look
at that later.

Hopefully this will help ensure that everyone's directory tree and Tomcat
config is in sync.  Of course, I've only tried this on my own system, so
please report (or fix) any problems you encounter.


Regards,
Jim

[xmlWiki-developers] CVS status

[Jim K. <ka...@ie...>]

The latest versions of the files in CVS will probably not work correctly.  I
will fix this tonight.  The source code is fine, but I haven't had time to
add the special 'web.xml' customization you'll need for Tomcat to run
properly.

Radu:  Diff the latest versions of your two files...  I think you'll be
kicking yourself when you see why the path was always wrong.
Hugo and Chris:  I modified 'build.xml' to exclude your files since they
don't compile.  Once they do, feel free to undo that exclusion.

Later,
Jim

[xmlWiki-developers] Fw: What do you think of the following?

[Arnaldo C. <ar...@mi...>]

Almost forgot that Hugo asked me to forward this to the group during our
meeting last night.
--Arnaldo
----- Original Message -----
From: "Hugo Garcia" <xm...@ne...>
To: <ar...@mi...>
Sent: Wednesday, November 14, 2001 2:03 PM
Subject: Re: What do you think of the following?


> around Tuesday, November 13, 2001, 5:09:48 PM, Laurent Bossavit wrote:
>
>
>  > I'd like to ask for more information on this from Ron, or anyone
>  > who's had experience providing XP coaching services or XP-related
>  > consulting services : exactly what does a "professional" XP coach do,
>  > and how does he/she work ?
>
>
> Project assessments: look at the process and see how people are doing,
> what the consultant observes, recommendations.
>
> Coaching: close in, essentially daily presence, supporting the
> process, teaching the process over and over, helping to adjust.
>
> Coaching: visits every couple of weeks or a month, typically at
> iteration end/begin, observe results, help with retrospectives, help
> figure out what happened and what to do about it.
>
> Mentoring: help team learn specific techniques, pair programming, OO
> design, language, tools, ...
>
>
>  > Are you usually called upon specifically to coach teams in XP, or to
>  > provide other consulting services ?
>
>
> Most good consultants see their job as helping, not pushing a specific
> practice, so they will provide whatever help they can in whatever
> form. This will typically be consistent with the basic values of the
> consultant. So don't expect me to help you get to CMM 5.
>
>
>  > Who decides to retain an XP
>  > coach, and for what reasons ?
>
>
> Someone in management who can write a large check. (No, not kidding,
> this stuff is fairly expensive. Even a couple of days of a junior XP
> coach would cost a few thousand dollars.)
>
> Usually in my experience someone one or more levels above a small
> group project manager. Often CTO or equivalent.
>
>
>  > Do you usually start by diagnosing the
>  > existing process, or other aspects of the business such as management
>  > style and structure, or just get right down to coaching in the
>  > practices ?
>
>
> Depends. I think an assessment is always appropriate. If one isn't
> done up front, the consultant will be building it incrementally over
> time anyway ...
>
>
>  > How long, typically, are such coaching engagements - what do you
>  > usually expect to achieve over these periods ?
>
>
> All over the map, from a one-week immersion course to 90 or 180 days
> of full-time or nearly full-time coaching.
>
> Achievements from "provide information or training" to "get us actually
> doing XP" to "get us as productive as we can be".
>
>
>  > Are there cases where
>  > you'd recommend against installing XP ?
>
>
> Yes. Mostly social issues like desire to develop the software
> offshore. Usually complex questions. Often XP needs to be customized,
> which is one of the biggest values of a very experienced coach.
>
>
>  > E.g. is there a minimum of
>  > team expertise required in, say, OO design or coding for the
>  > engagement to be worthwhile ?
>
>
> Total dolts are probably not a productive target. If they can program
> competently, they probably are. Some technical training might be
> recommended as things go on.
>
> How's that for an off-the-top-of-the-head reply? Does it help?
>
> Ron Jeffries
> www.XProgramming.com
> XP says: Don't just sit on your DUF, do something. Get some feedback.
>
> AND =================================
>
> Speaking of XP consultants, isn't *anyone* going to answer my
>  >questions about what XP consultants actually do ? I'll repost them
>  >for easy reference :
>
>
> Laurant,
>
> We coach rather than consult.  For many folks, coaching implies team while
> consulting implies high prices and little results.
>
> We do something called the Agility Assessment
> (http://industriallogic.com/xp/assessment.html).   We recommend this
> service to companies that are considering going agile or extreme.  It is a
> good way for them to explore whether or not they could have success with
an
> agile method.  We negotiate the number of days needed for the assessment -
> which can vary from 2 days to 2 weeks.  As a case in point, I just spoke
> with a company about doing this service after it became clear that they
> were very interested in xp, but weren't sure they could do it.  They
agreed
> to purchase the assessment.  I expect that it will help them decide how
> best to proceed through the agile landscape.
>
> We also provide a service called the Extreme Exchange
> (http://industriallogic.com/xp/exchange.html) in which two of us coach a
> team for weeks at a time.  Our goal is to help the team fully implement
the
> xp practices and mentor a new coach so we can move on.  We find that by
> pair-coaching, we're smarter than any one of us.   We've had good results
> with this service.
>
> Professional coaching also involves knowing when a company needs or
doesn't
> need training.  When they do, two of us (who've coached and programmed on
> xp projects) coach a team through 5 intensive days of xp training --
called
> The eXtreme Programming Workshop
> (http://industriallogic.com/training/xpw.html).   We continue to not offer
> a 1-day or 2-day or smaller version of this workshop, because most teams
> need 5 full days to really get it.  We also find that the games and
> simulations we use in the workshop help people educate their colleagues
who
> could not attend the training.
>
> Finally, we've speculated that companies could use help on
> Release/Iteration planning or Iteration Retrospectives - but to date, we
> haven't had takers for those services.
>
> hope that helps,
> jk
>
> I n d u s t r i a l  L o g i c , I n c .
> Joshua Kerievsky
> Founder, Extreme Programmer & Coach
> http://industriallogic.com
> 510-540-8336
>
>
>
> ar...@mi... wrote:
>
> > Well, I must say that my vote would be for Jim.  I think he's already
> > basically doing the job.  But, I think it's certainly worth bringing up.
> > ----- Original Message -----
> > From: "Hugo Garcia" <xm...@ne...>
> > To: <ar...@mi...>
> > Sent: Wednesday, November 14, 2001 1:28 PM
> > Subject: Re: What do you think of the following?
> >
> >
> >
> >>Well, I will leave it to your discression to decide if you want to
> >>forward to the group email or if you want to bring it up in the group
> >>discussion.
> >>
> >>Something in the lines as :
> >>
> >>Hugo stays as Customer and Developer (we are one odd person in the
> >>group) which seems to work. Someone else take the role of coach. Mi vote
> >>goes for Arnaldo.
> >>
> >>-H
> >>
> >>ar...@mi... wrote:
> >>
> >>
> >>>Hugo,
> >>>    I think that there is defintely some strong cause for consideration
> >>>
> > in
> >
> >>>your thoughts, and that (if you're OK with it) we should discuss this
> >>>tomorrow night with the entire group.  If people agree with you, the
> >>>
> > logical
> >
> >>>outcome would be to assign someone else to be coach (while you continue
> >>>
> > as
> >
> >>>customer) and this is something that is certainly up to the group to
> >>>
> > decide.
> >
> >>>--Arnaldo
> >>>----- Original Message -----
> >>>From: "Hugo Garcia" <xm...@ne...>
> >>>To: <ar...@mi...>
> >>>Sent: Wednesday, November 14, 2001 7:50 AM
> >>>Subject: What do you think of the following?
> >>>
> >>>
> >>>
> >>>
> >>>>One way of making the customer responsible.
> >>>>
> >>>>My argument is particular to projects that are started by a developer
or
> >>>>a group of developers where there is no non technical customer. I
think
> >>>>that as long as the developer who is wearing the customer hat makes
sure
> >>>>to write the user stories AND to write the acceptance test before she
> >>>>goes ahead to code will be able to start on the path of having the
> >>>>self-dicipline to stick to XP.
> >>>>
> >>>>If there is a team of developers then it seems that the best bet is to
> >>>>assign a Developer to be a Customer and another to be a Coach. Mixing
> >>>>the roles doesn't seem to work because the Customer/Coach duality
gives
> >>>>to much power to one person (leading to such nasties as
> >>>>micro-management). But, curiosly enough the developer that is the
> >>>>Customer can succesfully pair program as long as that developer does
not
> >>>>do any large scope design. It seems that the check and balances of
> >>>>normal XP are altered and it is the check and balances of the
> >>>>distributed team that are not well categorized.
> >>>>
> >>>>-H
> >>>>
> >>>>PS I based my comment on the ongoing project I am involve in
> >>>>http://xmlwiki.sourcefore.net
> >>>>
> >>>>ron...@ac... wrote:
> >>>>
> >>>>
> >>>>>Around Tuesday, November 13, 2001, 12:00:11 PM, Bryan Dollery wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>>I think that this is a particularly dangerous practice. By agreeing
> >>>>>>
> >>>>to 'be
> >>>>
> >>>>>>the customer' a developer is absolving the customer of
> >>>>>>
> >>>>responsibility, and
> >>>>
> >>>>>>this is a bad thing.
> >>>>>>
> >>>>>>
> >>>>>I agree with your remarks. Right on!
> >>>>>
> >>>>>Ron Jeffries
> >>>>>www.XProgramming.com
> >>>>>It is not because things are difficult that we do not dare,
> >>>>>it is because we do not dare that they are difficult. --Seneca
> >>>>>
> >>>>>
> >>>>>To Post a message, send it to:   ext...@eG...
> >>>>>
> >>>>>To Unsubscribe, send a blank message to:
> >>>>>
> >>>>ext...@eG...
> >>>>
> >>>>>ad-free courtesy of objectmentor.com
> >>>>>
> >>>>>Your use of Yahoo! Groups is subject to
> >>>>>
> >>>>http://docs.yahoo.com/info/terms/
> >>>>
> >>>>>
> >>>>>
> >>>>
> >>
> >
>
>

[xmlWiki-developers] 15 Nov meeting minutes

[Arnaldo C. <ar...@mi...>]

All,
    Long (90 min) but very productive meeting:
-Iterations that have been finished: Save, Create, Preview.  Work has =
been done on Browse, but it hasn't been integrated with the rest of the =
code quite yet.
-Our project velocity would have us on track to finish Edit by the end =
of the 2nd iteration (which is also the first release, and the end of =
the semester)
-Hugo suggested that a dual-hatted Customer/Coach may not be the best =
idea; new Coach is yours truly
-Everyone, send me any thoughts you have to be included in the initial =
draft of our "reflections" document that will be turned in with our =
final artifacts
-Radu will be running meetings next week for those who are available =
during the Thanksgiving holiday; I'll be back in the saddle Nov 26th
-implementing controller module in Wiki architecture: we decided to go =
with a strategy that uses a special centralized controller servlet
-Jim wisely stressed the need to write rigorous tests before coding; one =
of the best ways to show that we're following XP.
-After much discussion, the group is going to dogpile the Edit story, =
the controller, and debugging/refactoring/integrating existing code:
    -check in code *as you go* to CVS
    -log into the xmlWiki chat room as you work to ensure that no one =
else is doing the same work as your pair simultaneously
    -hopefully "everyone being assigned everything" in this iteration =
will encourage more collective code ownership that was a bit lacking =
last iteration
    -it should also serve to enforce more frequent check-ins to CVS
    -work on Translate, etc. is extra credit: don't let it get in the =
way of the Edit story or the controller, and don't let it get in the way =
of a good book report or a good grade on your final (we want everyone to =
do well in the course, not just the project)

So, let's go get that Edit story, and the controller!  I'm on my way =
home for the Thanksgiving holidays.
-Arnaldo

[xmlWiki-developers] tonight's meeting minutes

[Arnaldo C. <arn...@ya...>]

Lots to cover tonight, but hopefully we can make it efficient:
-Check on what we've actually done by tonight's iteration deadline
-check project velocity and readjust as necessary
-next iteration planning: what do we (what does the customer) really want in
it?
-submitted by Hugo: issues regarding combined roles of Customer and Coach
-submitted by Radu: implementing controller module in Wiki architecture
     -special servlet that handles all requests and redirect them to the
appropriate servlet?
     -each servlet handles its own actions(for ex: in Preview we can have
'Save' and 'Edit')?

See you in an hour or so...
--Arnaldo


__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com

[xmlWiki-developers] Simplified servlet URL

[Jim K. <ka...@ie...>]

As the org.xmlwiki.* was added to the already-long URL, I decide to actually
read a bit about server.xml and web.xml to simplify the mapping from URL to
servlet.

Under the WEB-INF directory of the servlet in question (ie. ServletSpike),
create a 'web.xml' file with contents similar to the one I attached.  The
will map the portion of the URL after the /ServletSpike to a specific class,
like org.xmlwiki.PreviewPage.  In your 'server.xml' file in the Tomcat /conf
directory, add the following context:

<Context path="/xmlWiki"
          docBase="webapps/ServletSpike"
                 crossContext="false"
                 debug="0"
                 reloadable="true" >
</Context>

This maps everything after the base address to the proper servlet directory.
The net result of these two minor changes:

old -   http://127.0.0.1:8080/ServletSpike/servlet/org.xmlwiki.PreviewPage
new -  http://127.0.0.1:8080/xmlWiki

Much cleaner...

Enjoy,
Jim

Re: [xmlWiki-developers] Encouragement

[CS327 TA <cs3...@cs...>]

> Based on my understanding of comments Andrew has made, the vast
> majority of 327 projects find themselves far behind the schedule they
> originally anticipated meeting.

Oh, I wouldn't limit that to just student projects... ;)

 - Andrew.

[xmlWiki-developers] Radu's transformer

[Jim K. <ka...@ie...>]

Radu,

Good job on the transformer... I got it to work just fine.  About the path
though, until the bug is fixed it will look in the Tomcat startup dir, not
necessarily system32.  I had to put it under 'bin' in Tomcat.  If anyone
gets an error, they can just refer to the console stack trace and look for
the name of the file which isn't being found.  That should reveal where you
need to put it.

I'm going to add your file to CVS just so it's easier to get at.  (I suppose
you'll be checking in a newer version tonight... if nothing else the diff
will teach people how to deal with the path issue.)


Regards,
Jim

[xmlWiki-developers] Encouragement

[Arnaldo C. <ar...@mi...>]

All,
    Based on my understanding of comments Andrew has made, the vast =
majority of 327 projects find themselves far behind the schedule they =
originally anticipated meeting.  Using this as a standard of reference, =
this puts us right on track.  :)
    I don't know exactly how much of our intended first iteration will =
be ready by our internal deadline of tomorrow night's meeting, but keep =
in mind that part of XP is expecting your planning estimates to be =
wrong.  We'll reestablish our project velocity tomorrow night and plan =
accordingly.
    What are we being graded on here?  Well, a big part of what we're =
being graded on is a)how closely we followed the process, and, by what =
I've gathered from Andrew, b)how we dealt with problems as we encoutered =
them.  Note that the last item there wasn't *if* we encountered =
problems.  In corporate America (in my case, in the military), often the =
best strategy is to deal with problems without reporting them.  =
Fortunately for us, that's neither what the course staff wants nor =
expects.  On the contrary, we need to be sure and intelligently describe =
what snags we hit, and why we reacted as we did.
    Having said this, I think it would be easy for our group to get so =
focused on the code at this point that we forget to produce the other =
part of what we're being graded on.  I think that it would be very =
helpful to draft a document for the course staff that tackles, roughly, =
the following aspects of our project this semester:
-chronology
    --point-by-point progress
    --specific problems encountered
    --how we dealt with them
    --how (specifically) we stuck to or had to depart from XP
    --defense of the decisions we've made.
-obstacles/advantages that have been with us*throughout* the semester
    --how they've affected us, how we've dealt with them
-general observations about XP in geographically distributed groups
    -what XP practices become impossible?
    -what XP practices become difficult?
    -what XP practices are not affected?
    -any other "intangibles" that have affected our project?
-other musings about what we've learned this semester.
-a UML diagram of our interfaces

I'd like to volunteer to write the document described above.  (Since =
I've been summarizing our meetings, I'm probably the most logical =
candidate.)  I'd get it to the group a week and a half before we intend =
to turn it in.  That way, group members can check over it and suggest =
additions and changes.  (I'm sure there'll be many - as Johnson says, =
"Criticism is easier than Creation.")  If people can suggest all their =
changes by two or three days before the due dates for artifacts, I'll be =
able to incorporate them and have it ready to turn in.
    So, much of our success is process-oriented, rather than =
product-oriented.  Is the product unimportant?  Absolutely not - but, =
we're not expected to have a final working product by this semester's =
end; that comes in May.  Personally, I think by this semester's end we =
need a base of code that can be hacked on and refactored, and we need to =
be done with the intial planning phases, poised to continue growing our =
product.
    We can discuss some of this tomorrow night.  I look forward to our =
meeting then.
--Arnaldo

[xmlWiki-developers] Sources

[Radu D. <rd...@ly...>]

Jim,

The attachement are the files you need fr the preview page.
All you have to do is to copy the content of xikiXML.xml in the text area, save the page then preview. Always save before preview. For now.

The only problem is: wikiXSL.xsl must be in c:\winnt\system32.I'll fix the problem tonight.

For this iteration, we will have only XML->HTML transformation.
wiki<->XML will be available for the next one.We're working on it.
To run the servlet, use the same URL with your spike servlet, but replace SpikeServlet with PreviewPage.

I'll have cleaner sources for tomorrow deadline !!!!

Please disregard the coding style.
If you have questions, feel free to ask.

Regards,

Radu

Re: [xmlWiki-developers] REMINDER-Nov 15th deadline!

[Jim K. <ka...@ie...>]

Create and Save are done, and the reason they are done is because there were
done simply and probably even have a few bugs that will be ironed out later.
We're ONE DAY from our iteration deadline and I haven't seen anything the
other groups have worked on...  I somewhat doubt that things will magically
work together on the first try, but if they don't, our release will slip.
Why is everyone sitting on their code?  Despite the CVS headaches, we could
have been posting the work-to-date somewhere and been working at
integration.  Deb and I spent last weekend making up a little test program
because we didn't have much else to do.  That would have been a perfect time
to try and tie other classes together, however incomplete or dysfunction.
Function stubs will compile too!  Let the world see your imperfect code.

Hopefully we can scrape something substantive together by tomorrow, but I
think for the next release we need to greatly improve in the area of
"Collective Ownership".

Regards,
Jim


----- Original Message -----
From: Arnaldo Cavazos
To: xml...@li...
Sent: Monday, November 12, 2001 11:58 AM
Subject: [xmlWiki-developers] REMINDER-Nov 15th deadline!


Iteration 1(Create, Save, Translate, Browse, & Preview) comes out on
November 15th.

Re: [xmlWiki-developers] Help: reading file in a web app

[Jim K. <ka...@ie...>]

You have to watch your current directory closely, as its usually something
related to where you started Tomcat.  You may want to consider accessing
%TOMCAT_HOME% and building the complete path to your file by appending to
it.  I haven't found a way yet to ensure that the starting directory is
where the servlet is located.

Jim
----- Original Message -----
From: "Radu Dram" <rd...@ly...>
To: <xml...@li...>
Sent: Wednesday, November 14, 2001 12:31 AM
Subject: [xmlWiki-developers] Help: reading file in a web app


> Hi, guys.
>
> I try to read a file located in the same location with the sources for the
web app., but I can't succeed. The only way in works is if the file is in
c:\winnt\system32.
> I used getServletContext().getResourceasStream("foo.xsl") but nothing.
>
> Could you please advise?
>
> Thank you.
>
> Radu
>
>
>
> _______________________________________________
> xmlWiki-developers mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlwiki-developers
>

[xmlWiki-developers] Help: reading file in a web app

[Radu D. <rd...@ly...>]

Hi, guys.

I try to read a file located in the same location with the sources for the web app., but I can't succeed. The only way in works is if the file is in c:\winnt\system32.
I used getServletContext().getResourceasStream("foo.xsl") but nothing.

Could you please advise?

Thank you.

Radu

[xmlWiki-developers] Controller in xmlWiki architecture

[Radu D. <rd...@ly...>]

Hi, gang.

We have to decide how we implement the controller module in our wiki architecture. There may be several alternatives: we can have a special servlet that handles all requests and redirect them to the appropriate servlet or each servlet handles its own actions(for ex: in Preview we can have 'Save' and 'Edit') or ...

If you have any idea, please let us know and let's make this subject a "bullet" in our Thurday evening meeting.

Thank you.

Radu

[xmlWiki-developers] New CVS files

[Jim K. <ka...@ie...>]

I just updated CVS with a slightly modified 'build.xml' and a test servlet.
You should be able to verify that your Tomcat is working as well as test the
WikiDB function with these additions.

Use 'ant deploy' to get it going.

Jim

[xmlWiki-developers] REMINDER-Nov 15th deadline!

[Arnaldo C. <ar...@mi...>]

Iteration 1(Create, Save, Translate, Browse, & Preview) comes out on =
November 15th.

[xmlWiki-developers] Thursday's meeting minutes

[Arnaldo C. <ar...@mi...>]

-The majority of people seem to have CVS working properly.  This is =
good; we can be sure to use that to update our code baseline.  As long =
as one person in each programming pair has CVS working, things should be =
OK.
-Those who don't have CVS working can use =
http://sourceforge.net/cvs/?group_id=3D20346 for an anonymous download.
-We decided that trying to get an "official" test running on some of the =
things that our Wiki needs to do will be too much of a pain to figure =
out.  Instead, we're going to go with some "unofficial tests" for some =
of these issues.  (e.g. instead of getting a JUnit test running for =
being able to Browse from page to page, just manually try to Browse)  We =
did this in accordance with the principles of =
http://www.extremeprogramming.org/rules/fixit.html .
-We also discusssed design of the translator mechanism some.  See the =
meeting log for questions.

No one has contacted me with any agenda items for tonight.  That means =
we'll probably just get together and chat. about design, etc, however =
the conversation flows.  It'll be another "stand-up" meeting, so it =
shouldn't last long.

RE: [xmlWiki-developers] Re: Servlet Testing

[HEISTAD,CHRIS (A-USA,ex2) <chr...@ag...>]

-> -----Original Message-----
-> From: Hugo Garcia [mailto:xm...@ne...]
-> Sent: Friday, November 09, 2001 1:58 PM
-> To: xml...@li...
-> Subject: [xmlWiki-developers] Re: Servlet Testing
-> 
-> 
-> I have experience with both. More with Cactus than HttpUnit.
-> 
-> If Chris is reading this then maybe he could email you the 
-> acceptance 
-> test that we have been working on.
-> 
-> The only tricky part of cactus is setting it up. Once that 
-> is done then 
-> it is a matter of just doing regular unit tests using the junit 
-> framework. This link is a very good intro that gives you the basic 
-> working knowledge to write unitTests :
-> 
-> http://junit.sourceforge.net/doc/cookbook/cookbook.htm
-> 
-> The nice thing about Cactus is that you can do real unit 
-> testing within 
-> the servlet container. You also have access to the HttpResponse and 
-> HttpRequest objects of the servlet being tested so that those can be 
-> tested to. On the other hand HttpUnit does not run in the servlet 
-> container (although there is a way of doing so). What it is 
-> good for is 
-> for veryfying the input and output of a web app thus its 
-> usefullness in 
-> doing Acceptance tests for web apps.
-> 
-> -H
-> 
-> rd...@ly... wrote:
-> 
-> > Hi, Hugo.
-> > 
-> > I am trying to create my first "Preview" page, something 
-> basic.According to XP rule "test then write code", I should 
-> have some test for this servlet.Are we gonna use HHTPUnit or 
-> Cactus for tests?Do you have experience with both and maybe 
-> you can give us some directions?
-> > 
-> > Thank you.
-> > 
-> > Radu
-> > 
-> > 
-> > 
-> > 
-> 
-> 
-> 
-> _______________________________________________
-> xmlWiki-developers mailing list
-> xml...@li...
-> https://lists.sourceforge.net/lists/listinfo/xmlwiki-developers
-> 

[xmlWiki-developers] Re: Servlet Testing

[Hugo G. <xm...@ne...>]

I have experience with both. More with Cactus than HttpUnit.

If Chris is reading this then maybe he could email you the acceptance 
test that we have been working on.

The only tricky part of cactus is setting it up. Once that is done then 
it is a matter of just doing regular unit tests using the junit 
framework. This link is a very good intro that gives you the basic 
working knowledge to write unitTests :

http://junit.sourceforge.net/doc/cookbook/cookbook.htm

The nice thing about Cactus is that you can do real unit testing within 
the servlet container. You also have access to the HttpResponse and 
HttpRequest objects of the servlet being tested so that those can be 
tested to. On the other hand HttpUnit does not run in the servlet 
container (although there is a way of doing so). What it is good for is 
for veryfying the input and output of a web app thus its usefullness in 
doing Acceptance tests for web apps.

-H

rd...@ly... wrote:

> Hi, Hugo.
> 
> I am trying to create my first "Preview" page, something basic.According to XP rule "test then write code", I should have some test for this servlet.Are we gonna use HHTPUnit or Cactus for tests?Do you have experience with both and maybe you can give us some directions?
> 
> Thank you.
> 
> Radu
> 
> 
> 
> 

[xmlWiki-developers] [Fwd: [XP] how to show XP practices?]

[Hugo G. <xm...@ne...>]

Hey all check out this new thread in the XP list!

-H

-------- Original Message --------
Subject: [XP] how to show XP practices?
Date: Thu, 8 Nov 2001 23:29:07 -0600
From: khare <kh...@st...>
Reply-To: ext...@ya...
To: ext...@ya...

Hi All,
I am one of the students of UIUC.We are doing a class project in which 
we have
to follow XP practices.The challenge before us is to show the professor 
that
we are following the XP faithfully.

we are offcampus student and we have a university website which will mirror
that we are following XP practices.

Can any one please help me (since I am a coach for the project) how can 
I show
that we are following XP practices effectively ?
uptill now we have posted  on our website the following:
1) Metaphore
2) Iteration Plan (we have finished one Iteration)
3) UML Models
4) Release Plan (first iteration code has been released)
5) our Meeting details
6) the code for the first iteration
7) task assignment(who all will pair with whome and what task they will do)

one thing more : our actual customer is offsite and is in usa we are in 
india
, so we have chosen one of us a on site customer.
Please help me ASAP .

Amit Khare



To Post a message, send it to:   ext...@eG...

To Unsubscribe, send a blank message to: 
ext...@eG...

ad-free courtesy of objectmentor.com

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

[xmlWiki-developers] Agile Modelling

[Hugo G. <xm...@ne...>]

Haven't read through it all but it sounds interesting...

http://www.agilemodeling.com/index.htm

-H

[xmlWiki-developers] [Fwd: [XP] What is XP?]

[Hugo G. <xm...@ne...>]

-------- Original Message --------
Subject: [XP] What is XP?
Date: Thu, 8 Nov 2001 09:32:19 -0500
From: Ron Jeffries <ron...@ac...>
Reply-To: ext...@ya...
Organization: XProgramming.com
To: ext...@ya...
References: <Pin...@pa...>

I've updated www.XProgramming.com with a new article on "What is
Extreme Programming". It's a different form of overview than what I've
used before. Please take a look and provide feedback. Thanks!

Ron Jeffries
www.XProgramming.com
"How do I get to XP?"  "Practice, man, practice."


To Post a message, send it to:   ext...@eG...

To Unsubscribe, send a blank message to: 
ext...@eG...

ad-free courtesy of objectmentor.com

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

[xmlWiki-developers] A running system is needed...

[Jim K. <ka...@ie...>]

    As food for thought before we begin our Thursday meeting, I like to
offer a suggestion that we quickly get a minimally functional system running
within Tomcat as soon as possible.  We are suffering from being
geographically separated, and as a result there is virtually no integration
to speak of.  Without a running system, it's harder for people to see just
how their work fits in at a functional level.  Furthermore, our customer
cannot see the fruits of our efforts and help direct us.  From my own
experience, I'm reassured that my test cases work, but I'd really like a
real server to run them on as well.
    In order to get a real server up and running, we do need some basic
means of accepting connections and providing a response.  I'm talking about
complexity along the lines of Deb's and my spike a few weeks back (~50
lines).  This would initially let us put the create and save stories online.
As other stories wrap up, they can be tied into a real system.  I'd view
this effort as sort of a 'pre-browse' story that just supports early
development and will be thrown away once the true Browse supplants it.  If
we don't do something we face a real integration problem coming up on our
first release.  Not only will it be completely counter to XP to delay
integration for so long, it will be hard to do period.
    I'd therefore like to offer to release a couple of classes into CVS,
along with a 'deploy' target that will install the built tree under Tomcat
and allow us to really test within the context we'll eventually be running.
BTW, getting all of this stuff under Linux is not a priority since you can
all install and use Tomcat yourselves.  For everyone else's part, we need to
dig in and get CVS going across the board.  That goes for all of the other
tools as well.  I don't think there have been any check-ins from other
groups, even from those who have CVS up and running.  Don't be bashful about
checking something in that's not perfect.  It's the only way for everyone to
learn what all the groups are doing.

See you all in 8 minutes.

Regards,
Jim

[xmlWiki-developers] tonight's meeting - November 8th

[Arnaldo C. <ar...@mi...>]

Results from last meeting:
    -Turkey week will not be a mandatory development week, but it can be =
for the intense performers among us.
    -Iteration 1(Create, Save, Translate, Browse, & Preview) comes out =
on November 15th
    -Iteration 2(Edit, and Refactor), which is also Release 1, comes out =
on December 6th

Tonight's meeting we need to discuss:
    -CVS!!=20
        -Who's gotten all of the ant tests to run
        -Who's using it
    -Anything else someone needs to bring up

Also, this is supposed to simulate a "stand-up meeting", so tonight =
let's not anyone feel like they have to stick around if they don't have =
any questions once we're done.  Last time we finished our agenda very =
quickly, then everyone stuck around for a long time.
--Arnaldo