
Hi all, Perldoc of Kernel/System/MasterSlave.pm states: Kernel::System::MasterSlave - to handle all ticket master slave tasks ... SYNOPSIS All functions to handle ticket master slave tasks ... PUBLIC INTERFACE new() create an object use Kernel::System::LinkObject; my $LinkObject = Kernel::System::LinkObject->new( ConfigObject => $ConfigObject, LogObject => $LogObject, DBObject => $DBObject, TimeObject => $TimeObject, MainObject => $MainObject, EncodeObject => $EncodeObject, ); Is it a typo or do I really need to create a LinkObject in order to use MasterSlave functionality? Should I do $LinkObject->MasterSlave() or MasterSlaveObject->MasterSlave()? Kind regards, Juan Clavero OTRS 3.1 on CentOSLinux [Apache and MySQL ] connected to an Active Directory for Agents and Customers.

Hi Juan Manuel,
For sure it is a typo and it will be fixed in OTRSMasterSlave 1.3.2, in fact it was totally wrong, please use the following:
create an object
use Kernel::Config;
use Kernel::System::Encode;
use Kernel::System::Log;
use Kernel::System::Time;
use Kernel::System::Main;
use Kernel::System::DB;
use Kernel::System::Ticket;
use Kernel::System::MasterSlaveObject;
my $ConfigObject = Kernel::Config->new();
my $EncodeObject = Kernel::System::Encode->new(
ConfigObject => $ConfigObject,
);
my $LogObject = Kernel::System::Log->new(
ConfigObject => $ConfigObject,
EncodeObject => $EncodeObject,
);
my $TimeObject = Kernel::System::Time->new(
ConfigObject => $ConfigObject,
LogObject => $LogObject,
);
my $MainObject = Kernel::System::Main->new(
ConfigObject => $ConfigObject,
EncodeObject => $EncodeObject,
LogObject => $LogObject,
);
my $DBObject = Kernel::System::DB->new(
ConfigObject => $ConfigObject,
EncodeObject => $EncodeObject,
LogObject => $LogObject,
MainObject => $MainObject,
);
my $TicketObject = Kernel::System::Ticket->new(
ConfigObject => $ConfigObject,
LogObject => $LogObject,
DBObject => $DBObject,
MainObject => $MainObject,
TimeObject => $TimeObject,
EncodeObject => $EncodeObject,
GroupObject => $GroupObject, # if given
CustomerUserObject => $CustomerUserObject, # if given
QueueObject => $QueueObject, # if given
);
my $MasterSlaveObject = Kernel::System::MasterSlaveObject->new(
LogObject => $LogObject,
TicketObject => $TicketObject
);
((enjoy))
Carlos Rodríguez
On Jan 30, 2013, at 8:41 AM, Juan Manuel Clavero Almirón
Hi all, Perldoc of Kernel/System/MasterSlave.pm states:
Kernel::System::MasterSlave - to handle all ticket master slave tasks ...
SYNOPSIS All functions to handle ticket master slave tasks ...
PUBLIC INTERFACE new() create an object
use Kernel::System::LinkObject;
my $LinkObject = Kernel::System::LinkObject->new( ConfigObject => $ConfigObject, LogObject => $LogObject, DBObject => $DBObject, TimeObject => $TimeObject, MainObject => $MainObject, EncodeObject => $EncodeObject, );
Is it a typo or do I really need to create a LinkObject in order to use MasterSlave functionality? Should I do $LinkObject->MasterSlave() or MasterSlaveObject->MasterSlave()?
Kind regards, Juan Clavero
OTRS 3.1 on CentOSLinux [Apache and MySQL ] connected to an Active Directory for Agents and Customers.
_______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
participants (2)
-
Carlos Rodríguez
-
Juan Manuel Clavero Almirón