Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When you’re adding javaDoc comments to your code and you’re outlining the structure of an XML document that you’re passing back, what’s the best way to represent attributes? Is there a best practice for this?
My general structure for my javaDoc comments is like this:
/** * ... * * @return XML document in the form: * * <pre> * <ROOT_ELEMENT> * <AN_ELEMENT> * <MULTIPLE_ELEMENTS>* * </ROOT_ELEMENT> * </pre> */
Not sure I clearly understand your question.
My preferred solution would be to embed the schema XSD or DTC in the description of the return parameter. Your solution seems to lead to personal idioms on how to represent things like multiple elements or others. Using a standard like XSD or DTD allows you to have a well know and recognized language on how to describe the structure of a XML document.
Regarding the JavaDoc representation if you are using Eclipse you can specify under Save Actions to format your document. This way you can write normally with > and < and see it converted to the escaped HTML codes.