I'm not sure mixing static configuration and runtime deployment is a good idea, even if it will work.
I would recommend using only a static configuration or using only SUs and deploy them. It does not really affect which component you can use or write. For you business component, if you do not plan to create a container and support SUs, i would recommend to write a lightweight component instead of a full blown component. Take a look at the examples in recent snapshot distribution (or the non official yet 3.0), you will see different deployment style. If you plan to use SU, i would recommend the maven tooling to ease that and to create the basis for your component (if you write one). On 9/15/06, jhair <[EMAIL PROTECTED]> wrote:
I need to poll a directory for files, transform the files using a stylesheet, do some business logic, and then save the transformed to a file. For polling, transforming, and writing to a file, I'd like to use the FilePoller, XsltComponent, & FileWriter, respectively. For these components, I'd like the configuration to exist within the servicemix.xml used when starting ServiceMix (due to the need to specify local directories, etc). For my business component, is it best to create a full jbi-component? If so, how would I configure servicemix.xml for SM startup? Should I create some classes and deploy using a SU? If so, it doesn't appear as though I can configure the boot servicemix.xml using components configured within an SU. Or should my business component/jar file need to be a share file? Thanx, jsh -- View this message in context: http://www.nabble.com/Deploying-SUs-tf2278624.html#a6328844 Sent from the ServiceMix - User forum at Nabble.com.
-- Cheers, Guillaume Nodet
