Maybe getIdentifier()? If the Processor subclasses AbstractProcessor or AbstractSessionFactoryProcessor, it also extends AbstractConfigurableComponent and the identifier will be set at initialization and available via getIdentifier(). I don’t have a debug instance handy so I can’t verify that’s what’s returned, but it might be worth a try :)
On 12/26/15, 2:00 PM, "Jagannathrao Mudda" <jagannathrao.mu...@lifelock.com> wrote: >Oleg, > >The type of the processor is known (which is the class name), however the >processor name can be different for every instance of the processor and >would like to know if there is any way I can get the processor name which >is given while creating the processor from UI. > >Thanks a lot >Mudda > >On 12/26/15, 5:37 AM, "Oleg Zhurakousky" <ozhurakou...@hortonworks.com> >wrote: > >>Muddy >> >>I am not sure I understand the question, since you have all the info >>about the processor when you implement its onTrigger method. >> >>Oleg >> >>> On Dec 26, 2015, at 2:59 AM, Jagannathrao Mudda >>><jagannathrao.mu...@lifelock.com> wrote: >>> >>> Hi, >>> >>> How do I get processor name and the type in onTrigger method? Please >>>let me know. >>> >>> I really appreciate your help. >>> >>> Thanks >>> Mudda >>> >>> ________________________________ >>> The information contained in this transmission may contain privileged >>>and confidential information. It is intended only for the use of the >>>person(s) named above. If you are not the intended recipient, you are >>>hereby notified that any review, dissemination, distribution or >>>duplication of this communication is strictly prohibited. If you are not >>>the intended recipient, please contact the sender by reply email and >>>destroy all copies of the original message. >>> ________________________________ >> > >________________________________ > The information contained in this transmission may contain privileged and > confidential information. It is intended only for the use of the person(s) > named above. If you are not the intended recipient, you are hereby notified > that any review, dissemination, distribution or duplication of this > communication is strictly prohibited. If you are not the intended recipient, > please contact the sender by reply email and destroy all copies of the > original message. >________________________________
