moxy | HTTP Reverse Proxy and Load Balancer | Load Balancing library

In short, I would like to perform the unmarshalling as mentioned here but along with Map I will have one more @XmlElement. So one field is annotated with (Map field) @XmlPath(".") and another field with (String field) @XmlElement and then I would like to perform unmarshalling.

My main goal of the application is to convert XML->JSON and JSON->XML using the JAXB/Moxy and Jackson library. I am trying to unmarshal the XML and map it to the Java POJO. My XML can have some dedicated elements and some user-defined elements which can appear random so I would like to store them in Map. Hence, I am making use of XMLAdapter. I am following the blog article to do so. I am not doing exactly the same but a bit different.

The problem I am facing is during unmarshalling the dedicated fields are not taken into consideration at all. All the values are unmarshalled to Map. As per my understanding it's happening because of the annotation @XmlPath(".") and usage of XMLAdapter but If I remove this annotation then it won't work as expected. Can someone please help me with this issue? The marshaling works fine with both @XmlPath(".") and XMLAdapter. The problem is arising only during unmarshalling.

Following is my XML that I would like to convert to JSON: (Note: Name and Age are dedicated fields and others is the user-defined field.)

I know there are a lot of questions related to generating the JSONSchema from JAXB annotated classes using the Jackson but I could not find any example where JSONSchema generated using the MOXY annotated class.

All I want to know is how can I generate JSONSchema for my MOXY annotated class? As of now when I generate the JSONSchema for my JAXB/Moxy annotated class then I get only one field:

I am trying to create XML using the Moxy Marshalling approach. Everything seems to be working fine except for one small thing. Basically, I would like to know how to add wrapper element to the class itself during the marshalling.

As we are aware we can add @XmlPath("test/name/text()") to add a wrapper to any of the String elements. Also for collection we can make use of @XmlElementWrapper(name="languages"), @XmlElement(name="language"). But these are for the fields within the class. How can I add the wrapper element to the class itself which is being marshalled?

I have the following class:

I am using the JaxB Marshalling to create the XML. My XML I have few custom fields which I am creating using the JAXB XmlAdapter option. The custom fields are created using the JAXBElement, in which QName is one of the parameters.

As per the QName documentation it takes 3 parameters NamespaceURI, LocalPart and Prefix. I am passing all these parameters. But for some reason, the created XML takes the default namespace prefix ns0, ns1, ns2 etc rather than the provided one in the QName creation parameter.

Everything is working as expected without any issue. I just want to know how can I make the QName take up the custom prefix value that I am passing as a parameter rather than the default namespace prefix it's adding automatically. I am aware that if I do not pass the prefix value then it would take the default namespace prefix but in my case, even after passing the custom prefix value, it's assigning the default namespaces prefix to XML which I want to avoid. I tried many things but still, nothing worked out.

Note: I am not using the javax Jaxb libraray rather than that I am using the EclipseLink Moxy which is based on Jaxb implementation.

Currently, the created XML would look something like this: (Please note that these do not root elements or XML header rather these are chunks taken from a certain part of the XML).

I am trying to create XML using the JaxB Marshalling approach. I want to skip the parent tag for certain children or may add a new XML parent tag for a certain element. Hence I am trying to use the @XmlPath from import org.eclipse.persistence.oxm.annotations.XmlPath;.

I am following the blog from the founder (Blog on @XmlPath) to make it work but for some reason, the @XmlPath has no impact and the output XML does not match as shown in the blog. I followed all the process mentioned within the blog and also mentioned on various answers here.

All my classes are within the model.jaxb package. Also, I have created a jaxb.properties file within that package.

Following is my Customer class:

I need to add XML-unmarshalling ability to my Eclipse RCP plugin. I'm using JAXB to work with XML-files. It all works great if I run RCP from my IDE. Then I build my plugin with mvn clean package and install it to my RCP with its UI. It all runs smoothly until I want my unmarshalling. In the code where I try to create JAXB context I get this exception:

I am trying to convert DOCX to HTML using DOCX4j, Java 11, Spring boot 2.3.5, Ubuntu 18.04.5, and I am running my .WAR file on tomcat 9.

When I run the code, I get this error. How can I fix this?

My Code

references:

1. export HTML to DOCX with Docx4j

2. https://github.com/plutext/docx4j-ImportXHTML/blob/master/src/samples/java/org/docx4j/samples/DocxToXhtmlAndBack.java

   ...

I'm getting major headaches trying to get Eclipse, Java 11, OSGI, and JAXB to cooperate.

My project consists of several modules:

1. A plain Java core library (let's call it The Core) that provides most of the functionality
2. A plain Java command line tool that uses the Core
3. An Eclipse Plug-in (for use in the IDE) (let's call this The Plug-in) that also uses the Core

The core has several points where functionality can be extended. On the plain Java side, this is automated through service loaders, but there are also hooks to manually register extensions. The Plug-in defines extension points and call those registration hooks with their data.

Here comes the problem: The Core has code to serialise and deserialise a model tree between my Java model and XML via JAXB. Some parts of the model come from extensions - when creating the JAXB context, I list my model root class and all extension classes as my context classes.

This works fine on the Java side, but causes problems on the Eclipse side, as I'll describe below.

I'm using Maven to build the whole project. Not because I like Maven (I don't), but because Eclipse's build documentation is horribly thin and I was at least roughly aware of methods to build Plug-ins with Maven. I've not been able to figure out how to create an Eclipse Plug-in project that directly includes my plain Java Core (without having to manually copy each updated Core build into the Plug-in), but after much fiddling with the Apache Felix Maven plugin, I've managed to get the following system of modules usable:

1. Core module (Packaging type: jar)
2. Command line module (Packaging type: jar, creates an executable jar; irrelevant for this discussion)
3. OSGI module (Packaging type: bundle)
4. Eclipse Plug-in (not a Maven module, but a plain Eclipse Plug-in project that has the OSGI module as a dependency)

This allows me to work on the core, run my Maven build with tests (which updates the OSGI project) and then simply do a Refresh/Maven update in Eclipse to get everything updated in the Plug-in project.

Now this works fine, including JAXB serialisation, as long as I don't have to access JAXB in the Plug-in myself (i.e. just calling my API methods in Core). Because of the extension mechanism, the Plug-in will now add extension classes to the model that need JAXB annotations. And not only that, they will (I assume) have to use the same JAXB API lib as the Core library (included in the Plug-in via the OSGI wrapper). Assumption: I have to export the JAXB API packages in the OSGI wrapper, so that client projects (i.e. the Plug-in) can use them, without having to bring their own (supposedly conflicting) JAXB dependencies.

And even that part works. Almost. Or sort of. I've actually managed to get it "running" by manually adding "javax.xml.bin.annotation" to the exported packages listed for the Felix plugin in my POM, and it produces an OSGI manifest that contains a matching "Export-Package" entry. And the Plug-in now compiles with JAXB annotations, and the Core handles the Plug-in's JAXB-annotated classes correctly.

But Eclipse complains about the OSGI manifest:

Package 'javax.xml.bind.annotation' does not exist in this plug-in

That not only means that I have to click away a warning dialogue every time I start the Plug-in (because Eclipse believes one of its dependencies is broken), but also a) that I expect major troubles with deployment once I've finished development and b) that I have an uncanny feeling that I'm going about this the wrong way.

Which after this long (but necessary, I guess) description comes down to these questions:

1. Why is Eclipse complaining about the OSGI manifest if it actually works in the actual Eclipse Plug-in? Is there a way I can fix the manifest?
2. Is it a correct approach to have the OSGI/Eclipse side of things get the JAXB dependencies from the plain Java Core?
3. If not, how can I get JAXB dependencies into the Plug-in the OSGI way? (I haven't found any info on how and where to get correct, up to date OSGI dependencies for either the standard implementation (java.xml.bind for the API and com.sun.xml.bind for the implementation if I've got that right) or Moxy) How can I make sure that my plain Java Core code, which handles the JAXB context and knows nothing about OSGI & Co, understands the annotations on the OSGI side if that brings its own separate JAXB depedencies?
4. (Bonus question) Is my OSGI wrapper project really necessary? Is there no way to have a Maven setup that builds a few plain Java modules and as its last item an Eclipse plug-in that directly depends on the earlier modules, along with their dependencies?

Using Jersey Client 2.28 I am trying to receive a DTO containing the following data: