Re: [VOTE] Release Apache Tomcat 7.0.109

[Igal Sapir]

On Thu, Apr 22, 2021 at 12:13 PM Violeta Georgieva 
wrote:

> The proposed Apache Tomcat 7.0.109 release is now available for voting.
> Please note that this is the last Tomcat 7 release.
>
> 
>
> The proposed 7.0.109 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.109 Stable
>

+1

Igal


>
> Regards,
> Violeta
>

CFP for ApacheCon 2021 closes in ONE WEEK

[Rich Bowen]

[You are receiving this because you're subscribed to one or more dev@
mailing lists for an Apache project, or the ApacheCon Announce list.]

Time is running out to submit your talk for ApacheCon 2021.

The Call for Presentations for ApacheCon @Home 2021, focused on Europe
and North America time zones, closes May 3rd, and is at
https://www.apachecon.com/acah2021/cfp.html

The CFP for ApacheCon Asia, focused on Asia/Pacific time zones, is at
https://apachecon.com/acasia2021/cfp.html and also closes on May 3rd.

ApacheCon is our main event, featuring content from any and all of our
projects, and is your best opportunity to get your project in front of
the largest audience of enthusiasts.

Please don't wait for the last minute. Get your talks in today!

--
Rich Bowen, VP Conferences
The Apache Software Foundation
https://apachecon.com/
@apachecon

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [websocket] proper SPI for encoder/decoder instantiation?

[Romain Manni-Bucau]

Here it is https://bz.apache.org/bugzilla/show_bug.cgi?id=65262

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le jeu. 22 avr. 2021 à 20:12, Mark Thomas  a écrit :

> On 22/04/2021 18:44, Romain Manni-Bucau wrote:
> > Le jeu. 22 avr. 2021 à 17:32, Mark Thomas  a écrit :
> >
> >> On 22/04/2021 16:24, Romain Manni-Bucau wrote:
> >>> Hi,
> >>>
> >>> Is it possible to reuse/add/have a SPI to create ws coders/decoders?
> >>>
> >>> Currently it is a hardcoded factory doing a "new"
> >>> (org.apache.tomcat.websocket.Util#getDecoders for decoders, for
> encoders
> >> it
> >>> is a bit worse since there is an instance as a check here
> >>> org.apache.tomcat.websocket.server.WsServerContainer#validateEncoders
> and
> >>> the instantiation happens here
> >>> org.apache.tomcat.websocket.WsRemoteEndpointImplBase#setEncoders).
> >>>
> >>> Best would likely be to reuse tomcat instance manager since it would
> make
> >>> it working OOTB for integrations/users and also enable to have a proper
> >>> lifecycle management (destroyInstance).
> >>>
> >>> Wdyt?
> >>
> >> -> https://github.com/eclipse-ee4j/websocket-api/issues
> >
> >
> > It is already required to cover 7.1.1.
>
> ACK. Tomcat pretty much ignored that section.
>
> > Currently tomee worked around it by dropping default sci and having a
> > custom one override what it can but it is not generally reusable in cdi
> app
> > easily so spi is needed and destroy phase too by spec ;).
>
> Switching to use the InstanceManager looks doable. It is already
> available on the WebSocketContainer.
>
> Worth opening a BZ issue to track it.
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

[Bug 65262] New: Enable websocket endpoints to be IoC friendly (javaee integration at least)

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=65262

Bug ID: 65262
   Summary: Enable websocket endpoints to be IoC friendly (javaee
integration at least)
   Product: Tomcat 10
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: WebSocket
  Assignee: dev@tomcat.apache.org
  Reporter: rmannibu...@gmail.com
  Target Milestone: --

Follow up of the dev list discussion.
Goal of the ticket is to use the InstanceManager to create websocket endpoints,
encoders, decoders in default configurators (server for sure and would be great
in client when possible - not sure it is that trivial since it is designed to
be standalone).
Note that except the wiring of the instance manager it also implies the proper
destroy call wiring too.

Side note on client side: if the wiring is too complicated cause you don't
always know if a server is running or not - so instance manager access can be
hard, it would be neat to enable to have a SPI to change the default
configurator implementation, goal is the same as on client side: enable to
respect 7.1.1 (javaee integration) spec part which says that endpoints are CDI
aware (in practise I guess it will do a CDI lookup to respect all CDI features
and not reimplement them).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org