[jboss-jira] [JBoss JIRA] Commented: (AS7-1709) Client JNDI support for AS7

[David Lloyd (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631063#comment-12631063 ] 

David Lloyd commented on AS7-1709:
----------------------------------

Not explicitly, no.  In fact this issue is out of date as we have elected to not use this particular mechanism on the client (outside of certain exceptional cases), so it will be closed.


> Client JNDI support for AS7
> ---------------------------
>
>                 Key: AS7-1709
>                 URL: https://issues.jboss.org/browse/AS7-1709
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Naming
>            Reporter: Carlo de Wolf
>            Assignee: John Bailey
>            Priority: Critical
>
> The following use case are applicable both to a remote/client VM and within AS7 itself.
> The configuration of the initial context is not specified in here, it'll be a resultant of this task and outlined in some documentation.
> Note that any {code}InitialContext ctx = new InitialContext();{code} might need {code}InitialContext ctx = new InitialContext(props);{code} where the actual contents of {{props}} is currently unspecified.
> h3. Calling AS7
> It *must* be possible for a client to call AS7 via the following code:
> {code}
> InitialContext ctx = new InitialContext();
> MyRemote bean = ctx.lookup("java:myserver1/myapp/myjar/myBean#MyRemote");
> {code}
> h3. Calling different AS7 instances
> It *should* be possible for a client to call two different AS7 instances via the following code:
> {code}
> InitialContext ctx = new InitialContext();
> MyRemote bean = ctx.lookup("java:myserver1/myapp/myJar/OtherBean#MyRemote");
> OtherRemote bean2 = ctx.lookup("java:myserver2/otherapp/otherjar/OtherBean2#OtherRemote");
> {code}
> Whether security and transaction propagation between the servers is available or possible is left beyond scope.
> h3. Calling different type/version of servers
> It *may* be possible for a client to call two different EAP versions via the following code:
> {code}
> InitialContext ctx = new InitialContext();
> MyRemote bean = ctx.lookup("java:myEAP6/myapp/myJar/OtherBean#MyRemote");
> OtherRemote bean2 = ctx.lookup("java:myEAP5/otherapp/otherjar/OtherBean2#OtherRemote");
> {code}
> The last one would require a context to be associated with a certain module to load the proper client classes. See also http://wolf-71.blogspot.com/2010/02/et-phone-home.html
> Whether security and transaction propagation between the servers is available or possible is left beyond scope. Also the propagation of the current established tx/sec context might not be available.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira