No worries.
The code starting the XML Attribute support for XML Stream, as discussed in
this email thread, went out with Axis2 2.0.0 release this past Monday.
Axis2 is now jakarta based, so you will need the latest Tomcat or Wildfly
to run it.
If you need any help finishing this support, let me
Thanks a lot for looking into this (and apologies for the late response) -
very much appreciated!
Am Donnerstag, 27. Februar 2025 um 16:38:40 MEZ hat robertlazarski
Folgendes geschrieben:
Thanks for posting your config files, that helped me understand a bit more of
what you are tryin
Thanks for posting your config files, that helped me understand a bit more
of what you are trying to do as I only use the "native" JSON approach with
POJO's at my day job. I haven't looked much at the Stax support code using
the XMLSchema project.
And you were correct in pointing out the comments
I'm using the services.xml without modification as per
samples.quickstartadb.resources.META-INF.services.xml. Please see attached.
Regarding the axis2.xml, I have modified according to the guidelines in Apache
Axis2 – How to configure Native approach and XML Stream API base approach for
the XM
I was able to follow your examples with the currency attribute and get some
results but it seems like you have some service.xml and axis2.xml
configurations I am unsure about - could you please post them?
With the service.xml and axis2.xml largely from the spring boot demo I
conjured up with the c
In between I have also looked into the source of
org.apache.axis2.json.moshi.MoshiXMLStreamReader and I find
public int getAttributeCount() {
if (isStartElement()) {
return 0; // don't support attributes on tags in JSON convention
} else {
throw new IllegalStateException("Only valid on S
Thanks for your feedback. Since xml attributes do not have a correspondance in
json, I would expect that there are conventions on how to handle these.For
example, when experimenting with mapped JSON, the generated soap message is
properly populated with attributes from the json string when usin
I'm attaching 2 debug logs:
- soap.log: processing of the getPrice request using the ADBClient from
samples.quickstartadb (modified only to set the required currency attribute
using StockQuoteService.setCurrency). This returns the expected result.
- json.log: processing of the getPrice
Disclaimer: I don't have experience using Axis facilities for JSON.
There isn't a distinction between attributes and elements in JSON.
Essentially, every field is an attribute, but attributes may have complex
content. So probably the JSON message should not use the '@' character to
distinguish a
Could you please paste or attach your logs? That may help me understand the
problem better. I don't have use cases combining XML and JSON in my own
projects but I know the code pretty well and I can probably help.
On Mon, Feb 17, 2025 at 5:23 AM Stefan Traud wrote:
> Hi Robert
> Using contract f
10 matches
Mail list logo
