portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glenn Golden <ggol...@umich.edu>
Subject RE: cvs commit: jakarta-jetspeed/webapp/WEB-INF/conf TurbineResou rces.properties
Date Wed, 07 Aug 2002 01:11:35 GMT
I have tested it, and I've attached the files I used to do so.  These
probably won't be runnable without some mods, as they work in our agumented
CHEF environment.  Basically, there's a velocity portlet that has a bunch of
test requests on a menu (this menu is actually rendered in a velocity macro
that I'm not including).  There are 4 or so tests of the
StateManagerService, which call a test object, which calls the service.  The
main set of test is pretty straight forward, there are 100 or so things
setup and tested for.  The other tests get tricky, to test separation of
state between different sessions, you have to run the tests from two
different sessions.  There's also a test that retires the http session,
which sort of messes things up after it happens, but you can see in the logs
that the objects that were in the state get notified...

When I run these, I get a report that 100 some tests succeded, 0 failed, so
I'm happy.

Also, all our portlets use session state, and a few classes this summer at
the University of Michigan have been using our pilot jetspeed based system,
so the system's getting some use.  We also run regular stress testing
sessions, and countless runs by the developers.  I know that the state
management is working, else all our tools would fail.  And from my tests, if
they are any good, I have more confidence that it works.

I'm really rushed this summer getting our CourseTools product build, which
is CHEF / Jetspeed based, and don't have much time for things out of band -
but I'm willing to learn how to write automated tests, and if such can be
done that require actual HTTP sessions and multiple http requests, then I
can, later, convert these tests into that form.

And, BTW, I'm about to add a new feature to the state manager, the ability
to get the "current" session state at any time, even if you don't have easy
access to the rundata.  This is useful for services that want to use or
access the stored states.  To do this, the StateManagerService will be
tracking http session per thread for each http request, in the same way as
the jetspeed run data service tracks the run data for each thread.  The
rundata service will be doing the plumbing, since it's garenteed to be
called by Turbine before and after each request, no matter what.

I'll have this tested and checked in shortly.

- Glenn

 <<TestAction.java>>  <<chef_test.vm>>  <<StateManagerTest.java>>

> ----------
> From: 	David Sean Taylor
> Reply To: 	Jetspeed Developers List
> Sent: 	Thursday, August 1, 2002 4:28 AM
> To: 	Jetspeed Developers List
> Subject: 	RE: cvs commit: jakarta-jetspeed/webapp/WEB-INF/conf
> TurbineResources.properties
> 
> Do you have unit tests for your new service?
> Im +1 for your new service. I would just like to see it tested and used
> for
> a while before we all switch over to it.
> 
> > -----Original Message-----
> > From: Glenn Golden [mailto:ggolden@umich.edu]
> > Sent: Monday, July 29, 2002 3:48 PM
> > To: 'Jetspeed Developers List'
> > Subject: RE: cvs commit: jakarta-jetspeed/webapp/WEB-INF/conf
> > TurbineResources.properties
> >
> >
> > I finally got time to go back and run my tests again on the http
> > version of
> > the state manager service, and they run just fine, including having the
> > objects that are placed into the session states freed and notified
> (using
> > the ??? Interface) when the session expires.
> >
> > Now that we have a reliable (and self cleaning) state management
> service,
> > I'm going to start changing some uses within Jetspeed of storing values
> in
> > the user.getTemp() to storing values in the state manager.  My goal is
> to
> > replace all user.getTemp() usage with state manager, properly (session,
> > page, portlet / portlet set) scoped.
> >
> > The first on my list is to fix a problem with the "pane" to display when
> > none is specified in the request - there's no distinction in the current
> > mechanism between different portal pages - so if a user is
> > switching between
> > portal pages, the "current" pane can be confused between them.
> > I'll change
> > it so that the "current" pane is a feature of the portlet set WITHIN a
> > portlet page (within a user session).
> >
> > - Glenn
> >
> > --------------------------------------------
> > Glenn R. Golden, Systems Research Programmer
> > University of Michigan School of Information
> > ggolden@umich.edu               734-615-1419
> > --------------------------------------------
> >
> >
> > > -----Original Message-----
> > > From: ggolden@apache.org [mailto:ggolden@apache.org]
> > > Sent: Monday, July 29, 2002 3:24 PM
> > > To: jakarta-jetspeed-cvs@apache.org
> > > Subject: cvs commit: jakarta-jetspeed/webapp/WEB-INF/conf
> > > TurbineResources.properties
> > >
> > >
> > > ggolden     2002/07/29 12:23:30
> > >
> > >   Modified:    webapp/WEB-INF/conf TurbineResources.properties
> > >   Log:
> > >   Switched to the JetspeedHttpStateManagerService, which stores
> > >   all state attributes (well wrapped) in the real HTTP
> > > session provided by the
> > >   container, and will clean up all values when sessions expire.
> > >
> > >   Revision  Changes    Path
> > >   1.57      +2 -2
> > > jakarta-jetspeed/webapp/WEB-INF/conf/TurbineResources.properties
> > >
> > >   Index: TurbineResources.properties
> > >   ===================================================================
> > >   RCS file:
> > > /home/cvs/jakarta-jetspeed/webapp/WEB-INF/conf/TurbineResource
> > > s.properties,v
> > >   retrieving revision 1.56
> > >   retrieving revision 1.57
> > >   diff -u -r1.56 -r1.57
> > >   --- TurbineResources.properties	18 Jul 2002 22:46:28
> > > -0000	1.56
> > >   +++ TurbineResources.properties	29 Jul 2002 19:23:30
> > > -0000	1.57
> > >   @@ -367,7 +367,7 @@
> > >
> > > #services.IntakeService.classname=org.apache.turbine.services.
> > > intake.TurbineIntakeService
> > >
> > > services.TemplateService.classname=org.apache.turbine.services
> > > .template.TurbineTemplateService
> > >
> > > #services.XSLTService.classname=org.apache.turbine.services.xs
> > > lt.TurbineXSLTService
> > >
> > > -services.StateManagerService.classname=org.apache.jetspeed.se
> > > rvices.statemanager.JetspeedStateManagerService
> > >
> > > +services.StateManagerService.classname=org.apache.jetspeed.se
> > > rvices.statemanager.JetspeedHttpStateManagerService
> > >
> > >    # Turn on the appropriate template service.
> > >
> > > services.JspService.classname=org.apache.turbine.services.jsp.
> > > TurbineJspService
> > >
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > > <mailto:jetspeed-dev-> unsubscribe@jakarta.apache.org>
> > > For
> > > additional commands,
> > > e-mail: <mailto:jetspeed-dev-help@jakarta.apache.org>
> > >
> >
> > --
> > To unsubscribe, e-mail:
> <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:jetspeed-dev-help@jakarta.apache.org>
> 
> 
> 
> --
> To unsubscribe, e-mail:
> <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:jetspeed-dev-help@jakarta.apache.org>
> 
> 

Mime
View raw message