The security context certainly seems to be transferred over. At least the the correct
CallerPrincipal seems to show up.
I didn't check what was happening with transactions though. It is, however, wired into
the AS 7 org.jboss.jboss-transaction-spi module.
Steve C
On 03/09/2012, at 6:12 PM, Jaikiran Pai <jpai(a)redhat.com> wrote:
I'm just catching up with that discussion and haven't fully
read it, but
one important thing to note is that although the invocation might work,
the tx and security support won't be propagated from the remote client
(on AS7) to the invocation which ends up on older versions of AS.
-Jaikiran
On Monday 03 September 2012 01:37 PM, Stephen Coy wrote:
> Hi there,
>
> For interest sake last week I worked out a solution to a user's problem related
to calling remote EJBs from JBoss 7 that were hosted on older versions of JBoss.
>
>
See<https://community.jboss.org/thread/204513?tstart=0> for the background.
>
> Anyway, I have since worked out that I could bundle this up in a module so that
clients would only need to add a jboss-deployment-structure.xml to their apps to get this
functionality:
>
> <jboss-deployment-structure>
> <deployment>
> <dependencies>
> <module name="org.jboss.ejb-client.compatibility" />
> </dependencies>
> </deployment>
> </jboss-deployment-structure>
>
> I've incorporated the module into my clone of the current JBoss master branch
at<https://github.com/sfcoy/jboss-as/tree/ejb-client.compatibility>.
>
> Should I send a pull request for this?
>
> Cheers,
>
> Stephen Coy
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev