* provide us with a JUnit test case that demonstrates your issue. e.g. if you think you've found a bug, can you create a test case to demonstrate the bug?
|* [submit a patch|Contributing] patch|Getting Involved] fixing the bug! (We also buy you beer when we meet you if you submit bug fixes :) |
|* for memory leaks or performance related issues, if you can run a profiler on your test case and attach the output as a file (or zipped file if its huge) to the JIRA we can normally fix things much faster. e.g. run JProfiler or YourKit on your code and send us the output. To find memory leaks its quicker to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure out whats wrong from that. |
There are two types of help available for Apache CXF:
If you are experiencing problems using CXF please report your problem via the Issue Tracker. You may also find it useful to discuss your issues with the community on the Mailing Lists. Below are some resources to check before asking for help:
Before asking for help with your issue, it's a very good idea to search for your issue in the mailing list archives and the FAQ. The majority of issues can be solved in this manner without having to send an email to the mailing list. If you don't find an answer, use the guidelines below when writing the e-mail.
Whenever you are reporting a problem, please be sure to include as much information as possible; the more we know, the better the chance of a quicker resolution.
We can help you much quicker if you try the following
There are several companies that support CXF directly or provide products and services based on CXF. See the Commercial CXF Offerings page for more information about those offerings.