"ALRubinger" wrote : "emuckenhuber" wrote : I guess it also should be possible to define a local-binding over the xml too?
|
| Yep, something in the XSD under session-beanType like:
|
| <xsd:element name="local-binding" type="jboss:local-bindingType" minOccurs="0" maxOccurs="1"/>
|
| Of course that "maxOccurs" depends on what you want to do now re: allowing more than one binding. :)
|
| S,
| ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185535#4185535
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185535
Actually, it should not be a deployer as it would be a deployer with no known inputs/outputs on which to generate the managed object for. There just should be a ManagedObjectCreator implementation that has the ManagedObjectFactory injected, and this in turn is injected into the DeployerWrapper/DeployersImpl. Right now the DeployerWrapper initializes its the ManagedObjectCreator from the Deployer if it implements that. This logic could be kept so that deployers could provide an override, but typically they would customize behavior using an InstanceClassFactory registration.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185501#4185501
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185501