[
https://issues.apache.org/jira/browse/CXF-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Stopp updated CXF-2728:
-----------------------------
Attachment: cxf-proxy-bug.zip
cxf-proxy-bug-patchs.zip
I tracked down the issue of the NPE on boot. The attachment "cxf-proxy-bug.zip"
is the Maven/Eclipse project which re-creates this error in a JUnit test case.
I also identified why it was a bug and that there was actually two potential
fixes.
If SpringAopClassHelper.getRealClassInternal (cxf-common-utilities) is never
supposed to return null (even when the underlying proxy has no target class),
then I provided a patch that ensures that. If the underlying proxy has no
target class, then it will return "Proxy??" via the last line in the method.
However if that is a valid scenario, then the ServerFactoryBean
(cxf-rt-frontend-simple) should account for the possibility of null, and
therefore I provided a patch that took that into consideration.
Both of those patches are in their appropriate project name subfolders in the
"-patches.zip" file. I have also included a patch to add a test case to the
SpringBeansTest (cxf-rt-frondend-simple) test class for this bug. If neither of
the fix patches are applied, that test should fail as well.
I will also point out that all of my patching was done against the v2.2.7 tag,
as i had difficulty getting the trunk to work in my local workspace(s).
Hope this helps!
-B
> CXF-1977 is still valid for CXF 2.2.7
> -------------------------------------
>
> Key: CXF-2728
> URL: https://issues.apache.org/jira/browse/CXF-2728
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.2.7
> Reporter: Bryan Stopp
> Attachments: cxf-binding-bug.zip, cxf-proxy-bug-patchs.zip,
> cxf-proxy-bug.zip, XMLBeanTypeInfo.java.patch
>
>
> I built a project with CXF v2.2.7 and experienced this bug: CXF-1977.
> I reverted my project back to v2.1.1 because I thought it may be an issue
> with 2.2.7 (as I had not used it in another project until this time). This
> did not fix the problem. As soon as i upgraded to v2.1.4 the bug was fixed
> (as identified in CXF-1977)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
