Hi Matthias, have a look at /trunk/extensions/e4x, this can serve as an example. To register extensions you have to put an entry into ode-axis2.properties or ode-jbi.properties:
ode-axis2.extension.bundles.runtime = fqcn-of-your-extensionbundle or ode-jbi.extension.bundles.runtime = fqcn-of-your-extensionbundle HTH, Tammo Matthias Richter wrote: > Hi Tammo, > > thanks and yes, I am on trunk. > > Now I need to integrate an extension with the mechanism provided in > EXTENSIONACTIVITY.java. Is there an example somewhere flying around > which I haven't seen? I want to utilise the <extensionActivity> element. > > Thank you > > Matthias > > > > Am 26.09.2008 um 10:32 schrieb Tammo van Lessen: > >> Hi Matthias, >> >> I assume you're using the trunk version, right? >> >> This is just a warning, coming from the BPEL compiler which just >> notices that this element does not belong to the BPEL namespace. >> However, it should be properly handled by the extension >> implementation. >> >> I agree that this warning is confusing and should be swallowed, for >> now you can simply ignore it. >> >> Cheers, >> Tammo >> >> On Tue, Sep 23, 2008 at 18:00, Matthias Richter <[EMAIL PROTECTED]> >> wrote: >>> Hi, >>> >>> I have a very simple bpel process with an <extensions> block, containing >>> >>> <extension mustUnderstand="no" >>> namespace="http://cosima.gm.fh-koeln.de/MT/BPEL4MM"; /> >>> >>> Now the Compiler says the following >>> >>> <org.apache.ode.bpel.compiler.bom.BpelObjectFactory> Unrecognized >>> element in >>> BPEL dom: >>> {http://docs.oasis-open.org/wsbpel/2.0/process/executable}extensions >>> >>> >>> can someone explain why extensions is unrecognized? >>> >>> --Matthias >>> >> >> >> >> -- >> Tammo van Lessen - [EMAIL PROTECTED] - http://www.taval.de > > -------- > > Matthias Richter > > [EMAIL PROTECTED] > 0221 356 46 17 > 0177 829 16 80 > Skype: samma_wk > Jabber / GTalk: [EMAIL PROTECTED] >
