RE: [wtp-dev] Looking for committer with an interesting server-side unit

[David M Williams <david_williams@xxxxxxxxxx>]

I wouldn't worry about clogging up list,
that's how we keep "development in the open" (as well as allowing
me 
one more avenue to publically admit
my ignorance :) and keep everyone informed. 

I understand now this is for "end
user" of WTP -- I missed significance right off!

I think this is a valuable thing, but
does sound like it needs long term solution with 
review/agreement from TPTP, as well
as positive review from 
planning/requirements part of WTP PMC
to be sure its "in scope" of WTP (since 
a defacto standard, not standards body
standard). For Release 1, 
can it be incorporated in WTP as a potentially
temporary plug-in? Perhaps as separate 
download? Part of SDK, but not "runtime"?
 

And, again, just questions, don't mean
to be difficult or limiting, just want to be sure things are
correctly reviewed at this late date
for R1.

"Daniel Somerfield" <dsomerfi@xxxxxxx>

05/11/2005 08:10 PM

To	"Timothy Deboer" <deboer@xxxxxxxxxx>, David M Williams/Raleigh/IBM@IBMUS
cc
Subject	RE: [wtp-dev] Looking for committer with an interestin        server-side        unit testing and a big heart

Hi guys. All fair questions.

 
Cactus is very, very simple.
There really isn’t much to it. All it really does is provide an HTTP-based
proxy so that you run a test locally with JUnit, and, in reality, it runs
the test in a servlet container. To JUnit, it looks like any other Unit
test, but in fact, cactus is sending HTTP requests to a servlet in the
container, telling it what tests to run, collecting the results and returning
them to JUnit.
 
It isn’t terribly complicated
and it isn’t terribly sophisticated, but it has become the defacto standard
since nothing else has stepped up. 
 
We don’t need to provide anything
on the server. Cactus provides the servlet. As the plugin exists now, the
user has to configure the web.xml by hand so servlet responds to the requests
and they have to drop a number of jars in their web-project. I would like
to automate both steps at some point, but this seems like a good first
step and avoids the whole issue of needing to ship third party jars, at
least for now.
 
I toyed for a while with trying
to make this a part of the TPTP project and they were receptive, but the
problem is that the most important part of the integration is the automatic
deployment that you get from WTP. I think it would be valuable to have
TPTP integration ultimately, but that would mean the cactus integration
would have both WTP and TPTP dependencies and it is unclear what that would
mean.
 
Anyway, cactus isn’t magic,
but I think it is what most people use for server-side unit testing.
 
I hope this helps. If you want
any more information on this, feel free to ask. In summary, is this is
something that we think our customers would use and we also think that
it is something other users of the WTP project would benefit from.
 
Oh, and yes, I am perfectly
prepared to maintain the code—that’s expected.
 
I sent this message just to
you two so I don’t clog up the list any more, but if either of you feel
this should be opened up to the group again, feel free to forward it on.
 
Thanks,
Dan

---

From: wtp-dev-bounces@xxxxxxxxxxx
[mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Wednesday, May 11, 2005 4:50 PM
To: General discussion of project-wide or architectural issues.
Subject: Re: [wtp-dev] Looking for committer with an interestin server-side
unit testing and a big heart
 

Dan, I confess my ignorance (too) and ask ... what's the benefit to WTP?
>From the Apache Cactus website, "Cactus
is a simple test framework for unit testing server-side java code (Servlets,
EJBs, Tag Libs, Filters, ...). ".
While this is a great thing, WTP isn't providing "server side java
code" per se, are we? 
So ... just wondering ... (I suspect you've explained this before/else
where and I've lost track). 
Thanks. (And, please, interpret the questions as interest, not resistance
:)

Timothy Deboer <deboer@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

05/11/2005 07:21 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	Re: [wtp-dev] Looking for committer with an interest in        server-side        unit testing and a big heart

 

Hi Dan, 

I'm the most likely candidate to adopt this code, and was going to respond
back to your earlier note. I think the code looks good and ready to go,
I just have a couple minor concerns that hopefully will be easy to resolve.
The first is that I have a passing familiarity with Cactus, but I'm definitely
not an expert. I was hoping the community would chime in with feedback
or even a "hey, that'd be great!". I'd like to get at least one
other person who is familiar with Cactus to give this a try and give a
thumbs-up. If nobody else offers, maybe one of the other guys at BEA?

Second, I don't have the resource to do anything more than review &
commit code, answer questions, etc. I doubt this is an issue, but I just
need to be clear that I'm expecting you to maintain the code with cleanup,
general release polishing, and fixing bugs.

We can take the rest of this offline and hopefully get the code in soon!

Thanks, 
Tim deBoer
WebSphere Tools - IBM Canada Ltd.
(905) 413-3503  (tieline 969)
deboer@xxxxxxxxxx

"Daniel Somerfield" <dsomerfi@xxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

05/11/2005 02:02 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	[wtp-dev] Looking for committer with an interest in server-side        unit testing and a big heart

 

Hi everyone, 
I am still in the market for a committer to adopt the cactus code. I would
love to see it get into 1.0. It is functional and has a very nice README
if you would like to try it out. I do need to take a few minutes to move
it into internal packages but I am holding off until I know where this
is going to be packaged and whether it is going to be in its own plug-in
or part of another. 
So be kind. Support server-side testing and adopt this poor lonely plug-in
that needs a home. 
Thanks, 
Dan 
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev