Hi, IMO that's not ugly, to communicate between JBI endpoint, you must ensure the peer endpoints use same MEP(message exchange pattern), and IIRC servicemix-quartz only support InOnly MEP.
Moreover, JBI components is kinda deprecated, so I don't think the community will put much effort to enhance JBI features. We suggest users to use camel component instead, it's more powerful and flexible. Freeman －－－－－－－－－－－－－ Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: http://weibo.com/u/1473905042 On 2012-12-5, at 下午6:14, Lorenzo Bolzani wrote: > 2012/12/5 Freeman Fang <[email protected]> > >> Hi, >> >> As you don't care about the return value, then add a oneway method in >> cxf-se is the right way to go. >> > > Hi, > this is an option but is quite ugly: I have a few methods on a couple of > webservices invoked through quartz. "Doubling" all those methods does not > look like very nice, also considering that in this way the generated wsdl > would be quite confusing. > > Do you think could be a good idea to file a RFE to have QuartzEndpoint to > optionally create a InOut exchange? > > > Thanks, bye > > Lorenzo
