Bug 822900 - [eap6] support for webservice endpoint child resources
Summary: [eap6] support for webservice endpoint child resources
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: as7-plugin 823571
TreeView+ depends on / blocked
 
Reported: 2012-05-18 12:58 UTC by Libor Zoubek
Modified: 2015-11-02 00:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 823571 (view as bug list)
Environment:
Last Closed: 2012-05-21 20:04:56 UTC
Embargoed:


Attachments (Terms of Use)
sample WAR with web service (2.26 KB, application/octet-stream)
2012-05-21 13:49 UTC, Libor Zoubek
no flags Details

Description Libor Zoubek 2012-05-18 12:58:34 UTC
Description of problem: If you deploy application with JAX-WS endpoints on EAP6 JON does not show these endpoints.


Version-Release number of selected component (if applicable):
JON 3.1.Beta1 EAP6.ER6

How reproducible:always


Steps to Reproduce:
1.have EAP6 running in standalone mode
2.deploy WAR that contains web service
3.check webservices subsystem
  
Actual results: endpoint contained in deployment does not show up. There is an auto-group called "Endpoints"


Expected results: we should support listing endpoints - admin console does that too.

Comment 1 Libor Zoubek 2012-05-21 13:49:52 UTC
Created attachment 585818 [details]
sample WAR with web service

Comment 2 Libor Zoubek 2012-05-21 14:34:36 UTC
endpoint child resources should appear under 'webservices' subsystem resource

Comment 3 Heiko W. Rupp 2012-05-21 16:02:48 UTC
The attached ws.war creates this entry in the CLI:

[standalone@localhost:9999 subsystem=webservices] :read-resource(include-runtime=true, recursive=true)
{
    "outcome" => "success",
    "result" => {
        "endpoint" => {},
        "modify-wsdl-address" => true,
        "wsdl-host" => expression "${jboss.bind.address:127.0.0.1}",
        "endpoint-config" => {
            "Standard-Endpoint-Config" => {
                "post-handler-chain" => undefined,
                "pre-handler-chain" => undefined,
                "property" => undefined
            },
            "Recording-Endpoint-Config" => {
                "post-handler-chain" => undefined,
                "property" => undefined,
                "pre-handler-chain" => {"recording-handlers" => {
                    "protocol-bindings" => "##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM",
                    "handler" => {"RecordingHandler" => {"class" => "org.jboss.ws.common.invocation.RecordingServerHandler"}}
                }}
            }
        }
    }
}


This has no endpoint defined; the modify-ws*, wsdl-host entries are on subsystem=webservices
and the endpoint-config is exposed.

What exactly are you missing here?

Comment 4 Heiko W. Rupp 2012-05-21 20:04:07 UTC
The endpoints{} list seems not in console either

Comment 5 Libor Zoubek 2012-05-22 07:41:13 UTC
I did not check CLI before, this BZ is based of what EAP6 web console shows, I was also confused about "Endpoint" resource type under /webservices subsystem in RHQ. 

So I expected WS endpoint that is exposed by ws.jar could appear among endpoints in webservice subsystem.

Comment 6 Heiko W. Rupp 2012-05-22 07:49:33 UTC
Console shows the endpoint as runtime data (runtime tab in the upper right), which corresponds to the data below /deployment=ws.war/


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