Another point.
I think it would be usefull for JBI users to not have to download the full
distribution to create a service unit for the JBI component. This is
currently not possible because the ant scripts require the bpel engine
jars. I think it would be better (in the future) to:
* allow deploying a bpel with the associated wsdl directly as the service
unit
the component should easily compile them at deployment time (as it
already has all the needed
jars) and give the compiled form the bpel engine
* or write a maven 2 plugin which would compile the bpel process (thus the
user does not have to
install anything, just reference the maven plugin).
Cheers,
Guillaume Nodet
On 7/26/06, Alex Boisvert <[EMAIL PROTECTED]> wrote:
Yes, thanks for pointing this out. For the sake of expediency, I went
straight with Ant since I needed to integrate with PXE ant tasks to
compile processes and the sendsoap ant task for testing.
I'm planning to package the example build scripts and example artifacts
with Maven2 such that they are all available when downloading Ode in the
future. That way, people downloading the distribution could play with
the examples, change the BPEL/WSDL files, run ant and easily deploy and
test the resulting service assembly.
alex
Guillaume Nodet wrote:
> Btw, servicemix has a maven plugin to help the creation and packaging
> of jbi
> components,
> service assemblies and service units (auto-generation of the jbi.xml
> file of
> the service
> assembly, etc..). This maven plugin does not tie the artifacts to
> ServiceMix in any way,
> so it may be useful for the examples and / or the component.
> But it seems everything is nearly finished, so ...
>
> Cheers,
> Guillaume Nodet
