JBoss ESB SoapProcessor - inspect the Contract for the Webservice

[alonzoburns]

Team,

I'm experiencing an issue with the SOAPProcessor publishing my web service contract information.  I'm using the webservice_producer example that comes with ESB 4.9 but the Contract is showing 'Unavailable' for JMS and Socket.  Does anyone have a clue how to resolve this?

ServiceCategory:WSProducerServiceWS front-end speaks natively to the ESB 

JMS

 

• Endpoint: jms:localhost:1099#queue/webservice_producer_esb 
• Contract: Unavailable

HTTP

 

• Endpoint: http://localhost:8765 
• Contract: http://localhost:8080/contract/contract.jsp?serviceCat=ServiceCategory&serviceName=WSProducerService&protocol=http

SOCKET 

• Endpoint: socket://localhost:8888 
• Contract: Unavailable

[tcunning]

Alonzo,

So I looked over your last couple posts - sorry, I assumed they were all on the same topic but they definitely are different issues.   Could you summarize where you are now and we'll try to work through your issues in this thread?     You have a number of issues that you've brought up here but I'm not sure they are all current, and I'm not what you've been able to work out on your own.

In the other post you mentioned that you were using ESB 4.9 + jboss AS 6.0.0.Final.      That's not a valid configuration.    ESB 4.10 was the first ESB version to have AS 6.0.0.Final support, but it appears like something's wrong with the webservice_producer QS on that configuration (4.10 + AS 6.0.0.Final) and I'm looking into that now.      If you're trying to get something working right now in that area, I'd suggest trying ESB 4.10 + AS 5.1.0.GA - I just ran webservice_producer successfully there.      Is that a configuration you can use for your project?

Let me know what issues you have outstanding at the moment, and we'll try to work through them here.

[alonzoburns]

Thanks for the follow-up Tom.  I guess they're somewhat related.  Here they are.

1) The webservice_producer example uses the SOAProcessor which should expose the service contract for the various transports defined (JMS,HTTP, Socket).  However, when I go to the contract UI the Contract shows unavailable for JMS and Socket, hence the posting above.

2) For the same example, I'm having problems calling the service when running the example.  You alluded to ' something being wrong with the webservice_producer QS'.  I'm glad you were able to identify the problem.  BTW, What is QS?

As for as the second item, unfortunately, we're moving into the ESB 4.10 AS 6.0.0. configuration direction.  We would like to avoid reverting back to AS 5.10.  BTW, I get the same error for this combination.  When do you think the fix will be available.

[tcunning]

As for the contract question, it's expected that only http(s):// contracts are made available by the JSP contract application.      Contracts for socket:// or jms:// will not currently appear.     If you want some background on this, you can look at http://community.jboss.org/message/350008#350008 - it was never really resolved though, and I can't find an open JIRA for the issue.     I'll log one later today.

As for the issues with webservice_producer quickstart on AS6, I am seeing issues when deploying the webservice_producer quickstart on AS6.     4.11 would be the likely timeframe for such a fix, but there's no schedule yet for an ESB 4.11.