svn commit: r1039881 - /axis/axis2/java/core/trunk/src/site/fml/faq.fml

[ve...@apache.org]

Author: veithen
Date: Sun Nov 28 13:28:01 2010
New Revision: 1039881

URL: http://svn.apache.org/viewvc?rev=1039881&view=rev
Log:
Added a FAQ entry about Unexpected subelement exceptions in ADB.

Modified:
    axis/axis2/java/core/trunk/src/site/fml/faq.fml

Modified: axis/axis2/java/core/trunk/src/site/fml/faq.fml
URL: http://svn.apache.org/viewvc/axis/axis2/java/core/trunk/src/site/fml/faq.fml?rev=1039881&r1=1039880&r2=1039881&view=diff
==============================================================================
--- axis/axis2/java/core/trunk/src/site/fml/faq.fml (original)
+++ axis/axis2/java/core/trunk/src/site/fml/faq.fml Sun Nov 28 13:28:01 2010
@@ -259,4 +259,41 @@ getClass().getClassLoader().getResourceA
             </answer>
         </faq>
     </part>
+    <part id="databindings">
+        <title>Databindings</title>
+        <faq id="unexpected_subelement">
+            <question>
+                When using ADB, I get an "Unexpected subelement" exception. Is this a bug?
+            </question>
+            <answer>
+                <p>
+                    In general, "Unexpected subelement" means that the message being processed
+                    doesn't conform to the WSDL that was used to generate the ADB code. If you are getting
+                    this exception on the client side, it means that the response from the server
+                    is invalid. If you are seeing the error on the server side, it means that the
+                    request received by the service is invalid.
+                </p>
+                <p>
+                    If you are sure that the message conforms to the WSDL and believe that there
+                    is an issue with the code generated by Axis2, you should do the following before
+                    opening a JIRA issue:
+                </p>
+                <ol>
+                    <li>
+                        Test the scenario with the latest Axis2 snapshot version. This includes
+                        regenerating the code with the latest codegen version.
+                    </li>
+                    <li>
+                        Provide the WSDL that causes the issue, or if for legal reasons you are not
+                        allowed to provide the original WSDL, provide a minimal WSDL that reproduces
+                        the problem.
+                    </li>
+                    <li>
+                        Provide some hard evidence that this is indeed an issue in Axis2. This means
+                        at least a transcript of the SOAP message that proves that it conforms to the WSDL.
+                    </li>
+                </ol>
+            </answer>
+        </faq>
+    </part>
 </faqs>