Using XAware 5.0 is the fastest and easiest way to start building a services layer for your data integration project. Contributions from the community are important to making sure the product continues to improve and incorporate innovation. By joining the XAware community, you can have a voice in the product's roadmap, features and reliability. Here are some ways to get involved:

• Report bugs or contribute enhancement requests or feature requests in our Trackers. Please see Report a bug for information about what we look for in a bug submission.
• Join the XAware Forums to ask questions of our community, share your use cases and ideas about how to improve XAware or help someone else with their issue.
  
• Submit patches for new and or fixed behavior. See below for details about how to submit code.
• Submit help system or documentation corrections or improvements by opening a new issue in the Patch Tracer and attaching the text. It is not necessary to submit a bug in the bug tracker for documentation or help system changes, although it is important to identify where the text should go.
• Join or start a community sandbox project to add or modify functionality. We will be adding documentation to the site describing how to join or start a community sandbox project that extends the functionality of XAware. Meanwhile, please post requests in the Forums. A community sandbox project has been intiated to add UN/EDIFACT processing capability, as described in the blog post EDIFACT Community Project - Help! .
• If you are interested in becoming a commiter, please review the Contributor Agreement and send email to This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

Submitting a Patch

Code submissions from the community are always appreciated. We ask that submissions comply with these guidelines:

• Submit the patch by creating a new issue (submit new button) in the Patch Tracker.
• Attach the patch files (upload and attach files button) and include clear file descriptions. Please don't place the patch in the Detailed Description field unless it is a single line patch.
• Review and follow the XAware Coding Standards.
• If this patch fixes a bug, make sure there is an open issue (submissions for closed or deleted issues won't get much attention) in the bug tracker and include the bug's Request ID in the patch Detailed Description.
• Also in the Detailed Description, include a clear description of the fix as well as some information about why the issue was fixed in this way; this is especially helpful to programmers.
• Any additional information or test cases are always welcome and will make it easier for programmers to understand the fix and how it might impact other areas of the system.
• Revisit the Patch Tracker for comments or status updates from the committers