anonymous wrote :
| That is what could be used now, but the problem with resolving the name is that its
not unique. If for a given ejb deployment, you use its local ejb-names this will just
work.
|
Right, but that unit of work happens inside a deployer anyway. So it's scoped to a
particular deployment.
anonymous wrote :
| ensuring the container name was made available on the JBossEnterpriseBeanMetaData,
|
Yes, that was my first idea as well. In the beginning i was thinking that a indirect
reference to the container using a lookup might be better way then picking the container
at deploy time and associating it with the web service meta data. However, both the ejb
and the web service deployer are chained anyway, so we shouldn't run into trouble
here.
Or do you see a technical reason to prefer invocation by lookup over direct association in
this case?
However, I will evaluate the later option today and let you know how it goes.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148060#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...