Mudda I think what Matt is saying is that you can simply use additional property for it. Call it 'type', 'name', 'qualifier' or anything else. It's value will be known to the processor during its initialization so you should have no issues correlating to specific metadata.
Oleg Sent from my iPhone > On Dec 27, 2015, at 16:13, Jagannathrao Mudda > <[email protected]> wrote: > > Matt, > > Thank you for the update. In our case, it may not work as the same > Processor (type) has different behavior based on the unique name and that > processor’s instance metadata. > > It would be good if that “name" is exposed in the context. If not we need > to find out some other way for now. > > Thanks, > Mudda > >> On 12/27/15, 10:02 AM, "Matt Burgess" <[email protected]> wrote: >> >> Since the name is not currently exposed, perhaps the processor could have >> a "type" property that performs the same function that you'd like to use >> "name" for? >> >> Sent from my iPhone >> >>> On Dec 27, 2015, at 12:21 AM, Jagannathrao Mudda >>> <[email protected]> wrote: >>> >>> Joe/Matthew, >>> >>> We have a generic Processor that can be used for different purposes by >>> associating the name with some metadata and hence there is a need to >>> know >>> the ³name² so that we can pull the respective metadata for specific >>> processing in onTrigger method. >>> >>> BTW: The Œname' is exposed in REST API response in ŒProcessorEntity', >>> and >>> it would have been good if the same is available in ProcessContext or >>> ProcessSesssion in onTrigger method. >>> >>> Thanks >>> Mudda >>> >>> >>>> On 12/26/15, 5:02 PM, "Joe Witt" <[email protected]> wrote: >>>> >>>> Hello Mudda >>>> >>>> As mentioned you can certainly get the processor's class type and you >>>> can get the identifier of the processor. The 'name' is not exposed to >>>> the processor though. Can you how having access to the display name >>>> value would be helpful? >>>> >>>> Thanks >>>> Joe >>>> >>>> On Sat, Dec 26, 2015 at 7:45 PM, Matthew Burgess <[email protected]> >>>> wrote: >>>>> 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" >>>>> <[email protected]> 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" >>>>>> <[email protected]> >>>>>> 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 >>>>>>>> <[email protected]> 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. >>>>>> ________________________________ >>> >>> ________________________________ >>> 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. > ________________________________
