[ 
https://issues.apache.org/activemq/browse/CAMEL-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian de Beer updated CAMEL-2150:
-------------------------------


I have checked out the latest and did a mvn install - I can not use 
2.1-SNAPSHOT in my project because there seems to be some camel/SPring context 
issues, but I have replaced both the Atom and RSS jars with the newly built. 
The problem is still there.
Here are the routes:
 int delay = 0;
        while (resultSet.next()) {
          delay = delay + 1000;
          String parameters = rssParameters + "&consumer.initialDelay=" + delay;
          String feedLocation = resultSet.getString("feed_location");
          String topicLocation = resultSet.getString("topic_location");
          String name = resultSet.getString("name");
          if (feedLocation.contains("?")) {
            feedLocation = feedLocation.replace("?", parameters + "&");
          }
          else {
            feedLocation = feedLocation + parameters;
          }
          String rssUri = "rss:foo?feedUri="   + feedLocation;
          System.out.println("feed(" + (i++) + ") = " + name + ": " + rssUri + 
" - " + topicLocation);
          from(rssUri).marshal().rss().
              filter().method("rssFilter", "filter").
              to("bean:responder?method=scrubRSSFeed").                         
              
              to("activemq:topic:VirtualTopic." + topicLocation + 
"?explicitQosEnabled=true&timeToLive=" + (messageLifeTime * 60000));
        }

> RSS Component - parameter filtering not working
> -----------------------------------------------
>
>                 Key: CAMEL-2150
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2150
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-rss
>    Affects Versions: 2.0.0
>         Environment: Mac OS X 10.6.1; JDK 6 64 bit; Camel 2.0
>            Reporter: Ian de Beer
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
>
>
> I have tried to sort RRS feeds or to split the entries  as described in the 
> documentation. The problem is that the parameters that are to be consumed by 
> Camel are passed through to the endpoint, who does not understand the 
> parameters.
> Here is my code:  from("rss:" + feedLocation+ 
> "?sortEntries=true&feedHeader=true").marshal().rss()...
> where feedLocation = "http://www.iafrica.com/pls/cms/grapevine.xml";
> It results in:
> java.io.FileNotFoundException: 
> http://www.iafrica.com/pls/cms/grapevine.xml?feedHeader=true&sortEntries=true
>       at 
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1311)
>       at java.net.URL.openStream(URL.java:1010)
>       at org.apache.camel.component.rss.RssUtils.createFeed(RssUtils.java:32)
>       at 
> org.apache.camel.component.rss.RssEntryPollingConsumer.createFeed(RssEntryPollingConsumer.java:54)
>       at 
> org.apache.camel.component.feed.FeedEntryPollingConsumer.poll(FeedEntryPollingConsumer.java:42)
>       at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:99)
>       at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>       at 
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>       at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>       at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>       at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
>       at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
>       at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>       at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>       at java.lang.Thread.run(Thread.java:637)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to