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?

Yeah, I missed the application usage requirement...  Thanks!  (It was pointed out to me by others as well... smile)


---------------------------------------------------
Kevin Sutter
STSM, Jakarta EE and MicroProfile architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn:
https://www.linkedin.com/in/kevinwsutter

Part-time schedule: Tue, Wed, Thu (off on Mon and Fri)




From:        David Blevins <dblevins@xxxxxxxxxxxxx>
To:        ejb developer discussions <ejb-dev@xxxxxxxxxxx>
Date:        02/25/2021 14:34
Subject:        [EXTERNAL] 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?
Sent by:        "ejb-dev" <ejb-dev-bounces@xxxxxxxxxxx>





> On Feb 25, 2021, at 12:07 PM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
>
> Our original status in EE prior to EJB 2.0 was that CORBA was optional and PortableRemoteObject.narrow was required. Specifically, servers could support CORBA or not, but users were strictly told they must always use PortableRemoteObject.narrow regardless.  The reason this was required was for application portability concerns; if an app didn't make the call, it couldn't be ported to a server that used CORBA.

Here is the description of why PortableRemoteObject.narrow was required.


-David

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





Back to the top