[
https://issues.apache.org/jira/browse/AXIS2-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Eranga Suriarachchi reassigned AXIS2-4494:
------------------------------------------------
Assignee: Isuru Eranga Suriarachchi
> catalog resolution doesn't work for schema references used by JAX-WS services
> -----------------------------------------------------------------------------
>
> Key: AXIS2-4494
> URL: https://issues.apache.org/jira/browse/AXIS2-4494
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Affects Versions: 1.5
> Environment: Windows XP SP3, Axis2 1.5, Tomcat 5.5.26
> Reporter: Will Lauer
> Assignee: Isuru Eranga Suriarachchi
> Priority: Minor
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Catalog resolution still isn't working always with Axis2 1.5, even with the
> fix for issue 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)?
--
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]
