[jade-develop] problems with contract-net-responder behaviour

Subject: [jade-develop] problems with contract-net-responder behaviour
From: Heiko Holtschneider (heiko.holtschneider@post.rwth-aachen.de)
Date: Thu Aug 15 2002 - 18:34:01 MET DST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Next message: Heiko Holtschneider: "[jade-develop] Problem running MeetingSchedulerAgent"
• Previous message: tluthra@att.net: "RE: [jade-develop] AbsAgentAction OntologyException"
• Next in thread: Caire Giovanni: "RE: [jade-develop] problems with contract-net-responder behaviour"

Dear Jaders,

I have a problem with the CNP responder behaviour.
I implemented the handleOutOfSequence, handleRejectProposal,
prepareResultNotification methods in a very simple way. They only write
something to standard output.
however, they don't react to REJECT_PROPOSALs, ACCEPT_PROPOSALs or
non-sense messages. I prepare those messages with createReply(). Yet,
I have observed that the CFP and the coresponding PROPOSE message have
the same conversationId. The REJECT_PROPOSAL or ACCEPT_PROPOSAL,
however, don't. Could this be the problem? Is it not alowed to use
createReply there?

Thanks in advance,
Heiko

-- 
Heiko Holtschneider
mailto:heiko.holtschneider@post.rwth-aachen.de
tel.:+49(0)241 9290797
_______________________________________________
jade-develop mailing list
jade-develop@sharon.cselt.it
http://sharon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT http://jade.cselt.it/mailing.htm#unsubscribe

• Next message: Heiko Holtschneider: "[jade-develop] Problem running MeetingSchedulerAgent"
• Previous message: tluthra@att.net: "RE: [jade-develop] AbsAgentAction OntologyException"
• Next in thread: Caire Giovanni: "RE: [jade-develop] problems with contract-net-responder behaviour"

This archive was generated by hypermail 2a22 : Tue Aug 20 2002 - 15:03:55 MET DST