jetty-server-nb-1.0 - plugin detail

Integrates jetty server 9.1 or above into the NetBeans IDE 7.4 or higher

NetBeans Plugin - jetty-server-nb-1.0
Plugin owner: Valery-Sh
Website: http://plugins.netbeans.org/plugin/54458
Added: 2014-04-14
License: CDDL
Category: Web Applications
Downloaded: 7,934 times
Rating:
 4.38, by 3 users

Plugin Log Show log

Versions available

Download plugin   Download size: 0.12 MB   Last Update: 2014-06-20

What's new in this version

Purpose

Allows to develop web projects with Jetty Http Server. Supports starting, debugging and profiling ant-based and/or maven-based web application (similar to the Tomcat server) .

Plugin provides API for Incremental deployment (compile on save and deploy on save) and jsp compilation.

System Requirements

The plugin supports Jetty version 9.1 and above. The recommended version of Jetty is 9.1.2 or higher, as earlier versions contain errors and startup of some web applications (JSF, CDI) may fail. The plugin does not contain any Jetty distribution kit and if the latter is not already installed on your computer, it can be downloaded from here .

The Jetty distribution kit does not require any special tools to install, it is a zip archive that may be unpacked to any directory of your file system.

To install the plugin, you need to have Java Developer Kit (JDK) v1.7.0 or higher and NetBeans IDE v7.4 and above pre-installed on the user computer.

Installation

How to create a Server Instance

Option 1.
To create and register a Server Instance in a usual NetBeans IDE manner, use the menu Tools → Servers → Add Server. In the dialog box "Add Server Instance" select "Jetty Server" item from the "Choose Server" list and click "Next".
  • Specify the name of the directory that will be used to configure and to customize the Server Instance. As you may know, Jetty 9.1 introduced the concept of Jetty Base and Jetty Home. This means that it is now possible to separate the installation of the jetty standalone server in a certain directory (known as ${jetty.home)) and the customizations for your specific environment (known as ${jetty.base}). Specify the directory for NetBeans to create jettybase subdirectory in the ‘Jetty Base Folder’ box; such subdirectory corresponds to the concept of ${jetty.base}.
  • Specify the path to the root directory with the binary installation of the standalone Jetty in the ‘Jetty Home’ box.
  • If required, change http port, debug port and stop (shutdown) port fields in the Connection tab ). If necessary, change the default values ​​for Http Timeout.

The Settings dialog box also contains tabs SPDY / SSL, JSF and CDI.

The SPDY/SSL tab contains two JCheckBox-type fields. The first one is used to enable the use of the SPDY. If selected, it will automatically activate SSL. The second field may be selected if you choose not to use SPDY.

To learn more about what happens behind the scenes, refer to the section SSL Support and SPDY Support.

The JSF tab contains a single JCheckBox-type field . If it is selected, the server instance must be created to provide support for Java Server Faces (JSF). For more information refer to JSF Support.

The CDI tab contains a single JCheckBox-type field. If it is selected, the server instance must be created to provide support for Contexts and Dependency Injection (CDI). For more information refer to CDI Support.

If there are no errors found, then once you click Finish the plugin creates a directory and inside it another directory named jettybase. The jettybase directory structure is consistent with the Jetty Base concept and contains the settings of the server instance and other files required for the plugin.

It is necessary to make an important note. NetBeans IDE recognized the created directory as an object of Project type, and therefore may be opened in the Project Explore tab. The project has a simple structure and currently does not extend any known types of NetBeans project. It also doesn't create nbproject directory and such files as project.xml, build.xml and build-impl.xml.

Option 2
We mentioned above, registration of a server instance in a standard manner leads to the creation of a project. Therefore, the plugin allows the creation of such a project by using the menu File -> New Project. In the dialog window in the Choose Project panel, go to the Categories list,choose JettyServer and then click the Next button. A new window is then opened containing the same fields and tabs as described in Option 1.. Use of Option 2 results in registration of a new Server Instance and creation of a new corresponding Project containing the jettybase subdirectory .
How to Start a Web Project
Creation and launch of web projects for Jetty is no different from the creation and launch of other servers, such as Tomcat or GlassFish.

Create an ant-based or a maven-based web project in NetBeans IDE. Assign it a registered Server Instance of the Jetty server. After that, you may run project activities such as Run, Debug, Profile, Deploy etc.

Changing the settings of the server instance

There is a number of subdirectories and files in the jettybase subdirectory that the developer can edit either manually or interactively. These are files such as start.ini, and directories such as start.d, etc, etc-cm, or modules.

To modify the settings of a Jetty Server Instance use the popup menu for the project. To do this, right-click the project in the Project Explore and select Properties. Or go to the Services tab, then sequentially choose Servers and the requested Server Instance. Right Click on the Server Instance and select the popup menu item Properties.

JSF Support

Jetty Server API does not provide a built-in support for Java Server Faces (JSF). Therefore, this support is disabled by default on creation of a server instance. However, JSF can be enabled. To do that, you should check the JCheckBox flag in the JSF tab when you create a server instance or change the settings through the Properties dialog. In this case, the file jsf.ini will be created in the ${jetty.base}/start.d directory with the following content:

        #
        # Initialize module Java Server Faces (jsf)
        #
        --module=jsf        
        

Modules

The module jsf.mod is placed in the directory ${jetty.base}/modules/jsf. Presented below is the module’s content:
        
        [depend]
        jsf-mojarra
        [lib]
        lib/jsf/*.jar
        [files]
        lib/
        lib/jsf/
        [ini-template]
        
        
As you can see the jsf.mod module depends on another module - jsf-mojarra.mod, which is placed in the same directory:

        [name]
        jsf-mojarra
        [files]
        http://repo1.maven.org/maven2/org/glassfish/javax.faces/2.2.5/javax.faces-2.2.5.jar:lib/jsf/javax.faces-2.2.5.jar
        [ini-template]  
        
There is a reference to the maven repository which contains the javax.faces-2.2.5.jar archive , and there is an indication of where you should place this file and how to name it. By default, the javax.faces-2.2.5.jar archive is placed in ${jetty.base}/lib/jsf under the same name.

Currently only Mojarra JSF is supported. However, the developer may manually modify jsf.mod in order for it to support other implementations of JSF, such as MyFaces.

Archive downloads via network either on the start of the server of a web-application, or on execution of the Refresh Libraries menu item. Please note, that in case javax.faces-2.2.5.jar file is already on your computer, you may copy it to the ${jetty.base}/lib/jsf directory, and the network download will not start.

Run sample Web Applications

NetBeans installation contains examples of web applications, including jsf-applications. By default, these applications use the GlassFish server, but some of them can also be run on Jetty Server using NetBeans IDE and this plugin. Go to the File -> New Project -> Samples -> Java EE and select the HTML5 JSF application. After the project is open, select it in the Project Explore, call the popup menu by clicking the right mouse button,execute the Properties menu item and then click Run in the Categories panel. A dialog box appears where you can specify Jetty Server Instance instead of GlassFish. Now you can work with this application in the way usual for NetBeans IDE

CDI Support

Jetty Server API does not provide a built-in support for Context and Dependency Injection (CDI). Therefore, on creation of a server instance, this support is disabled by default. However, you may enable CDI. To do this, check the JCheckBox labeled as Support Context and Dependency Injection (CDI) as selected in the CDI tab when you create a server instance or change the settings through the Properties dialog. In this case, the cdi.ini file will be created in the ${jetty.base}/start.d directory. Presented below is the content of the cdi.ini file:

        --module=cdi   
        

Modules

The cdi.mod module is placed in the ${jetty.base}/modules/jsf directory. Presented below is the module’s content:

        [depend]
        cdi-weld
        [lib]
        lib/cdi/*.jar
        [files]
        lib/
        lib/cdi/
        [ini-template]

        
As you can see the cdi.mod module depends on another module - cdi-weld.mod, which is placed in the same directory:
        
        [name]
        cdi-weld
        [files]
        http://central.maven.org/maven2/org/jboss/weld/servlet/weld-servlet/2.1.2.Final/weld-servlet-2.1.2.Final.jar:lib/cdi/weld-servlet-2.1.2.jar
        [ini-template]
        
There is a reference to the maven repository which contains the weld-servlet-2.1.2.Final.jar archive, together with an indication of where you should place this file and how to name it. By default, the weld-servlet-2.1.2.Final.jar archive is placed in $ {jetty.base}/lib/jsf with a slightly different name - weld-servlet-2.1.2.jar. Currently only Weld is supported (and, vice versa, Weld supports Jetty). However, the developer can manually modify cdi.mod to support other implementations of CDI.

Archive downloads via network either on the start of the server or web-application, or on execution of the Refresh Libraries menu item.

Please note, that in case the weld-servlet-2.1.2.jar file is already on your computer, you may copy it to the ${jetty.base}/lib/cdi directory, and the network download will not start.

Run Sample Applications

NetBeans installation contains examples of web applications, including cdi-applications. By default, these applications use the GlassFish server, but some of them can be run on Jetty Server using NetBeans IDE and this plugin. Go to the File -> New Project -> Samples -> Java EE application and select Java Server Faces CDI (JavaEE 7). After the project opens, select it in the Project Explore, call the popup menu by clicking the right mouse button, execute the Properties menu item and then click Run in the Categories panel. A dialog box appears where you can specify Jetty Server Instance instead of GlassFish. Now you can work with this application in the way usual for NetBeans IDE

SSL Support

Various customization procedures are described here

SPDY Support

The current version of the plugin allows you to activate or deactivate SPDY support , as well as to set or modify a number of parameters. For browsers that do not support SDPY, communication is performed via the ordinary Http protocol. SPDY can be activated either on creation of a server instance or on change of settings in Properties. To do that, check the JCheckBox labeled as Enable SPDY in the SPDY tab. The results of the SPDY activation are two files - spdy.ini and ssl.ini created in the ${jetty.base}/start.d directory.

Note that activation of the SPDY automatically entails SSL activation. Information on use and customization of SPDY in Jetty may be found here

HTTPS Support

The current version of the plugin allows you to activate or deactivate HTTPS support , as well as to set or modify a number of parameters. HTTPS can be activated either on creation of a server instance or on change of settings in Properties. The results of the HTTPS activation are two files https.ini and ssl.ini created in the ${jetty.base}/start.d directory.

Note that activation of the HTTPS automatically entails SSL activation.



Verifications for NetBeans versions

Plugin is not subject to any verification

Download plugin   Download size: 0.12 MB   Last Update: 2014-06-20

What's new in this version

Purpose

Allows to develop web projects with Jetty Http Server. Supports starting, debugging and profiling ant-based and/or maven-based web application (similar to the Tomcat server) .

Plugin provides API for Incremental deployment (compile on save and deploy on save) and jsp compilation.

System Requirements

The plugin supports Jetty version 9.1 and above. The recommended version of Jetty is 9.1.2 or higher, as earlier versions contain errors and startup of some web applications (JSF, CDI) may fail. The plugin does not contain any Jetty distribution kit and if the latter is not already installed on your computer, it can be downloaded from here .

The Jetty distribution kit does not require any special tools to install, it is a zip archive that may be unpacked to any directory of your file system.

To install the plugin, you need to have Java Developer Kit (JDK) v1.7.0 or higher and NetBeans IDE v7.4 and above pre-installed on the user computer.

Installation

How to create a Server Instance

Option 1.
To create and register a Server Instance in a usual NetBeans IDE manner, use the menu Tools → Servers → Add Server. In the dialog box "Add Server Instance" select "Jetty Server" item from the "Choose Server" list and click "Next".
  • Specify the name of the directory that will be used to configure and to customize the Server Instance. As you may know, Jetty 9.1 introduced the concept of Jetty Base and Jetty Home. This means that it is now possible to separate the installation of the jetty standalone server in a certain directory (known as ${jetty.home)) and the customizations for your specific environment (known as ${jetty.base}). Specify the directory for NetBeans to create jettybase subdirectory in the ‘Jetty Base Folder’ box; such subdirectory corresponds to the concept of ${jetty.base}.
  • Specify the path to the root directory with the binary installation of the standalone Jetty in the ‘Jetty Home’ box.
  • If required, change http port, debug port and stop (shutdown) port fields in the Connection tab ). If necessary, change the default values ​​for Http Timeout.

The Settings dialog box also contains tabs SPDY / SSL, JSF and CDI.

The SPDY/SSL tab contains two JCheckBox-type fields. The first one is used to enable the use of the SPDY. If selected, it will automatically activate SSL. The second field may be selected if you choose not to use SPDY.

To learn more about what happens behind the scenes, refer to the section SSL Support and SPDY Support.

The JSF tab contains a single JCheckBox-type field . If it is selected, the server instance must be created to provide support for Java Server Faces (JSF). For more information refer to JSF Support.

The CDI tab contains a single JCheckBox-type field. If it is selected, the server instance must be created to provide support for Contexts and Dependency Injection (CDI). For more information refer to CDI Support.

If there are no errors found, then once you click Finish the plugin creates a directory and inside it another directory named jettybase. The jettybase directory structure is consistent with the Jetty Base concept and contains the settings of the server instance and other files required for the plugin.

It is necessary to make an important note. NetBeans IDE recognized the created directory as an object of Project type, and therefore may be opened in the Project Explore tab. The project has a simple structure and currently does not extend any known types of NetBeans project. It also doesn't create nbproject directory and such files as project.xml, build.xml and build-impl.xml.

Option 2
We mentioned above, registration of a server instance in a standard manner leads to the creation of a project. Therefore, the plugin allows the creation of such a project by using the menu File -> New Project. In the dialog window in the Choose Project panel, go to the Categories list,choose JettyServer and then click the Next button. A new window is then opened containing the same fields and tabs as described in Option 1.. Use of Option 2 results in registration of a new Server Instance and creation of a new corresponding Project containing the jettybase subdirectory .
How to Start a Web Project
Creation and launch of web projects for Jetty is no different from the creation and launch of other servers, such as Tomcat or GlassFish.

Create an ant-based or a maven-based web project in NetBeans IDE. Assign it a registered Server Instance of the Jetty server. After that, you may run project activities such as Run, Debug, Profile, Deploy etc.

Changing the settings of the server instance

There is a number of subdirectories and files in the jettybase subdirectory that the developer can edit either manually or interactively. These are files such as start.ini, and directories such as start.d, etc, etc-cm, or modules.

To modify the settings of a Jetty Server Instance use the popup menu for the project. To do this, right-click the project in the Project Explore and select Properties. Or go to the Services tab, then sequentially choose Servers and the requested Server Instance. Right Click on the Server Instance and select the popup menu item Properties.

JSF Support

Jetty Server API does not provide a built-in support for Java Server Faces (JSF). Therefore, this support is disabled by default on creation of a server instance. However, JSF can be enabled. To do that, you should check the JCheckBox flag in the JSF tab when you create a server instance or change the settings through the Properties dialog. In this case, the file jsf.ini will be created in the ${jetty.base}/start.d directory with the following content:

        #
        # Initialize module Java Server Faces (jsf)
        #
        --module=jsf        
        

Modules

The module jsf.mod is placed in the directory ${jetty.base}/modules/jsf. Presented below is the module’s content:
        
        [depend]
        jsf-mojarra
        [lib]
        lib/jsf/*.jar
        [files]
        lib/
        lib/jsf/
        [ini-template]
        
        
As you can see the jsf.mod module depends on another module - jsf-mojarra.mod, which is placed in the same directory:

        [name]
        jsf-mojarra
        [files]
        http://repo1.maven.org/maven2/org/glassfish/javax.faces/2.2.5/javax.faces-2.2.5.jar:lib/jsf/javax.faces-2.2.5.jar
        [ini-template]  
        
There is a reference to the maven repository which contains the javax.faces-2.2.5.jar archive , and there is an indication of where you should place this file and how to name it. By default, the javax.faces-2.2.5.jar archive is placed in ${jetty.base}/lib/jsf under the same name.

Currently only Mojarra JSF is supported. However, the developer may manually modify jsf.mod in order for it to support other implementations of JSF, such as MyFaces.

Archive downloads via network either on the start of the server of a web-application, or on execution of the Refresh Libraries menu item. Please note, that in case javax.faces-2.2.5.jar file is already on your computer, you may copy it to the ${jetty.base}/lib/jsf directory, and the network download will not start.

Run sample Web Applications

NetBeans installation contains examples of web applications, including jsf-applications. By default, these applications use the GlassFish server, but some of them can also be run on Jetty Server using NetBeans IDE and this plugin. Go to the File -> New Project -> Samples -> Java EE and select the HTML5 JSF application. After the project is open, select it in the Project Explore, call the popup menu by clicking the right mouse button,execute the Properties menu item and then click Run in the Categories panel. A dialog box appears where you can specify Jetty Server Instance instead of GlassFish. Now you can work with this application in the way usual for NetBeans IDE

CDI Support

Jetty Server API does not provide a built-in support for Context and Dependency Injection (CDI). Therefore, on creation of a server instance, this support is disabled by default. However, you may enable CDI. To do this, check the JCheckBox labeled as Support Context and Dependency Injection (CDI) as selected in the CDI tab when you create a server instance or change the settings through the Properties dialog. In this case, the cdi.ini file will be created in the ${jetty.base}/start.d directory. Presented below is the content of the cdi.ini file:

        --module=cdi   
        

Modules

The cdi.mod module is placed in the ${jetty.base}/modules/jsf directory. Presented below is the module’s content:

        [depend]
        cdi-weld
        [lib]
        lib/cdi/*.jar
        [files]
        lib/
        lib/cdi/
        [ini-template]

        
As you can see the cdi.mod module depends on another module - cdi-weld.mod, which is placed in the same directory:
        
        [name]
        cdi-weld
        [files]
        http://central.maven.org/maven2/org/jboss/weld/servlet/weld-servlet/2.1.2.Final/weld-servlet-2.1.2.Final.jar:lib/cdi/weld-servlet-2.1.2.jar
        [ini-template]
        
There is a reference to the maven repository which contains the weld-servlet-2.1.2.Final.jar archive, together with an indication of where you should place this file and how to name it. By default, the weld-servlet-2.1.2.Final.jar archive is placed in $ {jetty.base}/lib/jsf with a slightly different name - weld-servlet-2.1.2.jar. Currently only Weld is supported (and, vice versa, Weld supports Jetty). However, the developer can manually modify cdi.mod to support other implementations of CDI.

Archive downloads via network either on the start of the server or web-application, or on execution of the Refresh Libraries menu item.

Please note, that in case the weld-servlet-2.1.2.jar file is already on your computer, you may copy it to the ${jetty.base}/lib/cdi directory, and the network download will not start.

Run Sample Applications

NetBeans installation contains examples of web applications, including cdi-applications. By default, these applications use the GlassFish server, but some of them can be run on Jetty Server using NetBeans IDE and this plugin. Go to the File -> New Project -> Samples -> Java EE application and select Java Server Faces CDI (JavaEE 7). After the project opens, select it in the Project Explore, call the popup menu by clicking the right mouse button, execute the Properties menu item and then click Run in the Categories panel. A dialog box appears where you can specify Jetty Server Instance instead of GlassFish. Now you can work with this application in the way usual for NetBeans IDE

SSL Support

Various customization procedures are described here

SPDY Support

The current version of the plugin allows you to activate or deactivate SPDY support , as well as to set or modify a number of parameters. For browsers that do not support SDPY, communication is performed via the ordinary Http protocol. SPDY can be activated either on creation of a server instance or on change of settings in Properties. To do that, check the JCheckBox labeled as Enable SPDY in the SPDY tab. The results of the SPDY activation are two files - spdy.ini and ssl.ini created in the ${jetty.base}/start.d directory.

Note that activation of the SPDY automatically entails SSL activation. Information on use and customization of SPDY in Jetty may be found here

HTTPS Support

The current version of the plugin allows you to activate or deactivate HTTPS support , as well as to set or modify a number of parameters. HTTPS can be activated either on creation of a server instance or on change of settings in Properties. The results of the HTTPS activation are two files https.ini and ssl.ini created in the ${jetty.base}/start.d directory.

Note that activation of the HTTPS automatically entails SSL activation.



Verifications for NetBeans versions

Plugin is not subject to any verification



Introduction

Allows to develop web projects with Jetty Http Server. Supports starting, debugging and profiling ant-based and/or maven-based web application (similar to the Tomcat server) .

Plugin provides API for Incremental deployment (compile on save and deploy on save) and jsp compilation.

System Requirements

The plugin supports Jetty version 9.1 and above. The recommended version of Jetty is 9.1.2 or higher, as earlier versions contain errors and startup of some web applications (JSF, CDI) may fail. The plugin does not contain any Jetty distribution kit and if the latter is not already installed on your computer, it can be downloaded from here .

The Jetty distribution kit does not require any special tools to install, it is a zip archive that may be unpacked to any directory of your file system.

To install the plugin, you need to have Java Developer Kit (JDK) v1.7.0 or higher and NetBeans IDE v7.4 and above pre-installed on the user computer.

[ You have to be logged in to be able to comment. ]

User Comments

  

Netbeans 8.1 compatibility?

I've installed into Netbeans 8.1, unfortunately Netbeans can't start any more :(
Any suggestions?
Posted by nevzat74 on Apr 12, 2016
  

Netbeans 8.1

Is this going to be updated for Netbeans 8.1?
I tried installing but it doesn't work.
It gives me the message
"The plugin org.netbeans.modules.jeeserver.base.deployment is requested in version 1.0."
Posted by cyberoblivion on Dec 16, 2015
  

Plugin Source Code

You can find the source code here

https://github.com/Valery-Sh/jee-server-api
Posted by Valery-Sh on Jun 09, 2015
  

Sources available?

Hi,
does the sources resides somewhere, like on github?
Would be nice to have a chance to contribute

Thank you
Posted by lcapra on Jun 05, 2015
  

what is the jetty.home path

I am using netbeans 8.0.1 and installed the plugin successfully on my mac OSX. Now the question where to find the jetty.home path when I tried to add jetty as the serve.

Thanks.
Posted by tao.zhao on May 13, 2015
  

How to reopen server log output

Hi,

The plugin doesn't have any menu whatsoever to reopen the server log in the output, how do I reopen it?
Posted by jimi_mx on Dec 04, 2014
  

Sorry, Wrong Jetty Version

Sorry I have tested with a wrong Jetty version, the issue is for Jetty 9.2.

I have upgrade Jetty from 9.2.1 to 9.2.3, and it get a different error. The server can be started now but it failed to start an example web application:

2014-09-10 12:38:17.016:WARN:oejuc.AbstractLifeCycle:qtp1942925132-13: FAILED o.e.j.w.WebAppContext@6ec6dd79{/WebProfileLab,file:/C:/Users/wzhang/AppData/Local/Temp/jetty-0.0.0.0-8088-web-_WebProfileLab-any-5634996914325642048.dir/webapp/,STARTING}{C:\apps\workspaces\netbeans\WebProfileLab\build\web}: java.lang.ExceptionInInitializerError
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:374)
at org.eclipse.jetty.server.handler.ContextHandler$Context.createInstance(ContextHandler.java:2370)
at org.eclipse.jetty.servlet.ServletContextHandler$Context.createServlet(ServletContextHandler.java:1166)
at org.eclipse.jetty.servlet.ServletHolder.newInstance(ServletHolder.java:1121)
at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:578)
at org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:389)
at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:869)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298)
at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1341)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1334)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:497)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.jetty.custom.handlers.CommandManager.start(CommandManager.java:485)
at org.jetty.custom.handlers.CommandManager.start(CommandManager.java:468)
at org.jetty.custom.handlers.CommandManager.handle(CommandManager.java:127)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:497)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248)
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:610)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:539)
at java.lang.Thread.run(Thread.java:745)
Caused by:
java.util.MissingResourceException: Can't find javax.faces.LogStrings bundle
at java.util.logging.Logger.setupResourceInfo(Logger.java:1534)
at java.util.logging.Logger.(Logger.java:267)
Posted by waynezhang on Sep 10, 2014
  

It works on NetBeans 8.0.1 and Jetty 9.1

The previous issue reported by over-tm seems been fixed in NetBeans 8.0.1.

I can reproduce this issue on NetBeans 8.0 but it works when I upgrade to NetBeans 8.0.1.

Cheers,
Posted by waynezhang on Sep 10, 2014
  

Plugin problems

Thank You for the messages.I'l try to solve the problems soon.
Posted by Valery-Sh on Jun 17, 2014
  

One more problem: servlet + JDK 8 + Jetty 9

A new problem. I try to add a new servlet and get the exception (see below).
Solution - change "source/binary format" from JDK 8 to JDK 7. What's wrong in combination of JDK 8 and Jetty 9?

!!! deploy started for cp=/WebApplication1; webDir=C:\!_NetBeansProjects\WebApplication1
2014-06-15 22:45:37.408:WARN:oejw.WebAppContext:qtp1364335809-20: Failed startup of context o.e.j.w.WebAppContext@7abc6f93

{/WebApplication1,file:/C:/Users/username/AppData/Local/Temp/jetty-0.0.0.0-8080-web-_WebApplication1-any-

8286282825607596389.dir/webapp/,STARTING}{C:\!_NetBeansProjects\WebApplication1\build\web}
java.lang.RuntimeException: Error scanning file NewServlet.class
at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:705) at

org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:705)
deploy: success
redeploy: success
at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:686)
at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:821)
at org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:159)
at org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:542)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
at java.lang.Thread.run(Thread.java:745)
Caused by:
java.lang.IllegalArgumentException
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:970)
at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:700)
at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:686)
at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:821)
at org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:159)
at org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:542)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
at java.lang.Thread.run(Thread.java:745)
--- handle target=/
Posted by over-tm on Jun 15, 2014
  

Problem with jetty 9.2.0, 9.2.1

Hi,
I try to use NetBeans IDE 8.0 with jee-server-jetty plugin.
If I create WebApplication (New Project > Java Web > Web Application) and set Jetty as an application server, I get the following messages during the startup

** Unable to continue, required dependency missing.
[jsp-impl/${jsp-impl}-jstl]
** As configured, Jetty is unable to start due to a missing enabled
module dependency.
** This may be due to a transitive dependency akin to spdy on npn,
which resolves based on the JDK in use.

Probably, the problem appears if you add --module=jsp in start.ini only with the next

version of jetty 9.2.0, 9.2.1.

Everything is OK with jetty 9.1.5

Full information
Product Version: NetBeans IDE 8.0 (Build 201403101706)
Updates: NetBeans IDE is updated to version NetBeans 8.0 Patch 1.1
Java: 1.8.0_05; Java HotSpot(TM) 64-Bit Server VM 25.5-b02
Runtime: Java(TM) SE Runtime Environment 1.8.0_05-b13
System: Windows 8 version 6.2 running on amd64; Cp1251; en_US (nb)
User directory: C:\Users\avpadmin\AppData\Roaming\NetBeans\8.0
Posted by over-tm on Jun 15, 2014
By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo