I have a couple hours a week to work on this so the communication may be slow, but there will be progress soon.
Thanks for the offer to help Nandika, I see that you are an Axis committer so you will be needed along with Bill Blough for the 3 votes needed to release. The end goal includes getting some Jira issues fixed that anyone can help with. For right now though I can use some help getting oriented in the project and while I spent many years programming professionally in C/C++, it's been a while since I programmed in it every day. The INSTALL doc is confusing as it says run ./configure as usual but it isn't there without executing the script. Running "sh build_for_tests.sh" shows errors in the Makefile: /usr/bin/install: 'AUTHORS' and '/home/robert/repos/axis-axis2-c-core/AUTHORS' are the same file make[2]: *** [Makefile:504: install-dataDATA] Error 1 make[2]: Leaving directory '/home/robert/repos/axis-axis2-c-core' make[1]: *** [Makefile:948: install-am] Error 2 make[1]: Leaving directory '/home/robert/repos/axis-axis2-c-core' make: *** [Makefile:636: install-recursive] Error 1 In the end I manually edited the Makefile so "install" would complete - as shown via diff, I need to find the right place to fix this: 426,427c426 < data_DATA = samples/server/axis2.xml README \ < INSTALL CREDITS COPYING NEWS NOTICE AUTHORS --- > data_DATA = samples/server/axis2.xml 1105d1103 < cp -r docs $(DESTDIR)$(docsdir) Running "sh run-tests.sh" shows one error - an HTTP 500 error on "Service not Found" which arguably could be a 404. The log dir shows: [Sun Mar 2 06:03:09 2025] [info] Service Not found. Endpoint reference is : http ://127.0.0.1:9090/axis2/services/echo/echo Looks like libtoolize aclocal autoheader autoconf automake --add-missing ./configure make make install cp -r /usr/local/axis2c/services/echo/ $AXIS2C_HOME/services Then it fails here - about : AddressSanitizer: CHECK failed: sanitizer_thread_arg_retval.cpp:57 "((!t->second.deta ched)) != (0)" (0x0, 0x0) (tid=335462) About my motivation to help - JSON, and the current Axis2/C support. ./configure --enable-json Returns this error. Seems like you applied the patch to support JSON back in 2013. https://issues.apache.org/jira/browse/AXIS2C-1645 Is there some Ubuntu package I need to install? Simply "json" not found isn't clear to me. I see json.h in a couple places. I tried "apt install libjson-c-dev" from Ubuntu 22.04 since it also has json_object but it didn't help. checking for json... no configure: error: Package requirements (json) were not met: Package 'json', required by 'virtual:world', not found On Mon, Feb 17, 2025 at 7:41 PM Nandika Jayawardana <jayaw...@gmail.com> wrote: > Hi Robert, > > As Bill mentioned, running the build_for_tests.sh makes sure that > everything builds correctly. If you are going to work on releasing axis2/c > 2.0.0, I would also like to help. > > Regards > Nandika > > On Tue, 18 Feb 2025 at 01:57, Bill Blough <de...@blough.us.invalid> wrote: > >> 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 >> >>
