Hi Martin, You have two big ways : 1/ Create a dedicated BindingComponent It can be solution. You need to code : - the component itself (responsible of sending and reading NormalizedMessage from the NMR) - the marshaler (responsible of the messages transformation) You can see an exemple of a simple BindingComponent (SMPP) here : http://svn.nanthrax.net
2/ Using bean or CXF-SE ServiceEngine : You can encapsulate the mainframe process in a POJO exposed by CXF-SE. The process logic is present in the NMR and you can publish using another binding component (such as HTTP). Regards JB On Wednesday 21 January 2009 - 06:46, Martin Kuhn wrote: > > HI, > > I've to integrate the callability of SMX4 from a mainframe. > > Usually a simple java class from a middleware provider (thirdparty) is used > to connect to a middleware server (with certain serverinfos). The class is > already used in a standalone java prog. After this connecting process > requests come in and the prog instance is able to handle the requests. > > Now I've to integrate this funct. in SMX4. My first thought was to develop a > BindingComponent. > > My questions: > - is this the correct approach? (or is it possible to do it simpler) > - which functionality do I have to implement? > > Any help would be appreciated! > > TIA > Martin > -- > View this message in context: > http://www.nabble.com/Own-BindingComponent-required-----calling-the-ESB-from-a-mainframe-tp21584515p21584515.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > -- Jean-Baptiste Onofré (Nanthrax) BuildProcess/AutoDeploy Project Leader http://buildprocess.sourceforge.net [email protected] PGP : 17D4F086
