Bug 1321941 - EAP7 - Undertow - new created Servlet Container not loaded
Summary: EAP7 - Undertow - new created Servlet Container not loaded
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 7
Version: JON 3.3.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER01
: One-off release
Assignee: Josejulio Martínez
QA Contact: Hayk Hovsepyan
URL:
Whiteboard:
Depends On:
Blocks: 1314853
TreeView+ depends on / blocked
 
Reported: 2016-03-29 12:22 UTC by Hayk Hovsepyan
Modified: 2016-06-06 18:57 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-06 18:57:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hayk Hovsepyan 2016-03-29 12:22:07 UTC
Description of problem:
When adding new "Servlet Container" in Undertow, and then loading it's configurations, it fails with error "No configuration was retrieved. This means that either the plugin failed to load the configuration or that configuration collection is merely switched off in the connection settings."

The problem is that "Servet Container" is created without creating it's settings, which are "jsp" and "websocket".

So alongside creating new Servlet Container on Undertow side, it needs to be created it's settings as well, like:
"/subsystem=undertow/servlet-container=testcontainer/setting=jsp:add(...)"
:/subsystem=undertow/servlet-container=testcontainer/setting=websockets:add(...)"

Comment 1 Josejulio Martínez 2016-04-06 22:07:02 UTC
Creates the settings (jsp and websockets) upon "Servlet Container" creation.
This also fixes error introduced in the commit of Bug 1313955.

commit da07b04076014e80f3f1befb694da0bf98165f3b
Author: Josejulio Mart\u00ednez <jmartine>
Date:   Thu Mar 31 13:25:49 2016 -0600

    Bug 1321941 - EAP7 - Undertow - new created Servlet Container not loaded
    
    Creates JSP and Websockets settings nodes when trying to create Servlet Container.
    Fixes XML error (changed readonly for readOnly)

Comment 4 Hayk Hovsepyan 2016-04-12 17:06:13 UTC
Verified on revision jon33-eap-update04 ER01


Note You need to log in before you can comment on or make changes to this bug.