[Design of EJB 3.0] - Re: WS EJB invocation
by scott.stark@jboss.org
The following has been added and will be in the jboss-metadata-1.0.0.Beta11 release. calling determineContainerName() is what you would do to reliably get the name the container was registered under.
| Added:
|
| /**
| * Get the kernel name for the ejb container. This is the managed property
| * version admin tools may use to control the name. Generally its not set
| * and the server will set the name via the generatedContainerName
| * non-managed property.
| *
| * @see #setGeneratedContainerName(String)
| * @return containerName property value.
| */
| public String getContainerName()
| public void setContainerName(String containerName)
|
| /**
| * Get the generated kernel name for the ejb container. This is the
| * non-managed property version that the server would use to set the name
| * it generated when no containerName property existed.
| *
| * @see #getContainerName()
| * @return generatedContainerName property value.
| */
| @XmlTransient
| public String getGeneratedContainerName()
| public void setGeneratedContainerName(String containerName)
|
| /**
| * Get the kernel name for the ejb container. This is either the
| * containerName managed property, or a runtime generated name set via
| * the non-managed generatedContainerName property.
| * @return the kernel name for the ejb container
| */
| public String determineContainerName()
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148103#4148103
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148103
16 years, 8 months
[Design of EJB 3.0] - Re: WS EJB invocation
by heiko.braun@jboss.com
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#4148060
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148060
16 years, 8 months