I assume you are talking about the j2ca work manager we've had for a
long time rather than a newer choice -- I think the ee concurrent spec
may also have a work manager and I don't know about ejb 3.1.
The default work manager isn't bound in jndi right now. To bind it
you can include a binding gbean like we use for the transaction
manager -- see the plan at plugins/connector/transaction/src/main/plan/
plan.xml or inside the transaction car. I think yours will look like
this:
<gbean name="WorkManagerBinding"
class="org.apache.geronimo.gjndi.binding.GBeanBinding">
<attribute name="name">DefaultWorkManager</attribute>
<attribute name="abstractNameQuery">?name=
DefaultWorkManager#</attribute>
<reference name="Context">
<name>JavaContext</name>
</reference>
</gbean>
I think the work manager will then be at java:DefaultWorkManager
I think you can put this gbean in your geronimo plan for your web app
although there might be ordering issues if you try to look it up
during servlet initialization... you could experiment.
thanks
david jencks
On Jan 11, 2009, at 8:16 AM, fladimir wrote:
I've tried searching for this a lot, but I haven't found any
documentation
yet of any JNDI name for DefaultWorkManager or anything similar.
Any advice? The WorkManager is to be used by a session bean.
--
View this message in context:
http://www.nabble.com/How-to-get-hold-of-a-WorkManager-in-a-web-app--tp21400861s134p21400861.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
