Just to keep things on list.
------
Hi Ricardo,
glad I can help. I think I forgot mentioning
- xerces 2.12.2
- xalan 2.7.3
- xalan serializer 2.7.3
Also take a look here, but the versions are a little bit outdated:
https://axis.apache.org/axis/java/compat/dependencies.html
Putting it all into ERJars is a good idea I think. Honestly, in our
company we even dropped ERJars. We do Maven build a custom fat Jar
with all WO/WOnder requirements and integrated that into our CI. So
I only need to update a single POM.
Previously we had also
- axis 1.4
- axis-jaxrpc 1.4
- axis-saaj 1.4
But these are very outdated in the official Maven repos. So now we
build the current axis1 from source [1] into the fat Jar, too, but
only axis (core), axis-jaxrpc and axis-saaj.
It is all a bit hacky, but it is integrated and it works.
We build axis1 sources (only core, jaxrpc, and saaj) from master
branch from here:
[1] https://github.com/apache/axis-axis1-java
This repo contains many fixes and updates to the original axis1
from 2006.
Michael
On 5/23/2023 4:44 AM, Ricardo Parada wrote:
> Thanks for the info Michael. I did some of that. I’ll review exactly
what I did and compare with the info you are providing me.
>
> Thank you.
>
> Sent from my iPhone
>
>> On May 22, 2023, at 5:40 AM, Michael Schmiedgen
<schmied...@takwa.de> wrote:
>>
>> Hi,
>>
>> I recommend dropping the XML framework, its an old pile of s**t. We
>> have done that for years. I think it is mostly needed for WS. You
>> can replace it with latest Axis1 and dependencies [1][2].
>>
>> [1] https://github.com/apache/axis-axis1-java
>> [2] javax.activation 1.1.1, javax.mail 1.4.7, javax.servlet 2.4,
>> wsdl4j 1.6.3
>>
>> Michael
>>
>>
>>
>>> On 5/22/2023 10:17 AM, René Bock via Webobjects-dev wrote:
>>> Hi Ricardo,
>>> are you using ant or maven for building?
>>> Keep in mind, that a very old version of log4j1 is bundled in the
JavaXML framework. So you have to kick out this framework in order to
get completely rid of log4j1
>>> Am 20.05.2023 um 01:00 schrieb Ricardo Parada via Webobjects-dev
<webobjects-dev@lists.apple.com>:
>>> Hi everyone,
>>> Our build system is still using ant and relies on the .classpath
entries.
>>> I have added a couple of frameworks to our Wonder fork:
>>> * ERLog4j1Extensions
>>> * ERLog4j2Extensions
>>> If I want my apps in to use the old log4j 1.2 logging library then
I simply put a classpathentry in the .classpath for the
ERLog4j1Extensions framework like this:
>>> <classpathentry kind=“con” path=“WOFramework/ERLog4j1Extensions“>
>>> If I want to switch to the latest log4j2 then I replace the above
with an entry for the ERLog4j2Extensions framework like this:
>>> <classpathentry kind=“con” path=“WOFramework/ERLog4j2Extensions“>
>>> The problem is that I have a lot of apps that need their .classpath
updated. And switching back and forth during my testing is a lot of
.classpath that I need to update. I could probably write a script but
I’m hoping there is an easier way.
>>> Is there a trick to make the logging framework a variable that can
be set externally somewhere else and all the .classpath files pick it
up, e.g. ${ERLoggingFrameworkName} and without breaking Eclipse? ;-D
>>> Thanks for any ideas
>>> Ricardo Parada
--
___________________________
Michael Schmiedgen, BSc
Senior Software Engineer
Takwa GmbH
Friedrich-List-Str. 15
99096 Erfurt GERMANY
Tel +49 361 6534096
Fax +49 361 6534097
Mail schmied...@takwa.de
Web http://www.takwa.de/
___________________________
Amtsgericht Jena HRB 112964
Geschäftsführung: Ingo Buchholz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
