"jesper.pedersen" wrote : I've created the following task to track the SPI
|
|
http://jira.jboss.com/jira/browse/JBAS-5426
|
| and imported the first version into jboss-integration. The classes lives under the
org.jboss.jca.spi package as it seem like a good choice when looking at jboss-jca.
|
I haven't looked at it. The spi needs implementing to validate it works.
anonymous wrote :
| I havn't added the JMXEndpoint interface yet as I could find the correct Maven
artifact for this. Feel free to add the interface, Adrian :)
|
The JMXEndpoint should live in the appserver project. It is the backwards
compatibility implementation for EJB2.1
The invocation model is in the appserver's server project.
anonymous wrote :
| The next tasks would be to add an implementation in the AS -- currently the locator
looks for java:/EndpointActivationBus or org.jboss.jca.EndpointActivationBusManager.
|
The bus should just be injected.
anonymous wrote :
| Additional tasks/sub-tasks can be created for this work - or for work that enhanced
the current SPI.
|
| Feel free to share your design/implementation ideas, Adrian - or move code around as
you see fit,
The other thing that we will need is a mechanism to predetermine what the rar
resolves to such that the ejb can add the dependency during deployment.
Something like:
| public interface EndpointActivationBus
| {
| EndpointActivation activate(Endpoint endpoint,
Set<ActivationConfigProperties> properties, RarSelection selection);
|
| /**
| * Determine the dependency name for the rar
| * @param properties the config properties
| * @selection the rar selection parameters
| * @return the dependency name, e.g. JMX object name or MC name or null if it
cannot be determined
| */
| String resolveRarContext( Set<ActivationConfigProperties> properties,
RarSelection selection);
| }
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143819#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...