Hello Freeman, You may be right, but at the moment I first have to come up at the more technical way and have to exercise some realization patterns in the servicemix environment. So at the moment I study the source to see what options I have to do the things in the right way. Cheers Joerg
-----Ursprüngliche Nachricht----- Von: Freeman Fang [mailto:[email protected]] Gesendet: Donnerstag, 5. Februar 2009 10:31 An: [email protected] Betreff: Re: AW: SMX3.3 Writing a BC Hi, Then I think the better way is add features based on the currrent snmp bc, and if you want you can provide patch so that other guys can benefit from your work. :-) Regards Freeman Hubschneider Joerg (CI/TMP) wrote: > Hello Freemann > Thanks for your response. OK, I want to provide a fully featured SNMP > protocoll BC. I have taken a look to the existent snmp-bc from Lars > Heinemann, which is a OID polling component. If I want to support SNMP GET > (GET_WALK GET_BULK..) and SET actions and in addition receiving SNMP traps, I > have to set up the appropriated SNMP schemas and WSDLs for full featured SNMP > over WebServices inside a ESB. > OK, I hope my intention is more clear. > Kind regards > Joerg > > > -----Ursprüngliche Nachricht----- > Von: Freeman Fang [mailto:[email protected]] > Gesendet: Donnerstag, 5. Februar 2009 10:01 > An: [email protected] > Betreff: Re: SMX3.3 Writing a BC > > Hubschneider Joerg (CI/TMP) wrote: > >> Hello servicemix guys, >> >> I want to write a Binding Component with a cxf-se-wsdl-first SU >> provider. >> Is there a nice example which helps a newbie for a rapid startup? >> >> >> > I'm not sure I understand what you want here. > May I ask why you need write a Binding Component yourself, we already > have cxf binding component which also support asynchronous communication. > Freeman > >> In the second step, I want to provide asynchronous communication to the >> BC. Is there a useful pattern to identify a SE consumer at the enriched >> async BC provider side for a BC callback to a dynamically created (.. >> or pooled) SE "Listener" interface/portType consumer at the async >> response? >> >> Thanks for any ideas to such kind of (real world) playground. >> Joerg >> >> >> >> > > >
