I got it. I'll create the Jira and submit the patch as soon as I write a test
to confirm the fix.
On Oct 5, 2010, at 8:37 AM, Hadrian Zbarcea wrote:
> Yes, please create a jira. The problem is the simple parsing that doesn't
> account for commas (or semicolons) within quotes.
> We need to fix
There are some caveats when using Spring-DM and OSGI. Guillaume Nodet does a
far better job than I ever could explaining some of the issues in his blog:
http://gnodet.blogspot.com/2010/03/spring-dm-aries-blueprint-and-custom.html
Regards,
Tracy Snell
On Oct 12, 2010, at 3:08 AM, Christian
I'll write a patch and submit it sometime this week.
On Feb 13, 2010, at 4:15 AM, Claus Ibsen wrote:
> Hi
>
> I have created the ticket
> https://issues.apache.org/activemq/browse/CAMEL-2467
>
> On Fri, Feb 12, 2010 at 3:01 PM, Claus Ibsen wrote:
>> On Fri, Feb 12, 2010 at 2:54 PM, mcrive wro
Patch submitted.
On Feb 16, 2010, at 5:51 AM, mcrive wrote:
>
> Looking foreward for it :D
>
> Claus Ibsen-2 wrote:
>>
>> On Sat, Feb 13, 2010 at 2:38 PM, Tracy Snell wrote:
>>> I'll write a patch and submit it sometime this week.
>>>
>
On Mar 5, 2010, at 8:28 AM, Charles Moulliard wrote:
> In the camel jms documentation, it is mentioned that when we would
> like to use Durable Topic Subscription, the limitation that we have is
> that we can only consume message through one JMS connection (so one
> thread) :
>
> "If you wish to
Here's code I use to expose a REST url externally to an internal REST service.
from(BASE_URI + "/doctor?bindingStyle=SimpleConsumer&resourceClasses="
+ DoctorLookupService.class.getName())
.setHeader(Exchange.HTTP_URI,
simple("http://my.company.com/CT/GetContac
You can also just use a processor when you need more control. See
https://code.notsoclever.cc/camel-soap-rest-bridge-example/
On Nov 25, 2013, at 7:52 AM, trilochan237
wrote:
> Hi
>
> I need to consume RestFul services exposed on a remote machine.
>
> I tried with the following routing tech
Just put up a blog post demonstrating how to write a new Camel component.
http://code.notsoclever.cc/writing-camel-component-camel-static-resource/
tjs
Always have planned on committing that component. Just never got to it. Since
there’s interest I will.
tjs
On Sep 26, 2014, at 7:10 AM, scottdawson wrote:
> Hi Claus,
> Tracy Snell wrote the original code and it's his website that I provided the
> link to in my earlier post.
At long last I'm getting to spend time in Camel again. Writing a series of
simple examples. Things folks I work with had trouble figuring out how to do
mostly. Posted the first one
athttp://code.notsoclever.cc/camel-cxf-component-wsdl-first-example/.
tjs (slowly emerging from a year of PHP and
Hah! Thanks. I'm dyslexic in an odd way and literally have to stop and think
about things like that (and sometimes like in this case I still reverse thing).
My wife never asks me to tell her directions if I'm in the car with her, she
tells me to point. If I say turn left at the light she respond
I have 2 examples (one posted today).
1 - http://code.notsoclever.cc/camel-cxf-component-wsdl-first-example/
2 - http://code.notsoclever.cc/camel-cxfrs-jdbc-rest-example/
Both have full working source on github.
tjs
On Aug 13, 2013, at 12:07 AM, contactreji wrote:
> Hii.
>
> I am in the pro
Set the header:
Exchange.HTTP_URI String URI to call. Will override existing URI set
directly on the endpoint.
http://camel.apache.org/http4.html
As the above says, that'll override whatever address is in the .to. So
.to("http4://nowhere.com") will be replaced by Exchange.HTTP_URI if it
Same number of params each time? Restlet does it easily:
from("restlet:http://localhost:8080/service/inv/{country}/{item}/{store}/{size}";)….
On Aug 23, 2013, at 6:28 PM, gsamy wrote:
> How to extract the URL parameters using Spring DSL?
>
> For example:
> http://localhost:8080/service/inv/US
The library we use for HL7 is HAPI (http://hl7api.sourceforge.net/index.html).
Unfortunately it doesn't support V3. I'd also love to see V3 support. I'm going
to dig for appropriate libraries and consider adding that functionality.
Package version diffs can be seen at:
http://vdiff.notsoclever.cc/?v1=2.12.0&v2=2.12.1
On Sep 22, 2013, at 7:00 AM, Christian Mueller wrote:
> The Camel community announces the immediate availability of the new patch
> release Camel 2.12.1. This bug fix release is issued after only 9 days of
>
http://fusesource.com/redhat/?elq=56aa75f4214c4cd1bf363dfb6fb2c940&elqCampaignId=348
17 matches
Mail list logo
