Hi Robert, Comments inline below.
On Sun, Feb 16, 2025 at 10:00:32AM -1000, robertlazarski wrote: > > I'd like to add JSON support via one of the many cpp libs such as > simplejson that can be triggered from the client with the HTTP header > "Content-Type: > application/json" as a proof of concept - then release a 2.0.0. Any > thoughts or guidance appreciated. > > Axis2 / Java has that JSON support and I'd like to see that in axis2/c. Some sort of JSON support was added prior to me joining the project. I haven't tested it or even looked at it, so I have no idea if it's functional or to what extent. But it might be a place to start. There's a configure flag to enable it. > > Any other comments on a 2.0.0 release? What are the blockers? Is Jira the > right place to look where to start? When I joined the project, I did a lot of Jira clean up, identified quite a few issues that I felt needed to be addressed before release (mostly memory-related issues- leaks, crashes, etc.), and added some additional issues based on testing and production use at my then-employer. So most everything should be in Jira, though I may still have some local patches that I could upstream. I'll need to review what I have. The open issues I identified for the next release should be tagged with a fix version of 1.7.0. (N.B., there have been *a lot* of commits since 1.6.0, and those closed issues aren't consistently tagged with any kind of fix version. So that should probably be a consideration when it's time for release notes) It was also my goal to review the "Axis2-C Unofficial" fork to see if there were any fixes made there that were not reported/fixed in the official jira/codebase, and integrate any changes of interest. I would love to see a new release of Axis2-C. I haven't completely given up on it, but my available time to contribute is much less than it was previously. Also, I'm no longer at the employer where I used axis daily, so my ability to do exhaustive testing is significantly lower as well. So while I might not be able to contribute as much as I'd like, I'd be happy to help as much as I can, especially if there are others involved. (a long slog uphill often seems shorter when you're not alone) > > I was able to build the code from source using Ubuntu 24.04 with these > autoconf commands, though the INSTALL and README didn't help much with > autoconf. I ran these in the top dir and separately in the folders > axiom,neethi etc. In the root of the source tree, there's a helper script to build everything in order to run the test suite - build_for_tests.sh. There are also build.sh, and build_for_dist.sh, but they haven't been updated in quite some time, so they may need tweaking to be functional. > I was able to run apache in the bin dir but the client had this problem on > make in the samples dir: IIRC, the samples need an actual installation of axis to work properly. So in general, you need to do `make install` and then point the samples build (via AXIS2C_HOME env var) to that installation. But if you use the aforementioned build_for_tests script, it installs into a "deploy" subdirectory within the source tree, and points the samples build there. So for general testing and work, I recommend using the script to make things easier. Best regards, Bill --------------------------------------------------------------------- To unsubscribe, e-mail: c-user-unsubscr...@axis.apache.org For additional commands, e-mail: c-user-h...@axis.apache.org
