[
https://issues.apache.org/jira/browse/AXIS2-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569407#action_12569407
]
Davanum Srinivas commented on AXIS2-3499:
-----------------------------------------
Brian,
I was thinking about a worst case test...Here's one.
1) Concrete wsdl is specified in @wsdlLocation
2) Concrete wsdl uses wsdl:import to load an abstract wsdl (in another
directory)
3) The Abstract wsdl has an inline schema which uses xsd include to load a
schema (in another directory)
4) The schema uses another xsd include to load another schema (in yet another
directory)
When we load this puppy (web services), we should see traces in the catalog
resolver that it is called for each of the transitions (concrete wsdl ->
abstract wsdl -> 1st schema -> 2nd schema)
Also when we invoke ?wsdl and ?xsd we should see all the correct schemas and
wsdl's
thanks,
dims
> Introduce support in JAX-WS for OASIS XML Catalogs.
> ---------------------------------------------------
>
> Key: AXIS2-3499
> URL: https://issues.apache.org/jira/browse/AXIS2-3499
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
> Reporter: Brian Murray
> Attachments: 3499.patch
>
>
> Note the following in JSR-109:
> JAX-WS requires support for a OASIS XML Catalogs 1.1 specification to be used
> when resolving any Web
> service document that is part of the description of a Web service,
> specifically WSDL and XML Schema
> documents. Refer to section 4.4 of JAX-WS specification.
> I will take a crack at this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
