On 10/3/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
Nice work. It seems much more easier to write a JBI component
now. Only two classes for a simple Service Engine with
support for SU deployment is really nice :)
For the file component, I think the case is a bit different, as it
is a binding engine. So we may add more features like
endpoint resolution support, etc ...
Agreed
Btw, I guess that it would be better for such a BC to provide
two different endpoints implementation (<file:consumer />
and <file:provider />) and also support in/out MEPs (so maybe
we need more than two endpoints, need to think about it).
Yeah.
We may also want to support soap, but I guess it' s not
so useful for file base interactions.
Further refactoring for JBI BCs may be needed to provide
sensible implementations of endpoint resolution. It also
reminds me that the BC archetype needs to be finished.
Agreed.
Incidentally I managed to get the dynamic URI resolution working
nicely in servicemix-file; things are starting to look pretty nice and
clean when building components now
--
James
-------
http://radio.weblogs.com/0112098/
