ds,
> Raúl.
> On 31 May 2013 15:58, "Smith-John" <
> micha89@
> > wrote:
>
>> Raul Kripalani wrote
>> > Hi,
>> >
>> > I've seen this before too, but I never had the time to drill into it.
>> >
>> > It generally
t; Enterprise Architect, Open Source Integration specialist, Program
> Manager | Apache
> Camel Committer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
> On Thu, May 30, 2013 at 3:11 PM, Smith-John <
>
Hi,
I have a problem using camel (2.10.4) within a OSGi environment (equinox).
Sometimes I'm getting errors like "No component found with scheme: cxf" (or
stream or jetty or...).
Of course the components are there. After removing for example
org.apache.camel.component.cxf from imports and adding
Willem.Jiang wrote
> It looks like you are deploying the camel route into OSGi container?
> The warning means there are more than on javax.xml.ws.WebServiceProvider
> classes are loaded by deferent Classloader.
Hi,
still having
/WARNUNG: The javax.xml.ws.WebServiceProvider annotation was alrea
Ok, new try.
I want to create a generic SOAP consumer. The consumer should be able to
process all possible kinds of soap messages (+headers like ws-a...). As I'm
already using cxf component in my project I want (if possible) to realize
this with cxf too.
Now the problems I have:
-Using Message f
Hi,
I'm using Equinox.
I checked all my bundles for exporting javax.xml.ws.
But I only found one: jaxws-api-osgi2.2.8.jar. This was added because
cxf-rt-frontend-jaxws-2.7.3.jar needed the javax.xml.ws things.
But I found out that javax.xml.ws is already part of the system library (I'm
using jdk
Hi,
I'm using Equinox.
Regards.
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-create-a-generic-SOAP-consumer-tp5731741p5732584.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Will someone please help me?
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-create-a-generic-SOAP-consumer-tp5731741p5732538.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
my route now looks like this:
from("cxf:http://localhost:8050/service?dataFormat=PAYLOAD";)...
(PAYLOAD mode without wsdl and serviceClass).
But with this I get a NullPointer exception where I add the route to the
CamelContext (camelContext.addRoutes(new GenericSOAPRoute());).
Don't know if
Hi,
I have no problem with cxf and SOAP in general.
But the consumer I need has to be generic. It should be able to consume all
incoming SOAP messages however they look like. Therefore I either need a
"generic" wsdl (if this is possible) or I need a way to realise this without
a wsdl.
I would ap
Hi,
can you please give me a example how to use CXF_MESSAGE format?
http://camel.apache.org/cxf doesn't say much about it.
Trying it like
from("cxf:http://localhost:8080/service?dataFormat=CXF_MESSAGE";) I'm getting
a NP exception.
And with providing a wsdl like
from("cxf:http://localhost:8050/S
Hi, i tried it with:
Isn't this right?
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-create-a-generic-SOAP-consumer-tp5731741p57
Hi,
thanks for the survey.
But is it possible with cxf to get a generic SOAP consumer? With generic I
mean that it can handle all possible kinds of different SOAP messages. Using
MESSAGE dataformat it can't handle headers and with POJO dataformat I have
to provide e.g. serviceClass that I haven't
But I need to expose a Web Service first to receive the soap messages at all.
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-create-a-generic-SOAP-consumer-tp5731741p5731844.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Do you mean http://code.google.com/p/camel-soap/wiki/Introduction ?
I'm not sure about the license since this isn't an official camel component.
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-create-a-generic-SOAP-consumer-tp5731741p5731818.html
Sent from the Camel -
Hi,
I need a generic SOAP consumer but don't know how to build it.
The consumer should be able to consume any kind of SOAP message and should
be able to pick out the body of it.
I tried to realize it with cxf-component and MESSAGE format, but this way I
can't handle headers.
With PAYLOAD datafor
@Willem:
Hi,
I changed the route like you said. But this doesn't change anything
concerning the problem.
I created a Issue [1] and added everything needed to check the problem: the
Java class + wsdl to start the camel route & a SoapUI project for testing
it.
[1] https://issues.apache.org/jira/
Just to check if I understand you right:
Do you mean, my route should look like
from("cxf:XXX?wsdlURL=YYY&...")to(...)...to("cxf:${header[ReplyTo]}?wsdlURL=YYY&...&synchronous=true");
instead of
from("cxf:XXX?wsdlURL=YYY&...")to(...)...to("cxf:${header[ReplyTo]}?wsdlURL=YYY&...");
?
I
Yeah I know. But this doesn't fix the problem.
--
View this message in context:
http://camel.465427.n5.nabble.com/cxf-producer-needs-a-break-tp5730612p5731067.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
added the issue to the JIRA[1].
Regards.
[1]https://issues.apache.org/jira/browse/CAMEL-6295
--
View this message in context:
http://camel.465427.n5.nabble.com/cxf-producer-needs-a-break-tp5730612p5731036.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
I'm using 1.6.34.
Maybe better try a newer one than an older one?
Regards.
--
View this message in context:
http://camel.465427.n5.nabble.com/cxf-producer-needs-a-break-tp5730612p5730726.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I'm not sure if synchronous=false or true makes any difference in this route?
At any rate it doesn't fix my problem ;)
But I had an other idea: I'm not a http expert, but is it possible that
after sending a message via http to a certain port, this port is occupied
and needs to be released from htt
Hi,
I have a strange (at least for me) issue with my route respectively the cxf
component in it.
The route looks like
from("cxf:XXX?wsdlURL=YYY&...")to(...)...to("cxf:${header[ReplyTo]}?wsdlURL=YYY&...");
I get a one way SOAP message, do some work with it and send a response back
to the cal
Nobody knows something about how spring-ws camel component is implemented?
Also have another question: Since spring-ws component automatically adds the
SOAP-Envelope, is it possible to add custom namespace if needed?
--
View this message in context:
http://camel.465427.n5.nabble.com/spring-ws-
Hi,
unfortunately I didn't find a answer to my question.
In the spring ws documentation I read something about timeout settings and
callbacks.
But the question is: how does camel use/apply this things exactly.
Does camel maybe just set the timeout to infinite or does camel use callback
possibiliti
Hi,
I wanted to create a camel route with which it is possible to invoke various
SOAP-WebServices.
I ended up with following:
from("direct:Invoke").recipientList(this.header("WSAddress"));
and
Document response = template.requestBodyAndHeader("direct:Invoke", request,
"WSAddress", "spring-ws:"
Mhhh... lowering the Start Level of camel-stream and camel-core bundle
"fixed" this exceptions of not finding the components .
But now I'm getting:
17:54:07.812 ERROR o.a.camel.processor.DefaultErrorHandler:215Failed
delivery for (MessageId: ID-54038-1363798294273-1-2 on ExchangeId:
ID-5403
I replaced the old 2.10.3 camel bundles with the new 2.10.4 ones.
But now camel somehow even can't start because of not finding its
components:
e.g.
Failed to resolve endpoint: stream://out due to: No component found with
scheme: stream
or
Failed to resolve endpoint: direct://WS due to: No comp
java.lang.ClassNotFoundException: org.apache.xalan.xsltc.trax.DOM2SAX
at java.net.URLClassLoader$1.run(URLClassLoader.java:202) ~[na:1.6.0_34]
at java.security.AccessController.doPrivileged(Native Method)
~[na:1.6.0_34]
at java.net.URLClassLoader.findClass(URLClassLoader.jav
Hi,
does CXF support callbacks?
My route begins with
from("cxf:http://localhost:8080/create?wsdlURL=url2wsdl&serviceName={http://testit/}createService&dataFormat=PAYLOAD";)
using wsdl first approach.
I'm trying here to get cxf an callbacks to work.
Maybe my wsdl or my soapui ws-a properties are w
Sorry.
Camel 2.10.3.
Route looks like:
from("cxf:endpoint").unmarshal(jaxb).process(processorA).to("bean:myBean").process(processorB).marshal(jaxb)
Bundles added:
org.apache.servicemix.bundles.xalan-2.7.1_6.jar
org.apache.servicemix.bundles.xerces-2.10.0_1.jar
org.apache.servicemix.bundles.bcel-5.
Camel ist started with
OsgiServiceRegistry reg = new OsgiServiceRegistry(bundleContext);
OsgiDefaultCamelContext camelContext = new
OsgiDefaultCamelContext(bundleContext, reg);
camelContext.addRoutes(new Route());
camelContext.start();
--
View this message in context:
http://camel.465427.n5.na
Hi,
I got it to work.
I still use the .unmarshal(jaxb) part, but for the moment it is ok.
Maybe I will change this sometime later.
"example.ExampleResponse" is a generated jaxb-class.
Thx for helping.
--
View this message in context:
http://camel.465427.n5.nabble.com/cxf-response-tp5728106p57
Having a bundle with an interface and several implementations of it (all in
their own bundle), how can I decide which bundle to call?
Details:
Bundle 1 just defines an interface. (packageName.InterfaceName)
Bundle 2, 3 & 4 implement this interface.
Problem is, with
.to("bean:packageName.Interf
Thx Willem.
@Christian Mueller: No I have no problems to implement it. I just wanted to
know if I have to wrap the response into a xml document by myself or if
camel does this for me.
--
View this message in context:
http://camel.465427.n5.nabble.com/cxf-response-tp5728106p5728234.html
Sent fr
Hi,
I have a route that looks like
from("cxf:cxfEndpoint?wsdlURL&dataFormat=PAYLOAD").unmarshal(jaxb).process(new
Processor() {
(here I do some app logic)
}).to("bean:myBean");
The myBean just returns a string.
The wsdl of the cxf endpoint specifies the response with
So, the response should l
Hi,
I have problems using a OSGI-Service/bundle in a camel route. Read
tutorial-osgi-camel but didn't get it to work.
The setup:
bundle 1 defines a Service interface (separate bundle for interface
because there can be several implementations of it)
bundle 2 implements this interface
b
37 matches
Mail list logo
