Re: Using camel-mail in OSGi bundle

[Bruno Ledesma <le...@gmail.com>]

I facing problems like this one with the geronimo mail bundle, .
I cant find 1_6_2 on the http://people.apache.org/repo/. In this repo we can
find 1.8-r755222_1-SNAPSHOT/   and  1.8-r755223_2-SNAPSHOT/ .
The first one, still have the "unable to locate provider problem". The
second is not deleting messages and is throwing an exception : Error
accessing headers due to: Error issuing POP3 command: TOP 1 0. Another
problem im facing is that in the first polling , the poller cant found the
INBOX folder. 
The funny thing is that when i stop geronimo mail bundle and stop my mail
consumer bundle, the messages are deleted. 

My guess is that the folder INBOX is not been closed. And the Sun's PO3 Mail
API describes: "POP3 does not support the Folder.expunge() method. To delete
and expunge messages, set the Flags.Flag.DELETED flag on the messages and
close the folder using the Folder.close(true) method. You cannot expunge
without closing the folder. "

Maybe the bundle is mantaining the INBOX folder open after the polling,
consenquentially is not deleting the messages.

Does anyone have an idea of what is going on?

Thanks for your atention!


I am Noob wrote:
> 
> Dear All,
> 
>   I have difficulties in using Camel Mail Component in my custom bundle.
> When I start the bundle in ServiceMix, I always get the following error:
> 
> javax.mail.NoSuchProviderException: Unable to locate provider for
> protocol: imap
>         at javax.mail.Session.getProvider(Session.java:241)
>         at javax.mail.Session.getStore(Session.java:282)
>         at
> org.apache.camel.component.mail.MailConsumer.ensureIsConnected(MailConsumer.java:127)
>         at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:72)
>         at
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:66)
>         at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>         [...]
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:619)
> 
>   Here is my route:
>   <route>
>     <from
> uri="imap://imap.myserver.com:143/INBOX?username=noob&amp;password=abcd1234"
> />
>     <process ref="mailAttachmentProcessor" />
>     <to uri="activemq:Mail.Queue" />  
> 
>   <bean id="mailAttachmentProcessor"
> class="org.mydomain.camel.processor.MailAttachmentProcessor">
>     <property name="logDir" value="/home/noob/tmp/mail" />
>   </bean>
> 
>   <bean id="activemq"
> class="org.apache.activemq.camel.component.ActiveMQComponent">
>     <property name="brokerURL" value="tcp://localhost:61616" />
>   </bean>
> 
>   And in my pom.xml, I have the following dependencies declared:
>   camel-core, camel-spring, camel-mail, camel-jms, activemq-core,
> activemq-pool, activemq-camel
>   I also have dependencies on mail.jar and activation.jar (not sure if
> they are necessary)
> 
>   And my bundle plugin configures as follow:
> 
>   <plugin>
>     <groupId>org.apache.felix</groupId>
>     <artifactId>maven-bundle-plugin</artifactId>
>     <extensions>true</extensions>
>     <configuration>
>       <instructions>
>         <Bundle-SymbolicName>${pom.artifactId}</Bundle-SymbolicName>
>         <Import-Package>
>           *,
>           org.apache.camel.osgi,
>           org.apache.activemq.camel.component,
>           org.apache.camel.component.jms,
>           javax.xml.parsers,
>           javax.xml.transform,
>           org.apache.activemq.pool
>         </Import-Package>
>         <Private-Package>
>           org.mydomain.camel.processor
>         </Private-Package>
>       </instructions>
>     </configuration>
>   </plugin>
> 
>   When I google on this issue, I found somebody resolve that problem. Here
> is the link:
>   http://fusesource.com/forums/thread.jspa?messageID=1723
> 
>   Thanks.
>   
> 

-- 
View this message in context: http://www.nabble.com/Using-camel-mail-in-OSGi-bundle-tp22431428p23196450.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.