in Eclipse you can append the following snippet to the "jetty-context.xml" in "/home/./workspace/.metadata/.plugins/.core/tmpX/contexts/appname.xml" file: This is an known ISSUE Jetty 8.1.2 scans all classes on classpath if there is >= 1xServletContainerInitializer with HandlesTypes on the classpath, regardless of metadata-complete="true" for Jetty 8.1.2.Ī workaround is to use a pattern to limit the JAR files which will be included in the scanning process. Open the WIN500 program, select TSYS Objects tab > click on the Trunking Tables bar > click the drop down menu in the new window > select '800 MHz Rebanded. ![]() In Jetty 8.1.2 this is recognized due startup by the AnntionConfiguration Class but the scanning process occurs anyway. Theres a slightly smaller version, one that merely moves the 'rebanded' channels in front of the default 800 MHz table and is included in the current version of the WIN500 software. ![]() Normally this could be avoided with the "metadata-complete" option in the web.xml: This is a normal process since Servlet-API 2.5 which is looking for Servlet related Annotations in all Classes and Jars.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |