Re: Testing DSL based on Apache Camel

Sorry for my mistake, I din't realize that SOAUnit (should be perhaps renamed into WebService/REST ...) currently use camel component. So forget my previous remark. On Mon, Oct 7, 2013 at 8:41 AM, David MacDonald wrote: > Hi Charles, > > I'm not quite sure what you mean; I'm guessing you can set

Re: Testing DSL based on Apache Camel

Hi Charles, I'm not quite sure what you mean; I'm guessing you can set this via the standard CXF URI format that Camel follows. E.g. It might be possible to set WS-Policy like this but I haven't found a way yet. I was hoping to keep the Camel components quite separate to the testing dsl so that

Re: MD5 digest calculation

You can use the camel crypto component/dataformat for that purpose : http://camel.apache.org/crypto-digital-signatures.html On Mon, Oct 7, 2013 at 8:32 AM, Goyal, Arpit wrote: > Hi, > > Is there a component to do MD5 digest calculation in camel? > > Regards, > Arpit. > -- Charles Moulliard

MD5 digest calculation

Hi, Is there a component to do MD5 digest calculation in camel? Regards, Arpit.

Re: Testing DSL based on Apache Camel

The approach followed by SOAUnit is excellent. DSL should be nevertheless improved to allow to set which SOAP, WS-xxx (ws-security, ) spec will be used and provide parameters according to the spec / headers On Sun, Oct 6, 2013 at 11:49 PM, David MacDonald wrote: > Hi guys, > > I've recently

Re: URI Scheme Selections

Thank you for the explanation. Robert Sent from my iPad > On Oct 7, 2013, at 12:37 AM, "kraythe ." wrote: > > Camel URIs are part of the code of camel. They are used to select the > component that is being configured in the pipeline. They are not being used > to indicate a web siter remotel

Re: New Camel Components Considerations

Just food for thought. Perhaps I should of kept my thoughts to myself. I am not coding these. Robert Sent from my iPad > On Oct 7, 2013, at 12:34 AM, "kraythe ." wrote: > > I am sure they would love to take your code. When can we expect something to > look at? ;-) > > Robert Simmons Jr.

Re: URI Scheme Selections

Camel URIs are part of the code of camel. They are used to select the component that is being configured in the pipeline. They are not being used to indicate a web siter remotely or other considerations. For example it often throws people out when I write from(" http://www.foo.com?bridgeEndpoint=tr

Re: New Camel Components Considerations

I am sure they would love to take your code. When can we expect something to look at? ;-) *Robert Simmons Jr. MSc. - Lead Java Architect @ EA* *Author of: Hardcore Java (2003) and Maintainable Java (2012)* *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39* On Sun, Oct 6, 2013 at

Re: Memory leak - when an exception is thrown during the scheduling phase

Thanks James for the response .. I have created Jira issue. https://issues.apache.org/jira/browse/CAMEL-6832  Yes, I know which code causing this issue and how to fix that.  But I don't know other usecases (around the code where the fix needed).  I will spend some time and will update my findin

URI Scheme Selections

Just wondering... Why was ssh: selected instead of fish:? Why was smtp: selected instead of mailto:? Why was websocket: selected instead of ws:/wss:? Note: I'm assuming you guys made the right decisions here, I just don't understanding the significance of the URI Schemes being formally define

New Camel Components Considerations

Just food for thought... How about new components for the following: --> about:, aim:, bitcoin:, cap: (Calendar Access Protocol), data:, fax: and jira:? Reference: http://en.wikipedia.org/wiki/URI_scheme (To see URI format list, open in IE due to Firefox bug). Thanks, Robert

Re: bug : dns component

Right, so just to be clear, to treat it as optional it should be like this: Map headers = exchange.getIn().getHeaders(); //headers.put("dns.server", null); //headers.put("dns.server", ResolverConfig.getCurrentConfig().server()); headers.put("dns.class", ""); headers.put("dns.name", "www.example.co

Re: bug : dns component

Yes ! -- View this message in context: http://camel.465427.n5.nabble.com/bug-dns-component-tp5740962p5740993.html Sent from the Camel - Users mailing list archive at Nabble.com.

Testing DSL based on Apache Camel

Hi guys, I've recently started work on SOAUnit , a DSL for testing external (or Camel internal) integration artifacts that uses Apache Camel components and test framework. Basically our use case is to be able to automatically 'unit' test mega-ve

Re: The Camel Components Poster - PDF - FREE

I consider this issue as resolved. See [1] for details. [1] camel.465427.n5.nabble.com/Revoked-contribution-rights-td5740922.html Best, Christian - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/fo

Re: Revoked contribution rights.

I can see you edited [1] today. So, I consider this issue as resolved. [1] https://cwiki.apache.org/confluence/display/CAMEL/Component+List+Grouped Best, Christian -- View this message in context: http://camel.465427.n5.nabble.com/Revoked-contribution-rights-tp5740922p5740978.html Sent from t

Re: bug : dns component

Kuro, Would you consider it optional in that you don't specify it in the endpoint? On Sun, Oct 6, 2013 at 12:40 PM, kuro <962...@gmail.com> wrote: > Hi. > > From the camel wiki, dns.server option is "Optional". > > I will try to create a JIRA ticket. > > > > -- > View this message in context: >

How to return an image for a http get request without the original query params ?

 Hi , I am trying to set  up a route that 1) receives a http get request  2) extract a query parameter from the HttpRequest. 3) forward the extracted query parameter  to another endpoint. 4) Return an  1 by 1 pixel image to the http get request sender. I managed to do all the above, but the

Re: bug : dns component

Hi. >From the camel wiki, dns.server option is "Optional". I will try to create a JIRA ticket. -- View this message in context: http://camel.465427.n5.nabble.com/bug-dns-component-tp5740962p5740969.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: bug : dns component

Hi What is the purpose of setting the server to null? If its indeed a bug then you are welcome to log a JIRA and you are welcome to work on a patch. We love contributions, you can see more here http://camel.apache.org/contributing.html On Sun, Oct 6, 2013 at 3:38 PM, kuro <962...@gmail.com> wrot

bug : dns component

I found a bug in DnsDigEndpoint class. I cannot set the value of "dns.server" to null. Map headers = exchange.getIn().getHeaders(); headers.put("dns.server", null); //headers.put("dns.server", ResolverConfig.getCurrentConfig().server());

Re: splitting xml failed when running on tomcat

Thank you Willem. Solved per your suggestion! -- View this message in context: http://camel.465427.n5.nabble.com/splitting-xml-failed-when-running-on-tomcat-tp5740407p5740952.html Sent from the Camel - Users mailing list archive at Nabble.com.