There might be some lingo confusion - I've been a .NET guy for 13 years who
was thrown into a Java/Apache world where I have 0 experience.
When a client accesses our web services, they are accessed over TCP port 443
- where SSL is required.
The servers have their own SSL (x509) certificate for en
Hmm, I got the jist of it, but how would one add a SSL Certificate (client)
to an Exchange?
Let's say I'm going to https://mysite.com/foo The server I'm sending from
already has the server certificate, which is easy to do, but if I wanted to
attach a x509 certificate as a client cert, how would I
Effectively we`re doing our own Man in the Middle attack - but it`s allowed
due to firewall restrictions we have within our zone. This model will be
changing in the future, but for now it`s required.
--
View this message in context:
http://camel.465427.n5.nabble.com/SSL-Server-Certs-and-Client-
Thanks for the responses guys.
Willem - you're 2nd point is actually how we do it.
Our reverse proxy is connecting to our own back end in a more secure zone.
Effectively what I need:
*Client sends the message*
Client sends a SOAP message to our Camel-Reverse Proxy. The connection will
terminate
My camel app is running pretty well, however it's using our unsecured
webservice platform for development and PoC. I now need to change it so it
works with our server certificates (x509) and use client certificate
passthrough. We encrypt with the server cert. and use client certificates as
a lock/
I believe it's HL7v2; similar to HAPI.
--
View this message in context:
http://camel.465427.n5.nabble.com/HL7-v3-tp5732915p5732924.html
Sent from the Camel - Users mailing list archive at Nabble.com.
works perfectly! Thanks Claus. Didn't realize the splitter had that built in.
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-persist-data-from-aggregator-tp5732421p5732512.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hey Claus,
Thanks for the reply. I looked at that pattern, and I do get the aggregated
results back properly - in the Aggregate route. However, once processing
continues past that the exchange reverts back to what it was before it got
split->aggregated.
Using the link you posted, I changed my bat
I'm having an issue with aggregator.
I have an incoming Web Service request that will be split into 2 messages
and have the responses of both web requests aggregated together. This works
fine, and I do get a good aggregated message within the aggregation route.
However, once I'm out of that rout
I tried doing the following:
The direct:foo does contain the correct XML. But when all these routes
finish and finally start processing on the main route that called all of
this, that route has the wrong XML.
How do I get the AggregatedXML to be the actual Envelope for this process so
the Root R
I am successfully aggregating my XML into a single message, however once I
leave the route that does the Aggregation it goes back to the original XML.
I'm not sure why it reverts outside of the aggregate method... what is the
best practice to keep that envelope?
When the XML is "Not Correct" it tu
I realized that it only supports XPath 1.0, I changed it so the xPath is:
//v3:QUCR_IN200101BC | //v3:GetDemographics
However, when I do that I get this on the output:
[GetDemographics: null]
[v3:QUCR_IN200101BC: null]
It seems it grabbed the right nodes, but nothing under them. Thoughts?
--
Realized Camel only supports XPath 1.0. The xpath i was using was 2.0.
Modified and it's working.
--
View this message in context:
http://camel.465427.n5.nabble.com/Split-and-Xpath-tp5731569p5731570.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I'm having some issues running the xpath on my split. I know the Xpath for
the Choice isn't the best, but it works for now.
I'm getting errors saying:
Invalid xpath: //*[local-name()='QUCR_IN200101BC'],
//*[local-name()='GetDemographics']. Reason:
javax.xml.xpath.XPathExpressionException
Here's w
Thanks Christian.
I was uncertain on how the header would transfer through from the split.
Thank you for clarifying it.
/RT
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-DSL-setHeader-and-Aggregate2-strategy-tp5731382p5731460.html
Sent from the Camel - Users mailing
Camel is shooting me an error on this one:
What I want this to do:
1) XML Message is sent to route.
2) XML MEssage sent to HL7V3GetDemo.
3) Results from #2 logged and sent to the direct:Aggregate
I do not want to use Multicast as I do not want the same message used in
both cases.
I have somet
I'm trying to find how to set the header to a UUID before I split an XML
Message and send the results back to an Aggregator. This is erroring on the
lines below. I'm not sure how to use setHeader and pass in a value from a
Bean.
Also, should I be setting the Header on the main XML before it gets
I'm still not sure the best route to take.
If I have the XML Message:
I want to take the first node (which can be found through xpath) and send
that to another Web Service. I then need to check to see if the attribute
foo exists in the 2nd element, and if so, manually create another XML file
(p
I don't think the splitter can do what I want.
I want to take a single message, transform that message into X messages
(sometimes it might split, other times I'll have to take the original
incoming message, transform it based on an element based inside the
message).
Looking at other forums, some
Thanks for the reply Clause.
I've read the Split part and I understand it.
Based on my above example I know what I want to split, I'm just not sure how
the XML should look for the Split.
Example (psudo):
When an incoming message hits this section, it could only satisfy 1 of the
splits, other
QUick sample of my XML:
I know the names of the elements I want split, and the URL's they're going
to, each inner message will go to a unique Web service endpoint.
--
View this message in context:
http://camel.465427.n5.nabble.com/Splitting-XML-into-multiple-separate-bits-and-send-out-to-webs
I'm just starting out on Camel here. I'm trying to see if this can be done
with Spring XML and Camel, without the need for a lot of custom Java. If
it's needed, then it's needed.I have a scenario where I will have 1 incoming
XML Message (WebService request) that I need to split into multiple messag
22 matches
Mail list logo