Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ejb-dev] How can we best make the EJB30 tests that use Corba optional but still require other non-Corba tests to be run?



On Thu, Feb 25, 2021 at 4:43 PM David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
> On Feb 25, 2021, at 2:06 PM, Alasdair Nottingham <alasdair.nottingham@xxxxxxxxx> wrote:
>
>> A. PortableRemoteObject.narrow must remain a requirement for everyone, regardless if CORBA is or is not supported

To clarify, it's a requirement for everyone who supports the Jakarta Enterprise Beans 2.x API group, yes?

>> 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
>>
>> I'm fine with either option.  B has the perk that the class will be guaranteed to be there and old apps will deploy on any new Java 11 server.  It does mean we need to add signature tests for it in the TCK and require everyone to ship it.
>>
>
> I’m a little confused because your description of B seems a better fit for option A so I’m wondering if I’ve totally misunderstood your point, or if you mixed up A and B in the previous paragraph.

Thanks, Alasdair, I did mix them up.  Should be "A has the perk that the class will be guaranteed to be there...."


-David

_______________________________________________
ejb-dev mailing list
ejb-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ejb-dev


--
Brian Stansberry
Senior Principal Software Engineer and Manager
Principal Architect, Red Hat JBoss EAP
He/Him/His
If I am writing outside of normal office hours, it is my choice; you do not need to do the same

Back to the top