Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Prune EJB Embeddable Container?
Scopes are a CDI feature and I'm not sure its relationship with standalone EJB is written as it is within application servers. CDI 2.0 has a standalone mode but how that relates to EJB is not written.

I understand your concern but keep in mind the general consensus seems to be deprecating EJB in favour of CDI so even if we retain the embedded container now, it would only be as a temporal solution for existing users.

In my opinion, it's better to research actual use cases and provide a migration path. For example: CDI SE+JTA+MicroProfile REST client could replace application client with remote EJB.

What do you think?

El jue., 21 nov. 2019 17:34, Andy Bailey <Andy.Bailey@xxxxxxxxxxxxx> escribió:
Hi Guillermo,

Yes you can but they don't support all the scopes you might need, like SessionScoped.
Personally I am far more concerned about losing this facility than I am about retaining it in the spec.
Perhaps a wider, more public canvas to gather usage statitistics outside testing might give us more guidance?

On 21 Nov 2019 17:14, Guillermo González de Agüero <z06.guillermo@xxxxxxxxx> wrote:
I haven't used the embedded container myself but I assume for testing you'd be able to use any standalone implementation, no?

El jue., 21 nov. 2019 17:01, Andy Bailey <Andy.Bailey@xxxxxxxxxxxxx> escribió:
The EJB Embeddable Container has a lot of utility for Unit Testing, at least in enterprise projects I have been involved in.
If pruning this from the specification means losing this ability, this might be a loss to regret.

Andy Bailey

On 21 Nov 2019 16:46, carlos andres de la rosa <kusanagi12002@xxxxxxxxx> wrote:
Hello kevin

i think that we can vote for prune this if is something that is not widely used and like we discussed the last Jakarta EE call we can add it later if is necessary

IMHO

Thank you

On Thu, Nov 21, 2019 at 4:39 PM Kevin Sutter <sutter@xxxxxxxxxx> wrote:
Hi,
This idea came up during our IBM discussions relating to the Pruning Vote that Steve initiated.  What about the EJB Embeddable Container?  We provide one because the Spec requires it, but we have no customers using it (that we know of anyway).  Is the pruning of the EJB Embeddable Container something we could also put out for a Vote?  Or, is our customer usage an anomaly and there is industry interest in this artifact?  Thanks!

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev


--

Carlos Andres De La Rosa | Software Architect

Mobile: +32465445631  

Skype: carlosa.dlr


Faktor Zehn GmbH       Sitz der Gesellschaft: München  Registernummer: HRB 242535 Registergericht: Amtsgericht München
Geschaeftsfuehrung: Dr. Florian Schwandt, Joerg Renger
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev


Faktor Zehn GmbH       Sitz der Gesellschaft: München  Registernummer: HRB 242535 Registergericht: Amtsgericht München
Geschaeftsfuehrung: Dr. Florian Schwandt, Joerg Renger
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

Back to the top