A TIBCO message is nothing more than a NAME=VALUE pair structure that gets
sent onto the Message bus. It is the same thing a JMS, but the version we
are using is pre-JMS and doesn't support the new JMS api. Unfortunately, we
can't upgrade right now to their new JMS version.
Hmm, I've seen that approach before. They did the serialization, then
base64'd the char[] as a string..interesting.
Unfortunately, the logger has to handle NON-JAVA programs that can send
TIBCO messages, so they won't be able to serialize the objects because they
are in C/C++.
-----Original Message-----
From: Hansen, Richard [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 09, 2001 11:23 AM
To: 'LOG4J Users Mailing List'
Subject: RE: Is this possible for remote logging?
I don't know what a tibco message looks like or requires, but couldn't you
serialize to a stream then read the stream back as as a string, or char
array, or base 64 encoded or something that you can shove into the tibco
message? At the other end you pull it out from the messsage, stream it out
and then deserialize back into the object.
Rick Hansen
> -----Original Message-----
> From: Timothy Mulle' [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 09, 2001 10:10 AM
> To: 'LOG4J Users Mailing List'
> Subject: Is this possible for remote logging?
>
>
> Hi again,
>
> I'm building a TIBCO appender that will take all the
> event fields and build
> them into a TibrvMsg (Map). My question is that it doesn't
> look like I will
> be able to send or at least rebuild ALL the event information from the
> client side on the server side.
>
> For example, LocationInfo and Throwable information,
> Date/Time, and NDC
> information. I can get ALL the information and place it into
> the message to
> be sent, but I have no way of reconstructing the objects on
> the server side.
> LocationInfo has no public setXX() methods to manually set the fields
> instead of getting them from the Throwable object. The
> timestamp field in
> the LoggingEvent is private, and can't be set, except when
> the event is
> created. The same with Throwable, how can I rebuild the
> information on the
> server side. It would be useful for use to be able to log
> Throwables from
> the client side since our logging strategy is a centrally located one.
>
> I can get the NDC info string with NDC.get() and I was thinking on the
> server side I could do NDC.push(data_from_NDC_field) but not
> sure if that
> will work.
>
> Any ideas?? We can't use serialization for this appender so I
> need to use
> all String objects.
>
> Thanks,
> - Tim
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
