out this framework in order to
get completely rid of log4j1
>>> Am 20.05.2023 um 01:00 schrieb Ricardo Parada via Webobjects-dev
:
>>> Hi everyone,
>>> Our build system is still using ant and relies on the .classpath
entries.
>>> I have added a couple
o 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:
>>
&
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:
If I want to switch to the latest log4j2 then I replace the above with an entry
for the ERLog4j2Extensions framework like
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
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
eworks
(one for log4j, one for WSDL, and another one for the rest).
Regards,
Ricardo Parada
On Jan 27, 2023, at 4:04 AM, René Bock
mailto:b...@salient-doremus.de>> wrote:
Hi,
I successfully merged Henriques PR into our Wonder-fork and we are using
log4j2 now for our current proje
based build. I’m our code base we split the JavaXML framework into 3 separate frameworks (one for log4j, one for WSDL, and another one for the rest). Regards,Ricardo ParadaOn Jan 27, 2023, at 4:04 AM, René Bock wrote:
Hi,
I successfully merged Henriques PR into our Wonder-fork and we are using
framework into 3 separate frameworks (one for log4j, one for WSDL, and another one for the rest). Regards,Ricardo ParadaOn Jan 27, 2023, at 4:04 AM, René Bock wrote:
Hi,
I successfully merged Henriques PR into our Wonder-fork and we are using log4j2 now for our current projects
ogging and a little bit of the log4j 1 library, e.g.
org.apache.log4j. That is what I concluded b searching *.jar and *.java files
in Wonder.
And you mention it in your list of open issues on your pull request, e.g. open
issue # 2.8
I do not see Wonder using log4j 2, e.g. org.apache.logging.log4j. So I
Hi Henrique,
It is true that Wonder uses mostly the Apache commons logging library, e.g.
org.apache.commons.logging and a little bit of the log4j 1 library, e.g.
org.apache.log4j. That is what I concluded b searching *.jar and *.java files
in Wonder.
And you mention it in your list of open
Hey guys!
I'm replacing the log4j dependency with slf4j in Wonder, as promised. I've
created a draft pull request [1] on GitHub so more people can comment, test,
and assist me with this change. Please, take a look at it if you have time.
Your comments are always welcome.
Cheers,
HP
[1
On 28 Dec 2021, at 11:16 am, Aaron Rosenzweig wrote:
> Should we upgrade the Wonder jars to v2.16?
We could (and it's 2.17 now!), and Henrique mentioned on Slack he would take a
look at this. Unfortunately it's more complicated than just bumping version
numbers:
either.
> On Dec 16, 2021, at 5:13 PM, Paul Hoadley via Webobjects-dev
> wrote:
>
> Just to update this:
>
> On 14 Dec 2021, at 12:07, Paul Hoadley via Webobjects-dev
> mailto:webobjects-dev@lists.apple.com>>
> wrote:
>
>> * In any case, if you're
Just to update this:
On 14 Dec 2021, at 12:07, Paul Hoadley via Webobjects-dev
wrote:
> * In any case, if you're definitely using Log4J 2 (we are—I went to some
> effort months ago to set it up!), you can mitigate the issue immediately by
> re-launching all instances with
Hi Paul, hi Ken,
thank you so much for the info!!!
I use only Wonder, and the only Log4J I see in the class path is
log4j-1.2.17 from ERJar, so I think is ok.
Thanks again!!!
*Daniele Corti - **IT*
VINATI Srl
rs.dani...@vinati.com
tel: +39 030 2532813
fax: +39 030 2532814
Hello,
On 13 Dec 2021, at 20:56, Daniele Corti via Webobjects-dev
wrote:
> Today the vulnerability CVE-2021-44228 details (log4j) are out and looks like
> all log4j versions are affected!
>
> I’ve seen many attempt on the logs of the servers, but I was not able to
> unders
The vulnerability is only log4j 2
> On Dec 13, 2021, at 05:26, Daniele Corti via Webobjects-dev
> wrote:
>
>
> Hi List!
> Today the vulnerability CVE-2021-44228 details (log4j) are out and looks like
> all log4j versions are affected!
>
> I’ve seen many attempt
Hi List!
Today the vulnerability CVE-2021-44228 details (log4j) are out and looks
like all log4j versions are affected!
I’ve seen many attempt on the logs of the servers, but I was not able to
understand if also my ERJar which contains the log4j-1.2.17 is affected.
Anyone was able to check
Well, the fix seems easy if that works for you.
From: <webobjects-dev-bounces+chill=gevityinc@lists.apple.com> on behalf of
"o...@ocs.cz" <o...@ocs.cz>
Date: Tuesday, October 25, 2016 at 2:56 PM
To: WebObjects-Dev <webobjects-dev@lists.apple.com>
Subject: R
races, which makes for sort of difficult
> parsing. I guess I'm not the first one to swear :)
>
>> ... As for the hang, the code in the logging does seem like a likely culprit.
>
> Actually it looks like the culprit is log4j itself?!? What the heck! Anyroad,
> here's the dea
perhaps hash of the Thread
instance, looks like that) in the traces, which makes for sort of difficult
parsing. I guess I'm not the first one to swear :)
> ... As for the hang, the code in the logging does seem like a likely culprit.
Actually it looks like the culprit is log4j itself?!? What th
I have log4j shooting out emails on errors which is great, but does anyone
have any settings that make it sane to read on my iphone?
When I get errors sometimes I'm getting HUGE dumps that take me at least 30
seconds to scroll to the bottom, then when I do the formatting is so
illegible I can
hello there!
tries to set up log4j in tomcat working with WO-app.
put log4j.properties into classes directory, and than i have log file with
another structure than same in woa-app
and it generates only at start. after than in runtime - nothing writes into
this file
thanx
On 24/05/2012, at 7:00 PM, Ron X wrote:
hi4all
i have currently setted up log4j as:
#
log4j.rootLogger = COPY, INFO, A1
log4j.appender.COPY = org.apache.log4j.FileAppender
log4j.appender.COPY.layout = er.extensions.logging.ERXPatternLayout
with WOUnit since there are too many open bugs in
the tracker.
[1]https://github.com/hprange/wounit/issues/24
Cheers,
Henrique
On 10/04/2012, at 02:32, Paul Hoadley wrote:
Hi Henrique,
Should Log4J logging in EOs under test just work during WOUnit testing? The
EOs and WOUnit tests
Hi Henrique,
On 11/04/2012, at 2:46 AM, Henrique Prange wrote:
Properties files are not loaded when tests are executed by JUnit. There is an
issue [1] for that problem.
I was obviously imagining it yesterday when I wrote I can see the properties
get picked up at launch. You're right
Hi Henrique,
Should Log4J logging in EOs under test just work during WOUnit testing? The
EOs and WOUnit tests are in a single framework. I have Properties.paulh in
that framework where I'm setting log levels and properties for a console
appender. I can see the properties get picked up
/A] DEBUG NSLog - Initialized :
er.prototypes.ERPrototypes
So it look like log4j is not initialized when I'm in bundle-less mode and
WOLips is in the build path. I have no idea what could create that problem. In
/Library/Java/Extensions, I only have JDBC drivers. Nothing in
~/Library/Frameworks. I'm
:
er.prototypes.ERPrototypes
So it look like log4j is not initialized when I'm in bundle-less mode and
WOLips is in the build path. I have no idea what could create that problem.
In /Library/Java/Extensions, I only have JDBC drivers. Nothing in
~/Library/Frameworks. I'm really lost on this issue, I have no idea
:
/Users/probert/WebObjects.properties at path: /Users/probert
sept. 30 07:41:07 N/A[N/A] DEBUG NSLog - Initialized :
er.prototypes.ERPrototypes
So it look like log4j is not initialized when I'm in bundle-less mode and
WOLips is in the build path. I have no idea what could create
+the+Properties+file
just says you can control log4j, but does not have any detailed
information or examples.
Thanks!
Dave
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com
to the log4j directaction in development mode, configure
your logging, and then it will dump out the Properties file info for
you.
ms
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev
to the Properties file?
logger
name=com.bestmaid.bakeryManagement.server.routing.Routing
additivity=true
level value=debug/
appender-ref ref=debugAppender/
/logger
You can also go to the log4j directaction in development mode,
configure your logging, and then it will dump
logger
name=com.bestmaid.bakeryManagement.server.routing.Routing
additivity=true
level value=debug/
appender-ref ref=debugAppender/
/logger
I'm not sure about changing which appender a particular logger uses --
I only use the default console appender as configured
See. I knew it was going to be one of those Doh! That's just too
obvious! kind-of things.
Thanks again Mike!
Dave
On Apr 16, 2008, at 10:35 AM, Mike Schrag wrote:
log4j
.logger.com.bestmaid.bakeryManagement.server.routing.Routing=DEBUG
___
Do
Hi all,
I am trying to generate classes using EOgenerator but I get errors
like following
The import org.apache.log4j can not be resolved or
Logger can not be resolved
Since I am a newcomer to Eclipse / WOLips please help on what I have
to do. I installed Eclipse/WOLips following
().pathURLForResourceNamed(Resources/
log4j.xml, null, null);
NSLog.out.appendln(Initializing log4j from + configURL.toString());
DOMConfigurator.configure(configURL);
Thanks,
Dave ___
Do not post admin requests to the list
= resourceManager().pathURLForResourceNamed(
Resources/log4j.xml, null, null);
NSLog.out.appendln(Initializing log4j from + configURL.toString());
DOMConfigurator.configure(configURL);
try:
resourceManager().pathURLForResourceNamed(log4j.xml, null, null)
Thanks,
Dave
(Resources/
log4j.xml, null, null );
NSLog.out .appendln(Initializing log4j from +
configURL.toString());
DOMConfigurator.configure(configURL);
try:
resourceManager().pathURLForResourceNamed( log4j.xml, null, null)
Thanks,
Dave
___
Do not post admin
= resourceManager().pathURLForResourceNamed
(Resources/log4j.xml, null, null );
NSLog.out .appendln(Initializing log4j from + configURL.toString
());
DOMConfigurator.configure(configURL);
try:
resourceManager().pathURLForResourceNamed( log4j.xml, null, null)
Thanks,
Dave
file, it will
launch:
URL configURL =
resourceManager().pathURLForResourceNamed(Resources/log4j.xml, null,
null );
NSLog.out .appendln(Initializing log4j from + configURL.toString());
DOMConfigurator.configure(configURL);
try:
resourceManager().pathURLForResourceNamed( log4j.xml, null
the following out of the Application.java file, it
will launch:
URL configURL =
resourceManager().pathURLForResourceNamed(Resources/log4j.xml,
null, null );
NSLog.out .appendln(Initializing log4j from +
configURL.toString());
DOMConfigurator.configure(configURL);
try:
resourceManager
On Jan 23, 2008, at 9:32 AM, Daniele Corti wrote:
mmm Woodoo and Poltergeist are not valid tecnical solutions?
I've been trying those too, but the problem is likely that I have too
many pins stuck in my Mike Schrag doll. Maybe I should take a few out
- that and quit letting the dog chew
(WOApplication.java:411)
... 34 more
If I comment the following out of the Application.java file, it
will launch:
URL configURL = resourceManager().pathURLForResourceNamed
(Resources/log4j.xml, null, null);
NSLog.out.appendln(Initializing log4j from + configURL.toString
On Jan 23, 2008, at 6:47 AM, David Avendasora wrote:
On Jan 23, 2008, at 9:32 AM, Daniele Corti wrote:
mmm Woodoo and Poltergeist are not valid tecnical solutions?
I've been trying those too, but the problem is likely that I have
too many pins stuck in my Mike Schrag doll. Maybe I
On 13.11.2007, at 00:59, Lachlan Deck wrote:
I'm finding that log4j doesn't seem to be picking up changes to the
log properties file at runtime. I've got my log4j properties defined
in a file that's referenced in
er.extensions.ERXProperties.OptionalConfigurationFiles... so
presumably
On 14/11/2007, at 3:45 AM, Guido Neitzer wrote:
On 13.11.2007, at 00:59, Lachlan Deck wrote:
I'm finding that log4j doesn't seem to be picking up changes to the
log properties file at runtime. I've got my log4j properties defined
in a file that's referenced
On 13.11.2007, at 22:03, Lachlan Deck wrote:
Hmm. Security hole?
In development? Rarely. It works only in development or if you provide
a password.
I'm just wanting it to pick up the changes I make to the properties
file (like regularly configured log4j does)... is this possible
configured log4j does)... is this
possible?
Not sure whether you have it reload the Properties
I take it then that Wonder doesn't re-read Properties files (from
apps and frameworks) at some interval. Sounds like a TODO.
, but you can use the systemProperty direct action to push a value
Hi All
Another way to bundle your log4j.properties is to include it in the
framework /application jar and then use the log4j.conifguration system
property if you need to change the defaults in teh deployment environment.
That way there is no log4j configuration code in the application/framework
Hello -
I am now getting serious. ;-)
I want to use logging and in particular log4j.
In my Application constructor I have:
String log4jFile = resourceManager().pathURLForResourceNamed
(log4j.properties, null, null).toString();
then I have:
System.out.println(Log4j file (from .woa
never mind.
On Aug 15, 2007, at 10:22 AM, James Cicenia wrote:
Hello -
I am now getting serious. ;-)
I want to use logging and in particular log4j.
In my Application constructor I have:
String log4jFile = resourceManager().pathURLForResourceNamed
(log4j.properties, null, null).toString
On Aug 15, 2007, at 8:22 AM, James Cicenia wrote:
Hello -
I am now getting serious. ;-)
I want to use logging and in particular log4j.
In my Application constructor I have:
String log4jFile = resourceManager().pathURLForResourceNamed
(log4j.properties, null, null).toString();
Try
URL
Don't leave us hanging ;-) What was the fix?
On Aug 15, 2007, at 12:04 PM, James Cicenia wrote:
never mind.
On Aug 15, 2007, at 10:22 AM, James Cicenia wrote:
Hello -
I am now getting serious. ;-)
I want to use logging and in particular log4j.
In my Application constructor I have
and in particular log4j.
In my Application constructor I have:
String log4jFile = resourceManager().pathURLForResourceNamed
(log4j.properties, null, null).toString();
then I have:
System.out.println(Log4j file (from .woa): + log4jFile);
PropertyConfigurator.configure(log4jFile);
log
.
On Aug 15, 2007, at 10:22 AM, James Cicenia wrote:
Hello -
I am now getting serious. ;-)
I want to use logging and in particular log4j.
In my Application constructor I have:
String log4jFile = resourceManager().pathURLForResourceNamed
(log4j.properties, null, null).toString();
then I
Hi All
I'm sorry, i rarely get personal on these lists but could we please
not vent our frustrations about apple and eof on the wonder people,
because that is exactly the wrong place to siphon off energy. They
need constructive feedback and inspiration. If you doubt this, try
ruby on
Which bits of it would you like them to open up ? and why ?
I would like every bit of it opened up, and the reason is that Apple
moves like a glacier in response to fixing glaring issues that
WebObjects has had in the past. If you adopted Webobjects prior to
5.2, you know what I'm
I don't disagree with anything you are saying - and if it were open
source it would no doubt attract many more people to the platform.
But it's just not going to happen.
Here's a thought: We spent some time several months back looking at
alternative frameworks and one thing we did do was
On 30/06/2007, at 6:50 AM, Chuck Hill wrote:
On Jun 29, 2007, at 1:37 PM, Steven Mark McCraw wrote:
Their refusal to ever consider open sourcing it (in spite of how
Steve Jobs rants about how he looves open source) makes me
feel even more animosity about the platform.
I think I
I am not sure what happening here is fair anyway. You guys at wonder
are doing the job of an open source community, giving Apple the tools
it works with, and what is Apple doing in counterpart? Nothing!
Or very little. WO does not evolve, or so slowly. Apple does not even
maintain the tools.
On Jun 29, 2007, at 1:37 PM, Steven Mark McCraw wrote:
Their refusal to ever consider open sourcing it (in spite of how
Steve Jobs rants about how he looves open source) makes me
feel even more animosity about the platform.
I think I know why they won't do this. No, I won't tell
Their refusal to ever consider open sourcing it (in spite of how
Steve Jobs rants about how he looves open source) makes me
feel even more animosity about the platform.
Which bits of it would you like them to open up ? and why ?
Just about everything i want to tinker with is
Create a temporary app using the WOnderApplication project wizard in
Eclipse and use the Properties there as a starting point.
Also, I think you could add this to your Properties file right now to
fix this problem..
log4j.logger.er=INFO
On Jan 20, 2007, at 6:47 AM, Seabix GmbH -
Also change
log4j.rootCategory=DEBUG, A1
to
log4j.rootCategory=WARN, A1
HTH, Kieran
On Jan 20, 2007, at 6:47 AM, Seabix GmbH - Th.Kramis wrote:
Hi there
I'm having trouble with Project Wonders Logging. It can only
started in
DEBUG Modus with the following configuration set. Any other
If I change it to WARN my application hangs at startup. I can't do that.
Setting log4j.logger.er=INFO also doesn't do anything.
Am 20.1.2007 15:11 Uhr schrieb Kieran Kelleher unter
[EMAIL PROTECTED]:
Also change
log4j.rootCategory=DEBUG, A1
to
log4j.rootCategory=WARN, A1
HTH, Kieran
Forgot to say:
- I used the wonder/eclipse template as a starting point
- The app hangs afert the following lines:
ERXProperties has found the
following Properties files: ...
Am 20.1.2007 15:11 Uhr schrieb Kieran Kelleher unter
[EMAIL PROTECTED]:
Also change
log4j.rootCategory=DEBUG, A1
it's /opt/apple/. That might be the problem.
Kind regards,
David.
On 6 Jun 2006, at 04:50, Ian Joyner wrote:
Problem: The client side of an app is not finding class Logger:
Exception in thread AWT-EventQueue-0
java.lang.NoClassDefFoundError: org/apache/log4j/Logger
Sent: Sunday, January 29, 2006 7:12 PM
To: webobjects-dev@lists.apple.com
Subject: Calculator Web Service example - log4j/commons-logging discovery
Greetings -
I am new to Apple OS X WebObjects web services, so I will apologize
in advance for the remedial nature of my comments.
Attached
69 matches
Mail list logo
