On 10/13/05, Graham Klyne <[EMAIL PROTECTED]> wrote:
Unfortunately you're right. Our test coverage stinks! Definately an area we can use some help on. Contributions welcome.
No that I can think of, however, I just wrote an article on developing portlets with Pluto 1.1 that may have some of the info you're looking for. http://www.developer.com/java/web/article.php/3554396
If you have any other questions beyond what you find there, feel free to ask.
If I were you, I would recomend that you take a look at the 1.1 branch for this. I think you will find it much easier to work with. 1.1 is a refactoring and redesign of 1.0.1 and is where most of my and Zheng's attention lies at the moment. Especially if you're just beginning this project, I think it's your best bet.
I've also identified that the "Cannot find class
junit.framework.testcase on the build path" problems were caused
(unsurprisingly) by the junit jar not being on the classpath. Adding
junit in the Maven repo to the classpath for "testuite" and
"pluto-deploy" projects, I now get "no tests found".
Which leaves me wondering: are there any unit tests for the portal
container as a whole, or are the manual browser-driven tests the whole
story? Is pluto-descriptors really the only module with unit tests?
Unfortunately you're right. Our test coverage stinks! Definately an area we can use some help on. Contributions welcome.
Stepping back, are there any documents that describe how the various
sub-projects relate to each other. I've found the architecture
documents give a high-level view, but nothing that really helps me to
identify how the various source modules relate to this. Are there any
pointers or overview documents anywhere that I've overlooked?
No that I can think of, however, I just wrote an article on developing portlets with Pluto 1.1 that may have some of the info you're looking for. http://www.developer.com/java/web/article.php/3554396
If you have any other questions beyond what you find there, feel free to ask.
What I am hoping to do is use the Pluto container, and adapt the portal
wrapper and other components, to create an automated test environment
for WSRP developments. As such, I'd like to replace the HTTP front-end
with a test driver, and portlet implementations to provide appropriate
responses. I see there are some pieces in
testsuite/src/java/org/apache/pluto/portalImpl/portlet/test that might
provide some help with the latter. I think I'd be looking to replace
the servlet logic in or about
portal/src/java/org/apache/pluto/portalImpl for the former, but there
are many modules here whose purpose is not immediately apparent.
If I were you, I would recomend that you take a look at the 1.1 branch for this. I think you will find it much easier to work with. 1.1 is a refactoring and redesign of 1.0.1 and is where most of my and Zheng's attention lies at the moment. Especially if you're just beginning this project, I think it's your best bet.
Any further pointers would be appreciated.
#g
--
Graham Klyne
For email:
http://www.ninebynine.org/#Contact
