Guillaumme, Thanks for reviewing the patch. I thought of having the flexibility of specifying opeations and their parameters either while configuring the endpoint (xbean.xml) or as part of the message. As the endpoint is required to be thread-safe I now feel that we can not have both the options. What are your thoughts on this.. May be I do not understand the internals completely...
I considered the follwing usecases. 1. Send InOnly exchanges to a target endpoint. 2. Answer to an InOut exchange (operations like file/directory listing, get file content etc) Again, when you talk about a real WSDL, if I understand correctly you mean to create static wsdl for all the operations possible. How do you envisage to differentiate the different MEPs for the same operations (sending the file content to a target vs returing to the consumer), do you expect to have different operations for them in the WSDL?? Can you please elaborate your thoughts on this? Regards, Rabi Mishra, Wipro Technologies,Office: +91-20-39104549, VOIP:842 2545,CELL+91(0)9890363765 http://rabisblog.blogspot.com/ c++; /* this makes c bigger but returns the old value */ -----Original Message----- From: Guillaume Nodet (JIRA) [mailto:[EMAIL PROTECTED] Sent: Monday, July 30, 2007 8:12 PM To: [EMAIL PROTECTED] Subject: [jira] Commented: (SM-1001) FtpReceiverEndpoint (InternalEndpoint) [ https://issues.apache.org/activemq/browse/SM-1001?page=com.atlassian.jir a.plugin.system.issuetabpanels:comment-tabpanel#action_39796 ] Guillaume Nodet commented on SM-1001: ------------------------------------- I think there is one big problem: the message contains some informations used to configure the endpoint when the message is received. This means that the endpoint is not thread safe. Endpoints have to be, as they are given exchanges concurrently. Another thing is that I' d really like to have a real WSDL to describe the interface for this endpoint, the operations and their parameters. > FtpReceiverEndpoint (InternalEndpoint) > --------------------------------------- > > Key: SM-1001 > URL: https://issues.apache.org/activemq/browse/SM-1001 > Project: ServiceMix > Issue Type: Improvement > Reporter: Rabi > Attachments: patch.txt > > > FtpReceiverEndpoint (InternalEndpoint) > - Can accpet in-out mep for listing files > - Supports InOnly mep for get/mget operations... > Usage: > xbean configuration: > ------------------------------ > <beans xmlns:ftp="http://servicemix.apache.org/ftp/1.0"; > xmlns:b="http://servicemix.apache.org/samples/ftp-receiver";> > <ftp:receiver service="b:ftpReceiver" > endpoint="endpoint" > uri="ftp://rabi:[EMAIL PROTECTED]"> > > <ftp:target> > <ftp:exchange-target service="b:pipeline"/> > </ftp:target> > </ftp:receiver> > Input Message structure > --------------------------------- > <?xml version="1.0" encoding="UTF-8"?> <ftp:input > xmlns:ftp="http://servicemix.apache.org/ftp/1.0"; operation="mget" > recursive="true" filter="*" relativeUri="/inbox"> </ftp:input> Output > for file listing > ---------------------------- > STATUS: 200 > <?xml version='1.0' encoding='UTF-8'?> <ftp:list > xmlns:ftp="http://servicemix.apache.org/ftp/1.0";> > <ftp:directory name="/http/inbox/data/inner"> > <ftp:file>/http/inbox/data/inner/tx.xml</ftp:file> > </ftp:directory> > <ftp:file>/http/inbox/data/servicemix.xml</ftp:file> > </ftp:list> > This is a very simple version. Please suggest on the improvements.. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
