10:47 p.m.
Good morning,
In the past we had
https://github.com/aerogear/aerogear-unifiedpush-server/pull/149. Any
specific reason for not having JBoss Logging or Log4j on UPS?
With the amount of traffic on UPS, it tends to become more complex to handle
log messages/files.
Thoughts?
--
abstractj
PGP: 0x84DC9914
1:50 a.m.
On Wed, Oct 29, 2014 at 4:47 AM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
Good morning,
In the past we had
https://github.com/aerogear/aerogear-unifiedpush-server/pull/149. Any
specific reason for not having JBoss Logging or Log4j on UPS?
yeah, there were some arguments against adding another dependency (since
JUL is part of the Java platform).
Also, as Burr said (see [1]) "we use it, we own it". That means, at some
point, we might be less or more the owner (e.g. regarding bugs inside of
JBoss logging),
also there cases when the runtime has a different version of JBoss logging
versus the one in UPS.
All these seamed not to be worth to go that route, in April this year
With the amount of traffic on UPS, it tends to become more complex to
handle
log messages/files.
Thoughts?
Sure, we can revisit this for the future 1.1.x line of the UnifiedPush
Server!
-Matthias
[1] http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007289.html
--
abstractj
PGP: 0x84DC9914
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
6:13 a.m.
On 2014-10-29, Matthias Wessendorf wrote:
On Wed, Oct 29, 2014 at 4:47 AM, Bruno Oliveira
<bruno(a)abstractj.org> wrote:
> Good morning,
>
> In the past we had
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/149. Any
> specific reason for not having JBoss Logging or Log4j on UPS?
>
yeah, there were some arguments against adding another dependency (since
JUL is part of the Java platform).
Also, as Burr said (see [1]) "we use it, we own it". That means, at some
point, we might be less or more the owner (e.g. regarding bugs inside of
JBoss logging),
also there cases when the runtime has a different version of JBoss logging
versus the one in UPS.
All these seamed not to be worth to go that route, in April this year
I totally understand, but I think is the same thing with Java APNS for
example. Also, today, I have no clue about how to audit the logs if
something goes wrong.
Just read WildFly/EAP logs and hope for the best?
>
> With the amount of traffic on UPS, it tends to become more complex to
> handle
> log messages/files.
>
> Thoughts?
>
Sure, we can revisit this for the future 1.1.x line of the UnifiedPush
Server!
-Matthias
[1] http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007289.html
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
PGP: 0x84DC9914
3711
days inactive
3711
days old
2 comments
3 participants
participants (3)
-
Bruno Oliveira -
Bruno Oliveira -
Matthias Wessendorf