Just to clarify, both services being injected the IoC way are developed by
me as part of the core program, so nothing sinister to be concerned about.
What would be useful to know is whether Tomcat instantiates classes
annotated with @ServerEndpoint inside or outside of the context of the WAR
app d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles,
On 4/6/19 22:32, Charles Mulvany wrote:
> Thanks Mark for looking into things. I did find out what my issue
> and I apologize and thank those that took the time to read this
> thread. I fixed it by adding a docbase to root context in tomcat
Hi John,
The server-side endpoint is itself implemented as a Tapestry 'service',
allowing it to be injected into other application classes for pushing
messages out to connected clients. Whereas the service injected into the
endpoint class itself allows the endpoint to query this service when a
cl
IoC - *shudders*
Can't this be used to "inject" mass surveillance into J2E apps? It
was curiously missing in the bullet items down the home page of
tapestry. :p
So, you're expecting to inject dependencies into components
instantiated on a websocket?
By "the rest of the application" below, are
Hi team,
I have developed a web application using the Apache Tapestry framework and
deployed on Apache Tomcat. The application also supports WebSocket
connections with desktop clent applications. Following the advice of the
Tapestry community, I included the server-side endpoint within the
Tapes
