Thanks Paul for the reply and sorry for the late response from my side. For some reasons I was not able to check mailsL.
I’m trying to develop a tool for some of our internal requirements. This tool sends a special xml message to the entry endpoint of a process which will be processed by my .aj class and will not be send further down the itinerary of the process (already deployed in domain and can’t be changed). This .aj class performs all my required tasks. The xml message that is sent from the tool contains info about that tasks needs to be performed by .aj class.
Now as our domain has multiple processes deployed with a wide range of message selector at their entry endpoint. The tool works fine for all the processes which don’t have message selector at entry endpoint but creates problem with process having message selector at entry endpoint. This is because the xml message sent from the tool will not be picked by the process entry and the .aj class will not be called.
Is there a way to skip the message selector so that the message can reach the .aj class ?
I also thought to fetch message selector of the process through API and set it in the outgoing message of the tool but I’m getting the message selector as null. Below is the code that I have used. Please let me now what I’m doing wrong here. This will be a complex logic and I would prefer the first way (skip message selector).
ESBAPI api = factory.createAPI("Domain1", "tcp://localhost:2508", "Administrator", "Administrator");
IProcessConfigAPI ss = api.getProcessConfigAPI();
IProcessConfig t = ss.getProcess("MyProcess");
IEndpointConfig eConfig = t.getEntryEndpointConfig();
IJMSEndpointConfig jms = (IJMSEndpointConfig)eConfig.getAdapter(com.sonicsw.esb.mgmtapi.config.IEndpointConfig.JMS_TOPIC);
System.out.println("MessageSelector ::"+jms.getMessageSelector());
I hope you are able to understand the requirement.
Thanks a lot,
Habin