This is covered in the recent issue
https://github.com/eclipse/jetty.project/issues/6123
Joakim Erdfelt / joa...@webtide.com
On Sat, Apr 3, 2021 at 11:56 PM hantsy bai wrote:
> I have tried to run my weld 4/mojarra 3/ jersey using jetty maven plugin,
> it failed in the default
Hi all,
It seems that adding websocket endpoints programmatically (via
ServerContainer.addEndpoint) does not work in jetty-10.0.x or at least I can't
get it to work ;-]
Here is the code from my ServletContextListener:
> public void contextInitialized(ServletContextEvent event) {
>
I've just verified that the app works ok on Tomcat in both cases, so it really
seems like a bug in Jetty. I've filed
https://github.com/eclipse/jetty.project/issues/6130
On 04/04/2021 15:27, Piotr Morgwai Kotarbinski wrote:
> Hi all,
> It seems that adding websocket endpoints programmatically
See video for resolution of same error.
https://youtu.be/HpWnnG0XDpk
5:00
It may be you just need to make an addition to specify
provided
On Sun, 4 Apr 2021, 05:56 hantsy bai, wrote:
> I have tried to run my weld 4/mojarra 3/ jersey using jetty maven plugin,
> it failed in the default
is only used when Jetty is in charge of serving static
content.
Or said another way, when there is a request for a resource that doesn't
match a url-pattern that the webapp has specified, then the servlet spec
Default Servlet kicks in and determines static content, welcome-files, etc
...
You
Let me put it another way.
If I remove web.xml why does the following code give me 404 in jetty 11 ?
import jakarta.ws.rs.GET;
import jakarta.ws.rs.Path;
import jakarta.ws.rs.Produces;
import jakarta.ws.rs.core.MediaType;
/**
* Root resource (exposed at "myresource" path)
*/
How can I achieve the same with embedded jetty.
{
"Instance Configuration": {
"Host": "192.168.100.50",
"Http Port(s)": "9090",
"Https Port(s)": "",
"Instance Name": "Proud-Sablefish",
"Instance Group": "MicroShoal",
"Hazelcast Member UUID":
Thank you I also agree that is the correct jetty reponse.
I am using embedded jetty 11.
Using webAppContext for configuration.
we also have agreed that
" in jetty 11 there is indeed no ClassList, so that part is "broken". ".
What other method of configuration I have available for adding
Som,
Without a web.xml, the Jersey servlet is not setup to handle requests.
Without Jersey, there is nothing in Jetty to map any request to MyResource.
Unless there is something annotated or in a discovered webfragment, then
Jetty has no handler for that request and 404 is the correct response.
A reminder this is the Main function I am working with for jetty 11.
import org.eclipse.jetty.server.Server;
import org.eclipse.jetty.webapp.WebAppContext;
/**
* This class launches the web application in an embedded Jetty container.
* This is the entry point to your application. The Java
Hi
On Sun, Apr 4, 2021 at 2:52 PM hantsy bai wrote:
>
> It seems too old, I rarely used Jetty in projects. I tried the way in the
> article in the above and weld doc, some config are out of data due to
> property not found or class not found etc.
> I think jetty is changed too frequently.
This is the pom.xml
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;>
4.0.0
com.example
heroku-webapp
war
1.0-SNAPSHOT
heroku-webapp
3.0.1
UTF-8
11.0.1
12 matches
Mail list logo
