You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Bryan Stopp (JIRA)" <ji...@apache.org> on 2010/03/24 16:41:33 UTC
[jira] Created: (CXF-2728) CXF-1977 is still valid for CXF 2.2.7
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
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.
[jira] Commented: (CXF-2728) CXF-1977 is still valid for CXF 2.2.7
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849580#action_12849580 ]
Daniel Kulp commented on CXF-2728:
----------------------------------
I'd LOVE a small maven based HelloWorld type project if at all possible. A JUnit test in there would be ideal, but even if the project generated a war that shows the issue would be fine.
Basically, I would need something that I can run relatively easy with a debugger to really see what the simple frontend is trying to dispatch on and where it's getting it's Method objects and such.
> 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
>
> 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.
[jira] Resolved: (CXF-2728) CXF-1977 is still valid for CXF 2.2.7
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2728.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.8
Assignee: Daniel Kulp
> 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
> Assignee: Daniel Kulp
> Fix For: 2.2.8
>
> 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.
[jira] Commented: (CXF-2728) CXF-1977 is still valid for CXF 2.2.7
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849283#action_12849283 ]
Daniel Kulp commented on CXF-2728:
----------------------------------
Please attach a testcase if possible.
> 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
>
> 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.
[jira] Updated: (CXF-2728) CXF-1977 is still valid for CXF 2.2.7
Posted by "Bryan Stopp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Stopp updated CXF-2728:
-----------------------------
Attachment: XMLBeanTypeInfo.java.patch
cxf-binding-bug.zip
It turns out it's not the same bug. It's actually a logic flaw in the XMLBeanTypeInfo when it parses the Aegis mapping files. It never sets the typeClass attribute of the mapped type, and therefore a NPE occurs later when the xsd:date override types are added to the dependencies of an object.
I've attached an eclipse/maven project which shows the bug, and a patch for the java class which is the root cause.
-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, 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.
[jira] Commented: (CXF-2728) CXF-1977 is still valid for CXF 2.2.7
Posted by "Bryan Stopp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849328#action_12849328 ]
Bryan Stopp commented on CXF-2728:
----------------------------------
What would you like? Code/XML/Spring configuration files or just a generic example? I want to make sure you get everything you need. Thanks!
> 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
>
> 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.
[jira] Commented: (CXF-2728) CXF-1977 is still valid for CXF 2.2.7
Posted by "Bryan Stopp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850918#action_12850918 ]
Bryan Stopp commented on CXF-2728:
----------------------------------
I apologize, the attached files do not fix this issue. I was actually experiencing two different issues, once i applied this patch locally I still ran into the same NPE on startup due to the proxy. I have opened CXF-2739 to fix the databinding bug, and i am working on creating a test case for this issue still.
-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, 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.
[jira] Updated: (CXF-2728) CXF-1977 is still valid for CXF 2.2.7
Posted by "Bryan Stopp (JIRA)" <ji...@apache.org>.
[ 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.