Deprecated API

Deprecated Interfaces
jade.proto.FIPAProtocolNames
          Use jade.domain.FIPANames.InteractionProtocol instead 
 

Deprecated Fields
jade.content.lang.sl.SL0Vocabulary.RESULT_ITEMS
          Use RESULT_VALUE instead 
 

Deprecated Methods
jade.wrapper.AgentContainer.getName()
          Use getPlatfromName instead. 
jade.domain.DFService.getNonBlockingBehaviour(Agent, AID, String)
          Use AchieveREInitiator instead 
jade.domain.DFService.getNonBlockingBehaviour(Agent, AID, String, DFAgentDescription)
          Use AchieveREInitiator instead 
jade.domain.DFService.getNonBlockingBehaviour(Agent, AID, String, DFAgentDescription, SearchConstraints)
          Use AchieveREInitiator instead 
jade.domain.DFService.getNonBlockingBehaviour(Agent, String)
          Use AchieveREInitiator instead 
jade.domain.DFService.getNonBlockingBehaviour(Agent, String, DFAgentDescription)
          Use AchieveREInitiator instead 
jade.domain.DFService.getNonBlockingBehaviour(Agent, String, DFAgentDescription, SearchConstraints)
          Use AchieveREInitiator instead 
jade.lang.acl.ACLMessage.getReplyBy()
          Since the value of this slot is a Date by definition, then the getReplyByDate should be used that returns a Date 
jade.domain.DFService.getSubscriptionMessage(Agent, AID, DFAgentDescription, SearchConstraints)
          Use createSubscriptionMessage() instead 
jade.content.abs.AbsPrimitive.toString()
          Use toString() instead 
 

Deprecated Constructors
jade.lang.acl.ACLMessage()
          Since every ACL Message must have a message type, you should use the new constructor which gets a message type as a parameter. To avoid problems, now this constructor silently sets the message type to not-understood. 
jade.core.AID(String)
          This constructor might generate a wrong AID, if the passed parameter is not a guid (globally unique identifier), but the local name of an agent (e.g. "da0"). 
 



JADE