[
https://issues.apache.org/jira/browse/CXF-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp updated CXF-2686:
-----------------------------
Fix Version/s: NeedMoreInfo
Is there a stack trace for the CNFE? We should be detecting if the StAXResult
is there and using our own if not.
Also, is this reproducible with 2.3.3 of CXF?
> CXF on WAS 6.1
> --------------
>
> Key: CXF-2686
> URL: https://issues.apache.org/jira/browse/CXF-2686
> Project: CXF
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 2.2.6
> Environment: Windows XP and AIX
> WAS 6.1.0.27 (no WS feature pack)
> Reporter: Stéphane Landelle
> Fix For: NeedMoreInfo
>
>
> I don't know if creating an issue is the right thing to do or if I should
> just post on the mailing list.
> Sorry if I'm wrong.
> I tried to deploy CXF 2.2.6 on WAS 6.1.0.27 (no WS feature pack) with the
> configuration detailed in the user guide, but it wouldn't work and I still
> got CNFE on javax.xml.transform.stax.StAXResult.
> I finally managed to deploy successfully with the following configuration
> (much simplier than the one in the user guide) :
> 1) have jaxp-api and jaxp-ri inside the WAR (check you don't have any double,
> such as jsr173_api, stax-api or geronimo-stax-api)
> 2) create a shared lib with wsdl4j
> 3) create a classloader on the server with this shared lib, set as PARENT_LAST
> 4) configure the WAR classloader as PARENT_LAST
> If this configuration is confirmed, the user guide should be updated.
> Sincerely,
> Stephane Landelle
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
