On 5/14/07, Scott Johnson <[EMAIL PROTECTED]> wrote:
This plays into something I'd like to try...so given this knowledge,
how reasonble is it to perform this operation on the fly:
1. Request comes in to perform a business process.
2. My Custom SE recieves request and parses process parameters,
notices that an FTP polling operation is needed to get input.
3. Custom SE forwards to my own custom FTP "gateway" component
4. FTP Gateway creates an endpoint as described below for the
servicemix-ftp component, specifying the parameters such as host and
directory as needed for the current process.
5. The newly-created FTP endpoint performs the act (it's sent a
message from my FTP Gateway synchronously so we know when it's
finished to get the results).
6. FTP Gateway disposes of the adhoc FTP endpoint as it's no longer
needed.
7. FTP Gateway forwards message to the next endpoint in my task's
workflow.
Does this make any sense and is it reasonble/possible to do?
(This would be in lieu of the ability to modify an endpoint's
configuration at runtime.)
You can certainly do this programatically via the API, but my first
question is about the need to do this dynamically. Why do this
dynamically when you can just configure a SU that is always deployed?
What's the advantage to doing this dynamically for every request vs. a
statically configured (xbean.xml) SU?
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
