Rickard wrote:
> Hi!
Hello. :)
> Well, logging is not a good example, since that would
> typically be done
> through the jBoss server. jBoss allows you to log all bean
> invocations,
> and if you do System.out.println's these will be redirected to the
> server logging system, which you can attach a filter to log
> bean output
> to a file. No coding involved.
Sounds good, but how would I go about attaching the filter.
Before I started upgrading my application to incorporate EJB, I reassigned
the standard output and error streams, so they would write to my log file.
So would the filter just create the file locally or how would it tie into
the scheme? Sorry if I'm trying to make this too complex (I should probably
just look at the code and figure this out).
> > Another example would be a simple class that contains one
> instance variable,
> > uniqueId, of type int and the sole purpose of this class is
> to increment and
> > return a unique id or value when requested.
>
> For these purposes we have a special singleton pool for stateless
> session beans. Make a stateless session bean, and choose the singleton
> container configuration for it. jBoss will only create one instance of
> this bean, which you can use for id's.
Okay, but in order to keep the code portable from any EJB server to any
other EJB server, is there an independent solution. I was thinking of just
creating an RMI object which I would then use JNDI to locate. Sound crazy?
:)
> Does this answer your query?
>
> /Rickard
Quite an excellent response. It is very much appreciated.
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
