I don't think there should be EJB integration, but rather JNDI
integration, where you specify a JNDI name, a method, and
parameters to invoke. Parameters are mapped in through the context/
message.
That way, anything that's bound in JNDI could be invoked. No
reason to make it EJB specific.
Or maybe you are talking about JPA?
Mark Little wrote:
> One of the community members (Jason) is working on Hibernate
> integration, though not for this release. EJB3 integration is one
> of the tasks we've got (
http://jira.jboss.com/jira/browse/
> JBESB-425) for after the release. Does that cover what you had in
> mind?
> Mark.
> On 21 Mar 2007, at 21:53, Bill Burke wrote:
>> Do we want to add EJB3 for busines_service? Probably add
>> another 4meg to the distro. But we would have Hibernate too.
>> Eventually somebody will write the Hibernate/JPA actions that
>> Burr suggested during the meeting in Westford.
>>
>> Kurt T Stam wrote:
>>> Starting work on more_action
>>> TODO
>>> business_service (this is ejb3, and will require deploying to
>>> the appserver)
>>> webservice_war1 (this requires a WS stack, which also requires
>>> the appserver).
>>> Mark Little wrote:
>>>> I thought we decided on today's SILC meeting to postpone the
>>>> jBPM demo because of lack of time?
>>>>
>>>> Mark.
>>>>
>>>>
>>>> On 21 Mar 2007, at 18:44, Kurt T Stam wrote:
>>>>
>>>>> 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
>>>>>>>
>>>>> _______________________________________________
>>>>> esb-dev mailing list
>>>>> esb-dev(a)lists.jboss.org <mailto:esb-dev@lists.jboss.org>
>>>>>
https://lists.jboss.org/mailman/listinfo/esb-dev
>>>>
>>> -------------------------------------------------------------------
>>> -----
>>> _______________________________________________
>>> esb-dev mailing list
>>> esb-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/esb-dev
>>
>> --Bill Burke
>> JBoss, a division of Red Hat Inc.
--
Bill Burke
JBoss, a division of Red Hat Inc.