Hi Fred,
you're confused. The parameter is the one you give to the participant
in the XML file. The object and objects are those that the
participant provides itself to the outside world. So you might very
well create an infinite loop.
This code accessed the properties, which also contain the init params:
System.out.println("##########################################");
System.out.println("# Prtcpt.initialize(): running... #");
System.out.println("##########################################");
HierarchicalProperties props = getRepository().getProperties();
for (String name : props.getNames())
{
System.out.println(name+" = "+props.getValueString(name));
}
On 18-dec-05, at 16:44, F Baube wrote:
Surely sendmail reeled when thusly spake Geert Bevin:
The init parameters of the servlet are automatically aggregated into
the properties or the repository, and thus also those of the
elements.
Unfortunately I am seeing some VERY odd interaction btwn Rep startup
and Tomcat.
I am making a number of Rep API calls in order to try to retrieve the
value of the attribute I want from the ServletContext, and also dump
other info.
When I run this code in my subclass of BlockingParticipant:
System.out.println("##########################################");
System.out.println("# ParticipantWA.initialize(): running... #");
System.out.println("##########################################");
System.out.println ("parameter: " + getParameter());
System.out.println ("threadName: " + getName());
System.out.println ("dfltObject: " + getObject().toString());
List LL = getObjects();
System.out.println ("Objects: nr: " + LL.size());
for (Object o : LL)
System.out.println ("Object: " + o.toString());
the last items written to the Tomcat logfile are these:
##########################################
# ParticipantWA.initialize(): running... #
##########################################
parameter: null
and then my app HANGS.
When I recode it like this, to try to fetch the "default object"
first:
System.out.println("##########################################");
System.out.println("# ParticipantWA.initialize(): running... #");
System.out.println("##########################################");
//System.out.println ("parameter: " + getParameter());
System.out.println ("dfltObject: " + getObject().toString());
System.out.println ("threadName: " + getName());
List LL = getObjects();
System.out.println ("Objects: nr: " + LL.size());
for (Object o : LL)
System.out.println ("Object: " + o.toString());
it logs this:
##########################################
# ParticipantWA.initialize(): running... #
##########################################
and hangs.
This tells me that some of these Rep calls are interfering with the
runtime.
For whatever reason, certain API calls appear to throw a wrench in
the works.
Can anyone explain what is going on here, and how to work around it ?
BTW it's not a problem with disk space.
thx
fred
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
