[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ejb-dev] [VOTE] Handling of PortableRemoteObject.narrow
|
I’m not sure if I’m eligible to vote, but I vote for A
> On Mar 1, 2021, at 10:50 PM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
>
> Here's the vote as promised last week. I think I can predict the outcome based on recent conversation, but as we had some miscommunication here an explicit choice / request for input from everyone would be very good.
>
> As noted in the discussion, the javax.rmi.PortableRemoteObject class has been removed from the JDK so there is some explicit action needed from us to guarantee the portability of applications on JDK 11.
>
> A. PortableRemoteObject.narrow must remain a requirement for users and servers that support EJB 2.x remote interfaces, which is part of the Enterprise Beans 2.x API optional group. Signature tests will be added to the TCK to verify servers that implement the Enterprise Beans 2.x API optional group are compliant. No specification changes in the Platform or Enterprise Beans specs would be needed for this approach.
>
> B. PortableRemoteObject.narrow is removed, required for no one, and servers deal with this under the covers as they do for EJB 3.0 remote interfaces. The section of the Platform spec that states PortableRemoteObject.narrow will be updated for Jakarta EE 9.1 Enterprise Beans spec would be updated at some later date to reflect this is no longer needed. The PortableRemoteObject.narrow calls in the TCK would be removed.
>
> Both options are orthogonal to if a server does or does not support COBRA.
>
> Let's aim to keep this open for 72 hours so this can be definitively wrapped up Friday morning.
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
> _______________________________________________
> ejb-dev mailing list
> ejb-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ejb-dev
