OK I think we should leave aggregator alone, as it has no real deployment now. I'm
starting on fun_cbr.
TODO:
business_service
webservice_war1
jbpm_simple1
more_action
Kurt T Stam wrote:
The work that needs be done is building an .esb archive much like
the
custom-action.jar but in addition it need to contain
a jboss-esb.xml in META-INF, and then changing the deployToSAR task to
deploy, which should deploy this archive to the
server/default/deploy directory. If the sample contains queue
definitions you may add this to the root of the .esb archive.
For most samples I'm leaving the "ant run" task to start esb through
the bootstrapper.
I'm taking static_router and simple_cbr right now.
Cheers,
--Kurt
Kurt T Stam wrote:
> TODO:
> aggregator
> business_service
> fun_cbr
> webservice_war1
> jbpm_simple1
> more_action
> simple_cbr
> static_router
>
> DONE:
> helloworld
> helloworld_action
> helloworld_db_registration
> helloworld_file_action
> helloworld_ftp_action
> helloworld_sql_action (I'm currently working on this one)
> scripting_groovy
>
>
>
> Bill Burke wrote:
>
>> We want to port the samples to the new .esb deployment right? Divide
>> an conquer here? We each take a few?
>>
>
> _______________________________________________
> esb-dev mailing list
> esb-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/esb-dev
>