-
1. Re: problems with quickstart_publish_as_webservice_inonly sa
scottdawson Oct 5, 2009 4:28 PM (in response to nikc.popov)I see the same problem in jbossesb-server-4.6. I can fix it by adding a valid outXsd attribute -- but that shouldn't be necessary since the intent of the quickstart is to create an in-only service.
Regards,
Scott -
2. Re: problems with quickstart_publish_as_webservice_inonly sa
scottdawson Oct 6, 2009 9:49 AM (in response to nikc.popov)According to https://jira.jboss.org/jira/browse/JBESB-1985 which was fixed prior to 4.5:
A oneway service will be defined if the outXsd attribute is not specified.
but it doesn't seem to work that way. -
3. Re: problems with quickstart_publish_as_webservice_inonly sa
nikc.popov Oct 6, 2009 1:01 PM (in response to nikc.popov)Hi all,
I'm new here. Should we reopen the:
https://jira.jboss.org/jira/browse/JBESB-1985
ticket? Do you know how to do that? -
4. Re: problems with quickstart_publish_as_webservice_inonly sa
scottdawson Oct 6, 2009 8:55 PM (in response to nikc.popov)OK, it does work in a jbossesb-server that I built from trunk a few days ago (revision 29515). The WSDL is accessible and the service works correctly. It just doesn't seem to work in the last 2 releases.
Regards,
Scott -
5. Re: problems with quickstart_publish_as_webservice_inonly sa
nikc.popov Oct 7, 2009 12:13 AM (in response to nikc.popov)well ..jbossesb 4.5GA is still not working.
I found yet another possible bug.
If the ESB application name is the same as the service category name that is to be exposed as web service is the same, the WSDL misses one of them.
i.e. if the app name is TestWS
and in jboss-esb.xml you have:
in the generated WSDL we will have:
<soap:address location='http://localhost:8080/TestWS/TestWSService'/>
as oppose of the expected:
<soap:address location='http://localhost:8080/TestWS/TestWS/TestWSService'/> -
6. Re: problems with quickstart_publish_as_webservice_inonly sa
sirocchj Oct 7, 2009 4:11 AM (in response to nikc.popov)"ScottDawson" wrote:
OK, it does work in a jbossesb-server that I built from trunk a few days ago (revision 29515). The WSDL is accessible and the service works correctly. It just doesn't seem to work in the last 2 releases.
Regards,
Scott
Hi all,
I have not run the quickstart myself but you might be incurring in https://jira.jboss.org/jira/browse/JBESB-2434
for which a resolution has been delivered into branches/JBESB_4_4_GA_CP. This was merged into the tags/JBESB_4_4_GA_CP3_CR7 maintenance release and, later, into the trunk (i.e. it did not make it into the 4.5.GA and 4.6 codebase).
Quick story short, if your WS is mep="OneWay" then org.jboss.internal.soa.esb.webservice.ESBResponseFilter.java (have a look at it to see where the problem is) will filter out all your requests, regardless they are POSTs or GETs, in an attempt to comply to the standards for a one-way service. This, however, means that your "GET /<web-service-endpoint>?wsdl" will be filtered out too (unless you update your ESBResponseFilter to the one in the trunk).
Hope this helps,
Regards,
\j