We have an application developed using switchyard 2.0 and deployed on JBOSS EAP 6.3.3. Our packaging is ear file which contains multiple jar files for switchyard projects.
Now we have a requirement wherein we need to add another project(switchyard or java) which will be used to do custom file processing. We don't want to use File binding for it and written code to pick and process the file. Challenge is that we are unable to trigger this bean without some sort of service binding.
Is it necessary to promote the interface as a service and use a binding to trigger the bean class
is there a way to instantiate this been when the ear is deployed and kill it as soon as the application is un-deployed.