Bug 815183

Magesh Bojan <mageshbk> made a comment on jira JBESB-3789

Tadayoshi,

Thanks for reporting this issue. The fix however is not the way as suggested by you. Please mention only the issue and not any suggestion for fix as this could confuse the issue at hand.

Magesh Bojan <mageshbk> made a comment on jira JBESB-3789

Tadayoshi,

Thanks for reporting this issue. The fix however may not be the way as suggested by you. Please mention only the issue and not any suggestion for fix as this could confuse the issue at hand.

Magesh Bojan <mageshbk> updated the status of jira JBESB-3789 to Closed

Magesh Bojan <mageshbk> made a comment on jira JBESB-3789

At revision: 38059

GSS considers this a 'high' priority, it is customer facing.


GSS is asking the customer if they can wait for 5.3 or will require a patch for 5.2.

Either way, we will need this fixed in 5.3.

If a patch is required, we'll open a new BZ for that and will make it part of a Roll up.

Magesh Bojan <mageshbk> updated the status of jira JBESB-3789 to Reopened

Magesh Bojan <mageshbk> made a comment on jira JBESB-3789

Reopening to add this fix to 4.10.CP branch

Magesh Bojan <mageshbk> updated the status of jira JBESB-3789 to Closed

Magesh Bojan <mageshbk> made a comment on jira JBESB-3789

At revision: 38069 on 4_10_CP branch.

Sato Tadayoshi <tasato> updated the status of jira JBESB-3789 to Reopened

Sato Tadayoshi <tasato> made a comment on jira JBESB-3789

Reopened because the fix is incomplete.

Sato Tadayoshi <tasato> made a comment on jira JBESB-3789

Thanks Magesh for quick fixing. But unfortunatelly I tested the fix and found it's not complete.

Explaining based on the reproducing step above, the WSDL contract actually becomes to be published by the fix but the WSDL /definitions/service/port/soap:address/@location (XPath notation for convenience) points to the original Web service (http://127.0.0.1:8080/Quickstart_webservice_producer_esb/GoodbyeWorldWS). What is expected here should be the http-gateway endpoint on ESB (http://127.0.0.1:8080/Quickstart_webservice_producer/http/MyServiceCategory/MyWSProducerService) because otherwise a client ends up calling the original Web service directly.

Magesh Bojan <mageshbk> made a comment on jira JBESB-3789

Terribly sorry! Fixed it, let me know any issues before closing it.

At revision: 38081 on 4_10_CP branch
At revision: 38082 on 4_11_CP branch

Magesh Bojan <mageshbk> made a comment on jira JBESB-3789

Terribly sorry! Fixed it, let me know any issues before closing it.

At revision: 38081 on 4_11_CP branch
At revision: 38082 on 4_10_CP branch

Sato Tadayoshi <tadayosi> made a comment on jira JBESB-3789

Magesh, thanks for the prompt correction! It works fine, and you can close it.

Magesh Bojan <mageshbk> updated the status of jira JBESB-3789 to Closed

Jason Shepherd <jason> updated the status of jira JBESB-3789 to Reopened

Jason Shepherd <jason> made a comment on jira JBESB-3789

From a sample, wrapped endpoint URL:

http://myTestServer/myapp-esb/http/myapp?wsdl

I get a WSDL back;

    <wsdl:import location="http://esb.mycompany.cub/schemas/Errors.wsdl"
        namespace="http://css.mycompany.com/ws/errors/v1/">
    </wsdl:import>
    <wsdl:types>
        <xsd:schema xmlns:err="http://css.mycompany.com/ws/errors/v1/"
            xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://css.mycompany.com/ws/sc/myapp/v1/"
            xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsi="http://ws-i.org/schemas/conformanceClaim/"
            xmlns:xsd="http://www.w3.org/2001/XMLSchema">
            <xsd:import namespace="http://css.mycompany.com/ws/sc/myapp/v1/"
                schemaLocation="http://myTestServer/myapp-esb-myapp-esb-ws-0.7.0-SNAPSHOT/myapp?xsd=myapp.xsd" />
        </xsd:schema>
    </wsdl:types>

where the original is

    <!-- Base Service Messages -->
    <wsdl:import namespace="http://css.mycompany.com/ws/errors/v1/"
        location="http://esb.mycompany.cub/schemas/Errors.wsdl" />

    <!-- Data types definition -->
    <wsdl:types>
        <xsd:schema>
            <xsd:import namespace="http://css.mycompany.com/ws/sc/myapp/v1/"
                schemaLocation="myapp.xsd" />
        </xsd:schema>
    </wsdl:types>

Jason Shepherd <jason> made a comment on jira JBESB-3789

From a sample, wrapped endpoint URL:

http://myTestServer/myapp-esb/http/myapp?wsdl

I get a WSDL back with a reference to a schema on the wrapped web service. The schema should be hosted relative to the WSDL, on the ESB instance.

    <wsdl:import location="http://esb.mycompany.cub/schemas/Errors.wsdl"
        namespace="http://css.mycompany.com/ws/errors/v1/">
    </wsdl:import>
    <wsdl:types>
        <xsd:schema xmlns:err="http://css.mycompany.com/ws/errors/v1/"
            xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://css.mycompany.com/ws/sc/myapp/v1/"
            xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsi="http://ws-i.org/schemas/conformanceClaim/"
            xmlns:xsd="http://www.w3.org/2001/XMLSchema">
            <xsd:import namespace="http://css.mycompany.com/ws/sc/myapp/v1/"
                schemaLocation="http://myTestServer/myapp-esb-myapp-esb-ws-0.7.0-SNAPSHOT/myapp?xsd=myapp.xsd" />
        </xsd:schema>
    </wsdl:types>

where the original is

    <!-- Base Service Messages -->
    <wsdl:import namespace="http://css.mycompany.com/ws/errors/v1/"
        location="http://esb.mycompany.cub/schemas/Errors.wsdl" />

    <!-- Data types definition -->
    <wsdl:types>
        <xsd:schema>
            <xsd:import namespace="http://css.mycompany.com/ws/sc/myapp/v1/"
                schemaLocation="myapp.xsd" />
        </xsd:schema>
    </wsdl:types>

Magesh Bojan <mageshbk> made a comment on jira JBESB-3789

Jason,

The SOAPProcessor is an action that exposes only Webservice endpoints that are internally hosted in the same container via JBossWS. This JIRA was created to mimic the behavior of JBR gateway in the new HTTP gateway. That has been done along with the endpoint address rewrite. Please do not overwhelm the issue here.

Just rewriting schema urls alone will not work, as such the resources like http://myTestServer/myapp-esb-myapp-esb-ws-0.7.0-SNAPSHOT/myapp?xsd=myapp.xsd do not exist in the server. The schema or WSDL imports will always point to the original Webservice's location only as done by JBR gateway. This needs to be handled in a separate JIRA. This encloses rewriting all JBR, HTTP gateway schema import urls and caching the schemas. Whether this feature will be acceptable or not we need to validate that separately. Users can inline their schema for the time being.

Tadayoshi,

The SOAP1.2 support is not there in SOAPProcessor/SOAPProxy as of now. The linked issue only states one small portion of re-writing that is not happening. That is definitely not related to this schema re-writing issue at all although they may touch the same files.

Magesh Bojan <mageshbk> updated the status of jira JBESB-3789 to Closed

Magesh Bojan <mageshbk> made a comment on jira JBESB-3789

Additional issue raised by Jason is handled here JBESB-3802.

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The SOAPProcessor could not publish WSDLs when used in conjunction with the HTTP Gateway. This is because the SOAPProcessor's annotated publisher (JBossWSWebserviceContractPublisher) only implements the ActionContractPublisher but the HTTP Gateway needs the ContractProvider when publishing a WSDL contract.

There are still outstanding issue with references XSD imported in the WSDL, explained here JBESB-3802. 

Can you address this is SOA-P 5.3 in this issue tracker ticket, or should I open a new one?

https://bugzilla.redhat.com/show_bug.cgi?id=823711 represents the issues explained in JBESB-3802.

Verified in SOA 5.3 ER5.

Contracts are now correctly made accessible. For the how-to reproduce case it is accessible via http://127.0.0.1:8080/Quickstart_webservice_producer/http/MyServiceCategory/MyWSProducerService?wsdl.