Hide Forgot
Title: Configure the Web Subsystem Describe the issue: There is no information given on how to configure handler-chains and handler. Also there is no list on what handlers are available, I only have found a reference to org.jboss.ws.common.invocation.RecordingServerHandler (btw this seems to be the corresponding part to org.jboss.wsf.framework.invocation.RecordingServerHandler from EAP 4/5 but no information is provided in the Migration Guide). Suggestions for improvement: Include information from https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.2/html-single/Development_Guide/#Configure_the_literalwebservicesliteral_Subsystem Example 13.4. Add a Handler Chain /profile=default/subsystem=webservices/endpoint-config=My-Endpoint-Config/post-handler-chain=my-handlers:add(protocol-bindings="##SOAP11_HTTP") Example 13.6. Add a Handler /profile=default/subsystem=webservices/endpoint-config=My-Endpoint-Config/post-handler-chain=my-handlers/handler=foo-handler:add(class="org.jboss.ws.common.invocation.RecordingServerHandler") Additional information:
Jochen, Can you spare a moment to look over the new content linked in the comment above and let me know if it's the kind of thing you had in mind when you made this request? Sorry it's been neglected for as long as it has.
My feedback on the new content as per link in comment 3 is as follows: 1. Since the adding of a handler and a handler chain is shown in the procedure, I think the "add" examples should be removed. I also think the "read" examples should be moved to the end of the topic, unless they add to the explanatory text. To me it seems that they interrupt the flow of the text. 2. Why is step 1 of the procedure starting JBoss EAP in "standalone" mode? At the end of the procedure is a check to see if the changes have taken effect, and mentions both 'domain' and 'standalone' configuration files. 3. My *preference* would be to remove the following from the example CLI commands, so that a user could copy and paste the command into a terminal, and not get the prompt's text: "[standalone@localhost:9999 /]" 4. It would be better to use a management CLI command to confirm the handlers' configuration has taken effect, rather than examining XML files because: (a) we are discouraging users from examining XML configuration files; (b) the CLI commands are the same regardless of JBoss EAP mode. 5. The procedure's title mentions only "add handlers" but also specify CLI commands to define a handler chain. 6. Does JBoss EAP need to be restarted, or a "reload" operation done to enable the handlers?
One more point... 7. I would remove "in JBoss EAP" from the topic's title since the content is *all* about JBoss EAP and having that text included does not add anything.
Cheers Russell. I've made the suggested changes (except the one about removing CLI prompts). Moving to MODIFIED to await stage rebuild.
Checked with docs revision 6.4.0-35 This doesn't belong to Web subsystem chapter. This is about Web Services which are described in next chapter (chapter 16) and thus should be moved there.
In addition to move to Web Services chapter, I would use FQDNs in list "Handler Classes in JBoss EAP" because add operation requires it.
Thanks for the suggestion, Jan. Rather than list out the FQDNs of each handler, I've added a link to the javadoc that contains the information I was using. This helps to future-proof the document against any changes that may happen in the codebase.
Verified with Revision 6.4.0-36