Re: CXF cross cutting concerns

ve themselves nicely and that should be the case. Brad -- View this message in context: http://camel.465427.n5.nabble.com/CXF-cross-cutting-concerns-tp5778798p5779128.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CXF cross cutting concerns

ttings. But there are a large number of these services with WSDLs for many aspects of inventory, supply, invoices, etc. -- View this message in context: http://camel.465427.n5.nabble.com/CXF-cross-cutting-concerns-tp5778798.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CXF cross cutting concerns

27.n5.nabble.com/CXF-cross-cutting-concerns-tp5778798p5779063.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CXF cross cutting concerns

aiming to keep this as simple as possible. But if there's a developing standard that does what I need it to I'd rather use that. -- View this message in context: http://camel.465427.n5.nabble.com/CXF-cross-cutting-concerns-tp5778798p5779062.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CXF cross cutting concerns

problem is manifesting on the endpoints in both directions. For > example, one of the systems I'm integrating with is JDEdwards SOAP services > which require PasswordCallbacks and http conduit settings. But there are a > large number of these services with WSDLs for many aspects

Re: CXF cross cutting concerns

it or not. So if I have different > security > requirements for invoices, supplier look up, etc. I can set that up in one > project and then whatever bundles get installed and register themselves > correctly will get picked up and exposed automatically. > > > > >

Re: CXF cross cutting concerns

s message in context: http://camel.465427.n5.nabble.com/CXF-cross-cutting-concerns-tp5778798p5779020.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CXF cross cutting concerns

loggingFeatureEnabled="true"loggingSizeLimit="20"> > > > > > ...set up other endpoints... > > class="com.svm.esb.financial.webservice.ServiceInvoker"/> > > > http://camel.apache.org/schema/blueprint";> > &

Re: CXF cross cutting concerns

lhost:9000"; /> -- View this message in context: http://camel.465427.n5.nabble.com/CXF-cross-cutting-concerns-tp5778798p5778937.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CXF cross cutting concerns

magic but becomes out of touch with the underlying libraries and APIs so anything that isn't normal or standard use becomes difficult to implement. -- View this message in context: http://camel.465427.n5.nabble.com/CXF-cross-cutting-concerns-tp5778798p5778887.html Sent from the Camel - Use

Re: CXF cross cutting concerns

-- View this message in context: http://camel.465427.n5.nabble.com/CXF-cross-cutting-concerns-tp5778798p5778886.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CXF cross cutting concerns

-- View this message in context: http://camel.465427.n5.nabble.com/CXF-cross-cutting-concerns-tp5778798.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Christian Schneider http://www.liquid-reality.de Open Source Architect http://www.talend.com

Re: CXF cross cutting concerns

r many aspects of inventory, supply, invoices, etc. -- View this message in context: http://camel.465427.n5.nabble.com/CXF-cross-cutting-concerns-tp5778798.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Sergey Beryozkin Talend Community Coders http://coders.talend.com/

CXF cross cutting concerns

ns. For example, one of the systems I'm integrating with is JDEdwards SOAP services which require PasswordCallbacks and http conduit settings. But there are a large number of these services with WSDLs for many aspects of inventory, supply, invoices, etc. -- View this message in context: