I'm aware that this is an old question but I came across it while searching for duplicates of another similar question. You then repeatedly marshal each individual instance of the repeated element. Basically it sounds like you want something roughly like this:. As you've discovered, if a class does not have the XmlRootElement annotation, then you can't pass an instance of that class to the marshaller. However, there is an easy way around this - wrap the object in a JAXBElement , and pass that to the marshaller instead.
Now JAXBElement is a rather clumsy beast, but what it does is contains the element name and namespace of the object that you want to marshal, information which would normally be contained in the XmlRootElement annotation.
Writing XML is a lot easier than reading it, so an solution for your problem might be to use a more "low level" approach. Just write your own marshaller using one of the available open source libraries for XML.
I think you can easily do what you want using dom4j. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Ask Question. Asked 12 years, 1 month ago. Artificial Intelligence. Cloud Computing. Data Science. Angular 7. Machine Learning. Data Structures. Operating System. Computer Network. Compiler Design. Computer Organization. Discrete Mathematics. Ethical Hacking.
Computer Graphics. Software Engineering. The Marshaller class is responsible for governing the process of serializing Java content trees back into XML data. OutputStream: m. Writer: m. Object ; otherwise, a Marshaller. There exist two mechanisms to enable marshalling an instance that is not a JAXB element. One method is to wrap the instance as a value of a JAXBElement , and pass the wrapper element as the first parameter to a Marshaller.
For java to schema binding, it is also possible to simply annotate the instance's class with XmlRootElement. OutputStream , or a java. Use the setProperty API to change the output encoding used during these marshal operations. Client applications are expected to supply a valid character encoding name as defined in the W3C XML 1. Validation and Well-Formedness Client applications are not required to validate the Java content tree prior to calling any of the marshal API's. Furthermore, there is no requirement that the Java content tree be valid with respect to its original schema in order to marshal it back into XML data.
Some JAXB Providers will fully allow marshalling invalid content, others will fail on the first validation error.
Even when schema validation is not explictly enabled for the marshal operation, it is possible that certain types of validation events will be detected during the operation. Validation events will be reported to the registered event handler. If the client application has not registered an event handler prior to invoking one of the marshal API's, then events will be delivered to a default event handler which will terminate the marshal operation after encountering the first error or fatal error.
Note that for JAXB 2. Some providers may support additional properties. String The output encoding to use when marshalling the XML data. The Marshaller will use "UTF-8" by default if this property is not specified. Boolean This property controls whether or not the Marshaller will format the resulting XML data with line breaks and indentation. A true value for this property indicates human readable indented xml data, while a false value indicates unformatted xml data. The Marshaller will default to false unformatted if this property is not specified.
String This property allows the client application to specify an xsi:schemaLocation attribute in the generated XML data. The format of the schemaLocation attribute value is discussed in an easy to understand, non-normative form in Section 5. Boolean This property determines whether or not document level events will be generated by the Marshaller. If the property is not specified, the default is false. This property has different implications depending on which marshal api you are using - when this property is set to true: marshal Object,ContentHandler - the Marshaller won't invoke ContentHandler.
Marshal Event Callbacks "The Marshaller provides two styles of callback mechanisms that allow application specific processing during key points in the unmarshalling process. In 'class defined' event callbacks, application specific code placed in JAXB mapped classes is triggered during marshalling. The external listener callback mechanism enables the registration of a Marshaller.
Listener instance with a setListener Listener. The external listener receives all callback events, allowing for more centralized processing than per class defined callback methods. The 'class defined' and external listener event callback methods are independent of each other, both can be called for one event. The invocation ordering when both listener callback methods exist is defined in Marshaller.
An event callback method throwing an exception terminates the current marshal process. Since: JAXB1.
0コメント