Mystery Endpoint JBoss 7 final

[mwr0707]

I'm attempting to deploy a top-down/wsdl-first service, using the "Generate Java Bean Skeleton" wizard.  The generated artifacts look ok, compile and seem to deploy ok.  I see the deployed EAR in the server, but all I get with Web Services Explorer or SoapUI is http 404s from JBoss.

I remember running into something similar in earlier versions that I was able to resolve by checking the endpoints using the previous ...jbossws/services URI to list the deployed endpoints.  I can't see anything like this feature in the JBoss 7 console.

So at this point, I'm not even sure how to verify the service endpoint has been properly deployed in the server.

jboss-as-7.0.2.Final

JBossAS Tools 2.3.0.v20110915-1551-H16-M3

Using enbedded JBoss WS soap stack.

1.  How do I check deployed service endpoints in the running server?

2.  How do I eliminate the project name from the service URI context so that the endpoint address is identical to what is contained in the WSDL?

Thanks!

[jim.ma]

1.  How do I check deployed service endpoints in the running server?

You can get check the endpoints in the admin console : http://localhost:9990/console/App.html#server/webservices.

2.  How do I eliminate the project name from the service URI context so that the endpoint address is identical to what is contained in the WSDL?

WEB-INF/jboss-web.xml can help:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">

<jboss-web>

    <context-root>your-context</context-root>

</jboss-web>

[asoldano]

Jim Ma wrote:

1.  How do I check deployed service endpoints in the running server?

You can get check the endpoints in the admin console : http://localhost:9990/console/App.html#server/webservices.

Mark, please check if you can see your endpoints in the console as explained by Jim. If not, there's might be a bug in the console with handling WS in some EAR deployments. Please let me know. Thanks.

[jdabrowski]

Hy Alessio,

first of all thank you for your last answer about @Context, it saved me a lot of time.

I would like to join to the threat because I've got a situation you've described:

I can't see any of my endpoints in console.

JBoss 7.0.2 with own cxf spring configuration, standalone mode. Example of configuration:

bean annotations:

@WebContext(secureWSDLAccess=false)

@Stateless

@WebService(endpointInterface=<webservice_interface>)

webservice interface annotations:

@WebService

jbossws-cxf.xml:

<beans xmlns='http://www.springframework.org/schema/beans'
    xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:beans='http://www.springframework.org/schema/beans'
    xmlns:jaxws='http://cxf.apache.org/jaxws' xmlns:wsa='http://cxf.apache.org/ws/addressing'
    xmlns:jms='http://cxf.apache.org/transports/jms' xmlns:soap='http://cxf.apache.org/bindings/soap'
    xsi:schemaLocation='http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://cxf.apache.org/transports/jms http://cxf.apache.org/schemas/configuration/jms.xsd http://cxf.apache.org/bindings/soap http://cxf.apache.org/schemas/configuration/soap.xsd http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd'>

    <jaxws:endpoint id='<BeanName>'
        address='/<jar-name>/<BeanName>'
        implementor='<BeanClassWithPackage>'
        serviceName='ns0:BeanNameService'
        xmlns:ns0='http://<reversed_bean_package>/'
        endpointName='ns1:BeanNamePort'
        xmlns:ns1='http://<reversed_bean_package>/'>
        <jaxws:invoker>
            <bean class='org.jboss.wsf.stack.cxf.JBossWSInvoker' />
        </jaxws:invoker>
    </jaxws:endpoint>
</beans>

I can access it by url and it works fine.

I thought it's not a bug, but an unimplemented feature. It would be easier if Heiko updates http://community.jboss.org/wiki/SubsystemManagementOperations. We would know what to expect and what should we report.

btw. now I'm not sure if EJB tab with session beans and message driven beans should be filled (it's empty on my server) or it's not implemented yet

[mwr0707]

Trying again with a fresh download of JBoss Tools. 

JBoss Tools Launching Support

Version: 3.3.0.v20111027-1555-H29-M4

Still on JBoss 7.0.2.Final

Trying the following link again:

http://localhost:9990/console/App.html#server/webservices

This just results in a redirect to:

http://localhost:9990/console/App.html#server/datasources

What is the correct way to browse deployed JAX-WS endpoints in the server?

Regards.

[mwr0707]

Update:  The endpoint deploys and is reachable as of AS 7.1.0Beta1b.  The web services section of the admin console now appears but the endpoint is still not visible there.

[asoldano]

OK, thanks for the check. Then I believe this is https://issues.jboss.org/browse/AS7-2196 (an issue with EAR deployments only)

[mwr0707]

Hi Alessio,

I was seeing the endpoints in the admin console after doing WAR deployments up through Flux Capacitor.  In Brontes they are no longer visible.  Instead I see a "Provider tab" with "The configuration of the web services subsystem" and an Edit button.

Modify SOAP Address: true

WSDL Port: 0

WSDL Host: ${jboss.bind.address:127.0.0.1}

WSDL Secure Port: 0

Regards

[asoldano]

The webservices subsystem is something new yet unrelated to this "issue". Please check Deployments->Webservices in the Runtime tab. If your deployments are not listed there, please file a console component jira in AS7 and assign to Heiko Braun. Thanks.

[mwr0707]

Ah - new location.  That was it.  Looks great.  Thank-you.

[rasras]

Hello All,

I know this post is very old but I was also facing the same issue & non of the above solutions worked me.

So posting my solution here might help someone else.

I access the URL: http://localhost:9990/jbossws/services  which directly landed me to a page of Registered Service Endpoints in JBOSS.

Thanks,

RAS