axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Lauer (JIRA)" <>
Subject [jira] Commented: (AXIS2-4209) OASIS catalog resolution does not work for schema references
Date Wed, 16 Sep 2009 16:25:58 GMT


Will Lauer commented on AXIS2-4209:

It's not clear to me that this completely fixes the issue. I'm seeing the same problem with
Axis2 1.5, and looking at the source, I see the referenced changes above already included.
It looks like the issue is in ServiceDescriptionImpl. The previous fix added "this.catalogManager
= this.composite.getCatalogManager();", but that doesn't account for the case where this.composite.getCatalogManager()
returns null, which is happening for me. Looks like that happens when ServiceDescriptionImpl
is called from DescriptionFactoryImpl.createServiceDescriptionFromDBCMap. Looking back the
call chain, it seems that DescriptionFactoryImpl.createServiceDescription(Class, ConfigurationContext)
calls JavaClassToDBCConverter.produceDBC, which generates composites whose catalogManager
is null.

I'm not sure what the appropriate solution for this is. Should produceDBC be changed, or is
this as simple as adding 
    	if (catalogManager == null) {
    		catalogManager = new OASISCatalogManager();
to ServiceDescriptionImpl (as is done in at least one of its other constructors)

> OASIS catalog resolution does not work for schema references
> ------------------------------------------------------------
>                 Key: AXIS2-4209
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>    Affects Versions: 1.5, nightly
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>             Fix For: 1.5, nightly
> OASIS catalog resolution does not work for schema references. I ran into the following
exception when wsdl had schema import to http://foo/foo.xsd and jax-ws-catalog.xml redirected
the import to a local file. That happened because the OASISCatalogManager associated with
the WSDL is not used when resolving XmlSchema references in WSDL11ToAxisServiceBuilder.
> java.lang.RuntimeException: foo
>         at
>         at
>         at
>         at
>         at
>         at org.apache.axis2.description.WSDLToAxisServiceBuilder.getXMLSchema(
>         at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.copyExtensibleElements(
>         at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(
>         at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(
>         at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(
>         at org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.buildAxisServiceFromWSDL(
>         at org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.setupAxisServiceFromDBL(
>         at org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.<init>(
>         at org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.<init>(
>         at org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.<init>(
>         at org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescriptionFromDBCMap(
>         at org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescriptionFromDBCMap(

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message