Re: Testing DSL based on Apache Camel

[Charles Moulliard]

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 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 the versions can change independently of each other.
>
> Cheers,
> David
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Testing-DSL-based-on-Apache-Camel-tp5740992p5741007.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog :  http://cmoulliard.github.io

Re: Testing DSL based on Apache Camel

[David MacDonald]

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 the versions can change independently of each other.  

Cheers,
David



--
View this message in context: 
http://camel.465427.n5.nabble.com/Testing-DSL-based-on-Apache-Camel-tp5740992p5741007.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: MD5 digest calculation

[Charles Moulliard]

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
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog :  http://cmoulliard.github.io

MD5 digest calculation

[Goyal, Arpit]

Hi,

Is there a component to do MD5 digest calculation in camel?

Regards,
Arpit.

Re: Testing DSL based on Apache Camel

[Charles Moulliard]

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 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-vendor enterprise service bus integration
> artifacts where we don't have the same flexibility with testing that
> something like Camel offers :). For example, if we have a PING web-service
> running on the mega-vendor's ESB that simply returns PONG then we can use
> the CXF component and Camel URI format:
>
> This will send the requestBody XML to localhost:8080, and check that the
> XML
> returned matches the expectedResponseBody. XML Comparisons are made using
> XMLUnit to allow for textual representation variations. Furthermore, the
> framework can support asynchronous transports and chaining of expectations
> to ensure orchestrated processes function as expected.
>
> I'm interested in getting some feedback as to where it could be improved,
> or
> new features which could be useful.
>
> Thanks,
> David
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Testing-DSL-based-on-Apache-Camel-tp5740992.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog :  http://cmoulliard.github.io

Re: URI Scheme Selections

[Robert Liguori]

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 remotely or other considerations. For example it 
> often throws people out when I write 
> from("http://www.foo.com?bridgeEndpoint=true";) and they say "hey that url 
> doesnt take that parameter." I know that, thw query string is passed 
> elsewhere, I am just configuring a registered component. Camel URIs indicate 
> some resource in the camel space, not the web space. 
> 
> 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 8:55 PM, Robert James Liguori  
>> wrote:
>> 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 defined by 
>> RFCs and being represented as such on Wikipedia. 
>> 
>> 
>> Do Camel URI's have a goal of conforming to RFCs?  Or are they a slightly 
>> different animal?
>> 
>> 
>> Reference:
>> http://en.wikipedia.org/wiki/URI_scheme
>> (Note: To see list of URI formats, open in IE)
> 

Re: New Camel Components Considerations

[Robert Liguori]

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. 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 8:49 PM, Robert James Liguori  
>> wrote:
>> 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: URI Scheme Selections

[kraythe .]

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=true";) and they say "hey that url doesnt
take that parameter." I know that, thw query string is passed elsewhere, I
am just configuring a registered component. Camel URIs indicate some
resource in the camel space, not the web space.

*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 8:55 PM, Robert James Liguori wrote:

> 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 defined by
> RFCs and being represented as such on Wikipedia.
>
>
> Do Camel URI's have a goal of conforming to RFCs?  Or are they a slightly
> different animal?
>
>
> Reference:
> http://en.wikipedia.org/wiki/URI_scheme
> (Note: To see list of URI formats, open in IE)
>

Re: New Camel Components Considerations

[kraythe .]

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 8:49 PM, Robert James Liguori wrote:

> 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: Memory leak - when an exception is thrown during the scheduling phase

[Nurali Techie]

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 finding/fix in Jira issue.

@All, Please follow Jira issue for further details.

Thanks,
Nurali


 From: James Carman 
To: "users@camel.apache.org" ; Nurali Techie 
 
Sent: Friday, October 4, 2013 4:32 PM
Subject: Re: Memory leak - when an exception is thrown during the scheduling 
phase
 


Create a JIRA.  Looks like you may have a patch in mind?  Do you have test 
cases?

On Friday, October 4, 2013, Nurali Techie  wrote:

Hello,
>
>
>
>I have observed a memory leak for Quartz worker thread in case an exception is 
>thrown during the scheduling phase when schedule is set to past time.
>I have observed this issue with camel-quart 2.10.4, 2.11.0, 2.11.2 versions.
>
>For ex, assuming today is 4-Oct; If a schedule is provided for yesterday (i.e 
>3-Oct) then below sequence happen:
>
>1. Quartz create worker thread for new schedule [generally TEN Threads with 
>name 'DefaultQuartzScheduler']
>2. Camel-quartz increment jobCounter for scheduler context [using 
>QuartzComponent.incrementJobCounter()]
>3. Camel-quartz tries to create new schedule [using Scheduler.scheduleJob()]
>4. scheduleJob() throws SchedulerException with the message - 'Based on 
>configured schedule, the given trigger will never fire'
>5. Camel-quartz does NOT decrement the job counter and jobCounter value 
>remains '1'
>6. Later Camel-Quartz stops the route and call QuartzComponent.doStop()
>7. In doStop(), Scheduler.shutdown() supposed to be called so that those TEN 
>threads are removed but to call shutdown() the pre-condition is that the 
>jobCounter should be '0'.  In this case jobCounter is '1' and 
>Scheduler.shutdown() will NOT be called and those TEN threads are NOT removed. 
> This is memory leak.
>
>Please find the stack trace [with Camel-Quartz 2.11.2 and 
>org.apache.servicemix.bundles.quartz-1.8.6_1 which wrapped Quartz Scheduler as 
>OSGi bundle] when SchedulerException is thrown at step 4 in above sequence.
>
>Let me know if you want me to create JIRA issue.
>
>Thanks,
>Nurali
>
>** Stack Trace:
>
>15:55:22.432 ERROR [Blueprint Extender: 1] o.a.c.b.BlueprintCamelContext 
>[BlueprintCamelContext.java:139] - Error occurred during starting Camel: 
>CamelContext(sfsftest35) due Based on configured schedule, the given trigger 
>will never fire.
>org.quartz.SchedulerException: Based on configured schedule, the given trigger 
>will never fire.
>at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:793) 
>~[na:na]
>at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:243) ~[na:na]
>at 
>org.apache.camel.component.quartz.QuartzComponent.doAddJob(QuartzComponent.java:232)
> ~[na:na]
>at 
>org.apache.camel.component.quartz.QuartzComponent.addJob(QuartzComponent.java:222)
> ~[na:na]
>at 
>org.apache.camel.component.quartz.QuartzEndpoint.addTrigger(QuartzEndpoint.java:81)
> ~[na:na]
>at 
>org.apache.camel.component.quartz.QuartzEndpoint.consumerStarted(QuartzEndpoint.java:213)
> ~[na:na]
>at 
>org.apache.camel.component.quartz.QuartzConsumer.doStart(QuartzConsumer.java:39)
> ~[na:na]
>at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
>~[na:na]
>at 
>org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:1819)
> ~[na:na]
>at 
>org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:2113)
> ~[na:na]
>at 
>org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:2049)
> ~[na:na]
>at 
>org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:1979)
> ~[na:na]
>at 
>org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:1758)
> ~[na:na]
>at 
>org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1633)
> ~[na:na]
>at 
>org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1500)
> ~[na:na]
>at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
>~[na:na]
>at 
>org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:1468) 
>~[na:na]
>at 
>org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:167)
> [bundlefile:2.11.2]
>at 
>org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:199)
> [bundlefile:2.11.2]
>at 
>org.apache.camel.blueprint.BlueprintCamelContext.serviceChanged(BlueprintCamelContext.java:137)
> [bundlefile:2.11.2]
>at 
>org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> [org.eclipse.org.eclipse.osgi-3.8.0.v20120529-1548.jar:na]
>at 
>org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEve

URI Scheme Selections

[Robert James Liguori]

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 defined by 
RFCs and being represented as such on Wikipedia.  


Do Camel URI's have a goal of conforming to RFCs?  Or are they a slightly 
different animal?


Reference:
http://en.wikipedia.org/wiki/URI_scheme
(Note: To see list of URI formats, open in IE)

New Camel Components Considerations

[Robert James Liguori]

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

[John D. Ament]

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.com");
headers.put("dns.type", "TXT");

On Sun, Oct 6, 2013 at 6:50 PM, kuro <962...@gmail.com> wrote:
> 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.

Re: bug : dns component

[kuro]

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

[David MacDonald]

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-vendor enterprise service bus integration
artifacts where we don't have the same flexibility with testing that
something like Camel offers :). For example, if we have a PING web-service
running on the mega-vendor's ESB that simply returns PONG then we can use
the CXF component and Camel URI format:

This will send the requestBody XML to localhost:8080, and check that the XML
returned matches the expectedResponseBody. XML Comparisons are made using
XMLUnit to allow for textual representation variations. Furthermore, the
framework can support asynchronous transports and chaining of expectations
to ensure orchestrated processes function as expected.

I'm interested in getting some feedback as to where it could be improved, or
new features which could be useful. 

Thanks,
David



--
View this message in context: 
http://camel.465427.n5.nabble.com/Testing-DSL-based-on-Apache-Camel-tp5740992.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: The Camel Components Poster - PDF - FREE

[Christian Müller]

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/foundation/
Apache Member: https://www.apache.org/foundation/members.html

https://www.linkedin.com/pub/christian-mueller/11/551/642


On Sun, Oct 6, 2013 at 7:23 PM, Christian Müller <
christian.muel...@gmail.com> wrote:

> @Shane, trademarks@, private@: We handle this issue. Please ignore this
> noise...
>
> @Robert, please stopping to send this message to so many list and bother
> people who cannot help with this.
> I already respond here [1]. If you still cannot edit the WIKI page, please
> use this mail thread to respond.
>
> [1]
> http://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/foundation/
> Apache Member: https://www.apache.org/foundation/members.html
>
> https://www.linkedin.com/pub/christian-mueller/11/551/642
>
>
> On Sat, Oct 5, 2013 at 6:25 PM, Robert James Liguori 
> wrote:
>
>> It's for the account with rob...@gliesian.com as the username...
>>
>> still not giving me access.
>>
>>   --
>>  *From:* Robert James Liguori 
>> *To:* Shane Curcuru ; "tradema...@apache.org" <
>> tradema...@apache.org>; "rob...@gliesian.com" 
>> *Cc:* Christian Müller ; "
>> priv...@camel.apache.org" 
>> *Sent:* Saturday, October 5, 2013 10:09 AM
>> *Subject:* Re: The Camel Components Poster - PDF - FREE
>>
>> Hi,
>>
>> It appears as if my confluence edit right have been revoked?  Can someone
>> tell me why I can no longer edit the web pages on camel.apache.org?
>>
>> Thanks,
>> Robert
>>
>>
>>
>>
>>
>

Re: Revoked contribution rights.

[Christian Mueller]

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 the Camel - Users mailing list archive at Nabble.com.

Re: bug : dns component

[John D. Ament]

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: 
> http://camel.465427.n5.nabble.com/bug-dns-component-tp5740962p5740969.html
> Sent from the Camel - Users mailing list archive at Nabble.com.

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

[Shing Hing Man]

 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 returned 1 by 1 image also contains the 
original query parameter. 


Below is my code.

public class JettyHttpServerDemo {
    private CamelContext context;

    public void run() throws Exception {
        context = new DefaultCamelContext();

        // add our route to the CamelContext
        context.addRoutes(new RouteBuilder() {
            @Override
            public void configure() {

                from("jetty:http://localhost:8081/test?matchOnUriPrefix=true";)
                        .process(new ImageProcessor()).to("stream:out");

            }

        });

        context.start();
        
        Thread.sleep(100);

    }

    private static class ImageProcessor implements Processor {
        private BufferedImage pixel;

        public ImageProcessor() {
            pixel = new BufferedImage(1, 1, BufferedImage.TYPE_INT_ARGB);
            pixel.setRGB(0, 0, (0xFF));
        }

        public void process(Exchange exchange) throws Exception {
            
            HttpServletRequest request = exchange.getIn().getBody(
                    HttpServletRequest.class);
            String name = request.getParameter("name");
            
            exchange.getIn().setBody("name=" + name);
            
            // send a response with 1 pixel.
            HttpServletResponse response = exchange.getIn().getBody(
                    HttpServletResponse.class);
            response.setContentType("image/png");

            OutputStream os = response.getOutputStream();

            ImageIO.write(pixel, "png", os);
            
        }
    }

    public static void main(String[] args) throws Exception {
 JettyHttpServerDemo demo = new JettyHttpServerDemo();
 demo.run();
    }
-


public class JettyHttpGetClient  {

    private CamelContext context;

    public void send() throws Exception{

        context = new DefaultCamelContext();


        ProducerTemplate template = context.createProducerTemplate();

    Exchange exchange = template.send("http://localhost:8081/test";, new 
Processor() {
    public void process(Exchange exchange) throws Exception {
    exchange.getIn().setHeader(Exchange.HTTP_QUERY, "name=foo");
    }
    });
    
    Message out = exchange.getOut();

    InputStream reply = (InputStream) exchange.getOut().getBody();
  // replyStr also contains the query parameter name=foo !
    String replyStr= inputStreamToString(reply);
    System.out.println("Response from http server has size :"+ 
replyStr.length());
    System.out.println("Response from http server is :"+ replyStr);
    System.out.println("status header is 
"+out.getHeader(Exchange.HTTP_RESPONSE_CODE));
    
        
        
    }

    private String inputStreamToString(InputStream inputStream) throws 
Exception{
        BufferedReader in = new BufferedReader(
            new InputStreamReader(inputStream));
        String inputLine;
        StringBuffer response = new StringBuffer();
 
        while ((inputLine = in.readLine()) != null) {
            response.append(inputLine);
        }
        in.close();
        
        return response.toString();
        
    }
    
    
    public static void main(String [] args) throws Exception{
         JettyHttpGetClient client = new JettyHttpGetClient();
         client.send();
        
        
    }
    
}
-

In debug mode, I can see that replyStr also contains "name=foo". 
Is there a way to return a 1 by 1 pixel image without the original query 
parameter ?

Thanks in advance for any assistance !

Shing

Re: bug : dns component

[kuro]

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

[Claus Ibsen]

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> wrote:
> 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());
> headers.put("dns.class", "");
> headers.put("dns.name", "www.example.com");
> headers.put("dns.type", "TXT");
>
> ProducerTemplate p = context.createProducerTemplate();
> Exchange respExchange = p.send("dns://dig", exchange);
>
>
>
> version: Apache camel 2.12.1
>
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/bug-dns-component-tp5740962.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

bug : dns component

[kuro]

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());
headers.put("dns.class", "");
headers.put("dns.name", "www.example.com");
headers.put("dns.type", "TXT");

ProducerTemplate p = context.createProducerTemplate();
Exchange respExchange = p.send("dns://dig", exchange);



version: Apache camel 2.12.1





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

Re: splitting xml failed when running on tomcat

[hutao722]

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.