"heiko.braun jboss.com" wrote : For me the easiest
would be to publish the ObjectName with DeploymentUnit
attachments using a fixed property name that's part of the
WS SPI.
|
| ...
| Looking closer makes me think that the best place would
be JBossEnterpriseBeanMetaData.
|
Using an ObjectName certainly makes no sense. We don't even
know if there is going to be a jmx view in the future. Its
certainly not the api for invoking on the container.
Identifying the endpoints at the JBossEnterpriseBeanMetaData
and on the servlet side, the
JBossWebMetaData/JBossServletMetaData is what makes sense.
You would still need an api to get hold of the container to
invoke on for the given ejb-name, servlet-name though. The
DeploymentScope.getEjbContainer(String ejbLink, Class
businessIntf, String vfsContext) works for the ejb-name. The
businessIntf is just for fallback if known, but is not
needed.
We can just add a method
DeploymentScope.getEjbContainer(String containerName) and
make the container name come from the
getContainerName/setContainerName on the
JBossEnterpriseBeanMetaData.
View the original post : http://www.jboss.com/index.html?
module=bb&op=viewtopic&p=4147975#4147975
Reply to the post : http://www.jboss.com/index.
html?module=bb&op=posting&mode=reply&p=4147975
a>
_______________________________________________
jboss-dev-forums mailing list
jboss-dev-forums lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-dev-foru
ms
|